From: Douglas Gilbert <dgilbert@interlog.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: how to recover from "medium format corrupted"?
Date: Mon, 14 Dec 2009 15:32:35 +0100 [thread overview]
Message-ID: <4B264C83.4080009@interlog.com> (raw)
In-Reply-To: <alpine.DEB.2.01.0912140158580.2915@bogon.housecafe.de>
Christian Kujau wrote:
> Hi there,
>
> I noticed that I cannot access one of the two 73GB SCSI disks any more
> (connected to a 53C1030 LSI/Fusion MPT controller); during bootup the
> message "READ CAPACITY failed" appears. Searching the net I've seen two
> very interesting posts [0] about this and I think this is exactly what
> happened to my disk:
>
> I was booting the same system into Solaris 10 earlier
> and wanted to erase the partition table via "dd if=/dev/zero ..." but as
> this wasn't working (the table was still in place) I "played around" with
> format[1] and may have issued the "FORMAT" command - but as it estimated
> to run ~100 minutes I interrupted the command and booted into Linux
> (2.6.32) only to see that sdb now has a different geometry:
>
> # hdparm -g /dev/sd[ab]
> /dev/sda: geometry = 8924/255/63, sectors = 143374744, start = 0
> /dev/sdb: geometry = 0/64/32, sectors = 0, start = 0
>
> Unfortunately, sg_format (as suggested by Douglas in the posts) were not
> able to recover the disk.
Christian,
Could you try the '--wait' option on the sg_format? The disk
does not seem to respond to the TEST UNIT READY poll. If
it is a modern disk it might respond to a REQUEST SENSE poll
but sg_format doesn't support that yet.
The '--wait' option will leave sg_format hanging until the
FORMAT UNIT finishes or 4 hours expires.
MEDIUM FORMAT CORRUPTED [asc/ascq=0x31,0x0] is caused by an
interrupted FORMAT UNIT.
Doug Gilbert
> I wonder if the disk is still OK (it was working earlier, SCSI FORMAT
> commands won't destroy the disk, right?) and if anyone knows some magic
> SCSI commands to issue so that the disk returns to a normal state again.
>
> I've the lsiutil[2] tool on my hands, just in case some more details are
> needed.
>
> Any ideas?
>
> Thanks,
> Christian.
>
> [0] http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg09553.html
> http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg07629.html
> [1] http://www.sun.com/bigadmin/content/submitted/format_utility.jsp
> [2] http://www.lsi.com/DistributionSystem/AssetDocument/LSIUtil_1.62.zip
>
>
> v40z1# dmesg | grep sdb
> sd 2:0:1:0: [sdb] READ CAPACITY failed
> sd 2:0:1:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
> sd 2:0:1:0: [sdb] Sense Key : 0x3 [current]
> sd 2:0:1:0: [sdb] ASC=0x31 ASCQ=0x0
> sd 2:0:1:0: [sdb] Write Protect is off
> sd 2:0:1:0: [sdb] Mode Sense: ab 00 10 08
> sd 2:0:1:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
> sd 2:0:1:0: [sdb] READ CAPACITY failed
> sd 2:0:1:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
> sd 2:0:1:0: [sdb] Sense Key : 0x3 [current]
> sd 2:0:1:0: [sdb] ASC=0x31 ASCQ=0x0
> sd 2:0:1:0: [sdb] Attached SCSI disk
>
> v40z1# sg_format --format -vvv /dev/sdb
> open /dev/sdb with flags=0x802
> inquiry cdb: 12 00 00 00 24 00
> duration=0 ms
> SEAGATE ST373307LC 0007 peripheral_type: disk [0x0]
> PROTECT=0
> mode sense (10) cdb: 5a 00 01 00 00 00 00 00 fc 00
> duration=0 ms
> mode sense (10): requested 252 bytes but got 28 bytes
> mode sense (10): response
> 00 1a 00 10 00 00 00 08 08 8b b9 98 00 00 02 00
> 81 0a c0 0b ff 00 00 00 05 00 ff ff
> Mode Sense (block descriptor) data, prior to changes:
> Number of blocks=143374744 [0x88bb998]
> Block size=512 [0x200]
>
> A FORMAT will commence in 10 seconds
> ALL data on /dev/sdb will be DESTROYED
> Press control-C to abort
> A FORMAT will commence in 5 seconds
> ALL data on /dev/sdb will be DESTROYED
> Press control-C to abort
> format cdb: 04 18 00 00 00 00
> format parameter list:
> 00 02 00 00
> duration=280 ms
>
> Format has started
> test unit ready cdb: 00 00 00 00 00 00
> sense buffer empty
> FORMAT Complete
> v40z1# echo $?
> 0
>
next prev parent reply other threads:[~2009-12-14 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 10:19 how to recover from "medium format corrupted"? Christian Kujau
2009-12-14 14:32 ` Douglas Gilbert [this message]
2009-12-14 21:24 ` Christian Kujau
2009-12-16 5:18 ` Christian Kujau
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=4B264C83.4080009@interlog.com \
--to=dgilbert@interlog.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lists@nerdbynature.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.