[Bug 396564] Re: grub2 shows 'biosdisk read error', then boots
Hi FriDisch, If you have a physical FDD connected, as a workaround, try having a formatted floppy in the drive when you boot. -- grub2 shows 'biosdisk read error', then boots https://bugs.launchpad.net/bugs/396564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 396564] Re: grub2 shows 'biosdisk read error', then boots
Felix, Here are answers to the questions that you asked... Did you install GRUB 2 to a MBR of a different disk then /boot/grub is on? No, I have a RAID1 boot configuration with GRUB 2 installed to the MBR of both drives so that I can boot from either one. Check if `echo $prefix' or just `set' in GRUB's commandline shows prefix as a normal GRUB device (hdx,y)/boot/grub or as (UUID=abc123...)/boot/grub If it's UUID= it can happen that it still accesses the floppy device. When I check $prefix, it's set to (md0)/boot/grub. FWIW, I put about half of a dozen echo commands at the top of my grub.cfg file to determine if the error was a result of something in grub.cfg or not. I found that the error occurred before the echo commands were processed, so the problem doesn't seem to be related to the contents of grub.cfg. (Which doesn't necessarily rule out the possibility that it's related to finding grub.cfg in the first place...) Makes me wonder if this error isn't BIOS specific. The machine that I get the error on has AMI bios. I did a klean Karmic install on two different machines with Award bios and didn't see the error on either of them... -- grub2 shows 'biosdisk read error', then boots https://bugs.launchpad.net/bugs/396564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 396564] Re: grub2 shows 'biosdisk read error', then boots
I receive the same biosdisk read error displayed briefly before my grub menu is displayed. On my system, the error occurs right after grub does a seek to the floppy drive, after grub loads but before the menu is displayed. So thinking the seek and the error were related, I decided to test that theory. I found that if I have a formatted floppy in the floppy drive, I don't get the error. That leads me to believe that there's a problem with the processing of the search command in grub.cfg. My version of the command is: search --no-floppy --fs-uuid --set 387a3584-1f7f-470e-bb9b-89346e2edf22 I couldn't find any documentation on the search command in the grub wiki, but if the purpose of the search command is to identify all the bios devices and raid devices that later grub.cfg commands use to boot OS's, shouldn't --no-floppy prevent grub from looking at the floppy drive at all? The error is more of an annoyance than a problem as my system also continues on to boot from my raid1, but I'd be curious to know if others that are getting the error can work around by putting a floppy in the floppy drive... My grub version is: GNU GRUB 1.97~beta4 -- grub2 shows 'biosdisk read error', then boots https://bugs.launchpad.net/bugs/396564 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
