All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Fwd: Cannot wipe header on device
Date: Mon, 14 Dec 2015 21:39:23 +0100	[thread overview]
Message-ID: <20151214203923.GA25321@tansi.org> (raw)
In-Reply-To: <n4n6on$nji$1@ger.gmane.org>

On Mon, Dec 14, 2015 at 20:53:59 CET, Robert Nichols wrote:
> On 12/14/2015 02:44 AM, Luís de Sousa wrote:
> >I understand this is not an issue with cryptsetup, but would anyone
> >have suggestions on how to proceed? Is there any hope of "fixing"
> >this, e.g. marking this sector as unusable?
> >
> >Thank you,
> >
> >Luís
> >
> >$ sudo dd if=/dev/zero of=/dev/sdb1 bs=4096 count=1 oflag=sync,direct
> >dd: error writing ‘/dev/sdb1’: Remote I/O error
> >1+0 records in
> >0+0 records out
> >0 bytes (0 B) copied, 0.00142455 s, 0.0 kB/s
> 
> There should also have been some system error messages logged which
> might be informative.
> 
> When any reasonably modern (last 20 years, or so) drive shows an
> I/O error on a write operation, it generally means that the drive
> has run out of spare sectors or has some problem other than media
> errors.  Such a drive is long past the time it should have been
> replaced.

I second that. Errors on reads may be fixable (though it is not
a very good idea to try), errors on write signal imminent death.
 
> It would be interesting to see the output from
> "smartctl -A /dev/sdb", if the interface supports it. (Not all
> USB <=> SATA bridge chips support the necessary commands.)

Especially not very old ones.

Regards,
Arno
-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

  reply	other threads:[~2015-12-14 20:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 10:18 [dm-crypt] Cannot wipe header on device Luís de Sousa
2015-12-10 13:35 ` Michael Kjörling
2015-12-10 16:49 ` H McCurdy
2015-12-10 17:24   ` Luís de Sousa
2015-12-10 17:37     ` H McCurdy
2015-12-10 18:25       ` Luís de Sousa
2015-12-10 19:54         ` H McCurdy
2015-12-11  4:33           ` Arno Wagner
     [not found]           ` <CAEtdG7sSJQC79cAqCGcMwREH_nTb8NakiXSfCr3+vv3vyo0w+A@mail.gmail.com>
2015-12-11 14:09             ` [dm-crypt] Fwd: " Luís de Sousa
2015-12-11 14:34               ` Milan Broz
2015-12-11 14:56                 ` Luís de Sousa
2015-12-11 15:10                   ` Milan Broz
2015-12-13 19:52                   ` Milan Broz
2015-12-14  8:44                     ` Luís de Sousa
2015-12-14 14:46                       ` Sven Eschenberg
2015-12-14 19:53                       ` Robert Nichols
2015-12-14 20:39                         ` Arno Wagner [this message]
2015-12-15  8:53                       ` Luís de Sousa
2015-12-15  9:37                         ` Milan Broz
2015-12-15 17:53                         ` Robert Nichols
2015-12-16  4:06                         ` David Christensen
2015-12-10 19:06 ` [dm-crypt] " David Christensen

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=20151214203923.GA25321@tansi.org \
    --to=arno@wagner.name \
    --cc=dm-crypt@saout.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.