Cannot access 5big network 2

[Jocko]

kernel handles an index to set properly the device name. So mybe this can explain this behaviour.

@pacco
please to follow only this sequence (nas stopping):
1/unplug the failed disk (5th)
2/plug the new disk
3/start fvdw-sl console and load the kernel
4/upload udevstart and mdadm
5/run udevstart at this step please...
6/ build the raid with the command

Code: Select all

mdadm --assemble /dev/sd[abcd]2

-< please to use it

then post the content of /proc/partitions and

Code: Select all

ls -l /dev/sd[abcde]

with your last post
:pound :pound :pound you missed to update the dev nodes :mrgreen: :mrgreen:
and the right command is

Code: Select all

cat /proc/partitions|busybox grep -r /dev/sd[abcde]$

[pacco]

at which stage do I enter the command

Code: Select all

cat /proc/partitions|busybox grep -r /dev/sd[abcde]$

[Mijzelf]

To me (as a very big novice) is appears d and e are swapped!

They are. For some reason the disks in the Lacie are not detected in the physical sequence. To solve that the kernel renames them internally. The udev tool renames them externally. So without the udev tool the disks have their names not in physical order.

[Jocko]

I wrote that at each post you need to post the output

Code: Select all

ls -l /dev/sd[abcde]
cat /proc/partitions|grep -r /dev/sd[abcde]$

As sometimes you update the dev nodes and other times no. This prevents me to understand what happens. This allows us to understand better your outputs.

Please to note also: the time when you run udevstart is important. So always start it before running any linux commands.

[pacco]

I wrote that at each post you need to post the output

Code: Select all

ls -l /dev/sd[abcde]
cat /proc/partitions|grep -r /dev/sd[abcde]$

As sometimes you update the dev nodes and other times no. This prevents me to understand what happens. This allows us to understand better your outputs.

Please to note also: the time when you run udevstart is important. So always start it before running any linux commands.

I have a new one!

Code: Select all

root@fvdw-sta-kirkwood:/ # tftp -l /sbin/udevstart -r udevstart -g 192.168.10.10
udevstart            100% |*******************************|   470k  0:00:00 ETA
root@fvdw-sta-kirkwood:/ # tftp -l /sbin/mdadm -r mdadm -g 192.168.10.10
mdadm                100% |*******************************|  1100k  0:00:00 ETA
root@fvdw-sta-kirkwood:/ # chmod 755 /sbin/udevstart
root@fvdw-sta-kirkwood:/ # chmod 755 /sbin/mdadm
root@fvdw-sta-kirkwood:/ # udevstart
root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/sd[abcd]2
mdadm: device /dev/sda2 exists but is not an md array.

Code: Select all

root@fvdw-sta-kirkwood:/ # cat /proc/partitions
major minor  #blocks  name

  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0  976762584 sdc
   8        1          1 sdc1
   8        2  974751907 sdc2
   8        5     256977 sdc5
   8        6       8001 sdc6
   8        7       8001 sdc7
   8        8     851413 sdc8
   8        9     875511 sdc9
   8       10       8001 sdc10
   8       16  976762584 sdb
   8       17          1 sdb1
   8       18  974751907 sdb2
   8       21     256977 sdb5
   8       22       8001 sdb6
   8       23       8001 sdb7
   8       24     851413 sdb8
   8       25     875511 sdb9
   8       26       8001 sdb10
   8       32  976762584 sda
   8       33          1 sda1
   8       34  974751907 sda2
   8       37     256977 sda5
   8       38       8001 sda6
   8       39       8001 sda7
   8       40     851413 sda8
   8       41     875511 sda9
   8       42       8001 sda10
   8       48  976762584 sde
   8       64  976762584 sdd
   8       65          1 sdd1
   8       66  974751907 sdd2
   8       69     256977 sdd5
   8       70       8001 sdd6
   8       71       8001 sdd7
   8       72     851413 sdd8
   8       73     875511 sdd9
   8       74       8001 sdd10


Code: Select all

root@fvdw-sta-kirkwood:/ # ls -l /dev/sd[abcde]
brw-rw----    1 root     root        8,   0 May  3 11:01 /dev/sda
brw-rw-r--    1 root     root        8,  16 May  3 11:01 /dev/sdb
brw-rw----    1 root     root        8,  32 May  3 11:01 /dev/sdc
brw-rw----    1 root     root        8,  64 May  3 11:01 /dev/sde
root@fvdw-sta-kirkwood:/ # cat /proc/partitions|grep -r /dev/sd[abcde]$
root@fvdw-sta-kirkwood:/ #


[pacco]

Shouldn't it be: mdadm --assemble /dev/md0 /dev/sd[abcd]2 --run?

[Mijzelf]

Shouldn't it be: mdadm --assemble /dev/md0 /dev/sd[abcd]2 --run?

Yep.

@Jocko: What does that udev tool exactly do? Can it be tricked by a disk without partitions?

[Jocko]

what udevstart do you use? Mijzelf script or the the downloaded binary?

@pacco
Sorry for my last error
Please to note I updated the command

Code: Select all

cat /proc/partitions|busybox grep -r /dev/sd[abcde]$

[pacco]

what udevstart do you use? Mijzelf script or the the downloaded binary?

The downloaded binary (mdadm 8-7-2013 18:23 1.101kb).

[Jocko]

The binary is not mdadm but udevstart.

As you name Mijzelf script udevstart, the issue is: do you use the script or the binary available from plugout?