GNU GRUB - Bugs: bug #8900, grub-install cannot handle...
You are not allowed to post comments on this tracker with your current authentication level.
bug #8900: grub-install cannot handle Compaq/HP SmartArrays and SystemConfigurator
Submitter: | Mark Seger <seger> | ||
Submitted: | Wed 12 May 2004 11:43:41 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:51:15 PM UTC, comment #1: |
Robert Millan <robertmh> |
Wed 12 May 2004 11:43:41 AM UTC, original submission:
I'm told that the disk naming convention of ...discX/partY is common to multiple linux environments and that's why SystemConfigurator uses it even though RedHat (where I'm running) doesn't. When using SmartArray controllers, disks therefore get named something like /dev/cciss/disc0/part1 and the parsing of this fails in the convert() function, where the variable tmp_part is being determined. It's only looking for strings start contain disk/partX and this fails because there is no disk number. I've implemented a patch that remaps devices from that format back to /dev/cciss/c0d0 which in fact is what's stored in device.map. I've entered a previous bug in which I cannot allow grub to generate its own device map because it comes up without disks in it.
|
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-05-12 | seger | Attached File | - | Added grub-install, #1293 |
Powered by Savane 3.13-caa5.
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