meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
hw:qnap_ts-228 [2023/02/21 17:53] – niziakhw:qnap_ts-228 [2023/03/16 13:19] (current) – niziak
Line 169: Line 169:
 Volume is encrypted. It contains standard LUKS header. Volume is encrypted. It contains standard LUKS header.
 Google says encryption password is derived from user supplied password using not know algo. Google says encryption password is derived from user supplied password using not know algo.
-It points to NAS local utility+It points to NAS local utility:
  
 <code bash> <code bash>
Line 175: Line 175:
 Encrypted passwd is: ………………………………….. Encrypted passwd is: …………………………………..
 </code> </code>
 +
 +Reference: 
 +  * [[https://unix.stackexchange.com/questions/685821/how-to-mount-on-linux-a-qnap-external-drive-with-luks-partition]]
 +  * [[https://www.linux-howto.info/mount-qnap-encrypted-volume/]]
  
 ==== Try to run x86 QTS in Proxmox VM ==== ==== Try to run x86 QTS in Proxmox VM ====
Line 189: Line 193:
  
 And it works. Generated password opens LUKS storage. And it works. Generated password opens LUKS storage.
 +
 +==== mkpasswd ====
 +
 +After making Docker image, I found post on QNAP forum that the password can be generated using simple MD5 hash:
 +<code bash>
 +mkpasswd -m md5 -S YCCaQNAP
 +</code>
  
  
 <code bash> <code bash>
 cryptsetup luksOpen /dev/vg1/lv1 nas cryptsetup luksOpen /dev/vg1/lv1 nas
 +mount /dev/mapper/nas /mnt/nas
 </code> </code>
  
Line 204: Line 216:
  
  
 +===== unmount and shutdown =====
  
 +<code bash>
 +umount /dev/mapper/nas
 +cryptsetup luksClose nas
 +dmsetup remove vg1-lv544
 +dmsetup remove vg1-lv1
 +mdadm --stop /dev/md1
 +
 +mdadm --stop /dev/md256
 +mdadm --stop /dev/md9
 +mdadm --stop /dev/md322
 +mdadm --stop /dev/md13
 +</code>