From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] OT: scsi sense error code hardware error 40 83?
Date: Tue, 3 Oct 2006 15:10:01 +0200 [thread overview]
Message-ID: <200610031310.k93DA2d19372@zamenhof.cs.utwente.nl> (raw)
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.
next reply other threads:[~2006-10-03 13:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 13:10 Axel Belinfante [this message]
2006-10-03 18:17 ` geoff
2006-10-03 20:13 ` [9fans] kenfs config? (was: OT: scsi sense error code hardware error 40 83?) Axel Belinfante
2006-10-03 21:19 ` [9fans] kenfs config? (was: OT: scsi sense error code hardware geoff
2006-10-17 15:55 ` Axel Belinfante
2006-10-17 20:18 ` geoff
2006-10-17 21:05 ` Axel Belinfante
2006-10-17 21:35 ` geoff
2006-10-17 23:55 ` Axel Belinfante
2006-10-03 20:20 ` [9fans] gs Charles Forsyth
2006-10-03 20:39 ` geoff
2006-10-03 20:41 ` Francisco J Ballesteros
2006-10-03 20:48 ` Jack Johnson
2006-10-03 21:37 ` LiteStar numnums
2006-10-03 22:07 ` Andy Newman
2006-10-04 2:18 ` jmk
2006-10-06 0:00 ` Bruce Ellis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200610031310.k93DA2d19372@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).