![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=419550
User t-o-m@gmx.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=419550#c2
--- Comment #2 from Tom Tom
Please attach y2logs. If you are in doubt follow:
http://en.opensuse.org/Bugs/YaST
Thanks!
Hello Cyril! Unfortunately I have no y2logs, since I deleted this installation right after. But as I found a workarround in the mean time, I think I know where the problem is located. Here is the work arround: 1. Install openSUSE 11 with the option to install grub on /boot, but NOT the bootloader anywhere. Installation completes without any errors, and System starts as usual into runlevel 5. 2. Reboot the system with "SystemRescueCD 1.0.x" or newer which is found at www.sysresccd.org. This CD comes with a patched version of GRUB legacy (0.97), which supports GPT disklabels. 3. Copy the grub files of this CD to /boot (but keep the existing menu.lst) 4. Tell Grub to use /boot as it's root 5. Install the bootloader with GRUB Finished- now the /boot partition has the patched grub files from the CD and a bootloader so that the system is ready to boot as usual. CONCLUSION: The only problem is, that the GRUB version shipped with openSUSE 11 is a version, that is NOT capable of handling GPT disklabels, but only the 20-year old and obsolete MBR. But only GPT-labeled disks are capable of adressing disks or partitions larger then 2 Terrabyte. Since I have a RAID with 12 disks 1 TB each, and the RAID controller exports this array as a 12 Terrabyte harddisk to the system, I am forced to use GPT! SUGGESTION: Can't you issue a patched version of GRUB 0.97 and distribute it via YAST-online-update (YOU) to us? Best regards, Tom -- 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.