Here is the Message: ---snip--- There was an Exception received during the install that is outside of the normal install errors. (...) BootloaderError :FATAL: _map_device_to_grub_device: ERROR, could not map/dev/ide/c0d0 to anything in the device map. (...) ---snap---
Created attachment 99328 [details] used install profile
Created attachment 99329 [details] Error log
After this error I tried the following: <code> # mount /dev/ida/c0d0p3 /mnt/gentoo # mount none -t proc /mnt/gentoo/proc/ # chroot /mnt/gentoo /bin/bash # env-update livecd portage # env-update !!! Invalid PORTDIR_OVERLAY (not a dir): /root/catalyst/overlays/portage >>> Regenerating /etc/ld.so.cache... # . /etc/profile # grub grub> root ( </code> when pressing tab grub returns me an new line instead of listing possible devices: <code> grub> root ( </code> looks like grub cannot handle the device
Unfortunately, none of the devs has this hardware readily available to do any testing.
Which Compaq array controller, exactly? I might be able to get access to one for testing.
I have made another test with same installer selections exept that I chosed lilo for booting. The error was the same. I think every controller that uses devicenames like /dev/ida/c0d0 would produce the error. This is the controller: 0000:01:00.0 Unknown mass storage controller: Compaq Computer Corporation Smart-2/P RAID Controller (rev 03) Subsystem: Compaq Computer Corporation Smart-2SL Array Controller Flags: bus master, medium devsel, latency 0, IRQ 10 I/O ports at 7000 [size=256] Memory at 44000000 (32-bit, non-prefetchable) [size=256] Memory at 48000000 (32-bit, prefetchable) [size=128M]
(In reply to comment #5) > Which Compaq array controller, exactly? > > I might be able to get access to one for testing. > I have an older Proliant 1600R laying around here - just try to remember me to test 2007.0 pre-release stuff on that box.
Hrm, solution for this bug (at least for grub, haven't tested lilo on my box) is quite easy: If grub is to be installed on /dev/ida/* devices there needs to be a /boot/grub/device.map like this: (hd0) /dev/ida/c0d0
(In reply to comment #8) > Hrm, solution for this bug (at least for grub, haven't tested lilo on my box) > is quite easy: > > If grub is to be installed on /dev/ida/* devices there needs to be a > /boot/grub/device.map like this: > > (hd0) /dev/ida/c0d0 Currently, the installer depends on grub to generate a proper device.map. If grub doesn't see it, the installer doesn't either.
*** This bug has been marked as a duplicate of 148071 ***
