Found the attached document which basically helped me recover my iSCSI LUNs. I copied by iSCSI LUN files to the backup locations and rebuild by NAS volumes. I then follow the procedure #3 in the document to get my iSCSI LUNs back.
Showing posts with label QNAP. Show all posts
Showing posts with label QNAP. Show all posts
Friday, May 15, 2020
My QNAP TS-412 had a major issue, 2 of the RAID5 disks decided to fail at the same time. Luckily QNAP was still up and running and allow READ-ONLY access to my data. However, all the iSCSI LUNs are not accessible anymore from my iSCSI clients.
Found the attached document which basically helped me recover my iSCSI LUNs. I copied by iSCSI LUN files to the backup locations and rebuild by NAS volumes. I then follow the procedure #3 in the document to get my iSCSI LUNs back.
Found the attached document which basically helped me recover my iSCSI LUNs. I copied by iSCSI LUN files to the backup locations and rebuild by NAS volumes. I then follow the procedure #3 in the document to get my iSCSI LUNs back.
Wednesday, January 07, 2015
QNAP Reset Permissions
To reset QNAP file share permissions
SSH login to it
Run:
[#] set_volume_mode <Share Name>
For example
[#] set_volume_mode Public
Volume: news
Path: /share/MD0_DATA/news
this will Set directory mode to 0777 and file mode to 0666(keep execute permission)
SSH login to it
Run:
[#] set_volume_mode <Share Name>
For example
[#] set_volume_mode Public
Volume: news
Path: /share/MD0_DATA/news
this will Set directory mode to 0777 and file mode to 0666(keep execute permission)
Sunday, June 22, 2014
BitLocker Day
Today is the BitLocker day. I am BitLocking my file system with BitLocker. I have a QNAP and a File Server running Windows 2012 R2. My client machines, Windows 8.1 is having mapped drives that attach to the network shares on the File Server.
To secure the files:
Firstly I have a iSCSI drive set at QNAP and my File Server is using that drive by iSCSI initiator, lets say I: drive
Secondly, I create a VHDX file and store it in the I: drive. This newly created VHDX file is then mapped as a volume, lets say G: drive.
Thirdly, I have my data stored in the G: drive and share it as necessary to be used by my Windows 8.1 client.
Lastly, I enable BitLocker on the G: drive so that the VHDX is encrypted.
By having this configuration, the actual data is stored within the VHDX file which is encrypted by BitLocker. The I: drive is not encrypted - however it only contains .VHDX file(s) that need password if you want to mount that.
I purposely do not enable BitLocker auto-mount on G: drive. This to ensure if both File Server and QNAP are stolen, my data is not exposed. The only disadvantage of this method is that I need to mount the G: drive every time the File Server is rebooted - no biggie.
To secure the files:
Firstly I have a iSCSI drive set at QNAP and my File Server is using that drive by iSCSI initiator, lets say I: drive
Secondly, I create a VHDX file and store it in the I: drive. This newly created VHDX file is then mapped as a volume, lets say G: drive.
Thirdly, I have my data stored in the G: drive and share it as necessary to be used by my Windows 8.1 client.
Lastly, I enable BitLocker on the G: drive so that the VHDX is encrypted.
By having this configuration, the actual data is stored within the VHDX file which is encrypted by BitLocker. The I: drive is not encrypted - however it only contains .VHDX file(s) that need password if you want to mount that.
I purposely do not enable BitLocker auto-mount on G: drive. This to ensure if both File Server and QNAP are stolen, my data is not exposed. The only disadvantage of this method is that I need to mount the G: drive every time the File Server is rebooted - no biggie.