bin/163943: bsdinstall fails to detect CD device when booting with some media devices

Garrett Cooper yanegomi at
Mon Jan 9 07:30:13 UTC 2012

>Number:         163943
>Category:       bin
>Synopsis:       bsdinstall fails to detect CD device when booting with some media devices
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jan 09 07:30:11 UTC 2012
>Originator:     Garrett Cooper
>Release:        9.0-RELEASE
iXsystems, Inc.
FreeBSD freebsd-release.local 9.0-RELEASE FreeBSD 9.0-RELEASE #0: True Jan  3 07:46:30 UTC 2012    root at  amd64
I started reinstalling 9.0-RELEASE on a handful of test boxes at iXsystems, and the problem I've run into is that /dev/iso9660/FREEBSD_INSTALL doesn't exist as the IPMI-provided virtual CD drive (/dev/cd1) isn't attached to the system yet.

If I use ? at the panic screen and wait long enough, eventually the device and the label will appear, but not until then.

That being said I've also seen the issue with a handful of physical media drives as well with earlier 9.0 BETAs and RCs.

This issue no doubt also will occur with some USB media, given past experience with sysinstall.
1. Get access to the IPMI controller on a Supermicro box that's x86_64 capable.
2. Mount the 9.0-RELEASE-amd64 image via the virtual media manager.
3. Boot from the virtual CD drive.
There are a couple ways to either resolve or work around this issue.

1. Set to 20 seconds on the install media. This should quickly hack around the problem.

2. Rewrite the installer to instead bootstrap from an mfsroot, like sysinstall, then 'pivot' the root over to the CD, USB, etc media once it becomes available (a dumb while loop with a timeout should suffice). A detection mechanism for PXE booters should probably be added as a special case as I'm sure someday someone will hack the 9.0+ media to PXE boot.

3. Some other ata/cam fix could probably be applied to fix the overall general case, but I'm not sure what the solution might be...


More information about the freebsd-bugs mailing list