Swapping geli devices between machines: MD5 hash mismatch
Jan Henrik Sylvester
me at janh.de
Wed Feb 8 02:54:19 UTC 2012
I tried to attach a geli encrypted partition from a disk of a different
machine attached via eSATA, but I got:
geli: MD5 hash mismatch for ada1s2e.
Putting the disk back to the old machine, I was able to attach and use
the geli encrypted partition without an error.
Before I investigate further, is this supported in general?
The original machine is 9.0-RELEASE/i386 and does not support aesni. The
disk in question is the only harddisk and shows up as:
ada0 at ata0 bus 0 scbus0 target 0 lun 0
ada0: <ST9160827AS 3.AAA> ATA-8 SATA 1.x device
ada0: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes)
ada0: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad0
GEOM: ada0s2: geometry does not match label (255h,63s != 16h,63s).
The machine with the error is 9.0-RELEASE/amd64 and has aesni loaded.
The disk in question is attached via eSATA and shows up as:
ada1 at ahcich3 bus 0 scbus3 target 0 lun 0
ada1: <ST9160827AS 3.AAA> ATA-8 SATA 1.x device
ada1: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C)
ada1: Previously was known as ad10
GEOM: ada1s2: geometry does not match label (255h,63s != 16h,63s).
The geli partition was initialized on 9.0-RELEASE/i386.
The relevant data from fdisk are:
cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl)
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 83886081, size 125826429 (61438 Meg), flag 0
beg: cyl 1023/ head 255/ sector 63;
end: cyl 1023/ head 255/ sector 63
The bsdlabel is:
a: 48234496 0 4.2BSD 0 0 0
b: 2097152 48234496 swap
c: 125826429 0 unused 0 0 # "raw" part,
don't edit
e: 75494781 50331648 4.2BSD 0 0 0
I was able to mount and use the other (unencrypted) partition on the
machine with the geli error.
The major differences -- besides the completely different hardware --
are: SATA/eSATA, i386/amd64, and software/aesni.
What could be the issue here?
Thanks,
Jan Henrik
More information about the freebsd-questions
mailing list