I have two disks set up in a raid 0 array like so:
raiddev /dev/md0
raid-level 0
nr-raid-disks 2
persistent-superblock 1
chunk-size 64k
nr-spare-disks 0
device /dev/hda2
raid-disk 0
device /dev/hdc1
raid-disk 1
Where hda1 is the boot partition. This worked well for several months,
until several days ago the machine refused to boot because it couldn't
start the array. So, I put the array in another machine and changed the
raidtab around like so:
raiddev /dev/md0
raid-level 0
nr-raid-disks 2
persistent-superblock 1
chunk-size 64k
nr-spare-disks 0
device /dev/hdd2
raid-disk 0
device /dev/hdc1
raid-disk 1
but I still can't get the array to come up. md says these things:
md: md driver 0.90.0 MAX_MD_DEVS=256,MD_SB_DISKS=27
md: Autodetecting RAID arrays.
(read) hdd2's sb offset: 29287360 [events: 000000d0]
md: autorun ...
md: considering hdd2 ...
md: adding hdd2 ...
md: created md0
md: bind<hdd2,1>
md: running: <hdd2>
md: hdd2's event counter: 000000d0
md: device name has changed from hda2 to hdd2 since last import!
md0: former device hdc1 is unavailable, removing from array!
request_module[md-personality-2]: Root fs not mounted
md.c: personality 2 is not loaded!
md :do_md_run() returned -22
md: md0 stopped.
md: unbind<hdd2,0>
md: export_rdev(hdd2)
md: ... autorun DONE.
I don't understand why it thinks hdc1 is unavailable. How do I get it to
tell me more / start the array? Does this mean hdc is busted?
Thanks,
Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
