Bug 16471 - /boot makes for a difficult booting
Summary: /boot makes for a difficult booting
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Erik Troan
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-08-17 20:50 UTC by Michal Jaegermann
Modified: 2008-05-01 15:37 UTC (History)
0 users

Clone Of:
Last Closed: 2000-08-22 19:31:44 UTC

Attachments (Terms of Use)
commented listing of /boot after an upgrade (1.48 KB, text/plain)
2000-08-17 20:52 UTC, Michal Jaegermann
no flags Details
Could not verify problem above (see steps enclosed) (4.08 KB, text/plain)
2000-08-18 15:43 UTC, Brock Organ
no flags Details

Description Michal Jaegermann 2000-08-17 20:50:43 UTC
Running an upgrade to create Pinstripe2 leaves /boot directory in an
"interesting" state.  In particular new initrd images are not created
which makes rather hard to restart a machine with a SCSI controller (a
disk driver is loaded as a module).  Booting from a floppy, if there
is one, luckily still works but newbies will be very confused.

(This particular installation boots via GRUB and none of locations
for lilo proposed by an installer is acceptable for different reasons).

Directory /boot includes, among other things, links created in
an installation and leading nowhere and superflous files.
I attach a listing of a resulting /boot with explanatory comments.
See also #15701 (less detailed and not about upgrades).


Comment 1 Michal Jaegermann 2000-08-17 20:52:21 UTC
Created attachment 2617 [details]
commented listing of /boot after an upgrade

Comment 2 Michael Fulbright 2000-08-17 22:34:01 UTC
Brock need to verify this asap on a SCSI system.

Comment 3 Michal Jaegermann 2000-08-17 22:55:59 UTC
This is probably irrelevant, but I should add that the system in question
has one IDE and one SCSI drive with no Linux at all on IDE (so it does not
figure anywhere in an installation/upgrade).

Comment 4 Brock Organ 2000-08-18 15:42:19 UTC
hmmm ... I could not reproduce this behavior ... :(

Do the steps results outlined in the attachment follow your steps ...?

Comment 5 Brock Organ 2000-08-18 15:43:44 UTC
Created attachment 2657 [details]
Could not verify problem above (see steps enclosed)

Comment 6 Michal Jaegermann 2000-08-18 20:55:41 UTC
A resulting /boot was not from SMP machine and an effect of an upgrade from
Pinstripe to RC1 (only minor kernel version changed as opposed to major).
But see also #15701 where /boot was also not really clean and a result
of an installation from scratch.  Note, in particular, a 'module-info'
link to nowhere.

A newly created boot floppy was correct but if that step would be skipped
for whatever reason (a machine without floppy, for example) then booting
it would be entertaining.

Comment 7 Erik Troan 2000-08-22 15:50:09 UTC
Have you tried an upgrade from 6.2 to RC[1|2]? We can't reproduce this at all.

Note You need to log in before you can comment on or make changes to this bug.