Error on Linux / Raid 1 with encryption
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
hi, i have a raid 1 with 2x2TB hard drives. I used windows to encrypt the 2TB Raid which worked as expected. On Fedora i used Truecrypt which also worked as expected, simply mounting the device and everything was fine. Now i have Ubuntu 15.04 and Veracrypt, but seems like impossible to mount it. I guess it has nothing to do directly with veracrypt, more with how ubuntu deals the device, but maybe someone knows a solution for this??
when i try to mount the raid i can see in dmesg:
[ 6574.363730] device-mapper: table: 252:2: crypt: Device lookup failed
[ 6574.363735] device-mapper: ioctl: error adding target to table
[ 6575.180613] sdd: sdd1
[ 6575.524704] device-mapper: table: 252:2: crypt: Device lookup failed
[ 6575.524708] device-mapper: ioctl: error adding target to table
sdd and sdc are the devices used for the raid which holds the encrypted system.
On windows i can mount the raid without any problem in veracrypt.
Update: i noticed something whats a bit wierd:
Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xfee9b8ca
Device Boot Start End Sectors Size Id Type
/dev/sdd1 2052 3907018259 3907016208 1.8T 7 HPFS/NTFS/exFAT
Partition 2 beginnt nicht an einer physikalischen Sektorgrenze.
Disk /dev/mapper/isw_bifaffceif_Raid: 1.8 TiB, 2000395833344 bytes, 3907023112 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xfee9b8ca
Device Boot Start End Sectors Size Id Type
/dev/mapper/isw_bifaffceif_Raid1 2052 3907018259 3907016208 1.8T 7 HPFS/NTF
Partition 2 beginnt nicht an einer physikalischen Sektorgrenze.
The Raid1 device should be used, but seems like there is "something" wrong??
Smartmontools does not report anything.
If no one can tell me how to fix that, i will backup the encrypted drive, destroy it and rebuild it. Just found this as information: http://askubuntu.com/questions/156994/partition-does-not-start-on-physical-sector-boundary
Indeed, your partition starts at logical sector 2052 = 1050624 bytes which is not a multiple of 4096 but it should work nevertheless since your drive supports 512-bytes emulation.
Since it works on Windows, it appears that Linux kernel doesn't handle correctly this kind of alignment issues as it is the case on Windows.
If possible, try to rebuild your RAID by making the partition start at a logical sector aligned with the 4096-bytes boundary (for example make it start at logical sector 2056 = 1052672 bytes).