As you can read in post 78, I think your sdb and sdc are actually the 1st and 2nd disk from the left (seen on the back).
Yes, I think it's a good idea to rule out hardware/kernel problems first. So remove the first 3 disks, and put disk 1 in slot 3, leaving the first 2 slots empty. (Of course put a mark on the disks first). And have a look if mdadm can read the metadata of all remaining disks.
(3 hours lunch? Viva España)
@fvdw: There is no law which connects sda to minor 0, only a convention. You are allowed to create a devicenode /home/user/7200rpmSeagate if you wish. Don't think it's a good idea, though.
I had a look in the 5Big2 initrd, and it's /dev isn't populated. On boot 'mdev -s' is called to populate it. mdev is the lightweigth busybox counterpart of udev, and it's capable to dynamically create nodes, in collaboration with the kernel. So I guess it can handle the strange devicename/minor combination.
If your busybox has mdev included, you could try on your box:
- Code: Select all
mv /dev /dev.old
mkdir /dev
mdev -s
It might generate a non-standard set of device nodes.