This is where I'm a little unsure, not having done anything with software RAID5 before but I'm thinking that adding the drives to the array and perhaps forcing it to assemble may do it.
john@tower:~$ sudo mdadm --add /dev/md0 /dev/sde1 /dev/sdc1 /dev/sdd1 mdadm: cannot get array info for /dev/md0 john@tower:~$ sudo mdadm -Af /dev/md0 mdadm: no devices found for /dev/m
but I'm not completely sure and am also trying to figure out my own RAID problem here (new Intel server won't start after installing Ubuntu 10.04 server) so things are getting a bit confusing!
Anyway try that and see how you go, we're further ahead than before, it's not complaining of superblock issues although we've not asked it to be particularly verbose so I don't think it's all that far away from working - perhaps check out and see what's on offer via Google now things are a bit different. I keep hoping some RAID guru will show up with the perfect answer but not as yet... in the meantime I'll carry on with my problem and check again later to see how you're going - or in the morning if my issue carries on too long :-(
john@tower:~$ sudo mdadm -Af /dev/md0 /dev/sde1 /dev/sdc1 /dev/sdd1 mdadm: forcing event count in /dev/sdd1(1) from 81355 upto 81367 mdadm: forcing event count in /dev/sdc1(2) from 81355 upto 81367 mdadm: clearing FAULTY flag for device 2 in /dev/md0 for /dev/sdd1 mdadm: clearing FAULTY flag for device 1 in /dev/md0 for /dev/sdc1 mdadm: /dev/md0 has been started with 3 drives.
everything is still there and the array is online, but not sure what will happen after a reboot... would like for the array to automatically startup when the machine is rebooted (which it isnt very often, about twice a month)
You'd add it in fstab for it to start when you restart the machine. Just to confirm though, you've checked your data is there ok? I'd have thought you'd have needed to mount md0 first but perhaps you did that already...
FYI here's an example fstab from the same machine as I showed you the mdadm.conf info from:
# / was on /dev/md0 during installation UUID=66c88415-0051-4869-bf26-70d8f48d38c1 / ext3 errors=remount-ro 0 1
I gave up on mine for the night, I think it may be a bios problem or something similar so will probably need to discuss that with the suppliers in the morning.
Probably not. You didn't tell me whether you'd mounted the array and/or if your files were all there or not... what I suggest is that you have a good look at these two pages:
which should explain a bit about the process. It'll depend a bit on how/what you want to do. Personally I never name any file or folder with a space in it, I will also go to great lengths to keep file/folder names less than 8.3 characters which is a holdover from the ol' DOS days and I know we're not talking DOS here but it works for me! I need to deal with many OS's throughout the day and it's a policy that's stood me in good stead. So I'd be setting things in your system to read just 'library' for instance and leave 'the ' out of it altogether.
It sounds like you're out of the hole now which is good, from here on in it's probably a matter of taking a bit of breathing space and learning from the process. If you've got the facility to do it I'd backup your data on the array. It's good practice anyway and if things went awry then you've got a copy of your stuff. Have a good read of those pages and you'll understand things more and be able to make an informed decision on how and what to do from here on in :-)
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.