http://bugzilla.novell.com/show_bug.cgi?id=613873 http://bugzilla.novell.com/show_bug.cgi?id=613873#c2 Alex Müller changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzilla@go4more.de --- Comment #2 from Alex Müller 2010-06-16 15:18:45 UTC --- So it's not only my problem. Well, I'm annoyed by that, but at least I can with some luck cope with this problem. I wonder how somebody without Linux experience reacts to this problem. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613873 http://bugzilla.novell.com/show_bug.cgi?id=613873#c4 Alex Müller changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bugzilla@go4more.de | --- Comment #4 from Alex Müller 2010-06-21 14:09:12 UTC --- yast2-bootloader talks about "master boot record" without informing me whether the SATA or the PATA harddisk is supposed to be the one containing this master boot record. And, as you said, because the SATA/PATA mix is problematic, in different situations the master boot record can be interpreted to be on SATA or on PATA, without the user knowing about that?! So IMHO: - If YaST itself cannot discern the correct harddisk by itseld, it should give me enough information to do the right config myself (e.g. by adding the "/dev/disk-by-id" or, maybe more human-readable, the capacity information and/or the filesystem used on this disk). - YaST should at least warn during an installation that the SATA/PATA mix can cause problems and the proposed config should therefore be thoroughly checked. - YaST could warn about a valid Windows bootsector being overwritten by grub. Especially during updates, as it is extremely unlikely that on a running system grub will have to overwrite a Windows bootsector in this scenario! - YaST could have an option to leave certain drives untouched. Don't know if these are good and/or feasible workarounds :-/- -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613873 http://bugzilla.novell.com/show_bug.cgi?id=613873#c6 --- Comment #6 from Alex Müller 2010-06-30 18:42:12 UTC --- Judging from comment #3 I would say it's a know problem that grub/yast2-bootloader can (and will) mess up PATA/SATA-environments. As I just had once again to re-setup all that inhumane grub/bootloader-stuff when installing the current RC, I'd like to push this problem up. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613873 http://bugzilla.novell.com/show_bug.cgi?id=613873#c8 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bugzilla@go4more.de --- Comment #8 from Jozef Uhliarik 2010-07-01 08:34:42 UTC --- Please attach y2logs.If you're in doubt follow:http://en.opensuse.org/Bugs/YaST Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613873 http://bugzilla.novell.com/show_bug.cgi?id=613873#c10 Alex Müller changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bugzilla@go4more.de | --- Comment #10 from Alex Müller 2010-07-01 15:51:38 UTC --- @Jiri: I agree that disk-by-id is probably not the best way, you're right. As you said, you could discern the disks by model, size, filesystems or so. Or even "SATA 0" or "PATA, primary master" or so. The disk partitioner also gives you sufficient information about the harddisks you are going to mess around with. When fiddling with the boot sector, the same rules should apply. And, especially when updating a running system, YaST should pull the brakes if grub suddenly wants to install itself in an Other-OS bootsector, as then something is obviously completely wrong. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=613873 http://bugzilla.novell.com/show_bug.cgi?id=613873#c12 --- Comment #12 from Alex Müller 2010-07-02 12:51:39 UTC --- Created an attachment (id=373502) --> (http://bugzilla.novell.com/attachment.cgi?id=373502) y2logs Here the y2logs of the working system. Please note that this should not contain the bootloader config as determined by YaST2, but the corrected config. -- Configure bugmail: http://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=613873 https://bugzilla.novell.com/show_bug.cgi?id=613873#c Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|juhliarik@novell.com |jreidinger@novell.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.

https://bugzilla.novell.com/show_bug.cgi?id=613873 https://bugzilla.novell.com/show_bug.cgi?id=613873#c15 Alex Müller changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |FIXED --- Comment #15 from Alex Müller 2012-12-03 15:21:27 UTC --- I'll close this bug as there seems to be no activity in fixing it, and I cannot contribute anymore because of a nowadays SATA-only setup. -- 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.