From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <arno@wagner.name>
Received: from v6.tansi.org (ns.km31936-01.keymachine.de [87.118.116.4])
 by mail.server123.net (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Mon, 14 Dec 2015 21:39:24 +0100 (CET)
Received: from gatewagner.dyndns.org (77-57-54-224.dclient.hispeed.ch
 [77.57.54.224]) by v6.tansi.org (Postfix) with ESMTPA id 5684B20DC13E
 for <dm-crypt@saout.de>; Mon, 14 Dec 2015 21:39:24 +0100 (CET)
Date: Mon, 14 Dec 2015 21:39:23 +0100
From: Arno Wagner <arno@wagner.name>
Message-ID: <20151214203923.GA25321@tansi.org>
References: <CAEtdG7uDuvJDys=TT9-Ou5zR8VMCFkqAiWJDLaR5dPhicDfVTA@mail.gmail.com>
 <1308232842.375292.1449777297163.JavaMail.yahoo@mail.yahoo.com>
 <CAEtdG7sSJQC79cAqCGcMwREH_nTb8NakiXSfCr3+vv3vyo0w+A@mail.gmail.com>
 <CAEtdG7vzPtjzcaD0O4Fa4QoHLApMiBo4vaWRL0x8H-9aCbr+KQ@mail.gmail.com>
 <566ADEFA.7090509@gmail.com>
 <CAEtdG7vAYRf=t==w7vJ-gvfAaS85mT66fTOSKAhJeQfyefs6WQ@mail.gmail.com>
 <566DCC8B.10401@gmail.com>
 <CAEtdG7t713F63L=du_QDdsZ=iLevoM0cEiJ47p-S=GK+u-pKyw@mail.gmail.com>
 <n4n6on$nji$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <n4n6on$nji$1@ger.gmane.org>
Subject: Re: [dm-crypt] Fwd: Cannot wipe header on device
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

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