Fedora Core 9

Wed Aug 13 21:56:30 UTC 2008

I did as Patrick describe (I think). When I rebooted I no longer get a 
beeping sound, instead I get a continuous stream of text, repeating the 
word grub over and over again. I did a diff on my boot directory and the
backup boot directory, and they are identical.

I am not sure where to go now. I was thinking it was a problem with grub, 
since that is where it stalls when booting. Has anybody run into a similar
problem and found a solution? Why did this occur after updating packages? 
That seems to suggest there is something wrong with one of the new updates?

After the update finished, it asked be to reboot, which I did, and have
done many time before. Then this happened?

Jim

--- On Wed, 8/13/08, Aaron Konstam <akonstam at sbcglobal.net> wrote:

> From: Aaron Konstam <akonstam at sbcglobal.net>
> Subject: Re: Fedora Core 9
> To: jmpmcmanus at yahoo.com, "For users of Fedora" <fedora-list at redhat.com>
> Date: Wednesday, August 13, 2008, 5:31 PM
> On Wed, 2008-08-13 at 13:05 -0700, James McManus wrote:
> > --- On Wed, 8/13/08, Patrick Kaiser
> <patrick at argonius.de> wrote:
> > 
> > > From: Patrick Kaiser <patrick at argonius.de>
> > > Subject: Re: Fedora Core 9
> > > To: jmpmcmanus at yahoo.com, "For users of
> Fedora" <fedora-list at redhat.com>
> > > Date: Wednesday, August 13, 2008, 2:35 PM
> > > On Wed, Aug 13, 2008 at 10:50:58AM -0700, James
> McManus
> > > wrote:
> > > > --- On Wed, 8/13/08, Steve Searle
> > > <steve at stevesearle.com> wrote:
> > > > 
> > > > > From: Steve Searle
> <steve at stevesearle.com>
> > > > > Subject: Re: Fedora Core 9
> > > > > To: jmpmcmanus at yahoo.com, "For
> users of
> > > Fedora" <fedora-list at redhat.com>>
> > > Date: Wednesday, August 13, 2008, 12:41 PM
> > > > > Around 05:24pm on Wednesday, August 13,
> 2008 (UK
> > > time),
> > > > > James McManus scrawled:
> > > > > 
> > > > > > issues, related to the upgrade. 
> However,
> > > today I did
> > > > > an additional
> > > > > > upgrade of 7 packages including
> the kernal.
> > > When I
> > > > > rebooted my system,
> > > > > > it got to grub and then began
> beeping, and
> > > stalled out
> > > > > there.  I have
> > > > > > attempting to use the rescue OS,
> but need to
> > > find more
> > > > > information on
> > > > > > this problem. I suspect it has
> something to
> > > do with
> > > > > the new kernal. Is
> > > > > > anybody familiar with this
> problem?  
> > > > > 
> > > > > No.  But what happens if you select the
> previous
> > > kernel in
> > > > > the grub
> > > > > menu?
> > > > > 
> > > > > Steve
> > > > > 
> > > > > -- 
> > > > > 
> > > > > A:  Because it messes up the order in
> which
> > > people normally
> > > > > read text.
> > > > > Q:  Why is top-posting a bad thing?
> > > > > 
> > > > >  17:39:54 up 5 days,  3:42,  2 users, 
> load
> > > average: 0.00,
> > > > > 0.28, 0.84
> > > > 
> > > > Steve,
> > > > 
> > > > I do not get the grub menu. It stalls out
> just before.
> > > Because of this, I'm now thinking there may
> be a problem
> > > with my boot partition.  I rebooted using the
> rescue disk,
> > > and did a df -k to get information on my
> filesystems. A
> > > shorthand version of the output was:
> > > > 
> > > > Filesystem                          Mounted
> on
> > > > /dev                                /dev
> > > > /dev/loop0                         
> /mnt/runtime
> > > > /dev/mapper/VolGroup00-logVol00    
> /mnt/sysimage
> > > > /dev/sda1                          
> /mnt/sysimage/boot
> > > > /dev                               
> /mnt/sysimage/dev
> > > > 
> > > > from this /dev/sda1 appears to be my boot
> filesystem. 
> > > > 
> > > > I'm thinking, performing a fsck on the
> boot
> > > partition, may help
> > > > me find out what the problem is. However,
> when I run
> > > the following
> > > > command:
> > > > 
> > > > fsck -n /dev/sda1
> > > > 
> > > > I get these warnings:
> > > > 
> > > > WARNING! /dev/sda1 is mounted
> > > > WARNING: couldn't open /etc/fstab
> > > > 
> > > > What is the correct way to check my boot
> partition and
> > > 
> > > > possibly correct it?
> > > > 
> > > > Thanks
> > > > Jim
> > > > 
> > > > -- 
> > > > fedora-list mailing list
> > > > fedora-list at redhat.com
> > > > To unsubscribe:
> > >
> https://www.redhat.com/mailman/listinfo/fedora-list
> > > > 
> > > 
> > > Dear Jim,
> > > 
> > > maybe you shoud mount all the old partitions and
> chroot
> > > into them to get
> > > this working (so fdisk finds the right fstab)
> > > 
> > > Hope this helps.
> > > 
> > > Regards, Patrick
> > > 
> > > -- 
> > > 
> > > Patrick Kaiser
> > > 
> > > URL: http://argonius.de
> > > EMail: patrick.kaiser at argonius.de
> > > RIPE: PK3264-RIPE
> > 
> > Patrick,
> > 
> > The old partitions are already mounted. I used chroot,
> as you suggested, 
> > to change root to the (OLD) main partition. The path
> to fstab is now
> > /etc/fstab. When I run:
> > 
> > fsck -n LABEL=/boot
> > 
> > It gives me a warning that the filesystem is mounted,
> then tells me that
> > it is skipping journal recovery because doing a
> read-only filesystem 
> > check, and then finally it tells me /boot is clean and
> give me the # of
> > file and blocks.
> > 
> > In the past I have always use shutdown with the -F
> option to scan my 
> > disk, so I am unfamilier with fsck. Because of this I
> want to be very 
> > careful using this command. I am not sure the problem
> is with /boot, 
> > and do not want to create a bigger problem by using
> fsck. Is this the 
> > output I should expect? should I unmount /boot before
> running the 
> > command?
> > 
> > Jim
> > 
> You can not fsck a partition that is mounted so you would
> have to umount
> the /dev/sda1/boot partition when you boot through the
> rescue disk.
> --
> =======================================================================
> It is all right to hold a conversation, but you should let
> go of it now
> and then. -- Richard Armour
> =======================================================================
> Aaron Konstam telephone: (210) 656-0355 e-mail:
> akonstam at sbcglobal.net