the latest vol_id gives more verbose output...this is probably where the problem lies:
root@bigboy:~# vol_id /dev/sda2 ID_FS_USAGE=crypto ID_FS_TYPE=crypto_LUKS ID_FS_VERSION= ID_FS_UUID=18942279-eaf5-4e86-a174-8b04b5d3127e ID_FS_LABEL= ID_FS_LABEL_SAFE= root@bigboy:~#
it seems that luks has left some traces on this partition.
BUT
root@bigboy:~# dumpe2fs /dev/sda2 | head -n 5 dumpe2fs 1.40-WIP (14-Nov-2006) Filesystem volume name: root Last mounted on: <not available> Filesystem UUID: caa107c2-d2ba-11db-a205-0013cea46521 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) root@bigboy:~#
NB the UUIDs are different. how does that work? i dont really know what this means but i hope its useful to somebody...
the latest vol_id gives more verbose output...this is probably where the problem lies:
root@bigboy:~# vol_id /dev/sda2 crypto_ LUKS 18942279- eaf5-4e86- a174-8b04b5d312 7e
ID_FS_USAGE=crypto
ID_FS_TYPE=
ID_FS_VERSION=
ID_FS_UUID=
ID_FS_LABEL=
ID_FS_LABEL_SAFE=
root@bigboy:~#
it seems that luks has left some traces on this partition.
BUT
root@bigboy:~# dumpe2fs /dev/sda2 | head -n 5 d2ba-11db- a205-0013cea465 21
dumpe2fs 1.40-WIP (14-Nov-2006)
Filesystem volume name: root
Last mounted on: <not available>
Filesystem UUID: caa107c2-
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
root@bigboy:~#
NB the UUIDs are different. how does that work? i dont really know what this means but i hope its useful to somebody...