Actually, the only way I fixed this issue on my pc was to use LILO with the lba32 option, by creating an appropriate /etc/lilo.conf file(in this case, since on my pc there was also Opensuse, I edited the /etc/lilo.conf file created by Yast2 to make it work with Ubuntu's liloconfig, however it is more reccomended to follow the instructions on http://wiki.debian.org/LILO?highlight=%28LILO%29) and then running liloconfig. Furthermore, I also had to make new initrd image for the kernel with Yaird (http://wiki.debian.org/InitrdReplacementOptions), because the ones made by initramfs-tools didn't seem to work out of the box. Unfortunately, you have to use Yaird to create a new initrd image, edit /etc/lilo.conf and run liloconfig each time there is a kernel or modules update. of course, the easiest way to fix this problem is to update the BIOS, however if the mainboard is too old or if you use a laptop there is the risk not to have an update for the BIOS to introduce a 48-bit lba. The only solution I had to permanently solve this problem was to buy a second-hand pc with a bios with a 48-bit lba, with which I could use GRUB. I don't think, however, that buying a new pc is the right solution to this bug...
-- grub fails to boot on computers having a 28-bit lba and an hard disk larger than 128 GB https://bugs.launchpad.net/bugs/279307 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
