https://bugzilla.novell.com/show_bug.cgi?id=398360
User ckm@vienenbox.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=398360#c18
--- Comment #18 from Carsten Koch-Mauthe
There's only one 150GB Samsung disk and it was never hda. At least not when 10.3 was installed. My guess is that Carsten did upgrade his 75GB disk (that was indeed hda) at some point and the grub device.map was left unchanged. Sorry, I see no way to track this kind of disk change.
I've upgraded the harddisk 2 Years or so ago but this PC is a Laptop, so how should the interface change from hdx to sdx with changing to a greater Harddisk ? There is only one harddisk interface. I think already the first installed Suse Version was 10.0 or maybe older and the kernel of this version has used hdx instead of sdx.
yast2-bootloader _might_ have noticed the invalid device.map, though. Maybe it could give a warning or such.
Maybe creating a new one with the actual parameters ? Why touching the Windows Sections in menu.lst at all in case of upgrade ??? -- 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.