Derek_

Yeah, nah I'm far too much a noob, and i'm not likely to change the encryption password very often at all. But if you have this scripting wizardry, perhaps suggest it to the devs who can GUIfy it and thank you for your brilliance

Simple.. yeah 😮

Yes, i forgot to mention that parity wasn't part of it, i guess i implied it as parity isn't encrypted. But thank you for clarifying that. I found it quite handy to use the terminal command: # lsblk ...which outputted all my devices. Anything with the word "crypt" against it was what i added/removed the password for. I've trimmed my output to just show the encrypted devices, so you won't see parity or anything else. Below, sdX is my cache (btrfs encrypted RAID1), mdX is my data array but not the parity disk as @doron has mentioned (XFS encrypted): sdb 8:16 0 238.5G 0 disk └─sdb1 8:17 0 238.5G 0 part └─sdb1 254:2 0 238.5G 0 crypt <<< This one sdc 8:32 0 238.5G 0 disk └─sdc1 8:33 0 238.5G 0 part └─sdc1 254:3 0 238.5G 0 crypt /mnt/cache <<< This one md1 9:1 0 5.5T 0 md └─md1 254:0 0 5.5T 0 crypt /mnt/disk1 <<< This one md2 9:2 0 5.5T 0 md └─md2 254:1 0 5.5T 0 crypt /mnt/disk2 <<< This one The community here is really good Glad i paid up, i'm getting the hang of it

@doron Thank you. I do appreciate your patience with me Where X is the disk number, and done for all encrypted disks either array or cache: # cryptsetup luksAddKey /dev/mdX reboot & test # cryptsetup luksRemoveKey /dev/mdX reboot & test I did per instructed, rebooted, used the new key and everything was fine. My only docker functioned normally and i could read data i had on the array and in the cache drives (very little atm). I copied a fresh file across and it was fine too. Removed the old password per instructions and rebooted. Tried the old password: as expected - it doesn't work. New password: still works. I did not do my 'quick way' (change, rather than add > remove) because i agree it is far more risky, and i think maybe it'd cause problems with anything was running. So i didn't do it, and i don't recommend anyone else tries it. So THANK YOU (and 'limetech'). Last question(s): i read that there's 8 key slots available to use. Do i still have 7 left, or is a used/deleted slot forever taken? And does will it matter what slot this, or any other key is in? Does this new key now revert to the 1st slot?

Thanks again. What about Dockers and VMs - should they be stopped?

Noob question.. what's the difference between the Binhex Krusader and the... non-Binhex Krusader?

Thanks @doron, that is somewhat clearer. Should the array be stopped before doing the deed?

I came here looking for an answer to the same question I understand your apprehension, and it's not helped that we can't seem to find clear instructions in the Wiki (that i could see): https://wiki.unraid.net/index.php/UnRAID_Topical_Index#Encryption and the forum post above is many pages long, isn't current (as is the nature of forums) and anyone could put an incorrect solution that be followed. I had trouble following the conversation, let alone finding the specific instructions to change the password. What i did see was something about adding and then removing keys. I believe there's an easier way but i don't know how to apply it to unRAID (i.e. the /dev/??? - no idea what to put there) so try it at your own risk: root@tower:~# cryptsetup luksChangeKey /dev/??? Enter LUKS passphrase to be changed: Enter new LUKS passphrase: I'm new to unRAID, but it seems that the Wiki is very out of date in many cases so its hard to find current and accurate stuff there. I was looking up sleep/wake stuff and it was so damned complicated. I found the easy way via Space Invader on YouTube (and another guy on YouTube). Clearly that Wiki page is outdated (or at best incomplete). I realise this isn't Arch Linux, but now there is an amazing Wiki!

My hardware is fairly old, Intel i7-3770, so maybe I should stick with BIOS then. The motherboard is a budget AsRock Extreme4. It only ever had I think two firmware updates, so it wasn't a highly supported board. UEFI was still fairly new at the time - certainly comparitively so. Thanks, I'll switch back to BIOS. Maybe on some future hardware I buy in 3-4 years time I'll re-examine.

Hiya! I had to create my USB manually (drag'n'drop, use batch file to make bootable). Being a noob, i didn't really think about BIOS vs UEFI. I booted the USB and started playing around a bit, and i've setup my UPS and done some basic configuration and i remembered the UEFI thing all of a sudden. It didn't even occur to me i was booting via BIOS rather than UEFI but of course i was. I changed the mobo to UEFI and it wouldn't boot. So i looked it up and i found a thread that talked about the directory being called EFI- by default, and to rename it. So i did that. Everything booted ok. And it seems normal. No ill-effects (note it's quite early in my configuration, i don't even have an array configured yet). The real question is: Is it perfectly safe to change the boot mode from BIOS to UEFI after you've made and starting configuring your unRAID? What nuance or caveats could one expect? Cheers p.s. i decided to do the switch because i saw somewhere that if i want to do VM passthrough stuff that i should be using UEFI. Is that right? Whether right or wrong - are there benefits to one over the other? Cheers x2