From: "T. Ermlich" <pelegrine@gmx.net>
To: Gordon Henderson <gordon@drogon.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Broken harddisk
Date: Sat, 29 Jan 2005 19:18:06 +0100 [thread overview]
Message-ID: <41FBD35E.2020404@gmx.net> (raw)
In-Reply-To: <41FBBE1B.7060406@gmx.net>
Some more info
T. Ermlich scribbled on 29.01.2005 17:47:
[...]
>> badblocks -s -c 256 /dev/sdb6
>> badblocks -s -c 256 /dev/sdb7
>> badblocks -s -c 256 /dev/sdb8
suse92:/ # badblocks -s -c 256 /dev/sda6
Suche nach defekten Blöcken (Nur-Lesen-Modus):done
suse92:/ # badblocks -s -c 256 /dev/sda7
Suche nach defekten Blöcken (Nur-Lesen-Modus):done
suse92:/ # badblocks -s -c 256 /dev/sda8
Suche nach defekten Blöcken (Nur-Lesen-Modus):done
suse92:/ # badblocks -s -c 256 /dev/sda5
Suche nach defekten Blöcken (Nur-Lesen-Modus): 26188800/ 52436097
Then the system hungs .. I did it twice, and twice it hung.
The last messages in /var/log/messages are:
Jan 29 19:06:11 suse92 kernel: Current sda: sense key Medium Error
Jan 29 19:06:11 suse92 kernel: Additional sense: Unrecovered read error
- auto reallocate failed
Jan 29 19:06:11 suse92 kernel: end_request: I/O error, dev sda, sector
52460485
Jan 29 19:06:12 suse92 kernel: ata2: status=0x51 { DriveReady
SeekComplete Error }
Jan 29 19:06:12 suse92 kernel: ata2: error=0x40 { UncorrectableError }
Jan 29 19:06:12 suse92 kernel: scsi1: ERROR on channel 0, id 0, lun 0,
CDB: Read (10) 00 03 20 7b c6 00 00 b8 00
Jan 29 19:06:12 suse92 kernel: Current sda: sense key Medium Error
Jan 29 19:06:12 suse92 kernel: Additional sense: Unrecovered read error
- auto reallocate failed
Jan 29 19:06:12 suse92 kernel: end_request: I/O error, dev sda, sector
52460486
Jan 29 19:06:13 suse92 kernel: ata2: status=0x51 { DriveReady
SeekComplete Error }
Jan 29 19:06:13 suse92 kernel: ata2: error=0x40 { UncorrectableError }
Jan 29 19:06:13 suse92 kernel: scsi1: ERROR on channel 0, id 0, lun 0,
CDB: Read (10) 00 03 20 7b c7 00 00 b7 00
Jan 29 19:06:13 suse92 kernel: Current sda: sense key Medium Error
Jan 29 19:06:13 suse92 kernel: Additional sense: Unrecovered read error
- auto reallocate failed
Jan 29 19:06:13 suse92 kernel: end_request: I/O error, dev sda, sector
52460487
Jan 29 19:06:14 suse92 kernel: ata2: status=0x51 { DriveReady
SeekComplete Error }
Jan 29 19:06:14 suse92 kernel: ata2: error=0x40 { UncorrectableError }
Jan 29 19:06:14 suse92 kernel: scsi1: ERROR on channel 0, id 0, lun 0,
CDB: Read (10) 00 03 20 7b c8 00 00 b6 00
Jan 29 19:06:14 suse92 kernel: Current sda: sense key Medium Error
Jan 29 19:06:14 suse92 kernel: Additional sense: Unrecovered read error
- auto reallocate failed
Jan 29 19:06:14 suse92 kernel: end_request: I/O error, dev sda, sector
52460488
Well, now I think, as only sda5 is involved, I'll re-format it, check it
for badblocks, and copy the previciously copied data back on it ...
c y
Torsten
next prev parent reply other threads:[~2005-01-29 18:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 0:22 Broken harddisk T. Ermlich
2005-01-29 12:46 ` Gordon Henderson
2005-01-29 15:34 ` T. Ermlich
2005-01-29 15:56 ` Gordon Henderson
2005-01-29 16:19 ` Guy
2005-01-29 18:31 ` Mike Hardy
2005-01-29 23:30 ` berk walker
2005-02-01 15:02 ` Robin Bowes
2005-02-01 22:57 ` Luca Berra
2005-02-01 23:24 ` Robin Bowes
2005-01-29 16:47 ` T. Ermlich
2005-01-29 18:18 ` T. Ermlich [this message]
2005-01-29 23:12 ` T. Ermlich
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=41FBD35E.2020404@gmx.net \
--to=pelegrine@gmx.net \
--cc=gordon@drogon.net \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).