Errors booting Fedora Core 2 (System shutdown uncleanly)

Fudge150 · 08-07-2004, 04:40 PM

Hmm, where do i start...

When i shut down my system last, it crashed when closing the desktop (GNOME) and i had to manually reset the machine. Now when i come to boot the system (2.6.7 kernel-smp) it states that the system shut down 'uncleanly' and asks whether I want to do a disk integrity check.

If i say yes, it checks, repairs a few errors then reports a problem at about 80%. It fails and gives me results - 1.6% non-contig. It then drops me to a root shell, if i reboot from there i get the same thing next time i restart.

If i say no, it attempts to boot but hangs after a few mins. It tries to apply an IA32 Microcode update, and hangs during that.

As far as performing maintenance while in a root shell goes, i'm relatively new to linux (2 months) and don't know where to start.

I also cannot enter interactive startup.

I will reply posting the actual error messages i get ASAP (running a dual boot Linux/WinXP).

Please help me see Tux again

!

Jamie

btmiller · 08-07-2004, 04:46 PM

When you're in the root shell run fsck with no arguments on ther partition the boot is hanging up on. Chances are there's some error in that filesystem which fsck doesn't want to correct automatically, so it will ask you whether or not to fix it. Say yes unless you really know what you're doing.

Fudge150 · 08-07-2004, 05:08 PM

Wow that was a fast response! TY.

The entire thing that happens is:

Code:

 
The system was last shutdown uncleanly.
Press Y to check filesystem integrity...2 seconds......y
Checking root filesystem:

/1: Deleted inode 669020 has zero dtime. FIXED
/1: Inode 674954, i_blocks is 1736 should be 1720. FIXED
/1: Inode 674990, i_blocks is 240 should be 184. FIXED
/1: 243828/1026144 files (1.6% non-contiguous), 1477073/2048287 blocks 
                                                                                    [FAILED]

*** Error ocurred during integrity check, dropping to root shell for maintenance***
Enter root password: 

(Repair filesystem) 1#

I will reboot now and do what you suggested - perhaps the above will help?

Thanks, Jamie

Fudge150 · 08-07-2004, 05:30 PM

Just to add to the confusion, when i rebooted to run fsck the disk check completed successfully with no problems and the system proceeded to boot as if i skipped the check. This then takes in the problem with the microcode update thing i mentioned earlier.

Code:

Enabling swap space:                                                                                      [OK]
<6> IA-32 Microcode Update Driver: v1.14 <tigram@veritas.com>
microcode: No new microdata for cpu0
microcode: No new microdata for cpu1

This is where the system hangs, which then brings me back to square one again (lol).

I then rebooted to try what you suggested, the result was:

Code:

/1: Clean, 1477073/2048287 blocks

This really stumped me, any ideas?

Jamie

Fudge150 · 08-08-2004, 06:14 PM

Adding to the information, I forced the e2fsck utility to check even though it says clean.

The results simply showed that there were no problems - if so, why does the system still claim that it was last shutdown uncleanly (even after halting as normal from the shell)?

Does anyone know of the problem with the IA32 Microcode update - why does it hang then?

And above all, is there a way to force the system to boot as normal (with X) even though it shut down uncleanly? (Perhaps a GRUB command?)

Thanks,

Jamie

P.S - If no-one can shed any light on this matter, can someone suggest where else I should ask for assistance? (I'm going to post to the Fedora-specific forums)

gone15 · 08-09-2004, 06:54 AM

I have the same problem during load up it gets stuck at enabling swap space and it goes no where i even left it overnight to see if it was just taking too long i noticed that the person who posted before me had the same problem but it doesnt say anything on what to do so if someone could help me it would be appreciated???? Thanks I think this might be happening because my computer froze and i had to shutdown manually!!!

Fudge150 · 08-09-2004, 09:00 AM

Depends on what distribution you are using; I was using Fedora Core 2 which (apparently) has a bug causing this.

I managed to get in by changing the grub.conf file to boot from my old (2.6.6 kernel-smp) kernel. I still cannot get it to load under the latest 2.6.7 kernel.

As for the problems with enabling the swap space; the problem was not with that particular function, it was with the IA32 Microcode Update - a quirk of the 2.6.7 kernel-sm

If you aren't running FC2, it may well be worth creating a new thread - as the title of this one is FC specific.

What distro are you using?

gone15 · 08-09-2004, 12:36 PM

I am running Fedora Core 2 but it hasnt happened on my laptop i also have it on my laptop!!! How could you edit ur grub file if you cant even boot into the os

Fudge150 · 08-09-2004, 02:24 PM

Two ways:

When the system cannot boot properly it runs fsck. If that fails then you are dropped to a root shell. You can repair it from there.

The other method is to download a viewer/editor or a windows driver for ext2fs or ext3fs (google it). Then you can mount your linux filesystem in windows and edit its files. (This was my method.)

The second one only works if you are dual booting (which I am); if you directly migrated then i can't help you

masand · 08-09-2004, 03:54 PM

when u r dropped at the prompt fot maintaionence
thenuse
fsck-y /dev/hdax

x=root patition no.

and if that too does not works

fsck -f /dev/hdax

regards
gaurav