General NAS-Central Forums

Welcome to the NAS community
It is currently Tue Oct 17, 2017 3:13 pm

All times are UTC




Post new topic Reply to topic  [ 25 posts ]  Go to page 1, 2  Next
Author Message
PostPosted: Sat Dec 05, 2015 9:38 pm 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
Hello.
I've recently acquired NAS this device but the problem is that it won't bootup. The NAS was given to me without any disks so I've installed two identical seagates 250GB HDD to try and get this NAS running again. Without success so far. I've also tried the LNA recovery but the NAS shuts down as soon as the LNA discovers it. I'd like to know were i can get the OS image so i can recover it. I've tried recreating the partitions using a linux box with these files listed here http://downloads.lacie.nas-central.org/Users/Mijzelf/2big/Partitions%202.2.3/ with this procedure http://lacie.nas-central.org/wiki/Installing_firmware_on_fresh_disks_(2Big_2)#Create_partitions but again without any success.

- The device starts up
- The front LED is blinking RED/BLUE (If the NAS is plugged into the network it will shutdown after this step).
- After about 5 seconds the front LED is going dark fo a couple seconds and then starts flashing blue forever (Back LEDs are flashing blue for a little while until they go solid blue)
- Device becoming unresponsive even when switching the back power button to the OFF position. (I have to unplug the device to be able to do futher debugging)

Note that i did not use a serial connection (yet) to see if the uboot was even outputing something.

I was under the impression that this was a 2BIG Network V1 so i thaught using the 2.2.3 layout would work but now I'm wondering now if this is even a 2Big Network model at all. I've opened a ticket at LaCie support and in fact the product is a "2BIGV2NAS" model "LAC301421U".

I would very much like to be able to run this NAS again so this is why i'm opening this thread with the hope someone will help me. I doubt to get help from LaCie for this defunct product but you never know.

db666


Top
 Profile  
 
PostPosted: Sun Dec 06, 2015 9:26 am 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
I,ve got some more info. At least i know it u-boot is outputing something

Code:
root@PXE:/home/pxe/clunc# ./clunc -i 192.168.121.12
Waiting for LUMP (0)
no lump receive; continuing
Marvell>> setenv serverip ${serverip}; tftpboot 0x800000 uImage_2.6.38-rc4_orion_lacie_net2big_fix_id_miniroot
setenv serverip ${serverip}; tftpboot 0x800000 uImage_2.6.38-rc4_orion_lacie_net2big_fix_id_miniroot
Using egiga0 device
TFTP from server 192.168.121.55; our IP address is 192.168.121.12
Filename 'uImage_2.6.38-rc4_orion_lacie_net2big_fix_id_miniroot'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ############################################################
done
Bytes transferred = 1966184 (1e0068 hex)
Marvell>> setenv bootargs ip=dhcp console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/
setenv bootargs ip=dhcp console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/
Marvell>> bootm 0x800000
bootm 0x800000
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.38-rc4-09713-ga6682f0-
   Created:      2011-02-24   9:26:43 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1966120 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

[   25.562698] Sending DHCP requests .
[   26.111441] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[   26.119138] ata1: edma_err_cause=00000010 pp_flags=00000000, dev connect
[   26.125950] ata1: SError: { PHYRdyChg DevExch }
[   26.130565] ata1: hard resetting link
[   26.572689] , OK
[   26.602698] IP-Config: Got DHCP answer from 192.168.121.55, my address is 192.168.121.200
[   26.611368] IP-Config: Complete:
[   26.614736] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   26.621160]      device=eth0, addr=192.168.121.200, mask=255.255.255.0, gw=192.168.121.1,
[   26.629293]      host=192.168.121.200, domain=, nis-domain=(none),
[   26.635886]      bootserver=192.168.121.55, rootserver=192.168.121.55, rootpath=
[   26.652820] ata2.00: ATA-8: ST3250312AS, JC45, max UDMA/133
[   26.658445] ata2.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   26.722822] ata2.00: configured for UDMA/133
[   26.743340] scsi 1:0:0:0: Direct-Access     ATA      ST3250312AS      JC45 PQ: 0 ANSI: 5
[   26.753946] sd 1:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[   26.762463] sd 1:0:0:0: Attached scsi generic sg0 type 0
[   26.768509] sd 1:0:0:0: [sda] Write Protect is off
[   26.774568] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   26.836166]  sda: sda1 < sda5 sda6 sda7 sda8 sda9 sda10 > sda2
[   26.849028] sd 1:0:0:0: [sda] Attached SCSI disk
[   26.854381] Freeing init memory: 1188K
[   27.381746] md: md4 stopped.
[   27.553132] md: bind<sda2>
[   27.558138] md: md3 stopped.
[   27.650535] md: bind<sda5>
[   27.656119] bio: create slab <bio-1> at 1
[   27.660625] md/raid1:md3: active with 1 out of 2 mirrors
[   27.666313] md3: detected capacity change from 0 to 131465216
[   27.674627] md: md0 stopped.
[   27.680532]  md3: unknown partition table
[   27.725711] md: bind<sda7>
[   27.731502] md/raid1:md0: active with 1 out of 2 mirrors
[   27.737214] md0: detected capacity change from 0 to 8126464
[   27.745489] md: md1 stopped.
[   27.751280]  md0: unknown partition table
[   27.818097] md: bind<sda8>
[   27.824022] md/raid1:md1: active with 1 out of 2 mirrors
[   27.829567] md1: detected capacity change from 0 to 180813824
[   27.838008] md: md2 stopped.
[   27.844059]  md1: unknown partition table
[   27.871601] md: bind<sda9>
[   27.877470] md/raid1:md2: active with 1 out of 2 mirrors
[   27.883197] md2: detected capacity change from 0 to 690814976
[   31.552732] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   31.592792] ata1.00: ATA-8: ST3250318AS, CC38, max UDMA/133
[   31.598417] ata1.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   31.662808] ata1.00: configured for UDMA/133
[   31.667159] ata1: EH complete
[   33.063331] scsi 0:0:0:0: Direct-Access     ATA      ST3250318AS      CC38 PQ: 0 ANSI: 5
[   33.078353] sd 0:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[   33.090886] sd 0:0:0:0: Attached scsi generic sg1 type 0
[   33.099055] sd 0:0:0:0: [sdb] Write Protect is off
[   33.107376] sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   33.166137]  sdb: sdb1 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 > sdb2
[   33.197965] sd 0:0:0:0: [sdb] Attached SCSI disk


Code:
[   17.010379] [b]ata1: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen[/b]
[   17.018071] ata1: edma_err_cause=00000010 pp_flags=00000000, dev connect
[   17.024879] ata1: SError: { PHYRdyChg DevExch }
[   17.029495] ata1: hard resetting link


This seem to be where the drives are shutting down

I'll keep at it tomorrow maybe with another drive i'll have better luck. If somebody can point me in the right direction it would be great help. I've just looked for that error and seen it was probably due to a bad S-ATA cable...


Top
 Profile  
 
PostPosted: Sun Dec 06, 2015 10:42 am 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
It would be helpfull to see aldo the beginning of the kernel boot log.
Anyhow this output from the kernel loading an initialisation of drivers. And some output from the lacie boot scripts executed after loading the kernel. Indeed there seems to be some disk errors but at least it finds disk sda. Stronger if the disk sda was not accesable the kernel would not load as it is taken from disk.
It seems sdb might have a problem. At the end of the output you posted it is found but that is very late. Maybe you should try another disk.
But I do not see a reason and indication that it reboots automatically in this output. Also you mentioned that it reboots when you try to access it via lacie assistent. Then it means the lacie firmware must have been loaded. That should be visible in the boot output. The disk errors shown will not cause a reboot.
More info is needed to find the reason.

Are you able to connect the serial console?


Top
 Profile  
 
PostPosted: Sun Dec 06, 2015 10:48 am 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
I edited my post


Top
 Profile  
 
PostPosted: Sun Dec 06, 2015 9:52 pm 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
Some new stuff. I was able to log in miniroot and get the beginning of boot log.

Code:
gameuser@gameshare:~$ telnet 192.168.121.200
Trying 192.168.121.200...
Connected to 192.168.121.200.
Escape character is '^]'.

miniroot login: root


BusyBox v1.15.3 (2011-02-22 18:51:38 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.

miniroot ~ # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:D0:4B:88:EC:69
          inet addr:192.168.121.200  Bcast:192.168.121.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:122 errors:0 dropped:0 overruns:0 frame:0
          TX packets:228 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10716 (10.4 KiB)  TX bytes:23940 (23.3 KiB)
          Interrupt:21

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

miniroot ~ # dmesg
[    0.000000] Linux version 2.6.38-rc4-09713-ga6682f0-svn-dirty (simon@X31) (gcc version 4.4.2 (crosstool-NG-hg_default@1665_60a47ac6cae1) ) #17 PREEMPT Thu Feb 24 10:26:28 CET 2011
[    0.000000] CPU: Feroceon [41069260] revision 0 (ARMv5TEJ), cr=a0053177
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: LaCie 2Big Network
[    0.000000] Clearing invalid memory bank 0KB@0x00000000
[    0.000000] Clearing invalid memory bank 0KB@0x00000000
[    0.000000] Clearing invalid memory bank 0KB@0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x41000403
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat c052d160, node_mem_map c05c1000
[    0.000000]   Normal zone: 256 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32512 pages, LIFO batch:7
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: ip=dhcp console=ttyS0,115200 netconsole=6666@192.168.121.12/,6666@192.168.121.55/
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 128MB = 128MB total
[    0.000000] Memory: 124020k/124020k available, 7052k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
[    0.000000]     vmalloc : 0xc8800000 - 0xfd800000   ( 848 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .init : 0xc0008000 - 0xc0131000   (1188 kB)
[    0.000000]       .text : 0xc0131000 - 0xc05098ec   (3939 kB)
[    0.000000]       .data : 0xc050a000 - 0xc052e620   ( 146 kB)
[    0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Preemptable hierarchical RCU implementation.
[    0.000000]  RCU-based detection of stalled CPUs is disabled.
[    0.000000]  Verbose stalled-CPUs detection is disabled.
[    0.000000] NR_IRQS:64
[    0.000000] sched_clock: 32 bits at 166MHz, resolution 5ns, wraps every 25769ms
[    0.000000] Console: colour dummy device 80x30
[   16.679680] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
[   16.919479] pid_max: default: 32768 minimum: 301
[   16.919819] Mount-cache hash table entries: 512
[   16.920514] CPU: Testing write buffer coherency: ok
[   16.924094] NET: Registered protocol family 16
[   16.928174] Orion ID: MV88F5182-A2. TCLK=166666667.
[   17.239473] net2big: power up SATA hard disks
[   17.241218] net2big: Flash writing is not yet supported.
[   17.279048] bio: create slab <bio-0> at 0
[   17.281481] vgaarb: loaded
[   17.282918] SCSI subsystem initialized
[   17.284080] libata version 3.00 loaded.
[   17.285984] usbcore: registered new interface driver usbfs
[   17.286417] usbcore: registered new interface driver hub
[   17.286943] usbcore: registered new device driver usb
[   17.289612] Switching to clocksource orion_clocksource
[   17.299487] Switched to NOHz mode on CPU #0
[   17.333197] NET: Registered protocol family 2
[   17.333395] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[   17.333888] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[   17.334146] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[   17.334290] TCP: Hash tables configured (established 4096 bind 4096)
[   17.334321] TCP reno registered
[   17.334360] UDP hash table entries: 256 (order: 0, 4096 bytes)
[   17.334437] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[   17.334936] NET: Registered protocol family 1
[   17.335464] RPC: Registered udp transport module.
[   17.335494] RPC: Registered tcp transport module.
[   17.335524] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   17.335565] PCI: CLS 0 bytes, default 32
[   17.411174] msgmni has been set to 242
[   17.412414] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[   17.412457] io scheduler noop registered
[   17.412485] io scheduler deadline registered
[   17.412705] io scheduler cfq registered (default)
[   17.433887] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   17.520457] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
[   17.910632] console [ttyS0] enabled
[   17.953191] sata_mv sata_mv.0: version 1.28
[   17.958379] sata_mv sata_mv.0: slots 32 ports 2
[   17.968430] scsi0 : sata_mv
[   17.972854] scsi1 : sata_mv
[   17.976725] ata1: SATA max UDMA/133 irq 29
[   17.981045] ata2: SATA max UDMA/133 irq 29
[   17.988433] physmap platform flash device: 00080000 at fff80000
[   17.994757] physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank. Manufacturer ID 0x0000c2 Chip ID 0x0000ba
[   18.010759] Support for command set 0002 not present
[   18.015724] gen_probe: No supported Vendor Command Set found
[   18.026432] physmap-flash physmap-flash.0: map_probe failed
[   18.037285] MV-643xx 10/100/1000 ethernet driver version 1.4
[   18.043577] mv643xx_eth smi: probed
[   18.053684] net eth0: port 0 with MAC address 00:d0:4b:88:ec:69
[   18.060159] netconsole: local port 6666
[   18.063999] netconsole: local IP 192.168.121.12
[   18.068530] netconsole: interface 'eth0'
[   18.072632] netconsole: remote port 6666
[   18.076562] netconsole: remote IP 192.168.121.55
[   18.081246] netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
[   18.087337] netconsole: device eth0 not up yet, forcing it
[   18.329739] ata1: SATA link down (SStatus 0 SControl 300)
[   19.982191] eth0: link up, 100 Mb/s, full duplex, flow control disabled
[   20.498222] console [netcon0] enabled
[   20.501971] netconsole: network logging started
[   20.506543] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   20.513229] orion-ehci orion-ehci.0: Marvell Orion EHCI
[   20.518537] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   20.569752] orion-ehci orion-ehci.0: irq 17, io mem 0xf1050000
[   20.589730] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   20.597393] hub 1-0:1.0: USB hub found
[   20.601340] hub 1-0:1.0: 1 port detected
[   20.605819] orion-ehci orion-ehci.1: Marvell Orion EHCI
[   20.611241] orion-ehci orion-ehci.1: new USB bus registered, assigned bus number 2
[   20.659753] orion-ehci orion-ehci.1: irq 12, io mem 0xf10a0000
[   20.679722] orion-ehci orion-ehci.1: USB 2.0 started, EHCI 1.00
[   20.687404] hub 2-0:1.0: USB hub found
[   20.691351] hub 2-0:1.0: 1 port detected
[   20.696610] Initializing USB Mass Storage driver...
[   20.702304] usbcore: registered new interface driver usb-storage
[   20.708354] USB Mass Storage support registered.
[   20.713549] usbcore: registered new interface driver ums-datafab
[   20.720109] usbcore: registered new interface driver ums-freecom
[   20.726612] usbcore: registered new interface driver ums-jumpshot
[   20.733225] usbcore: registered new interface driver ums-sddr09
[   20.739632] usbcore: registered new interface driver ums-sddr55
[   20.746211] mousedev: PS/2 mouse device common for all mice
[   20.752965] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[   20.761187] i2c /dev entries driver
[   20.769765] rtc-rs5c372 0-0032: rs5c372b found, 24hr, driver version 0.6
[   20.777185] rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
[   20.786274] at24 0-0050: 1024 byte 24c08 EEPROM, writable, 1 bytes/write
[   20.794185] md: linear personality registered for level -1
[   20.799904] md: raid0 personality registered for level 0
[   20.805263] md: raid1 personality registered for level 1
[   20.810678] cpuidle: using governor ladder
[   20.814812] cpuidle: using governor menu
[   20.818851] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[   20.859796] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   20.899797] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[   20.906799] Registered led device: net2big:red:power
[   20.907314] Registered led device: net2big:blue:power
[   20.907830] Registered led device: net2big:red:sata0
[   20.908346] Registered led device: net2big:red:sata1
[   20.909769] TCP cubic registered
[   20.913054] NET: Registered protocol family 17
[   20.921103] rtc-rs5c372 0-0032: setting system clock to 2000-01-02 21:09:33 UTC (946847373)
[   22.439710] Sending DHCP requests .
[   22.854205] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[   22.861906] ata1: edma_err_cause=00000010 pp_flags=00000000, dev connect
[   22.868662] ata1: SError: { PHYRdyChg DevExch }
[   22.873337] ata1: hard resetting link
[   23.249730] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   23.289796] ata2.00: ATA-8: ST3250318AS, CC38, max UDMA/133
[   23.295426] ata2.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   23.359813] ata2.00: configured for UDMA/133
[   23.380381] scsi 1:0:0:0: Direct-Access     ATA      ST3250318AS      CC38 PQ: 0 ANSI: 5
[   23.391000] sd 1:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[   23.399507] sd 1:0:0:0: Attached scsi generic sg0 type 0
[   23.405561] sd 1:0:0:0: [sda] Write Protect is off
[   23.411273] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   23.411599] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   23.449709] , OK
[   23.478896]  sda: sda1 < sda5 sda6 sda7 sda8 sda9 sda10 > sda2
[   23.484861] IP-Config: Got DHCP answer from 192.168.121.55, my address is 192.168.121.201
[   23.496205] IP-Config: Complete:
[   23.499468]      device=eth0, addr=192.168.121.201, mask=255.255.255.0, gw=192.168.121.1
[   23.512149] sd 1:0:0:0: [sda] Attached SCSI disk
[   23.517083] ,
[   23.517095]      host=192.168.121.201, domain=, nis-domain=(none),
[   23.524759]      bootserver=192.168.121.55, rootserver=192.168.121.55, rootpath=
[   23.533528] Freeing init memory: 1188K
[   24.002677] md: md4 stopped.
[   24.174135] md: bind<sda2>
[   24.179142] md: md3 stopped.
[   24.273633] md: bind<sda5>
[   24.279121] bio: create slab <bio-1> at 1
[   24.283728] md/raid1:md3: active with 1 out of 2 mirrors
[   24.289295] md3: detected capacity change from 0 to 131465216
[   24.297676] md: md0 stopped.
[   24.303647]  md3: unknown partition table
[   24.380341] md: bind<sda7>
[   24.386118] md/raid1:md0: active with 1 out of 2 mirrors
[   24.391804] md0: detected capacity change from 0 to 8126464
[   24.400036] md: md1 stopped.
[   24.405838]  md0: unknown partition table
[   24.492056] md: bind<sda8>
[   24.497863] md/raid1:md1: active with 1 out of 2 mirrors
[   24.503567] md1: detected capacity change from 0 to 180813824
[   24.511965] md: md2 stopped.
[   24.517811]  md1: unknown partition table
[   24.608372] md: bind<sda9>
[   24.614224] md/raid1:md2: active with 1 out of 2 mirrors
[   24.619963] md2: detected capacity change from 0 to 690814976
[   28.339746] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   28.399799] ata1.00: ATA-8: ST3250312AS, JC45, max UDMA/133
[   28.405425] ata1.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   28.469819] ata1.00: configured for UDMA/133
[   28.474165] ata1: EH complete
[   29.720315] scsi 0:0:0:0: Direct-Access     ATA      ST3250312AS      JC45 PQ: 0 ANSI: 5
[   29.735283] sd 0:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[   29.747897] sd 0:0:0:0: Attached scsi generic sg1 type 0
[   29.756089] sd 0:0:0:0: [sdb] Write Protect is off
[   29.764049] sd 0:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[   29.764401] sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   29.816061]  sdb: sdb1 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 > sdb2
[   29.847672] sd 0:0:0:0: [sdb] Attached SCSI disk
miniroot ~ # df -h
Filesystem                Size      Used Available Use% Mounted on
miniroot ~ # uname -a
Linux miniroot 2.6.38-rc4-09713-ga6682f0-svn-dirty #17 PREEMPT Thu Feb 24 10:26:28 CET 2011 armv5tel GNU/Linux
miniroot ~ # fdisk -l

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1         250     2008093+  5 Extended
/dev/sda2             251       30401   242187907+ fd Linux raid autodetect
/dev/sda5               1          32      256977  fd Linux raid autodetect
/dev/sda6              33          33        8001  83 Linux
/dev/sda7              34          34        8001  fd Linux raid autodetect
/dev/sda8              35         140      851413+ fd Linux raid autodetect
/dev/sda9             141         249      875511  fd Linux raid autodetect
/dev/sda10            250         250        8001  83 Linux

Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1         125     1004031   5 Extended
/dev/sdb2             126       30401   243191970  83 Linux
/dev/sdb5               1          16      128457  82 Linux swap
/dev/sdb6              17          17        8001  83 Linux
/dev/sdb7              18          18        8001  83 Linux
/dev/sdb8              19          40      176683+ 83 Linux
/dev/sdb9              41         124      674698+ 83 Linux
/dev/sdb10            125         125        8001  83 Linux


Last edited by danyboy666 on Tue Dec 08, 2015 9:30 pm, edited 1 time in total.

Top
 Profile  
 
PostPosted: Sun Dec 06, 2015 9:56 pm 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
As you mentioned there is a problem with sdb. It rewrote the partition info.


Top
 Profile  
 
PostPosted: Sun Dec 06, 2015 11:16 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
in this output I don't see disk errors, but why are the partition tables different ? this will gives problems with building a raid array
You mention that you "rewrote" the partition table of sdb.
If the different table is a result of that then you need to do it again and make it execaty the same as sda (including partition types)


Top
 Profile  
 
PostPosted: Mon Dec 07, 2015 12:29 am 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
fvdw wrote:
in this output I don't see disk errors, but why are the partition tables different ? this will gives problems with building a raid array
You mention that you "rewrote" the partition table of sdb.
If the different table is a result of that then you need to do it again and make it execaty the same as sda (including partition types)


The NAS rewrote sdb itself for some reason. I've redid the procedure and then reinserted it in the NAS.

Code:
miniroot ~ # fdisk -l

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1         250     2008093+  5 Extended
/dev/sda2             251       30401   242187907+ fd Linux raid autodetect
/dev/sda5               1          32      256977  fd Linux raid autodetect
/dev/sda6              33          33        8001  83 Linux
/dev/sda7              34          34        8001  fd Linux raid autodetect
/dev/sda8              35         140      851413+ fd Linux raid autodetect
/dev/sda9             141         249      875511  fd Linux raid autodetect
/dev/sda10            250         250        8001  83 Linux

Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1         250     2008093+  5 Extended
/dev/sdb2             251       30401   242187907+ fd Linux raid autodetect
/dev/sdb5               1          32      256977  fd Linux raid autodetect
/dev/sdb6              33          33        8001  83 Linux
/dev/sdb7              34          34        8001  fd Linux raid autodetect
/dev/sdb8              35         140      851413+ fd Linux raid autodetect
/dev/sdb9             141         249      875511  fd Linux raid autodetect
/dev/sdb10            250         250        8001  83 Linux


Code:
cat /proc/mdstat
Personalities : [linear] [raid0] [raid1]
md0 : active raid1 sdb2[0]
      242187840 blocks [2/1] [U_]

md2 : active raid1 sda9[0]
      674624 blocks [2/1] [U_]

md1 : active raid1 sda8[0]
      176576 blocks [2/1] [U_]

md3 : active raid1 sda5[0]
      128384 blocks [2/1] [U_]

md4 : inactive sda2[0]
      242187840 blocks

unused devices: <none>


Code:
miniroot ~ # mdadm --examine /dev/sd[b,c,d,e]2
/dev/sdb2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : d3051fbb:b0183304:91dc962a:2413d849
  Creation Time : Sun Dec  6 22:45:17 2015
     Raid Level : raid1
  Used Dev Size : 242187840 (230.97 GiB 248.00 GB)
     Array Size : 242187840 (230.97 GiB 248.00 GB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 0

    Update Time : Sun Dec  6 22:45:31 2015
          State : clean
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 9d72044c - correct
         Events : 3


      Number   Major   Minor   RaidDevice State
this     0       8       34        0      active sync

   0     0       8       34        0      active sync
   1     1       0        0        1      faulty removed <-- not sure abouth this


I've ran "mdadm --examine" on all partitions amd they all state that they are clean so i also doubt its HDD failure. I've rebooted after all this and still nothing except Front LED flashing blue and back HDD LEDs solid blue. I'm going to run clunc again and see what else i can debug.


Top
 Profile  
 
PostPosted: Mon Dec 07, 2015 12:42 am 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
Damn it's doing the same thing again

Code:
miniroot ~ # fdisk -l

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1         125     1004031   5 Extended
/dev/sda2             126       30401   243191970  83 Linux
/dev/sda5               1          16      128457  82 Linux swap
/dev/sda6              17          17        8001  83 Linux
/dev/sda7              18          18        8001  83 Linux
/dev/sda8              19          40      176683+ 83 Linux
/dev/sda9              41         124      674698+ 83 Linux
/dev/sda10            125         125        8001  83 Linux

Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1         250     2008093+  5 Extended
/dev/sdb2             251       30401   242187907+ fd Linux raid autodetect
/dev/sdb5               1          32      256977  fd Linux raid autodetect
/dev/sdb6              33          33        8001  83 Linux
/dev/sdb7              34          34        8001  fd Linux raid autodetect
/dev/sdb8              35         140      851413+ fd Linux raid autodetect
/dev/sdb9             141         249      875511  fd Linux raid autodetect
/dev/sdb10            250         250        8001  83 Linux


Top
 Profile  
 
PostPosted: Mon Dec 07, 2015 8:40 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
in the output you posted from dmesg you posted I see this

Quote:
[ 23.484861] IP-Config: Got DHCP answer from 192.168.121.55, my address is 192.168.121.201
[ 23.496205] IP-Config: Complete:
[ 23.499468] device=eth0, addr=192.168.121.201, mask=255.255.255.0, gw=192.168.121.1
[ 23.512149] sd 1:0:0:0: [sda] Attached SCSI disk
[ 23.517083] ,
[ 23.517095] host=192.168.121.201, domain=, nis-domain=(none),
[ 23.524759] bootserver=192.168.121.55, rootserver=192.168.121.55, rootpath=
[ 23.533528] Freeing init memory: 1188K

This is strange, so to see you have an dhcp server running on 192.168.121.55 while the gateway as ip 192.168.121.1 (most of the time this is the router). Normally the router is the dhcp server. Why do you have this set up ?
Further what does boot server means here, or did you use tftp boot ?

What is "mini root" exactly andhow did you install/set "mini root" ? never hear of it

It seems you uploaded by tftp a kernel and root files system or am I wrong.

ps. if the nas has problems with two dsks you could only install only one disk in your nas (assuming it has the lacie firmware) and see what that does


Top
 Profile  
 
PostPosted: Tue Dec 08, 2015 5:03 am 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
Thanks for your response.

Well here's my network setup:

192.168.121.1 DHCP server
192.168.121.55 TFTP server and NetConsole client
192.168.121.12 temporary static address assigned to lacie NAS.
192.168.121.200 address obtained by NAS via DHCP once booted into miniroot

I'll try to explain what is going on.

The NAS is running u-boot but since it won't boot up completely i am using a script named "clunc" wich gives me the options to connect to u-boot while the NAS is trying to boot. Once the NAS boot sequence is completed (failed) i can pass some DHCP arguments to u-boot and make it do pretty much everything i want. In this case i tell it to download a kernel image via tftp to the nas RAM which contain minimal set of tools to run on the nas. Maybe it's overkill though i didn't try to telnet directly into the NAS without clunc :P.

Quote:
This is strange, so to see you have an dhcp server running on 192.168.121.55 while the gateway as ip 192.168.121.1 (most of the time this is the router). Normally the router is the dhcp server. Why do you have this set up ?


- You are right the router/gateway (121.1) is handling DHCP request but in this case the tftp (boot server) server hands out network informations to the client (NAS).

Quote:
Further what does boot server means here, or did you use tftp boot ?


- I am using a little script named "Clunc" (Client for LaCie U-Boot NetConsole) which enable me to have serial output without having to go true JTAG interface
http://lacie-nas.org/doku.php?id=clunc
Everything is done via UDP.

Quote:
What is "mini root" exactly andhow did you install/set "mini root" ? never hear of it


- Miniroot is the kernel image (kernel+initramfs) that my tftp server is handling via tftp. It is supose to be the same as the NAS. Once the kernel is uploaded to the NAS i can connect to it from another PC via TELNET.

Quote:
It seems you uploaded by tftp a kernel and root files system or am I wrong.


- You are right.

Quote:
ps. if the nas has problems with two dsks you could only install only one disk in your nas (assuming it has the lacie firmware) and see what that does


I've tried that without succes. I know any raid1 setup should handle booting from a single disk but for whatever reason the LaCie NAS can't handle it. I've done several test (Safe100 and Big) and not a single of those test gives me proper result.

ps:
My network and computer knowledge is sufficient for me to understand what i'm doing but to explain and teach is quite another task which i'm not really confortable with. In any case i hope it was clear enough so you can at least understand my process.


Top
 Profile  
 
PostPosted: Tue Dec 08, 2015 10:06 am 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
Thx for explaining, I am quite familiar with clunc and the way to talk to uboot using netconsole. I even build an application that runs under windoes that does basically the same as what you do. Uploading via tftp a standalone kernel with an initramfs root filesystem. It runs fully from ram. More see http://plugout.net in diwnload section you can find this application (fvdw-sl) console.
There are also post of others struggling to get 2big2 up and running.
If yiu have access to u-boot then you can also set environment variable that passes a command line to the kernel specifying were it can find the root filesystem, so instead of using your mini root kernel, use the "normal" kernel and sett before loading the environment parameter "root" (it might be possible that is already set by uboot) If the lacie kernel has netconsole activated then you should be able to see were the boot scripts fails


Top
 Profile  
 
PostPosted: Tue Dec 08, 2015 8:52 pm 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
Yes i've created an account the other day on your forum. I might try your files if i can't recover the NAS with lacie's original filesystem.

Is it possible the NAS U-boot isn't compatible with the 2.2.3 firmware? This would maybe explain why the NAS tries to rewrite its partition info.

This partition scheme it rewrite isn't the same as the one described on the wiki.

http://lacie.nas-central.org/wiki/Installing_firmware_on_fresh_disks_(2Big_2)#Create_partitions

Code:
Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1         125     1004031   5 Extended
/dev/sdb2             126       30401   243191970  83 Linux
/dev/sdb5               1          16      128457  82 Linux swap
/dev/sdb6              17          17        8001  83 Linux
/dev/sdb7              18          18        8001  83 Linux
/dev/sdb8              19          40      176683+ 83 Linux
/dev/sdb9              41         124      674698+ 83 Linux
/dev/sdb10            125         125        8001  83 Linux


But when i tried getting some infos on it when i was in busybox it still stated that it wasn't reconizing the partition.

I'm only speculating here since i know the firmware is located on the HDD but it does seem that the NAS current U-boot was flashed with an older version which is not compatible with 2.2.3 fimware.

The kernel image i'm uploading to the NAS is dating from 2011-02-22. I really doubt the previous owner even updated the NAS original firmware it came with. I can try find an older kernel image for it today and see if it try to rewrite the partition info again.

Anywais i'll try to run more test today. I have good hope i can revive this device since i know now it's not completely dead or bricked. I have to redo a disk partitioning from another linux box since i've tried rebuilding it from the NAS itself the last time but it was missing a critical tool (mkfs.xfs) to enable me to complete the procedure from the NAS.

With all this said i still can't figure why the NAS won't boot with only a single disk. It's RAID1 after all...

Also LaCie support wrote back to me saying basicaly i couldn't RMA the device since it was out of warranty (i was kind of expecting that since the NAS was sold in 2009) but they sent me a link to the capsule needed to recover the NAS. The link only list 2.2.8 firmware. http://www.lacie.com/support/network-storage/2big-network/?sku=LAC301421U
None of these files works with LNA it's complaining that they are invalid.

The only capsule i could find which was compatible with LNA is "capsule-2Big-upgrade-2.2.3-r1802" which i got from a somewhere else but LNA does accept it and identify it as "2Big Network".

Anywais I've gave up on LNA so that's why I'm using clunc which at least give me a Cli to work with.


Top
 Profile  
 
PostPosted: Wed Dec 09, 2015 4:03 am 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
Thanks for your help. I will get it to work myself. I just wish there were a guide somewhere that would work for every revisions of this nas. The infos are scattered everywhere. A bit here a bit there but no definitive guide for every possibilities which comes with the right image files and partition table for us to use.


Top
 Profile  
 
PostPosted: Wed Dec 09, 2015 10:24 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
two things

Quote:
Is it possible the NAS U-boot isn't compatible with the 2.2.3 firmware?

u-boot just loads a kernel and a kernel command line, the kernel loads the boot scripts from lacie inside the root file system, so in principle u-boot is compatible with any version of the firmware as long as the kernel and root file system are on the correct place

Next I looked somewhat closer to your demsg output and see this
Code:
[   16.920514] CPU: Testing write buffer coherency: ok
[   16.924094] NET: Registered protocol family 16
[   16.928174] Orion ID: MV88F5182-A2. TCLK=166666667.

Notice the orion ID
This means don't have a 2big_v2 but a older orion based 2big_v1, or you have a replace motherboard inside this nas.
A 2big_v2 has a kirkwood processor with ID MV88F6182
You can check easily if you open it and look on the code on the processor, if it mentions 5182 then it is an orion based 2big_v1
It must mention this otherwise kernel won't run and won't gives this cpu id

Of course firmware and installation instructions for 2big_v2 will not work on this device ;)


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 25 posts ]  Go to page 1, 2  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 11 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group