Date: Wed, 29 Apr 1998 11:27:29 +0300 (EEST) From: Penisoara Adrian <ady@warpnet.ro> To: freebsd-scsi@FreeBSD.ORG Subject: sd1: HARDWARE FAILURE - info ? Message-ID: <Pine.BSF.3.96.980429110143.6685B-100000@ady.warpnet.ro> In-Reply-To: <19980118113444.17218@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
Sorry to intrude on the list with such a trivial issue, but could
someone plese translate for me what this error really means ?
--[ From /var/log/messages ]--------------------------------------------
Apr 29 10:21:30 ady /kernel: sd1: HARDWARE FAILURE info:0x3660f0 asc:9,8
Apr 29 10:21:30 ady /kernel: , retries:4
--[ uname -a ]----------------------------------------------------------
FreeBSD ady.warpnet.ro 3.0-971117-SNAP FreeBSD 3.0-971117-SNAP #0: Tue
Mar 17 20:45:43 EET 1998
root@ady.warpnet.ro:/usr/src/sys/compile/ADY-NONSMP i386
--[ dmesg (booted -v) ]-------------------------------------------------
FreeBSD 3.0-971117-SNAP #0: Tue Mar 17 20:45:43 EET 1998
root@ady.warpnet.ro:/usr/src/sys/compile/ADY-NONSMP
[...]
CPU: Pentium (132.94-MHz 586-class CPU)
Origin = "GenuineIntel" Id = 0x526 Stepping=6
Features=0x3bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC>
real memory = 67108864 (65536K bytes)
[...]
ahc0: <Adaptec 2940A Ultra SCSI host adapter> rev 0x01 int a irq 11 on pci0.20.0
ahc0: Reading SEEPROM...done.
low byte termination enabled, high byte termination disabled
ahc0: aic7860 Single Channel, SCSI Id=7, 3/8 SCBs
ahc0: Resetting Channel A
ahc0: Downloading Sequencer Program...ahc0: 416 instructions downloaded
Done
ahc0: Probing channel A
ahc0: waiting for scsi devices to settle
scbus0 at ahc0 bus 0
ahc0: target 4 synchronous at 10.0MHz, offset = 0xf
ahc0: target 4 Tagged Queuing Device
sd0 at scbus0 target 4 lun 0
sd0: <Quantum VP32170 89TC> type 0 fixed SCSI 2
sd0: Direct-Access 2069MB (4238640 512 byte sectors)
sd0: with 3907 cyls, 10 heads, and an average 108 sectors/track
ahc0: target 6 synchronous at 20.0MHz, offset = 0xf
ahc0: target 6 Tagged Queuing Device
sd1 at scbus0 target 6 lun 0
sd1: <QUANTUM FIREBALL SE6.4S PJ0A> type 0 fixed SCSI 2
sd1: Direct-Access 6149MB (12594960 512 byte sectors)
sd1: with 7637 cyls, 6 heads, and an average 18 sectors/track
[...]
BIOS Geometries:
0:03fe3f20 0..1022=1023 cylinders, 0..63=64 heads, 1..32=32 sectors
1:03fe3f20 0..1022=1023 cylinders, 0..63=64 heads, 1..32=32 sectors
0 accounted for
Device configuration finished.
IP packet filtering initialized, divert disabled, logging disabled
Considering FFS root f/s.
sd0s1: type 0xa5, start 0, end = 4238639, size 4238640
sd0s1: C/H/S end 312/199/63 (3943799) != end 4238639: invalid
sd1s1: type 0xa5, start 0, end = 12594959, size 12594960 : OK
A bit of background:
Since my Quantum VP3120 started to go wild ("grown defects" were growing
pretty fast) I decided to buy this Quantum FireballSE.
The new Quantum gave me some weird READ ERRORs but no blocks were marked
in the defects table (there are no grown defects until now). Now that I
came back to the old situation I started a test program on it (it randomly
reads and writes 16Kb blocks in a file that spans on all space, with a
specified delay after each operation).
The first 2 days I left it without ultra (sync. at 10Mhz, like the old
drive) and ran the program with 50ms delay. I had no problem.
Now that I switched him to utra (sync. at 20Mhz) and ran the program
with 10ms delay it gave this erorr after approx. 1/2 day.
Beeing that when I first installed the new Quantum I used utra (sync.
20Mhz) I believe I might have a problem with cabling/termination ? I know
that ultra speed needs special care (good cable/termination). What are
your opinions ?
Thank you,
Adrian Penisoara
Ady (@warpnet.ro)
Warp Net Technologies
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980429110143.6685B-100000>