From owner-freebsd-questions Wed Jan 3 21:56:23 2001 From owner-freebsd-questions@FreeBSD.ORG Wed Jan 3 21:56:21 2001 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 4937B37B400 for ; Wed, 3 Jan 2001 21:56:21 -0800 (PST) Received: (qmail 22038 invoked by uid 100); 4 Jan 2001 05:56:20 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14932.4228.869449.117980@guru.mired.org> Date: Wed, 3 Jan 2001 23:56:20 -0600 (CST) To: Michael Wells Cc: questions@freebsd.org Subject: Re: Mounting to ad3xxx after a new kernel In-Reply-To: <37615933@toto.iv> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Wells types: > Hi all, > > First up, thanks for the handbook and instructions on making a new > kernel. I've just made my first one, and it seems good to me - with just > one exception. > > My /etc/fstab previously had an entry I'd added, thus: > > /dev/ad3s1e /backups ufs rw,noatime 1 1 > > This is nothing special, I hope. I've got a hard drive I use for backups > connected to the secondary IDE bus. Unfortunately, it won't mount under > my new kernel (fine on the old one). I get this: > > su-2.04# mount /dev/ad3s1e /backups/ > mount: Device not configured > > This seems strange to me, and I would be really grateful for any advice. All > I have so far is a suspicion that my /sys/i386/conf/kernelconfig file > (actually called SUNRISE) doesn't define that drive, but I am none the > wiser as to fixing it. This could be lots of things. You could have left ad3 out of the kernel config, or you could have changed the option that controls drive numbering, so that it's no longer ad3. Start by checking dmesg for that drive. If you're otherwise using ad3 ok, you might try removing and recreating the devices in /dev, but that's a long shot. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message