GNU GRUB - Bugs: bug #8899, Failure to populate device.map for...
You are not allowed to post comments on this tracker with your current authentication level.
bug #8899: Failure to populate device.map for Compaq/HP Smart Array
Submitter: | Mark Seger <seger> | ||
Submitted: | Wed 12 May 2004 11:23:59 AM UTC | ||
Category: | Disk & Partition | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | Mark Seger |
Open/Closed: | Closed | Release: | None |
Release: | 0.93 | Reproducibility: | Every Time |
Planned Release: | None |
Sat 15 Dec 2007 12:50:59 PM UTC, comment #3: |
Robert Millan <robertmh> |
Wed 26 Jan 2005 06:02:51 PM UTC, comment #2: This also worked for me, with one exception. Entering (hd0) /dev/cciss/c0d0 in the devices.map did not work. What worked was to run "device (hd0) /dev/cciss/c0d0" at the grub prompt before running the two commands you gave. |
Anonymous |
Mon 26 Jul 2004 01:59:58 AM UTC, comment #1: Patch to allow grub to populate the devicemap with
|
Horms <horms> |
Wed 12 May 2004 11:23:59 AM UTC, original submission:
When requesting grub to populate a new device.map via --device-map=file (where file doesn't exist) or via grub-install --recheck, grub does not make any entries for SmartArray devices, specifically those with names such as /dev/cciss/c0d0. Rather, device.map is populated only with an entry for (fd0).
|
Mark Seger <seger> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2007-12-15 | robertmh | Open/Closed | Open | Closed | |
2004-07-26 | horms | Attached File | - | Added grub-cvs.200407260-cciss.patch, #1524 |
Powered by Savane 3.13-02a9.
Corresponding source code
We've moved to GRUB 2 as a development platform. Please can you check if this bug still applies there, and if it does, reopen it?
Thanks