Subject: Re: bad144 in march and later kernels
To: Robert Dobbs <banshee@gabriella.resort.com>
From: Jason Thorpe <thorpej@cs.orst.edu>
List: current-users
Date: 03/30/1994 10:52:08
On Wed, 30 Mar 1994 01:11:19 -0800
banshee@gabriella.resort.com (Robert Dobbs) wrote:
>
> I started getting these messages on boot with the march kernels.
>
> Mar 28 17:52:11 gabriella /netbsd: wdc0: extra interrupt
> Mar 28 17:52:12 gabriella /netbsd: wd0d: hard error reading fsbn 623696 (wd0 bn 623696; cn 1222 tn 14 sn 0)
> Mar 28 17:52:12 gabriella /netbsd: wd0d: hard error reading fsbn 623698 (wd0 bn 623698; cn 1222 tn 14 sn 2)
> Mar 28 17:52:12 gabriella /netbsd: wd0d: hard error reading fsbn 623700 (wd0 bn 623700; cn 1222 tn 14 sn 4)
> Mar 28 17:52:12 gabriella /netbsd: wd0d: hard error reading fsbn 623702 (wd0 bn 623702; cn 1222 tn 14 sn 6)
> Mar 28 17:52:12 gabriella /netbsd: wd0d: hard error reading fsbn 623704 (wd0 bn 623704; cn 1222 tn 14 sn 8)
>
> These sectors are obviously the ones reserved by bad144
> It _could_ be that the track which those are on is bad,
>
> I currently have no sectors on the drive marked bad.
>
> gabriella# bad144 wd0
> bad block information at sector 623696 in /dev//rwd0d:
> cartridge serial number: 0(10)
> gabriella#
>
> Has anyone else noticed behaviour similar to this?
> Any ideas? It _seems_ harmless but I haven't tried bad144
> with real arguments.
Last time this happened to me, I lost my root partition. I had to
unmount wd1 - once I did this, I quit getting the extra interrupt
messages and haven't had anymore problems...I'd really like to use that
other drive, thought...
-----------------------------------------------------------------------------
Jason R. Thorpe thorpej@cs.orst.edu 737-9533
OSU CS Support CSWest Room 12 737-2552
'These are my opinions and not necessarily those of anyone else.'
------------------------------------------------------------------------------