[Bug 257789] New: After this mornings update Kernel fails to boot with "waiting for device /dev/disk/by-id/ata-FUJITSU... to appear"
https://bugzilla.novell.com/show_bug.cgi?id=257789 Summary: After this mornings update Kernel fails to boot with "waiting for device /dev/disk/by-id/ata-FUJITSU... to appear" Product: openSUSE 10.3 Version: Alpha 2 Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: casualprogrammer@yahoo.com QAContact: qa@suse.de BugsThisDependsOn: 257340 +++ This bug was initially created as a copy of Bug #257340 +++ On an FSC Amilo Si1520 with openSuSE 10.3 alpha2plus, after updating to Kernel 2.6.21-rc4-git5-3-default the system is left unbootable :-( After correcting the boot device ( see bug 257340 ) the boot process is initiated, but stops again with: "waiting for device /dev/disk/by-id/ata-FUJITSU... to appear" After reverse updating to the old kernel and installing kernel 2.6.21-rc4-git5-3-debug, booting seems to work fine for 2.6.21-rc4-git5-3-debug . Booting to 2.6.21-rc4-git5-3-default still not possible. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #1 from casualprogrammer@yahoo.com 2007-03-26 21:49 MST ------- Created an attachment (id=126598) --> (https://bugzilla.novell.com/attachment.cgi?id=126598&action=view) Screenshot of stalled boot process with 2.6.21-rc4-git5-3-default -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #2 from casualprogrammer@yahoo.com 2007-03-26 21:50 MST ------- Created an attachment (id=126599) --> (https://bugzilla.novell.com/attachment.cgi?id=126599&action=view) ls /dev/disk/by-id/ after booting to 2.6.21-rc4-git5-3-debug -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Blocker -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #3 from casualprogrammer@yahoo.com 2007-03-29 06:07 MST ------- After this mornings update ( kernel 2.6.21-rc5-2-default ) it seems to be resolved. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 Bug 257789 depends on bug 257340, which changed state. Bug 257340 Summary: After this mornings update Kernel fails to boot with Error 23 (Error while parsing number) https://bugzilla.novell.com/show_bug.cgi?id=257340 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #4 from gregkh@novell.com 2007-03-29 11:04 MST ------- thanks for letting us know, now closing out. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | Version|Alpha 2 |Alpha 2plus ------- Comment #5 from casualprogrammer@yahoo.com 2007-04-03 09:14 MST ------- Actually, after this mornings update it happened again :-( "Downdating" from the alpha2 DVD kernel, autofs and finally udev made the system bootable again. So I think udev needs to be looked after. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #6 from casualprogrammer@yahoo.com 2007-04-03 09:26 MST ------- After finally re-updating udev from 106-3-i586 to 108-2-i586 everything still works properly, puzzled. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #7 from casualprogrammer@yahoo.com 2007-04-05 00:59 MST ------- Now, this is puzzling. After booting to Windows XP it tells me that "new devices" have been found and installed, the computer needs to be restarted to make things effective. After that Windows XP worked smooth as always. Only on rebooting into openSuSE the error "waiting for device /dev/disk/by-id/ata-FUJITSU... to appear" is back in all its beauty. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #8 from casualprogrammer@yahoo.com 2007-04-05 02:45 MST ------- This time I just "downdated" udev to 106-3-i586 ( the DVD ) and everything works nicely again. Only Windows still thinks it has changed devices and requires one reboot. Not sure how to find out just which devices are affected, it only states: "Geänderte Systemeinstellungen", details see screenshot. There seems to be no adverse effect to openSuSE with the "old" udev, so I'm sticking with it for the time being. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #9 from casualprogrammer@yahoo.com 2007-04-05 02:46 MST ------- Created an attachment (id=129174) --> (https://bugzilla.novell.com/attachment.cgi?id=129174&action=view) Screenshot of Windows XP message box -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID ------- Comment #10 from casualprogrammer@yahoo.com 2007-04-06 01:46 MST ------- After having reset the BIOS firmware to factory settings, it now seems to work. Closing again. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Major Status|RESOLVED |REOPENED Component|Kernel |YaST2 Resolution|INVALID | ------- Comment #11 from casualprogrammer@yahoo.com 2007-04-09 15:45 MST ------- OK, now I got somewhat nearer. After this mornings update it happened again. I had to "downdate" kernel etc to alpha2 ( DVD) the it worked. After upgrading again it still worked. On compiling and booting to my own kernel, same problem again. Luckily enough I could still boot the default kernel. After some investigation I came across /boot/grub/menu.lst. It contains erroneous information on root= in title "test" and title "2.6.21-rc5-git13-2-default-200704091147" After changing "root=/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4" to "root=/dev/disk/by-id/ata-FUJITSU_MHV2080BH_NW78T662BLKF-part4" in title "test", line beginning with "kernel" I could boot without problem. Obviously, by "downdating" kernel or related package, the menu.lst got reset to proper content, thus misleading me to believe in relation to those packages. -----------------------------------/boot/grub/menu.lst------------------------- # Modified by YaST2. Last modification on Mon Apr 9 13:23:05 CEST 2007 default 2 timeout 8 ##YaST - generic_mbr gfxmenu (hd0,3)/boot/message ##YaST - activate title test root (hd0,3) kernel /boot/vmlinuz-2.6.21-rc5-git13-2-default-200704091147 root=/dev/disk/by-id/ata-FUJITSU_MHV2080_NW78T662BLKF-part4 vga=0x314 splash=silent showopts initrd /boot/initrd-2.6.21-rc5-git13-2-default-200704091147 title 2.6.21-rc5-git13-2-default-200704091147 root (hd0,3) kernel /boot/vmlinuz-2.6.21-rc5-git13-2-default-200704091147 root=/dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part4 vga=0x314 splash=silent showopts initrd /boot/initrd-2.6.21-rc5-git13-2-default-200704091147 ###Don't change this comment - YaST2 identifier: Original name: windows 1### title Windows XP - C rootnoverify (hd0,0) chainloader (hd0,0)+1 ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.3 root (hd0,3) kernel /boot/vmlinuz root=/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4 vga=0x314 splash=silent showopts initrd /boot/initrd ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 10.3 root (hd0,3) kernel /boot/vmlinuz root=/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3 initrd /boot/initrd title openSUSE 10.3 -- Kernel-2.6.21-rc5-git13-2 root (hd0,3) kernel /boot/vmlinuz-2.6.21-rc5-git13-2-bigsmp root=/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4 vga=0x314 splash=silent showopts initrd /boot/initrd-2.6.21-rc5-git13-2-bigsmp title Failsafe -- Kernel-2.6.21-rc5-git13-2 root (hd0,3) kernel /boot/vmlinuz-2.6.21-rc5-git13-2-bigsmp root=/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off initrd /boot/initrd-2.6.21-rc5-git13-2-bigsmp ###Don't change this comment - YaST2 identifier: Original name: windows 2### title Windows XP - D rootnoverify (hd0,0) chainloader (hd0,1)+1 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #12 from casualprogrammer@yahoo.com 2007-04-10 03:43 MST ------- Created an attachment (id=130008) --> (https://bugzilla.novell.com/attachment.cgi?id=130008&action=view) ls /dev/disk/by-id after booting to default kernel -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #13 from casualprogrammer@yahoo.com 2007-04-10 03:43 MST ------- Created an attachment (id=130009) --> (https://bugzilla.novell.com/attachment.cgi?id=130009&action=view) ls /dev/disk/by-id after booting to test kernel -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #14 from casualprogrammer@yahoo.com 2007-04-10 03:53 MST ------- As far as I understand the issue ( which is not very far ) the EDD gets the device name from the BIOS, where it is called "FUJITSU MHV2080BH", and puts it to /dev/disk/by-id. Peculiarly /dev/disk/by-id contains multiple entries for the same disk, some concatenating the trailing "H" or even the "B" from the BIOS name. As both variants contain entries with the full BIOS name (ata-FUJITSU_MHV2080BH_NW78T662BLKF-part4) these are probably the ones to be used for detection. Not sure why there should be others with modified names as well. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #15 from casualprogrammer@yahoo.com 2007-04-16 02:00 MST ------- Not sure whether this fits in: On compiling a kernel today with oldconfig ( no changes made ) make install runs through, but reports errors: make install sh /usr/src/linux-2.6.21-rc5-git13-2/arch/i386/boot/install.sh 2.6.21-rc5-git13-2-default-cjp070416 arch/i386/boot/bzImage System.map "/boot" Root device: /dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4 (mounted on / as ext3) Module list: processor thermal ahci ata_piix fan jbd ext3 edd (xennet xenblk) Kernel image: /boot/vmlinuz-2.6.21-rc5-git13-2-default-cjp070416 Initrd image: /boot/initrd-2.6.21-rc5-git13-2-default-cjp070416 Shared libs: lib/ld-2.5.so lib/libacl.so.1.1.0 lib/libattr.so.1.1.0 lib/libblkid.so.1.0 lib/libc-2.5.so lib/libcom_err.so.2.1 lib/libdl-2.5.so lib/libext2fs.so.2.4 lib/libhistory.so.5.2 lib/libncurses.so.5.6 lib/libpthread-2.5.so lib/libreadline.so.5.2 lib/librt-2.5.so lib/libutil-2.5.so lib/libuuid.so.1.2 lib/libvolume_id.so.0.75.0 lib/libnss_files-2.5.so lib/libnss_files.so.2 lib/libgcc_s.so.1 Driver modules: scsi_mod sd_mod processor thermal libata ahci ata_piix fan edd Filesystem modules: jbd mbcache ext3 Including: initramfs fsck.ext3 Bootsplash: SuSE (800x600) 32771 blocks sh: -c: line 0: syntax error near unexpected token `(' sh: -c: line 0: `udevinfo -q symlink -n =(hd0,3) 2>/dev/null' sh: -c: line 0: syntax error near unexpected token `(' sh: -c: line 0: `udevinfo -q symlink -n =(hd0,3) 2>/dev/null' sh: -c: line 0: syntax error near unexpected token `(' sh: -c: line 0: `udevinfo -q symlink -n =(hd0,3) 2>/dev/null' sh: -c: line 0: syntax error near unexpected token `(' sh: -c: line 0: `udevinfo -q symlink -n =(hd0,3) 2>/dev/null' /boot/grub/menu.lst contains two new entries: title root (/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4) kernel /boot/vmlinuz-2.6.21-rc5-git13-2-default-cjp070416 root=/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4 vga=0x314 splash=silent showopts initrd /boot/initrd-2.6.21-rc5-git13-2-default-cjp070416 title 2.6.21-rc5-git13-2-default-cjp070416 root (/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4) kernel /boot/vmlinuz-2.6.21-rc5-git13-2-default-cjp070416 root=/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4 vga=0x314 splash=silent showopts initrd /boot/initrd-2.6.21-rc5-git13-2-default-cjp070416 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #16 from casualprogrammer@yahoo.com 2007-04-17 03:55 MST ------- Created an attachment (id=131676) --> (https://bugzilla.novell.com/attachment.cgi?id=131676&action=view) menu.lst after updating today ( Kernel-2.6.21-rc6-git4-2 ) Menu.lst corrupted again while updating -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #17 from casualprogrammer@yahoo.com 2007-04-17 04:00 MST ------- ls /dev/disk/by-id ata-FUJITSU_MHV2080BH_NW78T662BLKF ata-FUJITSU_MHV2080BH_NW78T662BLKF-part1 ata-FUJITSU_MHV2080BH_NW78T662BLKF-part2 ata-FUJITSU_MHV2080BH_NW78T662BLKF-part3 ata-FUJITSU_MHV2080BH_NW78T662BLKF-part4 edd-int13_dev80 edd-int13_dev80-part1 edd-int13_dev80-part2 edd-int13_dev80-part3 edd-int13_dev80-part4 scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part1 scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part2 scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part3 scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part4 so the entry in menu.lst should either read root=/dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part4 or root=/dev/disk/by-id/ata-FUJITSU_MHV2080BH_NW78T662BLKF-part4 but not root=/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version|SuSE Other |openSUSE 10.3 Version|Alpha 2plus |Alpha 3 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |kernel-maintainers@forge.provo.novell.com ------- Comment #18 from casualprogrammer@yahoo.com 2007-04-17 04:06 MST ------- Is actually anybody taking care of this ? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 jeffm@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|kernel- |casualprogrammer@yahoo.com |maintainers@forge.provo.nove| |ll.com | ------- Comment #19 from jeffm@novell.com 2007-04-17 10:03 MST ------- Yes, we're looking at it. I was able to reproduce the root (/path/to/dev) on my 10.3 alpha machine, but after updating perl-Bootloader and running: /usr/lib/bootloader/bootloader_entry add <version> <kernel name> <initrd name> .. I got the correct entry. We checked in a change to the kernel today that forces the kernel package to depend on a newer perl-Bootloader. Can you try updating perl-Bootloader to 0.4.14 and then forcing a re-install of the kernel to check if the problem has been solved for you? Also, please don't change the bug state to NEEDINFO. That usually indicates that we're waiting for information from the reporter, not the other way around. When NEEDINFO appears as the state in our bug list, those bugs can get overlooked until the state is changed again. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #20 from casualprogrammer@yahoo.com 2007-04-17 10:32 MST ------- Thanks for replying. Actually I had perl-Bootloader to 0.4.14 when I released Comment #17, anyway, to make sure I updated both perl-Bootloader (0.4.14-4 i586)as well as kernel-default (2.6.21_rc6_git4-2 i586). Opening /boot/grub/menu.lst shows two new entries afterwards: --------------------------------------------------------------------------------- # Modified by YaST2. Last modification on Tue Apr 17 18:21:06 CEST 2007 default 7 timeout 8 ##YaST - generic_mbr gfxmenu (hd0,3)/boot/message ##YaST - activate title openSUSE 10.3 -- Kernel-2.6.21-rc6-git4-2 root (/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4) kernel /boot/vmlinuz-2.6.21-rc6-git4-2-default root=/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4 vga=0x314 splash=silent showopts initrd /boot/initrd-2.6.21-rc6-git4-2-default title Failsafe -- Kernel-2.6.21-rc6-git4-2 root (/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4) kernel /boot/vmlinuz-2.6.21-rc6-git4-2-default root=/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off initrd /boot/initrd-2.6.21-rc6-git4-2-default --------------------------------------------------------------------------------- both of which are wrong and will fail to boot. Also YaST Bootloader is not capable of fixing them, if I try I get: --------------------------------------------------------------------------------- # Modified by YaST2. Last modification on Tue Apr 17 18:30:18 CEST 2007 default 7 timeout 8 ##YaST - generic_mbr gfxmenu (hd0,3)/boot/message ##YaST - activate title openSUSE 10.3 -- Kernel-2.6.21-rc6-git4-2 kernel (/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4)/boot/vmlinuz-2.6.21-rc6-git4-2-default root=/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4 vga=0x314 splash=silent showopts initrd (/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4)/boot/initrd-2.6.21-rc6-git4-2-default title Failsafe -- Kernel-2.6.21-rc6-git4-2 kernel (/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4)/boot/vmlinuz-2.6.21-rc6-git4-2-default root=/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off initrd (/dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-part4)/boot/initrd-2.6.21-rc6-git4-2-default --------------------------------------------------------------------------------- -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 casualprogrammer@yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|casualprogrammer@yahoo.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #21 from casualprogrammer@yahoo.com 2007-04-17 10:44 MST ------- Maybe there should be some kind of warning after installing a new kernel, that it won't hurt to check /boot/grub/menu.lst manually BEFORE rebooting. Saves a lot of trouble. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #22 from casualprogrammer@yahoo.com 2007-04-17 11:27 MST ------- Now this is interesting: While booting to entry: ------------------------------------------------------------------------- title openSUSE 10.3 -- Kernel-2.6.21-rc6-git4-2 root (hd0,3) kernel /boot/vmlinuz-2.6.21-rc6-git4-2-default root=/dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part4 vga=0x314 splash=silent showopts initrd /boot/initrd-2.6.21-rc6-git4-2-default ------------------------------------------------------------------------- the boot process informs me, it can't mount partitions /dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part1 /dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part2 which are the NTFS partitions. Checking /etc/fstab revealed, that references to all disks were via /dev/disk/by-id/ata-FUJITSU_MHV2080B_NW78T662BLKF-partx This time, instead of setting /boot/grub/menu.lst to the "ata-" values, I set /etc/fstab to the "scsi-SATA_" values On rebooting all partitions are mounted. Now I reinstalled both, perl-Bootloader as well as kernel-default once again and checked /boot/grub/menu.lst. This time the two new entries read: ------------------------------------------------------------------------- Modified by YaST2. Last modification on Tue Apr 17 18:30:18 CEST 2007 default 5 timeout 8 ##YaST - generic_mbr gfxmenu (hd0,3)/boot/message ##YaST - activate title openSUSE 10.3 -- Kernel-2.6.21-rc6-git4-2 root (hd0,3) kernel /boot/vmlinuz-2.6.21-rc6-git4-2-default root=/dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part4 vga=0x314 splash=silent showopts initrd /boot/initrd-2.6.21-rc6-git4-2-default title Failsafe -- Kernel-2.6.21-rc6-git4-2 root (hd0,3) kernel /boot/vmlinuz-2.6.21-rc6-git4-2-default root=/dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part4 vga=normal showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off initrd /boot/initrd-2.6.21-rc6-git4-2-default ------------------------------------------------------------------------- which is absolutely correct. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 jeffm@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |kasievers@novell.com ------- Comment #23 from jeffm@novell.com 2007-04-17 11:44 MST ------- Ok, so the perl-Bootloader portion of the bug is fixed. I'm curious as to why you get different values for ata- and scsi_SATA. On my system, the suffix is the same. Kay - Do you have any idea what's going on with this? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 kasievers@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|kasievers@novell.com | ------- Comment #24 from kasievers@novell.com 2007-04-17 11:57 MST ------- The SCSI-stack truncates the ata-vendor/product to the SCSI-defined limit of 8 and 16 chars. With the latest kernel, the data for the ata-link is retrieved by ata-passthrough, so they should be exactly the same strings as the /dev/hd* devices have returned. Note: For new installations, yast was changed to use scsi-*-links for /dev/s* devices, so the ata-*links will be used only for systems that get installed with ide-drivers and get updated at a later time. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #25 from casualprogrammer@yahoo.com 2007-04-17 12:20 MST ------- "Ok, so the perl-Bootloader portion of the bug is fixed" I don't think so, it should be able to handle the ata-* links as well as the scsi-SATA_* ones. Also there seems to be something wrong with YaST bootloader, if it can't cope with malformed entries in /boot/grub/menu.lst. This might be a bug in it's own right. "Note: For new installations, yast was changed to use scsi-*-links for /dev/s* devices, so the ata-*links will be used only for systems that get installed with ide-drivers and get updated at a later time." The latest installation from DVD was alpha2 and this set up fstab as well as menu.lst with ata-* values, although the only controller in the system is SATA. I still wonder why I seem to be the only one having this problem. If this is so, there might be something special about my hardware ?? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 ------- Comment #26 from casualprogrammer@yahoo.com 2007-04-25 05:18 MST ------- After a "clean" installation from the alpha3 DVD this does not occur, as /etc/fstab is set up with the scsi-SATA entries by default. I noticed though, that configuring the partitioning during install offers various options for setting up fstab. It should be made sure, that all of these settings result in proper setting up of /boot/grub/menu.lst as well as updating the system from an older version of SuSE. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #27 from gregkh@novell.com 2007-05-03 21:49 MST ------- closing due to the bug being fixed. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257789 Bug 257789 depends on bug 257340, which changed state. Bug 257340 Summary: After this mornings update Kernel fails to boot with Error 23 (Error while parsing number) https://bugzilla.novell.com/show_bug.cgi?id=257340 What |Old Value |New Value ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=257789 Bug 257789 depends on bug 257340, which changed state. Bug 257340 Summary: After this mornings update Kernel fails to boot with Error 23 (Error while parsing number) https://bugzilla.novell.com/show_bug.cgi?id=257340 What |Old Value |New Value ---------------------------------------------------------------------------- Status|REOPENED |NEW Status|NEW |ASSIGNED Status|ASSIGNED |RESOLVED Resolution| |FIXED -- 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.
participants (1)
-
bugzilla_noreply＠novell.com