Subject: kern/33728: Trouble with /dev/ld*
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <Christoph_Egger@gmx.de>
List: netbsd-bugs
Date: 06/14/2006 11:45:00
>Number: 33728
>Category: kern
>Synopsis: Trouble with /dev/ld*
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Jun 14 11:45:00 +0000 2006
>Originator: Christoph Egger
>Release: NetBSD 3.0
>Organization:
>Environment:
NetBSD 3.0 NetBSD 3.0 (GENERIC) #0: Mon Dec 19 01:04:02 UTC 2005 builds@works.netbsd.org:/home/builds/ab/netbsd-3-0-RELEASE/i386/200512182024Z-obj/home/builds/ab/netbsd-3-0-RELEASE/src/sys/arch/i386/compile/GENERIC i386
>Description:
I want to install a Xen Dom0. Following the instructions on the
NetBSD/Xen Howto I want to install the bootmanager GRUB.
grub-install /dev/rld0d says:
/dev/rld0d does not have any corresponding BIOS drive.
I created my own /grub/device.map and retried:
echo "(ld0) /dev/rld0d" >/grub/device.map
grub-install --no-floppy /dev/rld0d
/grub/device.map:1: error: Bad drive name
cmp: /tmp/grub-install.img.1336: No such file or directory
/grub/device.map:1: error: Bad drive name
cmp: /tmp/grub-install.img.1336: No such file or directory
/grub/device.map:1: error: Bad drive name
cmp: /tmp/grub-install.img.1336: No such file or directory
/grub/device.map:1: error: Bad drive name
cmp: /tmp/grub-install.img.1336: No such file or directory
/grub/device.map:1: error: Bad drive name
cmp: /tmp/grub-install.img.1336: No such file or directory
The file /grub/stage1 not read correctly.
Here the relevent snippet from the dmesg:
amr0 at pci2 dev 2 function 0: AMI RAID <MegaRAID SCSI 320-1>
amr0: interrupting at irq 11
amr0: firmware 1L37, BIOS G119, 64MB RAM
ld0 at amr0 unit 0: RAID 1, optimal
ld0: 136 GB, 17881 cyl, 255 head, 63 sec, 512 bytes/sect x 287272960 sectors
ld1 at amr0 unit 1: RAID 0, optimal
ld1: 136 GB, 17882 cyl, 255 head, 63 sec, 512 bytes/sect x 287275008 sectors
>How-To-Repeat:
>Fix:
Instead of reintroducing new disktypes you should make it
accessable as SCSI. The LSI RAID Controller has SCSI Disks, why should
they be accessed different?
Port the driver from OpenBSD, then the disks are accessable
as /dev/sd0a and /dev/sd1a
GRUB can deal with SCSI and the problem will go away.