All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Christensen <dpchrist@holgerdanske.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Cannot wipe header on device
Date: Thu, 10 Dec 2015 11:06:13 -0800	[thread overview]
Message-ID: <5669CD25.1060102@holgerdanske.com> (raw)
In-Reply-To: <CAEtdG7vb9Em9xLDkcyzeixfUukwWjQamzBd+iR0KfARR2pgiWA@mail.gmail.com>

On 12/10/2015 02:18 AM, Luís de Sousa wrote:
> I am trying to encrypt an external hard drive on Ubuntu 14.04 ...
> $ sudo cryptsetup -y -v luksFormat /dev/sdb1

Why "-y"?  It seems to be the default when I do "cryptsetup luksFormat" 
on Debian.


> Cannot wipe header on device /dev/sdb1.
> Command failed with code 5: Cannot wipe header on device /dev/sdb1.
...
> [ 3208.140990] usb 2-1.4: New USB device found, idVendor=059f, idProduct=0651
> [ 3208.141001] usb 2-1.4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [ 3208.141024] usb 2-1.4: Product: LaCie Hard Drive USB
> [ 3208.141031] usb 2-1.4: Manufacturer: LaCie

I prefer StarTech.


> [ 3209.176917] scsi 4:0:0:0: Direct-Access     SEAGATE  ST3160812A
>    3.AA PQ: 0 ANSI: 2
> [ 3209.177561] sd 4:0:0:0: Attached scsi generic sg2 type 0
> [ 3209.181342] sd 4:0:0:0: [sdb] 312581808 512-byte logical blocks:
> (160 GB/149 GiB)

That's an older PATA drive:

     http://www.seagate.com/support/disc/manuals/ata/100389997c.pdf


> $ tail /var/log/syslog
> Dec  8 09:18:20 MekanikDestruktiwKommandoh kernel: [ 3698.016311]
> end_request: critical target error, dev sdb, sector 0
> Dec  8 09:18:28 MekanikDestruktiwKommandoh wpa_supplicant[1188]:
> wlan0: CTRL-EVENT-SCAN-STARTED

Have you run the Seagate SeaTools Diagostics?  I prefer the DOS version 
-- it's a stand-alone bootable CD:

     http://www.seagate.com/support/downloads/seatools/


If SeaTools finds a problem:

1.  Plug the drive into a different machine and try again.

2.  If the problem persists, open up the USB case, pull the drive, put 
it into a desktop/ server machine with a PATA interface, and run 
SeaTools again.


Otherwise, it's something in Ubuntu.  Try another Linux distribution.


David

      parent reply	other threads:[~2015-12-10 19:23 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
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 ` David Christensen [this message]

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=5669CD25.1060102@holgerdanske.com \
    --to=dpchrist@holgerdanske.com \
    --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.