Mount a RAID-0 array

[lolo_]

Hi!

New to Linux! *wooh*
Backstory: my D-Link DNS-323 "crashed" (aka, one day it decided that it didn't want to read the RAID-setup in the box anymore and prompted me with "format disks! now!"... made me so sad) :'(
The D-Link is running a Linux filesystem (ext2 I believe), so while there's still data on the disk (tried to use diskinternals Raid Recovery tools for Windows which confirmed that there's files to recover but it kept freezing so I gave it up) I can't access it or save anything from it (since D-Link is Hitler and I'm Poland)...

I've plugged the disk into my desktop PC and installed Ubuntu (hopping for a way to fix it).
I can see the disk as a RAID-0 Array in the disk utility, I can also run benchmarks on it but I can't mount it...
It gives me this error message when I try to mount it:
Error mounting: mount: wrong fs type, bad option, bad superblock on /dev/md0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Could someone please help me or direct me in the right direction?
Would appreciate any help I could get!

Cheers
Lolo!

[zombykillah]

Hi,
fist a old joke:
You know what the 0 means in Raid 0?
That's the amount of data you will be able to recover after it fails.


Well ...
First you should create a backup.
You can use "dd"
Like:
dd if=/dev/sda > /media/sdc1/sda.dd.img
dd if=/dev/sdb > /media/sdc1/sdb.dd.img

Note:
The resulting files will have the size of the drives.
sda, sdb are meant to be the drives with the raid installed
sdc1 is meant to be a usb hdd or a different local drive.
As you copy all data of the drive ... that will take some time.

After that done you can start trying get the data back.

Since you found data with windows tools, your d-link must have used a MS filesystem, like FAT
Widows tools usually aren't able to read ext1, ext2, ext3, ext4, ReiserFs, xfs, ...

Well according to d-link forum it uses ext2
Print Page - DNS-323 Volume missing

So you should check for a ext2 fs:
fsck - Wikipedia, the free encyclopedia
=> e2fsck /dev/md0
e2fsck(: check ext2/ext3 file system - Linux man page

[lolo_]

Hi,
fist a old joke:
You know what the 0 means in Raid 0?
That's the amount of data you will be able to recover after it fails.

Haha! Good one

Yep it's Ext2, just saw it in the disk utility.
Also I get this error message when trying to mount it:
An error occurred while performning an operation on "3.0 TB Filesystem" (Whole-disk volume on 3.0 TB RAID-0 Array): Filesystem driver not installed.

[zombykillah]

e2fsck is meant to run when the drive ain't mounted.

It looks for errors in the file system.
"e2fsck -p" will try to repair it.

[lolo_]

oh! sorry for being a dumb blonde! :P
but how will I direct the e2fsck to run on the raid?
the device name is /dev/md0 but I get a premission denied when trying to run;
/dev/md0 e2fsck -p

... I'm doing it wrong! :'(

[zombykillah]

cmon, you aren't serious *gg*

e2fsck -p /dev/md0

Hope that works.

[lolo_]

cmon, you aren't serious *gg*

e2fsck -p /dev/md0

Hope that works.

Haha, well... I'm new to this! Be kind! ;D

Got to this point:
root@Hugo:~# e2fsck /dev/md0
e2fsck 1.41.12 (17-May-2010)
e2fsck: Group descriptors look bad... trying backup blocks...
/dev/md0 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 3360961 has EXTENTS_FL flag set on filesystem without extents support.
Clear<y>? yes

What's up with that? EXTENTS_FL flag set on filesystem without extents support?

(Hugo - yes I'm a LOST fan) ;P

[zombykillah]

Don't have any experience with ext2.
I usually use 3 or 4
I took a look at the basic tool man:
fsck(: check/repair file system - Linux man page

Here what happens when you add the option ext2 filesystem:
fsck.ext2(: check ext2/ext3 file system - Linux man page

So it is the right command ... for ext2 and ext3 filesystems

I hope that the problem isn't simpler as thought ...
Maybe it's just the order of the hdd in the raid.