I found the solution by using mdadm with "Assemble" mode. It's as simple as this:
# mdadm -A /dev/md0 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 mdadm: /dev/md0 has been started with 4 drivers. Lesson learnt: don't use raidstart anymore, use mdadm. On Sun, 2003-07-27 at 16:34, Tao Chen wrote: > This is probably one of the FAQs, I googled the error message but have > not found a solution. > > Had a RAID0 with 4 partitions: > > raiddev /dev/md0 > raid-level 0 > nr-raid-disks 4 > persistent-superblock 1 > chunk-size 8 > device /dev/sdb1 > raid-disk 0 > device /dev/sdc1 > raid-disk 1 > device /dev/sde1 > raid-disk 2 > device /dev/sdf1 > raid-disk 3 > > Problem happened after I pulled another disk out: sdd, which is not part > of the RAID. Obviously, raid code get confused because sde1 now becomes > sdd1, and sdf1 becomes sde1. > > The error message: > ... > md: device name has changed from sdf1 to sde1 since last import! > md0: former device sde1 is unavailable, removing from array! > md0: max total readahead window set to 992k > md0: 4 data-disks, max readahead per data-disk: 248k > md: md0, array needs 4 disks, has 3, aborting. > raid0: disks are not ordered, aborting! > md: pers->run() failed ... > md :do_md_run() returned -22 > md: md0 stopped. > ... > > I updated the /etc/raidtab file to: > raiddev /dev/md0 > raid-level 0 > nr-raid-disks 4 > persistent-superblock 1 > chunk-size 8 > device /dev/sdb1 > raid-disk 0 > device /dev/sdc1 > raid-disk 1 > device /dev/sdd1 > raid-disk 2 > device /dev/sde1 > raid-disk 3 > > but it doesn't help. > > I assume this is recoverable. > If so, please help me out with the steps or related links. > Is there a better way to build RAID at 2.4.xx ? > > Thanks in advance! -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
