Molle Bestefich <molle.bestefich <at> gmail.com> writes: > Karl Voit wrote: > > > root <at> ned ~ # mdadm --assemble /dev/md0 /dev/sda1 /dev/sdb1\ > > /dev/sdc1 /dev/sdd1 > > mdadm: cannot open device /dev/sda1: Device or resource busy > > mdadm: /dev/sda1 has no superblock - assembly aborted > > Odd message. Does "lsof | grep sda" show anything using /dev/sda(1)? Nope. > > The problem seems to be the superblocks. > > Which ones, those on sd[abcd]1 ? I guessed so. > You've probably destroyed them by syncing the array consisting of sd[abcd]. Sh.. > > Can I repair them? > > No, but you can recreate them without touching your data. > I think the suggestion from Andreas Gredler sounds sane. > > I'm unsure if hot-adding a device will recreate a superblock on it. > Therefore I'd probably run --create on all four devices and use sysfs > to force a repair, instead of (as Andreas suggests) creating the array > with one 'missing' device. > > Do remember to zero the superblocks on sd[abcd] first, to prevent mishaps... Just to make sure, that I do not make any dumb commands. Is it true, that I should try the following lines? mdadm --stop /dev/md0 mdadm --zero-superblock /dev/sda mdadm --zero-superblock /dev/sdb mdadm --zero-superblock /dev/sdc mdadm --zero-superblock /dev/sdd mdadm --assemble /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 --force (check, if it worked - probably not - and if not, try the following line) mdadm --create -n 4 -l 5 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 sysfs: Sorry, what should I do with sysfs. I do not know this tool yet. root@ned /sys/block/md0 # l total 0 -r--r--r-- 1 root root 4096 2006-07-10 13:38 dev -r--r--r-- 1 root root 4096 2006-07-10 13:38 range -r--r--r-- 1 root root 4096 2006-07-10 13:38 removable -r--r--r-- 1 root root 4096 2006-07-10 13:38 size -r--r--r-- 1 root root 4096 2006-07-10 13:38 stat root@ned /sys/block/md0 # Did you mean something like "echo repair > /sys/block/md0/md/sync_action" which I googled? - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
