Moritz Willers writes: > I assume this would be correct and my problem has moved on to biosdev?
It looks like it. One known issue here, though, is with CR 6437463. If you created your metadb on the same slice as you're trying to use for the root, lucreate will fail to make it bootable. It needs to be elsewhere. > biosdev: Could not match any!! > ERROR: Device mapping command </sbin/biosdev> failed. Please reboot > and try again. I've seen BIOS-related trouble here, but I've been unable to pin it down. On *some* platforms (particularly those with SATA), it seems that the BIOS will report an arbitrary subset of the attached drives. At least on my home system (Tyan 2885 motherboard), I was able to toy around with the boot priority lists in the BIOS menus until /sbin/biosdev reported my SATA drives as having valid BIOS ID numbers. I haven't tried to debug it since, but there does seem to be a problem of some sort here. > I haven't rebooted, yet. Not sure what purpose it could serve. > Booting of SATA disks. Not understanding much in that biosdev debug > output... which direction should I go now? File a bug. I _think_ this is a BIOS issue of some sort, but someone with the right skill set (and the time!) needs to get to the bottom of this. -- James Carlson, KISS Network <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
