Date: Wed, 22 Nov 2000 23:20:57 +0100 From: Wilko Bulte <wkb@freebie.demon.nl> To: Frederic Nguyen <chainess@worldnet.net> Cc: freebsd-stable@freebsd.org Subject: Re: 4.2-RELEASE + SCSI device unable to mount file system Message-ID: <20001122232057.G2163@freebie.demon.nl> In-Reply-To: <5.0.0.25.2.20001122225500.021fddc0@pop.worldnet.net>; from chainess@worldnet.net on Wed, Nov 22, 2000 at 11:04:31PM %2B0100 References: <00e001c05492$eca35760$0b6cffc8@infolink.com.br> <5.0.0.25.2.20001122225500.021fddc0@pop.worldnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 22, 2000 at 11:04:31PM +0100, Frederic Nguyen wrote: > Hello, > > did anybody encountered that problem while upgrading from 3.5 to 4.2? > (controller is an Adaptec 2940UW with an 18Gb SCSI HD) > > Mounting root from ufs:da0s1a > da0 at ahc1 bus 0 target 0 lun 0 > da0: <SEAGATE ST318275LW 0001> Fixed Direct Access SCSI-2 device > ... > da0: 17366MB (35566480 512 byte sectros: 255H 63S/T 2213C) > da0: bad sector table not supported > da0s1: bad sector table not supported > Root mount failed: 22 > Mounting root from ufs:da0a > da0: bad sector table not supported > da0s1: bad sector table not supported Why do you have a badsector table on a SCSI disk?? bad144 was canned quite some time ago, I think that might be causing this. Badsect tables are for old ESDI etc drives. Never been for SCSI -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001122232057.G2163>