Speech For Grandparents 60th Anniversary

Recovering a corrupted hard disk (and its data)

Error mount: mount: wrong fs type, bad option, bad superblock on / dev/sdb1,

, missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try

       dmesg But in my case did not match any:

(also try

e2fsck-p / dev / device

)

sabayon alex #

fsck / dev/sdb1 fsck

from util-linux ng-2.18

e2fsck 1:41:12 (17-May-2010) The filesystem size (according to the superblock) is 116736000 block (i)

The physical size of the block device is 116735992 (i)

is likely that the superblock or the partition table is corrupt!

to Cancel? no

/ dev/sdb1 contains a file system con errori, controllo forzato.
Passo 1: Controllo di inode, blocco(i) e dimensioni
Passo 2: Analisi della struttura delle directory Passo 3: Controllo della connettività di directory
Pass 4: Controllo del numero dei riferimenti
Pass 5: Checking gruppo summary information

/dev/sdb1: 18170/29188096 files (35.3% non-contiguous), 62000359/116736000 blocks

Il secondo passo è quello delle imprecazioni.

Il terzo, invece, è una scelta: possiamo cercare di recuperare direttamente la partizione o cercare invece prima di recuperare i dati.
Procedendo con la massima cautela, andiamo prima a vedere se i nostri dati sono ancora accessibili in some way. Yes
use the fantastic debugfs , which also gives access to file system corruption, both in read / write mode, which for the most desperate cases readonly.

What I want to do is get my Music and My Pictures folder, so I will give this command
sabayon alex # debugfs-w / dev/sdb1 debugfs 1:41:12 (17-May-2010) debugfs: help
debugfs: ls
debugfs:

rdump Music / media/2E78ED3D78ED0485/Musica

Before help control the list of available commands, then with the ls structure folder on my hard drive; rdump recursively copies the files, music represents the folder to be copied, and the next address is obviously the target. If not groped with the-w-c.
And voila! You will recover your files seemingly inaccessible!
Once that is done you can / need to restore the correct file. If, as in my case, it is a problem superblock format you can avoid giving the command: mke2fs-S
/ dev/sdb1 which deals only restore the superblock, then there is a chance that your files remain intact! (We always talk about a file system type EXT ! )
If this does not work, you just need to restore the partition with mke2fs always, if you want an ext4 fs:

mkfs.ext4 / dev / device


Done?