Hi I work on this harddrive for 3 days now ... I had noticed errors in kernel while working on a harddrive (120 gigas) but all continue to work fine (archives/directory).. So i have unmounted the driver and try e2fsck... bad ! e2fsck 1.34 (25-Jul-2003) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/hdc1 So i have tried to create 1 image of this drive with dd_rhelp and there are results : e2fsck 1.34 (25-Jul-2003) Group descriptors look bad... trying backup blocks... Superblock has a bad ext3 journal (inode 8). Clear<y>? yes *** ext3 journal has been deleted - filesystem is now ext2 only *** /hdd1/hdc1.os was not cleanly unmounted, check forced. Pass 1: Checking inodes, blocks, and sizes Root inode is not a directory. Clear<y>? (...) I have tried with -b <num> but with same result When i re-create then filesystem (with -S) and e2fsck i have all files in lost+found (all with <number>, not one file with his real name) So some questions : - There are no way to recover with filename ? - Where are stored files name / directory's name ? - why, where i try another superblocks i got same results ? My last chance are to wait the replacement harddrive, and copy it with DD But i'm affraid to got same results... I don't need to recover all files, but the maximum with names (even if files are not in real directory) And last question, there are not backup of journal stored like superblocks? I mean backup stored on harddrive ? Excuse me for my poor english :) Nota : harddrive are a very low count of badblocks, but the actual badblock seem to be on a very bad place ...
On Wed, 3 Mar 2004 23:24:33 +0100 "bill root" <pasdebill at hotmail.com> wrote:> e2fsck 1.34 (25-Jul-2003) > Group descriptors look bad... trying backup blocks... > Superblock has a bad ext3 journal (inode 8). > Clear<y>? yesI managed to reach that same point in completely unrelated way ... somehow irqs went foobar on my box and i did sysrq s u b ... after which my root fs was toasted. obviously some garbage was synced on the drive and all that fsck managed was to rescue a couple of files and put about 1/10 into lost+found. Most of the data was in digital heaven ... Luckily i have separate /usr /home /var partitions :) kernel 2.6.1 and fsck 1.34 -- Jure Pe?ar
Hi, On Wed, 2004-03-03 at 22:24, bill root wrote:> e2fsck 1.34 (25-Jul-2003) > Group descriptors look bad... trying backup blocks... > Superblock has a bad ext3 journal (inode 8). > Root inode is not a directory. Clear<y>?Bad news --- looks like the start of the inode table has been stomped on.> When i re-create then filesystem (with -S) and e2fsck i have all files in > lost+found (all with <number>, not one file with his real name) > > So some questions : > - There are no way to recover with filename ?No, if the directories are lost then there is no way to recover filenames.> - Where are stored files name / directory's name ?In the parent directory. There is absolutely no record of the filename in the file itself --- there can't be, because when you have hard links, it is possible to have many names for the same inode.> - why, where i try another superblocks i got same results ?Because the superblocks don't hold any directory information, they just contain the overall description of the filesystem such as how large it is, the block size etc.> And last question, there are not backup of journal stored like superblocks? > I mean backup stored on harddrive ?The journal is a dynamic data structure being updated all the time; the data in it is only valid for a very short time. Having a long term backup of the journal contents just doesn't have any value. (Backing up the journal metadata --- where the journal is --- would make sense, though.) But ultimately, everything in the journal eventually makes it back to disk, so losing the journal shouldn't be a complete disaster for the fs (that's why fsck could still work after nuking the journal and converting to ext2.) Cheers, Stephen