lacie 5 big network v.1 please support for fvdw

[fvdw]

no keep the 500 GB diks with the firmware and kernel in slot 1

place the 2TB disk you have in slot 5 now in slot 2 and check if the kernel finds it, so leave the disk in slot 1 as it is

[fvdw]

now lets try to fix the devices nodes

I assume you installed originally fvdw-sl-11-0, so that version is present on partition sda7.
later we installed fvdw-sl-14-0 on sda2 and that is the one it now uses for booting.

We need to adapt on as well sda7 as sda2 the main boot script.
This because the kernel always start to load the script form sda7 and then passes control to the boot script on sda2.
As both firmware version on sda7 and sda2 are different we need two different adapted boot script files

Attached two files one containing the boot script for partition sda7 (rcS-5big1-11-0-sda7.zip)
The other one the boot script for sda2 (rcS-5big1-14-0-sda2.zip)

How to install.
Take out all disk except the one in slot 1 (the 500GB one containing the firmware)
Boot the 5big1, the web interface should come up and ssh server should be working

Make in the shared folder "public" a sub folder with name fvdw-sl-11-0
Unpack the file rcS-5big1-11-0-sda7.zip in that subfolder, it should now contain a file with name rcS

Make in the shared folder "public" a sub folder with name fvdw-sl-14-0
Unpack the file rcS-5big1-14-0-sda2.zip in that subfolder, it should now contain a file with name rcS

Connect to the nas via ssh

On the command line give the commands

Code: Select all

mkdir sda2
mount /dev/sda2 sda2
cp /share/1000/public/fvdw-sl-14-0/rcS /sda2/etc/init.d/
chmod 755 /sda2/etc/init.d/rcS
umount sda2
rmdir sda2

mkdir sda7
mount /dev/sda7 sda7
cp /share/1000/public/fvdw-sl-11-0/rcS /sda7/etc/init.d/
chmod 755 /sda7/etc/init.d/rcS
umount sda7
rmdir sda7


reboot the nas using the webinterface and see if it comes up.

If ok switch it off and put in the disk in slot 5 en boot it again and see if it now comes up with the firmware

[taetae]

slot 2 2tb

[fvdw]

well it hasn't detected the disk in slot 2 :scratch
You will have to test slot 3 and 4 as well, maybe its an hardware problem with slot 2
(keep the 500 GB disk in slot 1)

[taetae]

Now I put the script


script slo1 only 500 gb

[taetae]

kernel panic
slot 5 only 500gb and slot2 and slot3

[taetae]

slot 4 only 500gb (I give him the "boot" command in order not to make the countdown)

[fvdw]

kernel panic
slot 5 only 500gb and slot2 and slot3

yep that is correct the disk in slot 5 is now sde and the kernel tries to find sda7, and cannot find it because no disk is present in slot 1 (=sda)
You will have to put the disk with the firmware always in slot 1

slot 4 only 500gb (I give him the "boot" command in order not to make the countdown)

Also this will fail for same reason, but it seems that uboot doesn't even detect a disk in slot 4 (and also not in slot 2 so probably also not in slot 3)

With this kernel the disk with firmware must always be in slot 1.
This means try the following combinations (this will tell us which slots will be detected in which not):

(1) slot 1 500 GB disk with firmware, other slots empty
(2) slot 1 500 GB disk, slot 2 2TB disk
(3) slot 1 500 GB disk, slot 3 2TB
(4) slot 1 500 GB disk, slot 4 2 TB
(5) slot 1 500 GB disk, slot 5 2TB

from all the kernel output...I know a lot of testing

[fvdw]

Remark; we might have a hardware problem with this device.

This part of the console output is coming from u-boot and not from the kernel

Code: Select all

Waiting for LUMP (5)
no lump receive; continuing

Reset IDE:
Marvell Serial ATA Adapter
Found adapter at bus 1, device 7 ... Scanning channels
  Device 0: OK
Model: WDC WD5000AADS-00S9B0                    Firm: 01.00A01 Ser#:      WD-WCAV90478832
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)


** Device 1 not available

** Device 2 not available

** Device 3 not available

** Device 4 not available

Loading from IDE device 0, partition 6: Name: hda6
  Type: U-Boot
   Image Name:   Linux-2.6.39.4
   Created:   

<snip>

The fact that your outputs doesn't show that u-boot can detect a disk in slot 2 (device 3) or slot 4 (device 1) but it detects just like the kernel a disk in slot 1 (device 4) and in slot 5 (device 0) is to my opinion not a good sign and could indicate a hardware problem.
If it was only the kernel not finding disks in these slots while u-boot did find them then it would be a kernel problem, but the fact the u-boot also doesn't find them in these slots makes it unlikely that this is a kernel issue. It could be a power failure preventing the disk from powering up. You need to check if a disk is in slot 2,3 or 4 is spinning up.

[taetae]

I bought 4 2tb disks if you want to try everything