From: Nix <nix@esperi.org.uk>
To: Wols Lists <antlists@youngman.org.uk>
Cc: Phil Turmel <philip@turmel.org>,
Roger Heflin <rogerheflin@gmail.com>,
David T-G <davidtg+robot@justpickone.org>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: hardware recovery and RAID5 services
Date: Mon, 31 Jan 2022 15:39:58 +0000 [thread overview]
Message-ID: <87leyvvrqp.fsf@esperi.org.uk> (raw)
In-Reply-To: <c3b7a580-952f-7c7a-fddc-88ca0b5fde84@youngman.org.uk> (Wols Lists's message of "Sat, 29 Jan 2022 15:36:21 +0000")
On 29 Jan 2022, Wols Lists told this:
> I believe there is also a way of injecting a hardware error onto a
> drive. Unless you can take a backup of the backup :-) I wouldn't
> recommend it at the moment, but there's some ATA command or whatever
> that tells the drive to flag a sector as bad, and return a read error
> until it's over-written.
See hdparm --make-bad-sector. The manpage says "EXCEPTIONALLY DANGEROUS.
DO NOT USE THIS OPTION!!". It is not lying. :)
(This is also --write-sector, which is merely VERY DANGEROUS, but can be
used to force rewrites of bad sectors. Make sure you get the sector
number right! Needless to say, if you don't, it's too late, and there's
no real way to test in advance...)
next prev parent reply other threads:[~2022-01-31 15:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 16:48 hardware recovery and RAID5 services David T-G
2022-01-21 19:31 ` Wols Lists
2022-01-21 19:34 ` Wols Lists
2022-01-21 19:47 ` Wols Lists
2022-01-22 14:23 ` Roger Heflin
2022-01-22 22:23 ` Phil Turmel
2022-01-23 0:20 ` anthony
2022-01-29 15:25 ` David T-G
2022-01-29 15:36 ` Wols Lists
2022-01-31 15:39 ` Nix [this message]
2022-01-31 18:59 ` Roger Heflin
2022-01-31 19:07 ` Geoff Back
2022-01-31 19:21 ` Phil Turmel
2022-01-31 19:46 ` Roger Heflin
2022-01-31 20:04 ` Geoff Back
2022-01-31 20:53 ` Wols Lists
2022-01-29 15:21 ` David T-G
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=87leyvvrqp.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=antlists@youngman.org.uk \
--cc=davidtg+robot@justpickone.org \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.org \
--cc=rogerheflin@gmail.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 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.