The problem was still there after upgrading to 16.04LTS.
I fixed it by first reinstalling the windows MBR, then reinstalling grub2-2.02.
Strange but solved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello,
As instructed, I disconnected the other drives, leaving the main harddrive and
the DVD-RW drive.
This did not had any effect: grub 2.02 showed the same error: error: disk
'hd0,msdos5' not found.
booting from a CD and restoring grub 2.00 (sudo dkpg -i grub* in the directory
where I keep a
** Attachment added: Grub output when setting debug to all
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1316068/+attachment/4109318/+files/IMG_20140510_165837.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
According to this, the faulty lines are in kern/disk.c, lines 196, 281
295
** Attachment added: Grub output after ls
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1316068/+attachment/4109325/+files/IMG_20140510_170007.jpg
--
You received this bug notification because you are a
The command sudo grub-probe -t drive /boot gives:
(hostdisk//dev/sda,msdos5)
with both versions 2.02~beta2-9 and 2.00-19ubuntu2.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316068
Title:
Hello,
The file parted_output.txt contains the output from the command sudo parted
-l.
** Attachment added: output from sudo parted -l
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1316068/+attachment/4108568/+files/parted_output.txt
--
You received this bug notification because you
Hello,
As asked, I have tried ls (hd1,msdos5)/ (with a 1 and not a zero for the
drive number), and grub answered error: disk 'hd0,msdos5' not found. (with a
zero, not a one).
Even the command reboot gives the same message, and no reboot. I have to use
the reset button.
--
You received this
Yes, I am sure.
To be 100% certain, I reinstalled grub 2.02~beta2-9, and tried the following
commands, as typed here after the * with no extra characters:
* ls
* ls -l
* lspci
* vbeinfo
* hello
* help
* functional_test
* all_functional_test
They _ALL_ answered by error: disk 'hd0,msdos5' not
ls, or wathever command at the grub command line prompt gives the same error:
error: disk 'hd0,msdos5' not found
instead of listing the available partitions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The motherboard is a MSI B74A-G43, model no MS-7758.
The hard drive hd0 is connected to the first SATA socket.
I have got the same Ubuntu on a eeePC (1005HA) withi no problem, but it
is a quite older hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
After upgrading the distribution, grub fails to boot any of the installed OSes.
Whatever the option selected in the grub menu, I get the same error message:
error: disk 'hd0,msdos5' not found.
Unfortunately, hd0,msdos5 is the partition where the root of the Xubuntu system
Three years after the original post, using now xubuntu 13.04 Raring and a SATA
only computer, I do not experience the issue anymore.
On my previous computer, I had a motherboard PATA interface, with the boot
disk, and a PCI to SATA card, with a second disk.
For this computer, sda and sdb tend to
Ridgeland,
Thanks for taking some time answering this.
In fact, as far as I remember, the stock grub.cfg uses UUID as well, so the
system boots, whatever the order of the drives.
Using UUID everywhere would not matter, except when I need to pass option via
the kernel boot options to the libata
I found that Bug #572086 is existing regarding the installer issue.
--
10.04RC system boot random assignment of sda, sdb
https://bugs.launchpad.net/bugs/569645
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I had the same issue, where the installer choose the wrong disk to write
grub2's MBR to.
I believe this is linked to Bug #569645: the system assign names to disk (sda,
sdb, etc) in a random order (to save boot time, as I understand). So sda is not
always the boot disk (as defined in the BIOS).
I forgot to mention that this issue is specific to lucid. Karmic was
well behaved.
--
upgrade karmic to lucid, grub was installed on wrong hd
https://bugs.launchpad.net/bugs/572086
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Same here. The system disk (should be sda) is connected to the motherboard IDE
port.
A secondary disk (should be sdb) is connected to a SATA controler on a PCI
card. I need to pass kernel options to libata, because the 80c cable is not
recognised, and the SATA controler is a VIA VT6421, to
17 matches
Mail list logo
