From: Matthias Andree <matthias.andree@gmx.de>
To: Guy <bugzilla@watkins-home.com>
Subject: Re: Help decoding: Info fld=0x25e6e3, Current sd08:b1: sense key Recovered Error
Date: Tue, 18 Jan 2005 22:08:45 +0100 [thread overview]
Message-ID: <m3llaqtpgi.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <200501182057.j0IKvw904493@www.watkins-home.com> (bugzilla@watkins-home.com's message of "Tue, 18 Jan 2005 15:55:49 -0500")
"Guy" <bugzilla@watkins-home.com> writes:
> Can anyone help decode this info?
>
> What is 0x25e6e3?
> What disk is sd08:b1?
/dev/sdl1 (ess dee ell one) - that's sedecimal notation for a device
with major 8 minor 0xb1 = 177;
$ ls -l /dev/sd* |grep " 8, 177"
brw-rw---- 1 root disk 8, 177 2004-10-02 10:38 /dev/sdl1
> kernel: Info fld=0x25e6e3, Current sd08:b1: sense key Recovered Error
> kernel: Additional sense indicates Recovered data with error corr. & retries
> applied
Time to check and possibly replace the drive, or at least refresh the
block.
smartmontools (on sourceforge) and perhaps badblocks or Jörg Schillings
sformat (careful!) may help you with that.
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-01-18 21:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200501121941.18058.david-b@pacbell.net>
2005-01-14 16:05 ` [PATCH as445] Fix reference to deallocated memory in sd.c Alan Stern
2005-01-18 14:56 ` [PATCH as448] Fix reference to deallocated memory in sr.c Alan Stern
2005-01-18 15:10 ` James Bottomley
2005-01-18 20:55 ` Help decoding: Info fld=0x25e6e3, Current sd08:b1: sense key Recovered Error Guy
2005-01-18 21:08 ` Matthias Andree [this message]
2005-01-18 23:32 ` Guy
2005-01-19 1:22 ` Douglas Gilbert
2005-01-19 4:32 ` Guy
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=m3llaqtpgi.fsf@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=bugzilla@watkins-home.com \
/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