[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #29739] GRUB 2 on nVidia MCP55 [10de:037f] fakeraid

From: Nathan Schulte
Subject: [bug #29739] GRUB 2 on nVidia MCP55 [10de:037f] fakeraid
Date: Sun, 02 May 2010 05:36:20 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/ Safari/532.5


                 Summary: GRUB 2 on nVidia MCP55 [10de:037f] fakeraid
                 Project: GNU GRUB
            Submitted by: reklipz
            Submitted on: Sun 02 May 2010 05:36:20 AM GMT
                Category: Booting
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 1.98
         Reproducibility: Every Time
         Planned Release: None



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

Thank you,


File Attachments:

Date: Sun 02 May 2010 05:36:20 AM GMT  Name: imgs.tar.bz2  Size: 218kB   By:



Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]