nalasimon816

Went through the long process of configuring parity drive and a 4 drive array in unraid only to find out i had the RAID controller in raid mode the whole time. I have all my docker containers configured and running.I need to get onto HBA mode obviously. so i see a couple avenues: A) follow chatgpt's advice which is to backup usb drive config + back up all my data, make note of drive assignment letter pairings with drive serial numbers, then switch to HBA, then re-assign the pairings correctly in unraid UI. then things should work as normal. im not fully sold on this being a plausible solution. B) Wipe parity drive and use it as temp store for my RAID data while I wipe array and re-configure as HBA, then migrate the data back. C) Buy another 28TB drive and use it as temp store for array data, then wipe array, then migrate data back onto array, then wipe the 28TB drive, add it to my array as a 5th disk. What's the best option here?

is the /boot/extra still supported in v7 unraid? im on 7.0.1. i dont see extra subdir in my boot dir. i wanted to install a .ko file for my raid controller into this folder. more details here https://www.reddit.com/r/unRAID/comments/1l00u72/can_i_install_nonslackware_tgz_files_in_extraboot/? The exact driver that would contain the .ko is here https://storage.microsemi.com/en-us/support/_eula/license-agree.php?aacraid-linux-src-1.2.1-52033.tgz adaptec 7000 series. the driver package is tgz not txz. i read another reddit post mentioning txz is required for this dir, is there any truth to that?