public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: xfs_repair Input/output error
Date: Wed, 29 Apr 2009 06:28:16 +0200	[thread overview]
Message-ID: <200904290628.20924@zmi.at> (raw)
In-Reply-To: <ff2243530904282040i1bb2cf12v3a329b045edf2f50@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1861 bytes --]

On Mittwoch 29 April 2009 Cory Coager wrote:
> When attempting to mount the partition the drive makes some funny
> noises and these messages spit out on the console:
>
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=268552872,
> high=16, low=117416, sector=268552868
> ide: failed opcode was: unknown
> end_request: I/O error, dev hda, sector 268552868

This is definitely your drive gone bad.

> I believe the drive is fine because check_ide_smart reports:

If the drive "makes funny noises" and I/O errors are logged, it has bad 
sectors. Try with
# smartctl -a /dev/sda
and look for a line like this:
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always  -  0

If the last number is >0, your drive has problems - replace it!

For a full SMART check, please try:
smartctl --smart=on --offlineauto=on --saveauto=on --test=long /dev/sda

This tells your drive to make a long selftest. It prints the estimated 
time for the test to run (usually 1-3h). Then check your smart values 
again. You should try to not use your drive during this time.

> I can xxd and dd this partition without getting any console errors. 

It is possible the drive remapped the bad sectors itself.

> I can also mount the partition with -o ro,norecovery.  How do I repair
> this and recover my data?

Plug in new drive.
Boot from recovery cd
dd if=/dev/sda of=/dev/sdb 
remove old drive
xfs_repair
enjoy

mfg zmi
-- 
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4


[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2009-04-29  4:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29  3:40 xfs_repair Input/output error Cory Coager
2009-04-29  4:28 ` Michael Monnerie [this message]

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=200904290628.20924@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --cc=xfs@oss.sgi.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