Photorec Recovery

Using PhotoRec to recover lost data
Post Reply
Message
Author
john410312
Posts: 5
Joined: 19 Jan 2017, 19:42

Photorec Recovery

#1 Post by john410312 » 20 Jan 2017, 20:05

I've a Raid 5 that I can't mount do to missing ext4

Code: Select all

john@nasmedia:~$ sudo mount -a
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

john@nasmedia:~$ dmesg | tail
[  616.187924] EXT4-fs (md0): VFS: Can't find ext4 filesystem
Could or should I attempt using Photorec first to see what I can pull off before attempting to fix the filesystem? Should I use Photorec on the raid (md0) as a whole or the individual drives?

Sponsored links

User avatar
cgrenier
Site Admin
Posts: 3562
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Photorec Recovery

#2 Post by cgrenier » 20 Jan 2017, 21:02

What is the results of TestDisk, /dev/md0, None, Advanced, Superblock ?
What is the output of "sudo fsck.ext4 -p /dev/md0" ?

john410312
Posts: 5
Joined: 19 Jan 2017, 19:42

Re: Photorec Recovery

#3 Post by john410312 » 21 Jan 2017, 20:45

Testdisk, dev/md0, None, Advanced, Type, ext4, Superblock gives me...

Code: Select all

TestDisk 6.14, Data Recovery Utility, July 2013
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org

Disk /dev/md0 - 9001 GB / 8383 GiB - CHS 2197600128 2 4

     Partition                  Start        End    Size in sectors

>[  Quit  ]
or did I do something wrong?

Code: Select all

john@nasmedia:~$ sudo fsck.ext4 -p /dev/md0
fsck.ext4: Bad magic number in super-block while trying to open /dev/md0
/dev/md0: 
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
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>
 or
    e2fsck -b 32768 <device>
For the record...

Code: Select all

john@nasmedia:~$ sudo mke2fs -n /dev/md0
mke2fs 1.42.9 (4-Feb-2014)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=128 blocks, Stripe width=384 blocks
274702336 inodes, 2197600128 blocks
109880006 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
67066 block groups
32768 blocks per group, 32768 fragments per group
4096 inodes per group
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
	102400000, 214990848, 512000000, 550731776, 644972544, 1934917632

john@nasmedia:~$ sudo e2fsck -b 32768 /dev/md0
e2fsck 1.42.9 (4-Feb-2014)
e2fsck: Bad magic number in super-block while trying to open /dev/md0

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
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>
 or
    e2fsck -b 32768 <device>

and returns same for every one.

john410312
Posts: 5
Joined: 19 Jan 2017, 19:42

Re: Photorec Recovery

#4 Post by john410312 » 14 Feb 2017, 23:05

bump

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests