strombrg at dcs.nac.uci.edu
Mon Dec 13 21:10:26 UTC 2004
I have nothing further to add at this time.
On Sun, 2004-12-12 at 19:21 -0800, Dan Stromberg wrote:
> On Mon, 2004-12-13 at 03:58 +0100, Alexander Dalloz wrote:
> > Am Mo, den 13.12.2004 schrieb Dan Stromberg um 3:44:
> > > I have an FC3 system, that was happy, but is now unhappy. This may be
> > > related to someone, who shall remain nameless, having shut off the power
> > > on it without doing an orderly shutdown. Then again, maybe it was
> > > because of a "yum -y update", because I put off rebooting for a while
> > > after that.
> > >
> > > Anyway, now when it tries to boot, I see:
> > >
> > > Red Hat nash version 4.1.18 starting
> > > Reading all physical volumes. This may take a while...
> > > Found volume group "VolGroup00" using metadata type lvm2
> > > 2 logical volume(s) in volume group "VolGroup00" now active
> > Booting without boot parameter "quiet" shows more?
> > > ...and that's it. I've left it there for over and hour, and it never
> > > gets past that.
> > >
> > > I booted off of an FC3 rescue cd, and found that I could mount the /boot
> > > partition, but I cannot mount the / partition. I ran various lvm
> > > commands that identified two lvm volumes on the system.
> > > fsck'ing /dev/hda2 (which is /) is getting me no where though - it just
> > > says "invalid argument".
> > No, you will have to check the filesystem of the LVM volume. It is
> > correct to boot with CD1 into rescue mode (or the rescue CD), then let
> > all what it finds be mounted only read-only. You have this choice. Then
> > fsck the LVM.
> > Alexander
> I was kind of thinking along those lines too, but when I boot up into
> the rescue CD and let it try to find my fedora install, it gets really
> confused. More specifically, it says:
> Searching for Fedora Core installations...
> 0% install exited abnormally -- received signal 15
> kernel panic - not syncing: Out of memory and no killable processes
> Additional information:
> If I remove "quiet" and add "single" to my boot options, I get:
> EXT3-fs: INFO: recovery required on readonly filesystem.
> EXT3-fs: write access will be enabled during recovery.
> kjournald starting. Commit interval 5 seconds
> EXT3-fs: dm-0: orphan cleanup on readonly fs
> ...and there it hangs.
> Also, I ran memtest86 on the box for a while (a little over an hour),
> and found no errors.
> > --
> > fedora-list mailing list
> > fedora-list at redhat.com
> > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
More information about the users