From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <luis.a.de.sousa@gmail.com>
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com
 [IPv6:2a00:1450:400c:c09::231])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Tue, 15 Dec 2015 09:53:40 +0100 (CET)
Received: by mail-wm0-x231.google.com with SMTP id n186so14861755wmn.0
 for <dm-crypt@saout.de>; Tue, 15 Dec 2015 00:53:40 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <CAEtdG7t713F63L=du_QDdsZ=iLevoM0cEiJ47p-S=GK+u-pKyw@mail.gmail.com>
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>
Date: Tue, 15 Dec 2015 09:53:39 +0100
Message-ID: <CAEtdG7vqPSH2c2VNKwdocJcUcRscq=Ax9JK244NDh1tRyJPqQA@mail.gmail.com>
From: =?UTF-8?Q?Lu=C3=ADs_de_Sousa?= <luis.a.de.sousa@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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

Hello again,

I have just consulted the mail list archive and it seems I am only
recieving a restricted number of replies to this thread. You can find
the smartctl output at the end of this message; it essentially says
nothing. Regarding system messages, I am not getting anything beyond
those I already posted here.

Yesterday I ran badblocks again in read-write mode; it took over 8
hours to complete and reported zero errors. The only new thing is the
output from fsck, that is reporting "Bad magic number in super-block"
- see the full output below. I recieve the same error if try one of
the alternate superblocks suggested.

I thank you once more for your help, I really appreciate you keep it
going in this list.

Lu=C3=ADs


$ sudo smartctl -A -d scsi /dev/sdb
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-48-generic] (local build=
)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=3D=3D=3D START OF READ SMART DATA SECTION =3D=3D=3D
Elements in grown defect list: 0

$ sudo fsck /dev/sdb1
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb1

The superblock could not be read or does not describe a valid ext2/ext3/ext=
4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext=
4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>