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] mistake with luksFormat
Date: Sat, 23 Dec 2017 19:16:02 +0100	[thread overview]
Message-ID: <20171223181602.GA25992@tansi.org> (raw)
In-Reply-To: <20171223172211.D93E8124CA44@shakotay.alphanet.ch>


Hi Amel,

cryptsetup does nothing to the drive. 
It cannot destroy hardware.

It sounds like the disk died at the same time 
you did the overwrite by pure random chance.

Regards,
Arno

On Sat, Dec 23, 2017 at 18:22:11 CET, A. Kapetanovic wrote:
> Thanks Arno,
> 
> If I have good understood, you think I can throw the HDD ? This command
> 
> cryptsetup -y -v luksFormat /dev/sdb
> 
> Simply destroys the drive ?
> 
> (I didn't ask any other operations on the sdb).
> 
> Regards,
> 
> Amel
> 
> 
> Arno Wagner writes:
> 
> >Hi Amel,
> >
> >I would say your disk died while you were doing the overwrite.
> >That is assuming nothing the OS uses was on sdb.
> >There is no logout-timer in ssh and anyways, it would not freeze.
> >
> >Regards,
> >Arno
> >
> >
> >On Sat, Dec 23, 2017 at 11:49:22 CET, A. Kapetanovic wrote:
> >>Hi everybody,
> >>
> >>I did something wrong, can please someone help me ? I followed these
> >>instructions to encrypt a internal HDD :
> >>
> >>https://www.cyberciti.biz/hardware/howto-linux-hard-disk-encryption-with-luks-cryptsetup-command/
> >>
> >>Unfortunately I did
> >>
> >>cryptsetup -y -v luksFormat /dev/sdb
> >>
> >>and not
> >>
> >>cryptsetup -y -v luksFormat /dev/sdb1
> >>
> >>After that I used fdisk to create sdb1 and did
> >>
> >>cryptsetup -y -v luksFormat /dev/sdb1
> >>cryptsetup luksOpen /dev/sdb1 prod
> >>
> >>and
> >>
> >>pv -tpreb /dev/zero | dd of=/dev/mapper/prod bs=128M
> >>
> >>all this I did through ssh
> >>
> >>but :
> >>
> >>1. After a time my shell was frozen. Perhaps has ssh a timer ?
> >>2. My HDD did repetitive noises several hours (now that has stopped), even
> >>after a reboot.
> >>
> >>So, my question please : have I to do something to erase what I did with
> >>
> >>cryptsetup -y -v luksFormat /dev/sdb
> >>
> >>And what is it ?
> >>
> >>Have I to do something more, or were the noises of the HDD simple my
> >>
> >>pv -tpreb /dev/zero | dd of=/dev/mapper/prod bs=128M
> >>
> >>command, even if
> >>
> >>ps -a | grep dd
> >>
> >>didn't display anything ?
> >>
> >>
> >>Thanks, best regards,
> >>
> >>Amel   :)
> >>_______________________________________________
> >>dm-crypt mailing list
> >>dm-crypt@saout.de
> >>http://www.saout.de/mailman/listinfo/dm-crypt
> >
> >--
> >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
> >_______________________________________________
> >dm-crypt mailing list
> >dm-crypt@saout.de
> >http://www.saout.de/mailman/listinfo/dm-crypt
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

-- 
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:[~2017-12-23 18:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-23 10:49 [dm-crypt] mistake with luksFormat A. Kapetanovic
2017-12-23 14:01 ` Arno Wagner
2017-12-23 17:22   ` A. Kapetanovic
2017-12-23 18:16     ` Arno Wagner [this message]
2017-12-23 19:23 ` Michael Kjörling
2017-12-24  2:04   ` David Christensen
2017-12-31  0:03     ` Wensday
2018-01-01 21:35       ` H McCurdy

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=20171223181602.GA25992@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.