Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Mar 1999 23:01:46 -0500
From:      Matthew Emmerton <memmerto@uwaterloo.ca>
To:        <freebsd-questions@freebsd.org>
Subject:   Problems with Quantum Hard Drive
Message-ID:  <000001be773d$5e496010$1200a8c0@matt.gsicomp.on.ca>

Next in thread | Raw E-Mail | Index | Archive | Help

I've been trying to figure out whether one of my Quantum drives is bad or
if it's a BIOS problem.
The machine is a NEC Ready 9012 (P90).
The BIOS detects the drive and enters CHS information properly.

Windows 95 cannot boot from floppy (freezes after checking HDD)
Windows 98 cannot boot from floppy (freezes after checking HDD)
Windows NT can be installed from floppy and boot from HDD, using FAT and
NTFS partitions (limited to 2 and 4 GB
respectively).  It doesn't report any driver errors or exhibit drive
problems.

FreeBSD 3.1 can be installed from floppy and use the entire drive.
However, it provides the below information.

Mar 26 09:24:36 myname /kernel: FreeBSD 3.1-RELEASE #0: Mon Feb 15
11:08:08 GMT 1999
Mar 26 09:24:36 myname /kernel:
jkh@usw3.freebsd.org:/usr/src/sys/compile/GENERIC
...
Mar 26 09:24:36 myname /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa
Mar 26 09:24:36 myname /kernel: wdc0: unit 0 (wd0): <QUANTUM Bigfoot
TX8.0AT>
Mar 26 09:24:37 myname /kernel: wd0: 7665MB (15698592 sectors), 15574
cyls, 16 heads, 63 S/T, 512 B/S
Mar 26 09:24:37 myname /kernel: wdc1 at 0x170-0x177 irq 15 on isa
Mar 26 09:24:37 myname /kernel: wdc1: unit 0 (atapi): <NEC CD-ROM
DRIVE:273/4.21>, removable, iordy
Mar 26 09:24:37 myname /kernel: atapi1.0: unknown phase
Mar 26 09:24:37 myname /kernel: atapi1.0: invalid command phase,
ireason=0x2, status=58<ready,opdone,drq>, error=0
Mar 26 09:24:37 myname /kernel: atapi1.0: invalid command phase,
ireason=0xd8, status=d8<busy,ready,opdone,drq>, error=d8<mchg>
Mar 26 09:24:37 myname /kernel: atapi1.0: controller not ready for cmd
Mar 26 09:24:37 myname /kernel: atapi1.0: controller not ready for cmd
...
Mar 26 09:26:23 myname /kernel: wd0: interrupt timeout (status
50<rdy,seekdone> error 0)
Mar 26 09:26:23 myname /kernel: wd0: wdtimeout() DMA status 4
Mar 26 09:26:23 myname /kernel: wd0: wdunwedge failed (status
d0<busy,rdy,seekdone> error d0<badblk,uncorr,no_id>)
Mar 26 09:26:23 myname /kernel: wd0s1a: wdstart: timeout waiting to give
command reading fsbn 39568 of 39568-39631 (wd0s1 bn 39568; cn 2 tn 116 sn
4) (status d0<busy,rdy,seekdone> error d0<badblk,uncorr,no_id>)
Mar 26 09:26:23 myname /kernel: wd0: wdunwedge failed (status
d0<busy,rdy,seekdone> error d0<badblk,uncorr,no_id>)
Mar 26 09:26:23 myname /kernel: wd0s1a: wdstart: timeout waiting to give
command reading fsbn 39568 of 39568-39631 (wd0s1 bn 39568; cn 2 tn 116 sn
4) (status d0<busy,rdy,seekdone> error d0<badblk,uncorr,no_id>)
Mar 26 09:26:23 myname /kernel: wd0: wdunwedge failed (status
d0<busy,rdy,seekdone> error d0<badblk,uncorr,no_id>)
Mar 26 09:26:23 myname /kernel: wd0s1a: wdstart: timeout waiting to give
command reading fsbn 39568 of 39568-39631 (wd0s1 bn 39568; cn 2 tn 116 sn
4) (status d0<busy,rdy,seekdone> error d0<badblk,uncorr,no_id>)



I did a fsck a few times, and each time when it was finished it reported
"DRIVE STILL DIRTY, RUN FSCK AGAIN."

I did a bad144, and this is what eventually cropped up after about 30
mins.

Mar 26 10:26:12 myname /kernel: fd0c: hard error writing fsbn 1 of 1-3
(ST0 40<abnrml> ST1 2<write_protect> ST2 0 cyl 0 hd 0 sec 2)
Mar 26 10:26:12 myname /kernel: fd0c: hard error writing fsbn 10 of 10-12
(ST0 40<abnrml> ST1 2<write_protect> ST2 0 cyl 0 hd 0 sec 11)
Mar 26 10:26:12 myname /kernel: fd0c: hard error writing fsbn 19 (ST0
40<abnrml> ST1 2<write_protect> ST2 0 cyl 0 hd 1 sec 2)
Mar 26 10:26:27 myname /kernel: fd0c: hard error writing fsbn 1013 (ST0
40<abnrml> ST1 2<write_protect> ST2 0 cyl 28 hd 0 sec 6)
Mar 26 10:26:34 myname last message repeated 28 times


Any ideas?  Quantum doesn't have any microcode updates for the drives (as
far as I can see).

--
Matthew Emmerton      || P: +1 (800) 217-5409 (Canada)
GSI Computer Services || F: +1 (519) 335-6584



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: <http://docs.FreeBSD.org/cgi/mid.cgi?000001be773d$5e496010$1200a8c0>