Re: fixing a corrupt /dev/hdar .. debugfs assistance...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for the help.
 
Does <2> refer to a superblock?  I.e.:
 
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616
 
The debugfs man page says the first arg of "clri" refers to a "file"?
 
Thanks,
 
Chris
On 3/20/06, Theodore Ts'o <tytso@xxxxxxx> wrote:
On Mon, Mar 20, 2006 at 04:27:22PM -0700, Chris Worley wrote:
> I used ddrescue to copy /dev/md1 to a disk of sufficient size, and
> re-ran e2fsck, and still get the error message that there's no root
> file system (I've tried most every superblock):

Using debugfs, copy out the the contents of "root inode"; since it
might contain useful data, e2fsck didn't want to delete it out of
hand.

debugfs: dump <2> /tmp/contents-of-inode-2

Then purge the inode away:

debugfs: clri <2>

Then run e2fsck, and it will create a new root directory for you.

Hope this helps!

                                               - Ted

_______________________________________________

Ext3-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ext3-users

[Index of Archives]         [Linux RAID]     [Kernel Development]     [Red Hat Install]     [Video 4 Linux]     [Postgresql]     [Fedora]     [Gimp]     [Yosemite News]

  Powered by Linux