Bug 17920

Summary:	ata/ad driver HARD ERROR failure with internal disk on an NCR laptop
Product:	Base System	Reporter:	pir-freebsd <pir-freebsd>
Component:	kern	Assignee:	Søren Schmidt <sos>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	4.0-STABLE
Hardware:	Any
OS:	Any

Description pir-freebsd 2000-04-11 05:50:01 UTC

hardware: NEC Versa V/50 laptop.
4.0 ATA driver fails with a HARD ERROR on the internal IDE disk.

From the 4.0-R install floppies the ATA controller is recognised during 
boot and then during device probe a pair of hard errors in the debug
screen;

  ad0: HARD READ ERROR blk# 0 status 51 error=04
  ad0: reading primary partition stable: error reading fsbn: 0
  ad0: HARD READ ERROR blk# 0 status 51 error=04
  ad0: reading primary partition stable: error reading fsbn: 0

I did the install by installing a minimal 3.4-PAO, which worked fine,
and then a manual installation of 4.0 via NFS (sysinstall wouldn't
recognise wd0 during a floppy install with a custom wdc kernel on
kern.flp).

I built a kernel on a 4.0-S machine using wdc instead of ata which
works perfectly;

  wdc0 at port 0x1f0-0x1f7 irq 14 on isa0
  wdc0: unit 0 (wd0): <IBM-H2344-A4>
  wd0: 328MB (672525 sectors), 915 cyls, 15 heads, 49 S/T, 512 B/S
  wdc0: driver is using old-style compatability shims

If I build an ATA kernel and try to boot from it I get;

  ad0: 320MB <IBM-H2344-A4> [915/15/49] at ata0-master using BIOSPIO
  Mounting root from ufs:/dev/ad0s1a
  ad0: HARD ERROR blk# 0 status=51 error=04
  ad0: reading primary partition stable: error reading fsbn 0

It was suggested that this could be the pio problem, but the messages
I've found imply it is already trying to use pio mode.

Fix: 

:/
How-To-Repeat: boot this laptop from 4.0-R install floppies.

Comment 1 Sheldon Hearn freebsd_committer

2000-04-11 13:52:45 UTC

Responsible Changed
From-To: freebsd-bugs->sos

Ah, an ata-related PR with a datapoint.  Perhaps Soren can help. :-)

Comment 2 Tim Vanderhoek 2000-05-16 21:08:49 UTC

The following was intended to be a follow-up to this PR.

----- Forwarded message from Tim Vanderhoek <tim@localhost.nowhere> -----

>   Description
>          
> An extra datapoint on this problem.
>
> I tracked down a spare disk in a caddy and disk for this machine so I
> could leave 3.4-PAO on the new disk (which is smaller) and test with
> 4.x on the old disk.
>
> 4.0-R doesn't produce the same errors with the new disk (a seagate
> ST9144A) so it looks like the old disk (or the combination of disk and
> controller) is the problem. It's an IBM OEM disk, IBM-H2344-A4 disk;
> 344Mb, 915/15/49.
>
> I don't have another machine I can test this disk in but would be
> quite happy to ship it to someone else who does and could spend time
> debugging the low level problem.
>
> P.
>
> --
> pir                  pir@pir.net                    pir@net.tufts.edu

----- End forwarded message -----


-- 
Signature withheld by request of author.

Comment 3 Søren Schmidt freebsd_committer

2000-11-14 08:45:07 UTC

State Changed
From-To: open->closed

Please upgrade to 4.2, and get back to me if problem persists.