Re: [dm-crypt] mistake with luksFormat

[Arno Wagner <arno@wagner.name>]

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