On Sunday 01 November 2009 10:40:29 Anne Wilson wrote: > On Sunday 01 November 2009 01:54:42 Ben Boeckel wrote: > > Anne Wilson wrote: > > > On Saturday 31 October 2009 16:19:32 Patrick Boutilier wrote: > > >> This should work: > > >> > > >> Copy data from SD card to hard drive, format SD card, copy data back > > >> to SD card. > > > > > > There's one big problem. Partition managers don't recognise > > > LUKS-encrypted drives, and I very much doubt if format does either. It > > > will have to be a command that partners the encryption command, I > > > guess. > > > > > > Anne > > > > Once the partition is decrypted, the block device under /dev/mapper > > should be readable by a partition manager. > > Well, mounting the device in Dolphin, I can see the data. Oops - now I > realise that it was the Windows data partition that I was seeing. There is > a second 'Volume' in Dolphin, and clicking on that bounces immediately to > 'home' (still in Places). This is the location '/media/-home' which > contains only lost+found. Clicking on that brings the message 'Could not > enter folder /media/-home/lost+found'. Entering it as root it says that > there are 0 items. > > Qtparted sees only my hard drive. I think this output from fdisk refers to > it, though: > > Disk /dev/mmcblk1: 7969 MB, 7969177600 bytes > 255 heads, 63 sectors/track, 968 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Disk identifier: 0x000eb694 > > Device Boot Start End Blocks Id System > /dev/mmcblk1p1 * 1 765 6144831 83 Linux > /dev/mmcblk1p2 766 903 1108485 83 Linux > /dev/mmcblk1p3 904 968 522112+ 82 Linux swap / > Solaris > > Disk /dev/dm-0: 1134 MB, 1134560256 bytes > 255 heads, 63 sectors/track, 137 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Disk identifier: 0x00000000 > > Disk /dev/dm-0 doesn't contain a valid partition table > > Fdisk and formatting is one place where I do not experiment :-), too > dangerous, so I welcome advice from someone with more experience. > > I have used fdisk to prepare an empty disk, but this is definitely beyond > my experience level. > Between finding an blog on the subject and reading the FM, I've come to the conclusion that the only way to handle this is through cryptsetup - which makes sense. The problem is that as far as I can see you can't get anywhere without knowing either the device name or it's mapping under /dev - and probably both. Based on the information above, I tried cryptsetup luksDump /dev/mmcblk0 Command failed: /dev/mmcblk0 is not a LUKS partition I don't know whether /dev/dm-0 is part of this puzzle or not, but that also is identified as not being a LUKS partition. Any ideas on how to proceed? Anne -- New to KDE4? - get help from http://userbase.kde.org Just found a cool new feature? Add it to UserBase -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://lists.fedoraproject.org/pipermail/kde/attachments/20091101/d061847a/attachment.bin
