[TriLUG] directory listing from a damaged RAID?

John Brier johnbrier at gmail.com
Sun Jan 3 12:41:09 EST 2010


On Sun, Jan 3, 2010 at 12:00 PM,  <trilug-request at trilug.org> wrote:

> is it worth trying something like restarting the array with mdadm of
> three drives, one active and two missing?

If you haven't tried and it's not working now what do you have to lose?

A quick google search suggests:
http://www.experts-exchange.com/OS/Linux/Administration/Q_21926825.html

mdadm --assemble  --force /dev/md5 /dev/sda7 /dev/sdb7 /dev/sdc7 /dev/sdd7

Or if it that won't work you can try recreating it with the existing drives:

http://www.linuxquestions.org/questions/linux-server-73/software-raid-5-md-recovery-using-mdadm-551732/#post2755664

mdadm --create /dev/md0 --level=5 --raid-devices=5 /dev/sd[d-h]1

I got the following messages during the process:
mdadm: /dev/sdd1 appears to contain an ext2fs file system
size=1953535744K mtime=Thu May 17 22:24:08 2007
mdadm: /dev/sdd1 appears to be part of a raid array:
level=raid5 devices=5 ctime=Sat May 5 15:19:07 2007
mdadm: /dev/sde1 appears to be part of a raid array:
level=raid5 devices=5 ctime=Sat May 5 15:19:07 2007
mdadm: /dev/sdf1 appears to be part of a raid array:
level=raid5 devices=5 ctime=Sat May 5 15:19:07 2007
mdadm: /dev/sdg1 appears to be part of a raid array:
level=raid5 devices=5 ctime=Sat May 5 15:19:07 2007
mdadm: /dev/sdh1 appears to contain an ext2fs file system
size=2005702402K mtime=Wed Nov 28 02:32:38 2007
mdadm: /dev/sdh1 appears to be part of a raid array:
level=raid5 devices=5 ctime=Sat May 5 15:19:07 2007
Continue creating array?y
mdadm: array /dev/md0 started.

I was then able to mount the array and access all files.

JB



More information about the TriLUG mailing list