Comment 13 for bug 610898
Revision history for this message
| bcbc (bcbc) wrote Re: "No such device" - grub-pc update renders computer unbootable | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
@Erick, it might...
But note, even if you did select /dev/sda (which is what the affected users did) it would have absolutely no impact - provided you installed wubi on the same partition as windows (as per my Follow Up comments in the bug description).
You can check this by:
1. looking for /host/wubildr (if it exists go ahead with the test with confidence that nothing should happen)
2. repeat the dpkg-reconfigure and select /dev/sda and press Forward
3. After completion, run bootinfoscript and check your MBR
There is no risk because you can backup and replace the MBR if need be (and bootinfoscript will show you what's in there) before rebooting - or just use lilo (that's what I did). But I think you'll find that it had no affect. That's what the lupin override does to grub on wubi.
It's the same as running grub-install /dev/sda - no affect on wubi (when it's installed on same partition as windows).
However, if you ran grub-install.real /dev/sda that would pooch the MBR.
I think the main thing is this: a typical wubi user has no knowledge of Ubuntu or linux. They probably don't know what an MBR or a bootloader. And when it says select where to install grub-pc: /dev/sda - it is frankly meaningless to them. After all, no one asked them to make this decision when they installed Wubi! So why do it now? My opinion is that grub-pc should be smarter - there's evidence everywhere that it's wubi (/ mounted on root.disk for instance), so why present anything at all?
PS I took your advice and did some lucid iso testing.