From nobody  Fri Apr  3 13:39:06 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA07482;
          Fri, 3 Apr 1998 13:39:06 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199804032139.NAA07482@hub.freebsd.org>
Date: Fri, 3 Apr 1998 13:39:06 -0800 (PST)
From: jkowall@coffeehaus.net
To: freebsd-gnats-submit@freebsd.org
Subject: wdc0 goes away with newest sources
X-Send-Pr-Version: www-1.0

>Number:         6204
>Category:       kern
>Synopsis:       wdc0 goes away with newest sources
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Apr  3 13:40:08 PST 1998
>Closed-Date:    Fri Apr 17 09:05:05 PDT 1998
>Last-Modified:  Fri Apr 17 09:07:36 PDT 1998
>Originator:     Jonah Kowall
>Release:        2.2.5-STABLE FreeBSD 2.2.5-STABLE #0
>Organization:
Coffeehaus Networks
>Environment:
FreeBSD freebsd.coffeehaus.net 2.2.5-STABLE FreeBSD 2.2.5-STABLE #0: Wed Mar  4 21:53:12 EST 1998     jkowall@freebsd.coffeehaus.net:/usr/src/sys/compile/JKOWALL  i386
>Description:
I have a 2940uw with a 4 gig scsi on it for the system and I am using a 2.5 gig eide for some user homes.  With the newest cvsup as of about 3 weeks ago the EIDE drive stopped showing up when I boot.  Its a pentium 133, and I have never had any problems with the IDE system on it.  When i boot with a old working kernel it sees the drive fine.  I am using the same config file for both kernels.  If you need any additional info please fell free to email me.  

Thanks!
>How-To-Repeat:
boot the machine with the newly conpiled kernel
>Fix:
boot with a older kernel
>Release-Note:
>Audit-Trail:

From: "Jonah Kowall" <jkowall@coffeehaus.net>
To: <freebsd-gnats-submit@freebsd.org>,
        "Jonah Kowall" <jkowall@coffeehaus.net>
Cc:  Subject: Re: kern/6204: wdc0 goes away with newest sources
Date: Thu, 16 Apr 1998 15:40:08 -0400

 This had to do with the device change in the STABLE tree.
 
 
 This message I found in the lists sums it up.  So please close the bug
 report.
 
 On Thu, 12 Mar 1998, Kent Vander Velden wrote:>
 >   Hos something changed in -current during the past two weeks that would
 > affect how the root filesystem is mounted?  The problem that I am seeing
 > at the moment is with a new -current kernel, the root file system will
 > fail to mount on boot.  Running mount with no arguments shows that /
 > has the device 'root_device' mounted on it and not '/dev/sd0a' as I would
 > aspect.  When I try to mount '/dev/sd0a' on / mount gives the error:
 > "Specified device does not match mounted device.\n".  I will try
 recompiling
 > mount in a moment.  Any other suggestions?Try sd0s1a.
 I think a change went into -stable too -- have had some complaints from
 stable users about a name change.
 
 
 - Jonah Kowall
 
  VP Technology
  Coffeehaus Networks / Content Advisor
 
State-Changed-From-To: open->closed 
State-Changed-By: des 
State-Changed-When: Fri Apr 17 09:05:05 PDT 1998 
State-Changed-Why:  
Author says error was due to slice name change and asks for PR to be closed. 
>Unformatted:
