Date: Wed, 3 Jan 2001 23:56:20 -0600 (CST) From: Mike Meyer <mwm@mired.org> To: Michael Wells <michael@wells.org.uk> Cc: questions@freebsd.org Subject: Re: Mounting to ad3xxx after a new kernel Message-ID: <14932.4228.869449.117980@guru.mired.org> In-Reply-To: <37615933@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Wells <michael@wells.org.uk> 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. <mike -- Mike Meyer <mwm@mired.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14932.4228.869449.117980>