Subject: Re: Install problem with disk mode sense
To: Jay Nelson <jnelson@newsstand.com>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: netbsd-help
Date: 03/27/2002 22:23:10
On Tue, Mar 26, 2002 at 07:28:31PM -0600, Jay Nelson wrote:
> On Tue, Mar 26, 2002 at 11:15:17PM +0100, Manuel Bouyer wrote:
> > On Tue, Mar 26, 2002 at 01:14:26PM -0600, Jay Nelson wrote:
> > > I can't get a bootable install off one particular box and I'm hoping
> > > someone can help.
> > > 
> > > The disk probe on boot is returning a mode sense "too large to make
> > > sense" message (or similar -- I'm working from memory.) The number
> > > cylinders picked up in sysinstall are, in fact, too large. (Something
> > > in excess of 33,000) Changing the geometry in sysinstall has no
> > > effect.
> > 
> > Can you try to post the NetBSD boot message here ?
>  
> It turns out, my memory wasn't very good. Reported cylinders are
> 13088. The msgbuf is below. I notice that the name of the drive is
> completely different. If FreeBSD dmesg output is helpful, I can send
> that, too.
> 
> This is an ASUS T2P4 motherboard with the SCSI bios disabled. The
> Symbios controller also has it's bios disabled.
> [...]
> scsibus1: waiting 2 seconds for devices to settle...
> adw0: target 0 using 8-bits wide, 20.8 MHz synchronous transfers
> sd0 at scsibus1 target 0 lun 0: <ALSV__L, 03193809 001\014000, 0000> SCSI3 0/direct fixed
> sd0: mode sense (4) returned nonsense; using fictitious geometry
> sd0: 13088 MB, 13088 cyl, 64 head, 32 sec, 512 bytes/sect x 26804227 sectors

Hum, the kernel seems to get corrupted data from disk (bad ident string,
bad mode sense). This is likely a bug in the adw driver.

Is there someone familiar with this driver around ?

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
--