Search:

Ah, yes...silly me. It's been a long week.


sudo dumpe2fs /dev/md0 | sudo grep superblockdumpe2fs 1.42 (29-Nov-2011)
Journal superblock magic number invalid!

sudo mdadm --assemble /dev/md0 /dev/sd[ifchdgbekjl]1
mdadm: /dev/md0 has been started with 11 drives.


sudo mdadm --detail /dev/md0/dev/md0:
Version : 0.90
Creation Time : Sun Mar 21...

Rubylaser:


> sudo mdadm -E /dev/sd[bcdefghijkl]1/dev/sdb1:
Magic : a92b4efc
Version : 0.90.00
UUID : e7db05b0:4a9008b8:98883325:0d269d95
Creation Time : Sun...

I dug up an old email that contained a /proc/mdstat reading showing the following:


md0 : active raid5 sdb1[8](F) sde1[9](F) sdd1[10](F) sdh1[11](F) sdc1[12](F) sdf1[13](F) sdg1[14](F)...

root@titanium:~# dumpe2fs /dev/md0dumpe2fs 1.42 (29-Nov-2011)
Filesystem volume name: <none>
Last mounted on: /media/storage
Filesystem UUID: ...

root@titanium:~# dumpe2fs /dev/md0 | grep -i superblockdumpe2fs 1.42 (29-Nov-2011)
Journal superblock magic number invalid!

Blah. I'm reading different things, and I'm worried that I'll do...

Hm.


root@titanium:~$ fsck /dev/md0fsck from util-linux 2.20.1
e2fsck 1.42 (29-Nov-2011)
Superblock has an invalid journal (inode 8).
Clear<y>?

Is this a good idea?

I've changed out the bad drive to a new good one and it recovered! Hooray.

Same problem still around though, that the drive won't mount (same error). Thoughts?

Thanks for all of your suggestions so far everyone! Funny thing...I woke up this morning, and the array was just about finished reshaping. Go figure, right? The drive 'sdi' is still failing, but I...

Yeah, mdadm --S /dev/md0 will stop the array. I didn't know if there was another specific command to simply stop rebuilding. I will have to mark the drive as failed and remove it from the array...

Could you point me to the command to cancel the reshape?

So the steps would be, mark the failing drive as failed, remove it from the array, replace it physically, format new drive, and start the...

CharlesA -- Here's what happens when I try to mount the array:


root@titanium:~# mount /dev/md0 /media/storagemount: wrong fs type, bad option, bad superblock on /dev/md0,
missing...

Well unless I want to wait about a year for the reshape to finish ;). I'll wait until tomorrow to see if anyone else responds, then I'll check out that link and possibly replace the failed drive. ...

That slow speed is after I received the email about the failed drive:


This is an automatically generated mail message from mdadm
running on titanium

A Fail event had been detected on md...

All of my important information is backed up via Amazon S3...but the TV shows and movies, I don't bother backing up.

Here's the output:


root@titanium:~# mdadm --detail --scan
ARRAY /dev/md0...

Hello all! First time posted, long time reader. By a long string of back luck coincidences, I feel like my only chance to recover (if not fully, then partially) my data is to defer to you. Here's...