# uname -a
Linux bwaters-desktop 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux
1. manually assemble the array (named vla) as root
# mdadm --assemble --scan --auto=md
2. mount the array (it contains a large ext4 filesystem)
# mount /dev/md/vla /mnt/vla
This large filesystem is shared by AFPD from the netatalk package.
3. reboot the computer from the GNOME "power symbol" menu (at the top right corner)
When the system comes back up, log in as user, open a terminal, sudo -i to become root.
Attempt to re-start the array yields ("/dev/sdc no superblock found") and the array is not started.
WORK-AROUND -- there is a spurious "array" that seems to be running after reboot. I stopped that "ghost array", and was able to get my array back into operation.
Cannot access RAID5 array upon reboot.
# uname -a
Linux bwaters-desktop 2.6.32-16-generic #25-Ubuntu SMP Tue Mar 9 16:33:12 UTC 2010 x86_64 GNU/Linux
1. manually assemble the array (named vla) as root
# mdadm --assemble --scan --auto=md
2. mount the array (it contains a large ext4 filesystem)
# mount /dev/md/vla /mnt/vla
This large filesystem is shared by AFPD from the netatalk package.
3. reboot the computer from the GNOME "power symbol" menu (at the top right corner)
When the system comes back up, log in as user, open a terminal, sudo -i to become root.
Attempt to re-start the array yields ("/dev/sdc no superblock found") and the array is not started.
WORK-AROUND -- there is a spurious "array" that seems to be running after reboot. I stopped that "ghost array", and was able to get my array back into operation.
$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md_d127 : inactive sdf[3](S)
1953514452 blocks super 1.1
unused devices: <none>
$ sudo -i
[sudo] password for bwaters:
# mdadm --stop /dev/md_d127
mdadm: stopped /dev/md_d127
# mdadm --assemble --scan --auto=md
mdadm: /dev/md/vla has been started with 6 drives.