On Fri, 2009-12-25 at 21:47 -0500, Rick Bragg wrote: > On Fri, 2009-12-25 at 20:33 -0500, Rick Bragg wrote: > > Hi, > > > > I have a raid 10 array and for some reason the system went down and I > > can't get it back. > > > > during re-boot, I get the following error: > > > > The superblock could not be read or does not describe a correct ext2 > > filesystem. If the device is valid and it really contains an ext2 > > filesystem (and not swap or ufs or something else), then the superblock > > is corrupt, and you might try running e2fsck with an alternate > > superblock: > > e2fsck -b 8193 <device> > > > > I have tried everything I can think of and I can't seem to do an fsck or > > repair the file system. > > > > what can I do? > > > > Thanks > > Rick > > > > > More info: > > My array is made up of /dev/sda, sdb, sdc, and sdd. However they are > not mounted right now. My OS is booted off of /dev/sde. I am running > ubuntu 9.04 > > mdadm -Q --detail /dev/md0 > mdadm: md device /dev/md0 does not appear to be active. > > Where do I take if from here? I'm not up on this as much as I should be > at all. In fact I am quite a newbe to this... Any help would be greatly > appreciated. > > Thanks > Rick > Here is even more info: # mdadm --assemble --scan mdadm: /dev/md0 assembled from 2 drives - not enough to start the array. # mdadm --assemble /dev/sda /dev/sdb /dev/sdc /dev/sdd mdadm: cannot open device /dev/sdb: Device or resource busy mdadm: /dev/sdb has no superblock - assembly aborted Is my array toast? What can I do? Thanks Rick
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
