https://bugzilla.novell.com/show_bug.cgi?id=325552#c20
--- Comment #20 from Thomas Fehr 2007-09-19 03:47:26 MST ---
As I already said, it could also be an initrd issue. This should be decidable
by looking into /proc/partition from emergency shell after failed boot.
If partitions are present in /proc/partitions it could be an udev issue or a
broken initrd.
Could be also other drivers being loaded in initrd as were loaded during
installation.
y2logmkinitrd contains the following:
Kernel image: /boot/vmlinuz-2.6.22.5-16-bigsmp
Initrd image: /boot/initrd-2.6.22.5-16-bigsmp
Root device: /dev/disk/by-id/scsi-SATA_WDC_WD800JB-00CWD-WCA8E6665404-part5
(/dev/sda5) (mounted on / as ext3)
Kernel Modules: processor thermal scsi_mod libata pata_sis fan jbd mbcache ext3
edd sd_mod usbcore ohci-hcd uhci-hcd ehci-hcd ff-memless hid usbhid
Features: block usb resume.userspace resume.kernel
Bootsplash: SuSE (1280x1024)
17880 blocks
ERROR: Bootloader::Library::SetLoaderType: Initializing for unknown bootloader
ERROR: Bootloader::Core::ListFiles: Running generic function, it should never
be called
ERROR: Bootloader::Core::ParseLines: Running generic function, it should never
be called
No idea if the lines starting with ERROR (that are normally not there) have
anything to do with this problem.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.