[wplug] can't boot my red hat 8.0 box to the new kernel

[Vanco, Donald]

The concept of partitioning labels exists to make systems resilient to the
insertion of other devices on the bus that might alter device names.

It's a concept that mainly holds true on SCSI systems where, (ferinstance)
if for some reason, your primary hard drive is ID3 and you insert a new
device at ID2 the "bump" in devices (e.g. /dev/sd<whatever>) won't screw up
an fstab based on "raw device" partitions as opposed to a label that is
"free to roam". An applied "label" of "/boot" is more fixed than the concept
of a device node that can change by altering the hardware profile.

Hope that makes sense.

Don

-----Original Message-----
From: Teodorski, Chris
To: 'wplug at wplug.org'
Sent: 3/11/03 3:59 PM
Subject: RE: [wplug] can't boot my red hat 8.0 box to the new kernel

I seem to have solved this by changing the

kernel /vmlinuz-2.4.18-26.8.0 ro root=LABEL=/

to

kernel /vmlinuz-2.4.18-26.8.0 ro root=/dev/hda5

someone smarter than me will have to explain why this worked.......I was
just trying different things.....I don't understand what the "=LABEL=/"
means


-----Original Message-----
From: Vanco, Donald [mailto:VANCOD at pios.com]
Sent: Tuesday, March 11, 2003 3:27 PM
To: ''wplug at wplug.org' '
Subject: RE: [wplug] can't boot my red hat 8.0 box to the new kernel


Go to /var/spool/up2date and look for the kernel rpm (it may not be
there if
up2date cleaned up after itself)

if there, run:
rpm -ivh "kernel-rpm-name" --force

DO NOT use -F as this will remove your functional kernel.


I suggest re-installing the kernel as "something is wrong" (to overstate
the
obvious) and I have not had up2date botch a kernel upgrade for me.


If that fails, look at the bootloader config file and edit accordingly
(provided you can figure out how - I suggest gedit if you've got gnome
installed).  I'd be curious to learn what OS you loaded first, and what
options you gave on partitioning (remove parts, initialize disk label,
etc).

FWIW - you may want to run:
up2date --configure

...and set it to
1) NOT upgrade kernels (voided, of course, if you check to install them
anyway - which I generally don't do unless there's a major issue with
the
kernel on my system)
2) NOT remove the rpms after install / upgrade - but keep in mind there
will
be lots of trash left in /var/spool/up2date


Opinion:
Too many Linux users have Windows Fever.  Upgrade only when required.
Every
one of my boxes sit behind a corporate firewall, and unless the update
in
question is a functionality fix (and so few of them are) I tend to wait
on
updates.  YMMV.

Don

-----Original Message-----
From: Teodorski, Chris
To: 'wplug at wplug.org'
Sent: 3/10/03 1:28 PM
Subject: [wplug] can't boot my red hat 8.0 box to the new kernel

Please be gentle.....I'm still a newbie.


I ran RedHat 8.0's Up2date today....and grabbed all updates which
included a kernel update (2.4.18-26.8.0)......the new kernel was an
available option in Grub after reboot.....but when I try to boot I get
the following message:

VFS: Cannot open root device "LABEL=/" or 00:00
Please append a correct "root=" boot option
Kernel panic VFS: Unable to mount root fs on 00:00

I can still boot to the original kernel (2.4.18-14)......I'm totally
lost as to what I need to do here.....some additional pertinant
information.....this box is dual booting between RH8.0 and winXP......

Thanks so much for the help....I hope I have provided enough
information....


_______________________________________________
wplug mailing list
wplug at wplug.org
http://www.wplug.org/mailman/listinfo/wplug
_______________________________________________
wplug mailing list
wplug at wplug.org
http://www.wplug.org/mailman/listinfo/wplug
_______________________________________________
wplug mailing list
wplug at wplug.org
http://www.wplug.org/mailman/listinfo/wplug