Using Debian Live
There's really nothing Debian-Live specific to do. Just use the standard tools.
The documents at tldp.org are probably your best bet- there's probably
no changes in how to repair ext2/3 filesystems since sarge.
I don't know what the big picture is of what you are trying to
accomplish but if it was me, I'd mount with '-o ro', rsync or tar off
the important stuff, and reinstall.
Fsck can repair a lot of stuff but to me a corrupt root inode is
indication that there's probably been a lot of corruption and I
wouldn't even bother trying to fix the partition.
Oh, and before you trust this drive for your data again, make sure you
test every sector, e.g. mkfs.ext3 -j -c -c (it's destructive, so
don't skip ahead to this step!)
Tony
On 10/11/07, John Lauterbach <lauterba at bellsouth.net> wrote:
> You are right. My error. Things worked right after I rebooted from CD-ROM;
> maybe loose nut at wheel. Bad news was that I could not boot from hard
> drive because of a corrupt root inode as found by ext2fsck.
>
> This brings more opportunity. How do I fix this problem with Debian Live,
> OR are things so bad that I need to reformat hard drive again.
>
> I would be glad to write help pages for you, but I don't know what I am
> doing.
>
> John
>
>
> ----- Original Message -----
> From: "Tony Godshall" <togo at of.net>
> To: "John Lauterbach" <lauterba at bellsouth.net>
> Cc: <debian-live-devel at lists.alioth.debian.org>
> Sent: Thursday, October 11, 2007 12:56 PM
> Subject: Re: Using Debian Live
>
>
> > On 10/11/07, John Lauterbach <lauterba at bellsouth.net> wrote:
> >>
> >>
> >> To Whom It May Concern:
> >>
> >> There appears to be either a lack of pointers to information or the
> >> information needed to use Debian Live to help repair a system that will
> >> not
> >> boot on account of a repairable hard drive error. In particular, I would
> >> like to run fsck on /dev/hda1 (or whatever it is called under Debian
> >> Live).
> >> Attempts to do that as well as similar activities on existing hard drives
> >> seem to result in less than common error messages.
> >>
> >> Perhaps you can clarify the situation.
> >
> > Perhaps you can clarify the errors.
> >
> > I've had no such experiences.
>
>
--
Best Regards.
Please keep in touch.
Reply to: