Mon 10 May 2010 02:10:21 AM UTC, comment #4:
No problem on the infos, glad I could help.
However, what do you mean by your comment? I was using the latest release of GRUB 2, 1.98. I didn't do any "ugrading" to resolve my issue, I just did some "heavy" detective work.
In my opinion, there is still a bug floating around somewhere. It was either fixed by the Ubuntu folks and never pushed back upstream, or pushed back upstream and not made its way to the Debian folks (which is odd seeing as how Debian is closer upstream from Ubuntu than the GRUB 2 project would be, but heh, what do I know).
|
Sun 02 May 2010 09:16:10 AM UTC, comment #2:
I resolved this issue by Installing Ubuntu 10.04. I had read success stories from Ubuntu later than 9.04, and figured I would give it a shot. I compared the output of grub-install with the --debug flag on Ubuntu to that of Debian. On Ubuntu, the command:
/usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=partmap --device /dev/mapper/nvidia_befjcfje1
returned:
partmap_module=part_msdos
On Debian, it did not return part_msdos. I then added "part_msdos" to the listing passed in via --modules, and it worked perfectly.
|
Sun 02 May 2010 05:36:20 AM UTC, original submission:
I am unable to get GRUB 2 to boot successfully on my Debian Squeeze installation. The debian-installer had issues and could not install properly, but that isn't the real issue.
I tried adding raid.mod and dm_nv.mod to core.img, using update-grub-install (and subsequently Debian's update-grub script for grub.cfg) to no avail. Booting always drops to a rescue prompt with message "error: no such device: <UUID>". The UUID is not the UUID of any block device I have in my system, so I can only assume that it is correct and that of the device provided by dmraid (and there's no reason it shouldn't be). Running ls at the prompt shows three drives, (hd0), (hd1), and (fd0). Running ls (hd0) or (hd1) returns message "error: unknown filesystem", which makes sense, as the dmraid driver is supposed to know how to handle the RAID (which is RAID 0, by the way).
I've spoken with phcoder on IRC, who suggested I send in some data specific to my hardware; the first and last 512KB of each drive (in hopes of catching some structure from the hardware I assume).
I have done such, and you will find it attached. When setting up the RAID in the option ROM, I added the drive on port 3.0 before the drive on port 3.1, which I assume means that /dev/sda is on port 3.0 and /dev/sdb is on port 3.1. Again, this would make sense given the naming of the udev devices and how the drivers would logically work...
Please let me know if there is anything I can provide, be it images of the array or even help coding and debugging. I will gladly contribute to the project.
Thank you,
-Nate
|