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).
Created attachment 2617 [details]
commented listing of /boot after an upgrade
Brock need to verify this asap on a SCSI system.
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).
hmmm ... I could not reproduce this behavior ... :(
Do the steps results outlined in the attachment follow your steps ...?
Created attachment 2657 [details]
Could not verify problem above (see steps enclosed)
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.
Have you tried an upgrade from 6.2 to RC[1|2]? We can't reproduce this at all.