stalled boot up process
Poole, John J
john.j.poole at usa-spaceops.com
Wed Feb 21 17:49:33 UTC 2007
Is is possible the disk is full?
John
-----Original Message-----
From: redhat-install-list-bounces at redhat.com
[mailto:redhat-install-list-bounces at redhat.com]On Behalf Of
redhat-install-list-request at redhat.com
Sent: Wednesday, February 21, 2007 12:01 PM
To: redhat-install-list at redhat.com
Subject: Redhat-install-list Digest, Vol 36, Issue 16
Send Redhat-install-list mailing list submissions to
redhat-install-list at redhat.com
To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/redhat-install-list
or, via email, send a message with subject or body 'help' to
redhat-install-list-request at redhat.com
You can reach the person managing the list at
redhat-install-list-owner at redhat.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Redhat-install-list digest..."
Today's Topics:
1. Re: stalled boot up process (Rick Stevens)
2. Re: YUM Errors !! (Micros50)
----------------------------------------------------------------------
Message: 1
Date: Tue, 20 Feb 2007 14:07:27 -0800
From: Rick Stevens <rstevens at vitalstream.com>
Subject: Re: stalled boot up process
To: Getting started with Red Hat Linux
<redhat-install-list at redhat.com>
Message-ID: <1172009247.569.19.camel at prophead.corp.publichost.com>
Content-Type: text/plain
On Mon, 2007-02-19 at 21:54 -0800, daisy wrote:
> My Red Hat linux system stalled one day and wouldn't allow any
> keyboard input. We only use this machine as a web server and no one
> was using the machine at the time.
>
> We tried to reboot the machine but couldn't. The boot up process just
> stops The first time it stops at the following line,
>
> INIT: version 2.78 booting
>
>
> At the second and third attempt to boot, the set up process stopped
> at
>
> Setting hostname www.mycomputer.com
>
>
> The last time it stopped at the following (Pressing Y did not do
> anything. Boot up is still stalled.)
>
> Initializing USB Controller (usb-uhci)
> Your system appears to have shut down uncleanly
> Press Y within X seconds to force file system integrity check.
>
>
> As shown the boot up process stops at different points. Does anybody
> have any idea what the problem could be? Hardward? Software? I am
> sorry but I have no idea how to proceed, and would be grateful for any
> help.
The system seems to think that it got shut down by a power failure or
something of that nature. Try booting again, but when you see the
"Press Y" prompt, press "Y". The system will attempt to do an fsck on
your root drive (the one with the "/" filesystem). If it finds badness
on the drive, it will try to repair it, but be warned that you may lose
some data if it finds the disk corrupted.
If pressing "Y" doesn't work, verify that the keyboard is functional.
Press the CAPS LOCK key and verify that the LED lights up. If it
doesn't, then you may have a hardware problem. It could be a bad
keyboard, a bad motherboard, bad memory or a bad power supply. If the
keyboard works at the BIOS prompts and such, then I'd try to boot off
the first install CD and at the "boot:" prompt, enter "memtest86" to
test your memory.
If the memory passes the test, then I'd start looking at the power
supply. If you know how to use a multimeter, check the power levels.
You'd be amazed at how flakey a system can get with a bad power supply.
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer rstevens at vitalstream.com -
- VitalStream, Inc. http://www.vitalstream.com -
- -
- Cuteness can be overcome through sufficient bastardry -
- --Mark 'Kamikaze' Hughes -
----------------------------------------------------------------------
------------------------------
Message: 2
Date: Tue, 20 Feb 2007 18:39:28 -0500
From: Micros50 <micros50 at verizon.net>
Subject: Re: YUM Errors !!
To: Getting started with Red Hat Linux
<redhat-install-list at redhat.com>
Message-ID: <1172014768.17017.8.camel at manhattan.ruffe.edu>
Content-Type: text/plain
On Mon, 2007-02-19 at 09:44 -0800, Rick Stevens wrote:
> On Sat, 2007-02-17 at 17:11 -0500, mylar wrote:
> > Hello, I recently installed FC6 on my machine to replace an aging
> > version of FC1. Thus far everything has gone well and I am very pleased
> > with the performance of FC6 as well as it's many improvements over FC1.
> > Quite naturally I have been using yum to perform package updates as well
> > as to install additional packages that I need for my day to day work.
> >
> > That said I have recently run into a little problem when doing
> > installations and updates with yum. The installation or update works
> > fine, the proper packages get updated and/or installed but, I am also
> > getting a bunch of error messages spit out at the end of each run if
> > yum.
> >
> > The error message states:
> >
> > "db4 error(-30987) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested
> > page not found."
> > error:error:(-30897) getting "" records from Requireversion index".
> >
> > Okay, anyone know what this means. The package or update gets done fine
> > but this message gets spit out a dozen times or more. Someone told me
> > that the rpm database is probably corrupt and that I should run "rpm
> > --rebuilddb". Any ideas if this will work ??
>
> It can't hurt. Here's the commands (as root, of course):
>
> # cd /var/lib/rpm
> # rm -f __db*
> # rpm --rebuilddb
>
> That's two underscore characters before the "db" in the second command.
> In fact you may not want to use the "-f" option, but delete each file
> itself. There will be three or four of them, depending on how many
> updates you've done.
>
> Note that the rpm command will take a while to complete, so don't panic.
Hi Rick.. Thanks for the help. I did a
# rpm --rebuilddb
and that seemed to correct the problem. However, when i did it I forgot
to remove the "__db*" files. Should I have removed them first ?
Everything seems to be working fine now I can install or update via rpm
and yum, but I wonder if perhaps I should still do a
# rm -f __db*
# rpm --rebuilddb
or should I leave everything alone at this point since it is working ? I
am inclined to leave well enough alone at this point and go through the
3 steps in the event I experience such problems again.
mylar
------------------------------
_______________________________________________
Redhat-install-list mailing list
Redhat-install-list at redhat.com
https://www.redhat.com/mailman/listinfo/redhat-install-list
End of Redhat-install-list Digest, Vol 36, Issue 16
***************************************************
More information about the Redhat-install-list
mailing list