Write error on RAW partition

How to use TestDisk to recover lost partition
Post Reply
Message
Author
serath
Posts: 3
Joined: 12 Oct 2012, 18:13

Write error on RAW partition

#1 Post by serath » 12 Oct 2012, 18:56

Hello,

I have a NAS (LG N2R1) with 2 HDs :
- 1 Tb Seagate
- 2 Tb Segate
They worked as individual disks.
I don't know why exactly (maybe power disconnection), the 2 TB disk can't be reablable anymore neither from Win7, nor Mac OS X (Mountain Lion).
With Ext2fsd, only one volume is seen as RAW instead of 3 ext3 partitions.

I ran Testdisk 6.14 under Win7, it finds 3 partitions :

Code: Select all

Analyse Disk /dev/sdb - 2000 GB / 1863 GiB - CHS 30400 255 63
Geometry from i386 MBR: head=255 sector=63
check_part_i386 failed for partition type FD
check_part_i386 failed for partition type FD
file_pread(5,1,buffer,3907024049(243200/254/48)) lseek err Invalid argument
file_pread(5,1,buffer,3907024063(243200/254/62)) lseek err Invalid argument
check_part_i386 failed for partition type FD
get_geometry_from_list_part_aux head=255 nbr=6
get_geometry_from_list_part_aux head=8 nbr=1
get_geometry_from_list_part_aux head=16 nbr=1
get_geometry_from_list_part_aux head=32 nbr=1
get_geometry_from_list_part_aux head=64 nbr=1
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=255 nbr=6
Current partition structure:
Invalid RAID superblock
 1 P Linux RAID               0   1  1  1216 254 63   19551042
 1 P Linux RAID               0   1  1  1216 254 63   19551042
Invalid RAID superblock
 2 P Linux RAID            1217   0  1  1248 254 63     514080
 2 P Linux RAID            1217   0  1  1248 254 63     514080
Invalid RAID superblock
 3 P Linux RAID            1249   0  1 243200 254 63 3886958880
 3 P Linux RAID            1249   0  1 243200 254 63 3886958880
No partition is bootable
As a result of the analysis, 3 primary partitions as expected.
But at this point, nothing happens when I type 'p' to parse the folders.

Code: Select all

Results
interface_load
Disk /dev/sdb - 2000 GB / 1863 GiB - CHS 30400 255 63 Thu Oct 11 20:48:21 2012
 1 P Linux RAID               0   1  1  1216 254 63   19551042
 2 P Linux RAID            1217   0  1  1248 254 63     514080
 3 P Linux RAID            1249   0  1 243200 254 63 3886958880
check_part_i386 failed for partition type FD
check_part_i386 failed for partition type FD
file_pread(5,1,buffer,3907024049(243200/254/48)) lseek err Invalid argument
file_pread(5,1,buffer,3907024063(243200/254/62)) lseek err Invalid argument
check_part_i386 failed for partition type FD
But when trying to write, I got an error :

Code: Select all

interface_write()
 1 P Linux RAID               0   1  1  1216 254 63   19551042
 2 P Linux RAID            1217   0  1  1248 254 63     514080
 3 P Linux RAID            1249   0  1 243200 254 63 3886958880
write!

write_mbr_i386: starting...
write_all_log_i386: starting...
No extended partition

Partition: Write error
There is no particulor error explanation, so I'm stuck here.
I ran Tesdisk as admin, and deactivated antivirus.

Do you know what mean those error ?
check_part_i386 failed for partition type FD
check_part_i386 failed for partition type FD
file_pread(5,1,buffer,3907024049(243200/254/48)) lseek err Invalid argument
file_pread(5,1,buffer,3907024063(243200/254/62)) lseek err Invalid argument
check_part_i386 failed for partition type FD


Have you an idea of why the soft cannot write ?
Or what can I do as next steps ?

Thanks for your help.

Sponsored links

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

Re: Write error on RAW partition

#2 Post by cgrenier » 13 Oct 2012, 17:44

The disks are configured as a Linux software RAID.
To access the data, run TestDisk, Advanced menu, change the type of the partition to Linux, List and if it works, copy your files
To repair the filesystems, boot from a Linux LiveCD, it should autodiscover the 3 raid volume. As root, run "fsck -a /dev/md0", "fsck -a /dev/md1", "fsck -a /dev/md2".
What are the results ?

serath
Posts: 3
Joined: 12 Oct 2012, 18:13

Re: Write error on RAW partition

#3 Post by serath » 15 Oct 2012, 19:41

Hi,

first of all, thanks for your response.
If I understand correctly, it's not a problem of partition, but of filesystem.

When using Advanced with Linux type, I can't parse the folders.

Then I've used Ubuntu LiveCD and run the fsck.

Code: Select all

ubuntu@ubuntu:~$ sudo fsck -a /dev/sdb1
fsck de util-linux 2.20.1
fsck.ext2: Numéro magique invalide dans le super-bloc lors de la tentative d'ouverture de /dev/sdb1
/dev/sdb1: 
Le superbloc n'a pu être lu ou ne contient pas un système de fichiers
ext2 correct. Si le périphérique est valide et qu'il contient réellement
un système de fichiers ext2 (et non pas de type swap, ufs ou autre),
alors le superbloc est corrompu, et vous pourriez tenter d'exécuter
e2fsck avec un autre superbloc :
    e2fsck -b 8193 <périphérique>

The magic number is invalid in the superblock when trying to open /dev/sdb1.
The superblock can't be read or don't contain a correct filesystem ext2. If the device is valid and really contain a filesystem ext. (and not swap, ufs, or other), so the superbloc is corrupted, and you could attempt to execute e2fsck with another superbloc.

(Sorry, I may have the french section).

On the 1tb disk, the one working, I know that it's configured as :
1. Linux ext3
2. Swap
3. Linux ext3

Is this something to try ?

serath
Posts: 3
Joined: 12 Oct 2012, 18:13

Re: Write error on RAW partition

#4 Post by serath » 15 Oct 2012, 21:49

I have read different methods to get the filesystem back (and the one on this website as well). It seems to be unlucky...

Running a mke2fs to determine the superblock backup on sdb1 :

Code: Select all

ubuntu@ubuntu:~$ sudo mke2fs -n /dev/sdb1
mke2fs 1.42 (29-Nov-2011)
Étiquette de système de fichiers=
Type de système d'exploitation : Linux
Taille de bloc=4096 (log=2)
Taille de fragment=4096 (log=2)
« Stride » = 0 blocs, « Stripe width » = 0 blocs
4890624 i-noeuds, 19551042 blocs
977552 blocs (5.00%) réservés pour le super utilisateur
Premier bloc de données=0
Nombre maximum de blocs du système de fichiers=4294967296
597 groupes de blocs
32768 blocs par groupe, 32768 fragments par groupe
8192 i-noeuds par groupe
Superblocs de secours stockés sur les blocs : 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424
Then, using e2fs

Code: Select all

ubuntu@ubuntu:~$ sudo e2fsck -p -b 1605633 /dev/sdb1
e2fsck: Argument invalide lors de la tentative d'ouverture de /dev/sdb1
/dev/sdb1: 
Le superbloc n'a pu être lu ou ne contient pas un système de fichiers
ext2 correct. Si le périphérique est valide et qu'il contient réellement
un système de fichiers ext2 (et non pas de type swap, ufs ou autre),
alors le superbloc est corrompu, et vous pourriez tenter d'exécuter
e2fsck avec un autre superbloc :
    e2fsck -b 8193 <périphérique>
With all superblocks.

Running a mount with sb=, it didn't find any filesystem...

Code: Select all

ubuntu@ubuntu:~$ sudo mount -o sb=655360 -t ext3 /dev/sdb1 /mnt
mount : mauvais type de système de fichiers, option erronée, superbloc
        erroné sur /dev/sdb1, page de code ou aide manquante, ou autre erreur
       Dans quelques cas certaines informations sont utiles dans syslog - essayez
       dmesg | tail  ou quelque chose du genre

Code: Select all

[ 2404.419577] EXT3-fs (sdb1): error: can't find ext3 filesystem on dev sdb1.
[ 2404.455651] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
[ 2404.606554] SQUASHFS error: Can't find a SQUASHFS superblock on sdb1
[ 2559.629237] EXT3-fs (sdb1): error: can't find ext3 filesystem on dev sdb1.
[ 2691.589775] EXT2-fs (sdb1): error: can't find an ext2 filesystem on dev sdb1.
[ 2840.653510] EXT3-fs (sdb1): error: can't find ext3 filesystem on dev sdb1
It sounds bad :( Am I missing somthing ?

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests