Help! Boot problem after kernal update

[t3dluke]

Installed FC2 T2 Today via FTP and was very impressed. Then I ran the up2date wizard and followed the steps. Told it to update everything so the system would be up2date including the latest kernal. After the update the system will now not boot, I've included a screenshot showing where the boot process stops. It should also be noted that the old kernal version still appears in the grub bootloader. I'm a linux newbie so go easy on me here, but I really need some help with this!

[tchung]

Nice screenshot! :)

But sorry, I would not recommend Test Releases to Linux Newbie.

Have you already experienced Fedora Core 1 Stable Release?

Thomas

[t3dluke]

When I say I'm a newbie, I'm not that much of a newbie and I'm a very advanced windows user. I know how to install programs and stuff in linux but don't use it as a main OS, too many things it can't do yet. Anyway, anyone any useful advise?

[tchung]

Hope this help.

http://www.redhat.com/archives/fedora-test-list/2004-April/msg00624.html

Thomas

[t3dluke]

He Says:

Rename '/etc/security/selinux/policy.' as
'/etc/security/selinux/policy.16'

How do I do this?

[kel]

simply type;
mv /etc/security/selinux/policy etc/security/selinux/policy.16

[t3dluke]

And how do I even get to a command line to type this in even?

[kel]

Let's see, can you get grub to boot with the original kernel? If so, then boot up using the older kernel and then open a Terminal (Start->System Tools->Terminal). Then you can issue the mv (move) command...

The other post'r is correct, your policy (or lack thereof) is causing a kernel panic....

[t3dluke]

The strange thing is that the old kernal version is still showing in Grub, and no it doesn't boot, so I'm f**ked then...

[kel]

no, it's not done yet. There's always another approach...albeit more time consuming...

I'm assuming the older kernel also stops in the same place. It seems like the upgrade you've done applies the "selinux" stuff and without a cogent security policy the thing won't book (I know RedHat was dreading just this sort of thing...). What you can do, is boot from the install CD, choose the 'rescue' option at the first splash page (I can't recall the exact wording) and then you'll get a kernel booted off of the CD and a simple shell. You can use this shell to modify the HD, such as the 'mv' command outlined above.

Realistically though, if you've only just installed the box and then performed the automated update, it might be just as efficient to reinstall, leaving you in a predictable state with a working box.

I hate to use echo the pat phrases I often see snidely thrown at folks trying things for the first time, but using a test release of Fedora can be challenging and one should expect that things won't work cleanly. I've installed Fedora Core 1 on literally >100 machines and have been pleasantly suprised by the smooth install and stability of the resulting OS. And, if your goal is to learn about *nix by playing with FC, using FC1 is likely to give you a much more satisfying experience....

[t3dluke]

Like I said this ain't my main OS so I don't mind fidling with this to get it to work. Trying what you said now. Will post soon with results. Using HTTP install you see so waiting for stage2.img to download, good job I'm on broadband now...

[t3dluke]

right, just tried it and it says theres no such file or directory. Think I'll reinstall tomorrow without SELinux enabled. Am I right in thinking that without SELinux enabled this wouldn't have happened?

[kel]

That's my general understanding....

[Prometheus]

probably, i havent tried fc2 t2 yet cause of the se issues, theyre a mess right now.

Anyway, when you boot off the FC1 cd there are a couple options. If you hit F12 (i think) itll take you to the rescue meny, also you can type "linux rescue" and itll get you to the same place. From there you can remove the old kernel and replace it or compeletly delete the se linux stuff ( i dont know where it is or if you can even do it as i havent experimetned with it yet) Your best bet is prolly to reinstall though.... if you wanna dink around with it though "linux rescue" is the command to do it.

[LordMorgul]

I am a proponent of learning by getting your feet wet, however I believe you will learn much faster if you first use Linux in a stable state so that (for instance, moving files and/or recovering from minor issues) will be simple for you when you begin messing with beta versions. This development process is not 'smooth' in any sense of the word due to the accelerated target schedule. You should install and use FC1 long enough to familiarize yourself with unix permissions and common cli commands.

Certainly if you intend to continue with FC2T2 leave SELinux out of the picture until it is released with FC2.

[mars_hall]

I have installed Core2 Test2 with the SeLinux disabled from the firewall set up screen. Everything is working fine. You still see the SeLinux errors when upgrading or installing .rpm files, but the files are not prevented from installing. For me C2T2 has been running very smoothly :) I am quite happy with the progress from test 1 to test 2.

[ieatlint]

For future reference....
To get really any linux machine to boot to a command line when things go boom to certain things... simply add 'single' to the kernel paramaters.

This is accomplished at the grub boot prompt. Select your kernel to boot, press 'a' and type ' single' then press enter and viola, you're booting into single user mode. Red Hat/Fedora won't prompt for password, but just throw you out after the chroot as the super user.
Other distributions often prompt for root passwords, but let's face it: physical access is full access under any circumstance.