Bug 13547

Summary:	FreeBSD will not boot after installing to /wd3 when /wd2 is a CD/DVD-ROM
Product:	Base System	Reporter:	beholder <beholder>
Component:	i386	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description beholder 1999-09-02 22:50:01 UTC

OS will install fine, but not boot up when there is a CD-ROM *before* the
hard drive on a secondary IDE chain.  It dies on boot saying that it 
can't mount /dev/wd1 (which is a CD-ROM, not my secondary harddrive)

Fix: 

Put both Hard drives on the Primary IDE chain, and both CD-ROM's on the
secondary chain.  

PS: Had to buy a new chasis case to do this :~(
How-To-Repeat: Get 2 HDD's and 2 CD-ROM's (my config). Set up the primary IDE chain as
(1)HDD (2)CD-ROM, and the secondary chain as (1)HDD (2)CD-ROM.  Then
install BSD on the second hard drive /wd3

Comment 1 Sheldon Hearn 1999-09-03 07:00:32 UTC

On Thu, 02 Sep 1999 14:44:00 MST, beholder@unios.dhs.org wrote:

> Get 2 HDD's and 2 CD-ROM's (my config). Set up the primary IDE chain as
> (1)HDD (2)CD-ROM, and the secondary chain as (1)HDD (2)CD-ROM.  Then
> install BSD on the second hard drive /wd3

Are you sure the second drive is wd3? Is that what it says in the boot
probe messages?

Have a look at the loader(8) manual page. In the EXAMPLES section, it
offers something that might help you:

     Sets the disk unit of the root device to 2, and then boots. This
     would be needed in the case of a two IDE disks system, with the
     second IDE hard-wired to wd2 instead of wd1.

           set root_disk_unit=2
           boot /kernel

You might play around with root_disk_unit, after doing

	   set rootdev=wd2s1a

	or

	   set rootdev=wd3s1a

If you don't come right, make sure you show us your kernel config. :-)

Later,
Sheldon.

Comment 2 beholder 1999-09-03 14:17:37 UTC

Sheldon Hearn wrote:

> On Thu, 02 Sep 1999 14:44:00 MST, beholder@unios.dhs.org wrote:
>
> > Get 2 HDD's and 2 CD-ROM's (my config). Set up the primary IDE chain as
> > (1)HDD (2)CD-ROM, and the secondary chain as (1)HDD (2)CD-ROM.  Then
> > install BSD on the second hard drive /wd3
>
> Are you sure the second drive is wd3? Is that what it says in the boot
> probe messages?

Sorry I think it was supposed to be /wd2  (I'm still new to BSD, I forgot
the drives started at 0 not A ;)

> Have a look at the loader(8) manual page. In the EXAMPLES section, it
> offers something that might help you:
>
>      Sets the disk unit of the root device to 2, and then boots. This
>      would be needed in the case of a two IDE disks system, with the
>      second IDE hard-wired to wd2 instead of wd1.
>
>            set root_disk_unit=2
>            boot /kernel

This probably would have fixed the problem.  However the installer didn't
seem to do this automatically, which I would consider a bug.  Everything
installs perfectly, but the kernel isn't updated with the proper boot device
I guess. What confused me was the fact that the FSTAB had the proper mount
points, but when the system booted it had a message:

changing root device to /wd1  (my CD-ROM)
root FS not found...  (or something similar)

> You might play around with root_disk_unit, after doing
>
>            set rootdev=wd2s1a
>
>         or
>
>            set rootdev=wd3s1a
>
> If you don't come right, make sure you show us your kernel config. :-)

Nothing special, it's just the generic kernel.  Just learned how to config
:)

>
>
> Later,
> Sheldon.

Comment 3 Sheldon Hearn 1999-09-03 16:59:34 UTC

On Fri, 03 Sep 1999 09:17:37 -0400, Beholder wrote:

> >            set root_disk_unit=2
> >            boot /kernel
> 
> This probably would have fixed the problem. 

Huh? What does "probably would have" mean? Have you tried it or haven't
you? :-)

> However the installer didn't seem to do this automatically, which I
> would consider a bug.

Were the drives configured _exactly_ as they are now when you first
installed?

> Everything
> installs perfectly, but the kernel isn't updated with the proper boot device
> I guess.

I'm not sure the kernel can be updated by sysinstall. ;-)

> What confused me was the fact that the FSTAB had the proper mount
> points, but when the system booted it had a message:

The loader doesn't use the fstab.

Later,
Sheldon.

Comment 4 Søren Schmidt freebsd_committer

2001-05-29 19:44:32 UTC

State Changed
From-To: open->closed

Obsoleted by the new ATA driver.