Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: "Michael Drüing" <michael@drueing.de>
To: linux-scsi@vger.kernel.org
Subject: Aborted sg_format; how to recover?
Date: Mon, 8 Mar 2010 21:40:13 +0100	[thread overview]
Message-ID: <7D05ACFE637E4AE08F92B348397AC586@aeris> (raw)

Hi,

I recently tried to re-format a couple of 520byte/sector SCSI harddisks to 512bytes/sector. Most of them worked fine; however, two formats have been aborted halfway through. One of them always reported "medium format corrupted", and I was able to fix this one by re-formatting the disk which worked on the 3rd try or so.

The other disk keeps reporting "not ready" and I can't seem to re-start the format on this disk. Here's the output of sg_format for this disk:

-------------------------------------------------------------------
lavie:~# sg_format --format -vvv --count=-1 --size=512 /dev/sg1
open /dev/sg1 with flags=0x802
    inquiry cdb: 12 00 00 00 24 00
      duration=4 ms
    SEAGATE   ST314680 CLAR146  7A10   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):  Fixed format, current;  Sense key: Not Ready
 Additional sense: Logical unit not ready, cause not reportable
  Field replaceable unit code: 2
 Raw sense data (in hex):
        70 00 02 00 00 00 00 0a  00 00 00 00 04 00 02 00
        00 00
    requested 252 bytes but got 0 bytes
MODE SENSE (10) command, device not ready
-------------------------------------------------------------------

Test Unit Ready also reports "not ready":

-------------------------------------------------------------------
lavie:~# sg_turs -vvv /dev/sg1
open /dev/sg1 with flags=0x800
    test unit ready cdb: 00 00 00 00 00 00
      duration=0 ms
test unit ready:  Fixed format, current;  Sense key: Not Ready
 Additional sense: Logical unit not ready, cause not reportable
  Field replaceable unit code: 2
 Raw sense data (in hex):
        70 00 02 00 00 00 00 0a  00 00 00 00 04 00 02 00
        00 00
device not ready
-------------------------------------------------------------------

And "start unit" doesn't work either:

-------------------------------------------------------------------
lavie:~# sg_start -vvv /dev/sg1
open /dev/sg1 with flags=0x802
    Start stop unit command: 1b 00 00 00 01 00
      duration=0 ms
start stop unit:  Fixed format, current;  Sense key: Not Ready
 Additional sense: Logical unit not ready, cause not reportable
  Field replaceable unit code: 2
 Raw sense data (in hex):
        70 00 02 00 00 00 00 0a  00 00 00 00 04 00 02 00
        00 00
START STOP UNIT command failed
-------------------------------------------------------------------

(The controller is an MPT FC card, /proc/scsi/mptfc/* says "LSIFC919 B0", just in case it matters)

Anyone know of any other method I could try to recover from this condition? Or is the disk eternally broken?

Thanks,
-Michael


                 reply	other threads:[~2010-03-08 20:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7D05ACFE637E4AE08F92B348397AC586@aeris \
    --to=michael@drueing.de \
    --cc=linux-scsi@vger.kernel.org \
    /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