Date: 19 Jan 1999 04:43:08 +0100 From: Dag-Erling Smorgrav <des@flood.ping.uio.no> To: scsi@FreeBSD.ORG Subject: Fireball woes (continued) Message-ID: <xzpd84c53n7.fsf@flood.ping.uio.no>
next in thread | raw e-mail | index | archive | help
Some of you may remember that I had a nearly brand-new Fireball act up on me last fall... well, it's acting up again: Jan 19 04:12:59 niobe /kernel: (da1:ahc0:0:4:0): READ(06). CDB: 8 2 57 0 10 0 Jan 19 04:12:59 niobe /kernel: (da1:ahc0:0:4:0): MEDIUM ERROR info:2570d asc:11,0 Jan 19 04:12:59 niobe /kernel: (da1:ahc0:0:4:0): Unrecovered read error Jan 19 04:12:59 niobe /kernel: /: got error 5 while accessing filesystem Jan 19 04:12:59 niobe /kernel: Lost type inodedep Jan 19 04:12:59 niobe last message repeated 12 times Jan 19 04:12:59 niobe /kernel: /: got error 5 while accessing filesystem Jan 19 04:12:59 niobe /kernel: Lost type inodedep Jan 19 04:12:59 niobe last message repeated 4 times Jan 19 04:12:59 niobe /kernel: /: got error 5 while accessing filesystem Jan 19 04:12:59 niobe /kernel: Lost type inodedep At that point, the system froze for about a minute, maybe less, then rebooted (it *may* have dropped into DDB; I tried typing "panic" and "continue" blind since I was in X at the time, and it rebooted at about the time I finished typing "continue" and hit enter) A short time after reboot, I get: Jan 19 04:31:19 niobe /kernel: (da1:ahc0:0:4:0): READ(06). CDB: 8 3 68 60 48 0 Jan 19 04:31:19 niobe /kernel: (da1:ahc0:0:4:0): MEDIUM ERROR info:36866 asc:11,1 Jan 19 04:31:19 niobe /kernel: (da1:ahc0:0:4:0): Read retries exhausted Jan 19 04:31:19 niobe /kernel: /usr/release: got error 5 while accessing filesystem Jan 19 04:31:19 niobe /kernel: Lost type pagedep Jan 19 04:31:19 niobe /kernel: /usr/release: got error 5 while accessing filesystem Jan 19 04:31:19 niobe /kernel: Lost type pagedep Jan 19 04:31:19 niobe /kernel: /usr/release: got error 5 while accessing filesystem Jan 19 04:31:19 niobe /kernel: Lost type pagedep Jan 19 04:31:19 niobe /kernel: /usr/release: got error 5 while accessing filesystem Jan 19 04:31:19 niobe /kernel: Lost type indirdep Jan 19 04:31:19 niobe /kernel: /usr/release: got error 5 while accessing filesystem Jan 19 04:31:19 niobe /kernel: Lost type pagedep Jan 19 04:31:19 niobe /kernel: spec_getpages: I/O read failure: (error code=5) Jan 19 04:31:19 niobe /kernel: size: 36864, resid: 36864, a_count: 36864, valid: 0x0 Jan 19 04:31:19 niobe /kernel: nread: 0, reqpage: 0, pindex: 80, pcount: 9 Jan 19 04:31:19 niobe /kernel: vm_fault: pager read error, pid 5406 (install) and make release which is running with CHROOTDIR=/usr/release dies with the following: ===> gnu/usr.bin/cc/cc1 install -c -s -o root -g wheel -m 555 cc1 /usr/release/usr/libexec install: /usr/release/usr/libexec/cc1: Bad address *** Error code 71 Stop. (which coincides with the message from vm_fault). "camcontrol defects -n da -u 1 -f block -G" gives me 15 defects, and the following log message as a bonus: Jan 19 04:39:33 niobe /kernel: (pass1:ahc0:0:4:0): READ DEFECT DATA(10). CDB: 37 0 8 0 0 0 0 fd e8 0 Jan 19 04:39:33 niobe /kernel: (pass1:ahc0:0:4:0): RECOVERED ERROR asc:1c,0 Jan 19 04:39:33 niobe /kernel: (pass1:ahc0:0:4:0): Defect list not found The permanent defect list has >600 entries. The disk is a six-months-old Quantum Fireball: an 19 04:18:58 niobe /kernel: da1 at ahc0 bus 0 target 4 lun 0 Jan 19 04:18:58 niobe /kernel: da1: <QUANTUM FIREBALL ST6.4S 0F0C> Fixed Direct Access SCSI-2 device Jan 19 04:18:58 niobe /kernel: da1: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled Jan 19 04:18:58 niobe /kernel: da1: 6180MB (12657717 512 byte sectors: 255H 63S/T 787C) Can anybody tell me what error 5 means, and how serious the disk's condition is? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no 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?xzpd84c53n7.fsf>