First off, lemme tell you the initial problem. I had a WD ShareSpace that
had one of the disk go bad. They sent a replacement and it was suppose to
rebuild on its own, however after the build, the array went bad and it was
no longer able to see any of the files.
I downloaded and tested the drives using windows data recovery tools I saw
that the ext3 was Linux FS and that using these tools would not help in the
recovery. However through the tools I was able to see and recover some of
the files, but the files themselves were usable. I confirmed with WD that
ext3 was in fact the FS and took steps to recover the data. These are the
steps I took in order for me to assemble the raid.
Right now I have 3/4 drives with the data. I did #mdadm --assemble --scan,
which let me assemble the raid. However at this point I was not able to see
any of the files or mount the drive to the mount point it was once at. I
have also tried #mdadm --create with the array in the right order /w the
missing disk.
Initially the --assemble --scan assembled the array /dev/md2 with the disks
in the wrong order. I know because I physically saw where the disks were in
relation to the disk order and wrote down the disk order on every HD.
Here's everything I could find in terms of information that you asked for.
It's a lot.
#dmesg
[ 339.440187] raid5: device sdb4 operational as raid disk 1
[ 339.440189] raid5: device sdd4 operational as raid disk 3
[ 339.440192] raid5: device sdc4 operational as raid disk 2
[ 339.440610] raid5: allocated 4219kB for md2
[ 339.440612] raid5: raid level 5 set md2 active with 3 out of 4 devices,
algorithm 2
[ 339.440615] RAID5 conf printout:
[ 339.440617] --- rd:4 wd:3
[ 339.440619] disk 1, o:1, dev:sdb4
[ 339.440620] disk 2, o:1, dev:sdc4
[ 339.440622] disk 3, o:1, dev:sdd4
[ 339.440817] md2: unknown partition table
[ 538.840033] kjournald starting. Commit interval 5 seconds
[ 538.891844] EXT3 FS on md0, internal journal
130 more lines
I've contacted just about everyone that knows a thing about RAID5, but no
one is really able to help me. Anyhow I've read up a lot on RAID5 arrays
and
how to properly assemble them. However I've run into a problem with a NAS
system from WD that I just can't seem to figure out.
I have a ¾ disks in the array, 1 went down and is out of commission. I've
been able to assemble my array through mdadm using --assemble --scan.
However
I cannot access the array due to the fact that the array cannot read a
filesystem. Everytime I try to mount I get mount: wrong fs type
etc. I
know that the FS is an ext3 FS. However I cannot seem to get this
thing going. I was wondering if anyone could point me in the right
direction with this. I can't seem to find anyone that is capable of
solving this. I would appreciate any help. Thanks!
What's the output of 'cat /proc/mdstat' after you assemble the array?
And what exact error (and dmesg output) do you get when trying to mount
it as ext3?
Cheers,
Robin
--
___
( ' } | Robin Hill [off-list ref] |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html