Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
/ # mdadm -A /dev/md0 /dev/sdb2 /dev/sdc2
mdadm: /dev/md0 has been started with 2 drives.
/ # e2fsck /dev/md0
e2fsck 1.41.0 (10-Jul-2008)
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/md0
Could this be a zero-length partition?
Any ideas? I can't find any relevant info on Google.
Offline
You are beyond my expertise, now. you could try using some of the options on e2fsck to force a check, or to specifically look for bad blocks. you could also try changing to a backup superblock (block that holds the raid/disk information). That is done with e2fsck, I believe.
Offline
Can't seem to find any documentation on Google regarding the mounting of a hard drive while ignoring bad sectors. Anyone out there have any ideas?
Offline
Well I think I'm about ready to throw in the towel on this one. e2fsck doesn't like any of my superblocks. I used mke2fs -n to find the superblock location and backup superblocks on the naughty hard drive--sadly, e2fsck just won't cooperate with them. I also tried using badblocks to no avail.
I just can't seem to find any howtos or walkthroughs or even forumposts regarding the situation I'm in anywhere. I've exhausted my technical knowledge and resources. I've asked all my techie friends for advice. I've had the best advice here in this forum from members like bq041 and fordem (thanks very much guys!). But in the end I just can't solve the problems.
It was a good project and it was fun to get my hands dirty again. But it's time to close this one out. Lesson learned: don't put anything important on RAID 0. When the RAID fails, you're pretty much screwed.
Thanks again for all the advice.
Offline
Sorry to hear that. It may be that you have a true hard drive failure, and that is a major drawback of JBOD and RAID 0.
Offline