Bug#401396: 20061202 - daily build for sparc32 floppy install
Frans Pop <elendil@planet.nl> wrote:On Thursday 21 December 2006 03:03, Dan Oglesby wrote:
> Could you file one new installation report for the issue that you need
> to press enter 4 times to get the root floppy loaded so we can keep
> track of that? I think that is now the only issue remaining.
Let's investigate the issue below a bit further in this report, but I'd
still appreciate a new report for the issue above so we can reassign it
properly and don't have to wade through all the history in this one.
Done. I sent an email regarding the installation floppy switch issues a few minutes ago.
> The install completes on the SS5-70, but will not successfully
boot
> after install. It doesn't appear to load the esp module from the
> initfs, and cannot locate the root filesystem.
OK. Let's start with the basic questions:
- what are the last messages (10-15) on the console?
- do you get dropped into a debug shell on the failure?
- if so, please check:
- if the module is present in the initrd (ls /lib/modules/....)
- if the module is loaded (lsmod)
- if the module is listed in /etc/modules or in
/etc/initramfs-tools/modules or similar
- if the device is recognized at all (dmesg)
I'm confident the installation process is correct with regards to the module. I verified that the disk I had in the SS5-70 would in fact boot with no modifications in an SS5-170 and the SS20 systems I have at my disposal. All I did was move the drive between the systems, and power up. All systems booted to a prompt.
So, the SS5-70 system is not loading
the esp module during boot from the initfs for some reason. It does load and configure the esp module automatically during the installation process.
I have the console up with a failed boot on the SS5-70. On the systems that boot successfully (SS20 and SS5-170), I do see where the esp module is loaded and the output it generates when the drives and SCSI devices are detected. I do not see this output when I boot the SS5-70 system.
The only lines that appear to be error messages are the last four, which are:
VFS: Cannot open root device "sda2" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing; VFS: Unable to mount root fs on unknown-block(0,0)
<0>Press Stop-A (L1-A) to return to the boot prom
Pressing L1-A does nothing, and I am not dropped to a debug shell, or see an option at any time for a debug shell. The only way to reset the system is to power cycle
it at this point.
--Dan __________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Reply to: