From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200610031310.k93DA2d19372@zamenhof.cs.utwente.nl>
To: 9fans@cse.psu.edu
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <19366.1159880999.1@zamenhof.cs.utwente.nl.cs.utwente.nl>
Date: Tue,  3 Oct 2006 15:10:01 +0200
Subject: [9fans] OT: scsi sense error code hardware error 40 83?
Topicbox-Message-UUID: c43eeba0-ead1-11e9-9d60-3106f5b1d025

after moving my fake worm kenfs there appears to be
a problem with the main disk.
(the fs kernel doesn't even get to probing the other disks)

the last succesful boot told me the disk is a
Thu Dec  8 15:29:58: scsi#0.0: QUANTUM XP34550S        LXQ1184630312388

as far a I could find the '40 83' means:
    DIAGNOSTIC FAILURE ON COMPONENT NN (80h-FFh)
but I could not find more details.

I still have to try to run some diagnostic program (scsimax(?))
just curious if anybody instantly recognizes the code.



related question (that is here under the wrong heading, but ok)
assuming a kenfs file server with config

filsys main cp(w0)0.50f(w5w1)

now assuming I lost only the w0, but the w5w1 making
up the fake worm are still there, am I right in assuming
that the correct procedure to resurrect the fs would be:
 - get a new disk to replace w0
   (no problem if it differs from the original?)
 - boot the fs kernel
 - enter config mode
 - in config mode enter the usual stuff, as when initializing
   the fs as explained in the fsconfig man page, EXCEPT
 - where the examples say 'ream main' do 'recover main'
right?


These are the boot messages I get (thanks to consolefs)
Tue Oct  3 15:19:37: sysinit
Tue Oct  3 15:19:37: config w0
Tue Oct  3 15:19:37: 	devinit w0
Tue Oct  3 15:19:37: scsi#0.0: unavailable, status 2
Tue Oct  3 15:19:37: 	drive w0:
Tue Oct  3 15:19:37: 		8890759 blocks at 512 bytes each
Tue Oct  3 15:19:37: 		1111345 logical blocks at 4096 bytes each
Tue Oct  3 15:19:37: 		8 multiplier
Tue Oct  3 15:19:37: scsi#0.0: reqsense: 'not ready' code #40 #83
Tue Oct  3 15:19:37: scsi#0.0: byte 2: #02, bytes 15-17: #00 #00 #00
Tue Oct  3 15:19:37: lastcmd (6):  #00 #00 #00 #00 #00 #00
Tue Oct  3 15:19:37: scsi#0.0: unavailable, status 2
Tue Oct  3 15:19:37: scsi#0.0: reqsense: 'hardware error' code #40 #83
Tue Oct  3 15:19:37: scsi#0.0: byte 2: #04, bytes 15-17: #00 #00 #00
Tue Oct  3 15:19:37: lastcmd (10):  #28 #00 #00 #00 #00 #00 #00 #00 #08 #00
[this repeats for a while until it gives up:]
Tue Oct  3 15:19:39: wrenread: w0(0) bad status 0002
Tue Oct  3 15:19:39: stack trace of 2
[stack trace omitted]
Tue Oct  3 15:19:40: 1220 stack used out of 16000
Tue Oct  3 15:19:40: 
Tue Oct  3 15:19:40: panic: config io


Axel.