Interesting. This one was new for me. Arno On Mon, Oct 28, 2013 at 20:28:31 CET, metageek wrote: > Ok, problem solved now, > > the last poster was spot on, for some reason that I cannot figure out, there > was a regular file /dev/sdb1. After removing it (with the drive > disconnected), everything works. > > The drive is a Seagate Backup Plus portable drive > > I'm running cryptsetup version 1.4.3 (the version in Slackware64 14.0, > running kernel 3.8.8) > > # dd if=/dev/zero of=/dev/sdb bs=1GB > dd: writing '/dev/sdb': No space left on device > 1001+0 records in > 1000+0 records out > 1000204885504 bytes (1.0 TB) copied, 12064.5 s, 82.9 MB/s > > so it is really 1.0 TB there (not a fake one) > > #smartctl -i > /dev/sdb: Unknown USB bridge [0x0bc2:0xa013 (0x100)] > > Now, status reports the full drive and no loopback: > > # cryptsetup -v status pjhomecrypt > /dev/mapper/pjhomecrypt is active. > type: LUKS1 > cipher: aes-cbc-essiv:sha256 > keysize: 256 bits > device: /dev/sdb1 > offset: 4096 sectors > size: 1953521008 sectors > mode: read/write > Command successful. > > The filesystem was created successfully with ~ 1 TB. > > Problem solved. > Thanks everyone! > > > > _______________________________________________ > dm-crypt mailing list > dm-crypt@xxxxxxxx > http://www.saout.de/mailman/listinfo/dm-crypt -- Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@xxxxxxxxxxx GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718 ---- There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult. --Tony Hoare _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
