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

Re: Can't rescue, read-only filesystem



on Mon, Mar 19, 2001 at 01:47:55PM -0800, Morgan Fletcher (morgan@hahaha.org) wrote:
> kmself@ix.netcom.com writes:
> > Boot a standalone floppy or CDR GNU/Linux system and examine your HD.
> > I'd recommend Tom's Root Boot if you're running a 2.1.x kernel (TRB
> > doesn't handle some instances of 2.2.x ext2 filesystems), or the
> > LinuxCare Bootable Business Card (BBC), which uses a 2.2.x kernel.
> > 
> > I suspect HD damage, which may prevent you from accessing your HD and/or
> > a Linux kernel located on it.
> 
> Wouldn't HD damage affect execution before the reboot? System has been
> up all through the weekend, and I had rebooted and gone through LILO
> four days ago. 
> 
> I think it has something to do with the way the rescue disk is
> starting the system. Not sure, however.
> 
> The boot sequence goes quite a way, until it gets to loading this
> module. I'm inclined to think the disk is OK.

If you're unable to boot the system from onboard images, booting from an
external image is recommended.  Simple fact is that if you cannot boot
the system you have no way of determining whether or not the HD is
trashed or not.

Boot a rescue disk (again, BBS, TRB, or similar), and sniff around.

-- 
Karsten M. Self <kmself@ix.netcom.com>    http://kmself.home.netcom.com/
 What part of "Gestalt" don't you understand?       There is no K5 cabal
  http://gestalt-system.sourceforge.net/         http://www.kuro5hin.org

Attachment: pgpAm0s18KooS.pgp
Description: PGP signature


Reply to: