OrneryTaurus

I’m only using the card for data drives, not to boot from so no UEFI BIOS update was done. You’d might need to do the same steps as performed with the bios update but reference the x64sas2.rom if available but I’m not sure.

I'd stick with Supermciro personally but Rosewill or SilverStone might be a good alternative.

I was able to successfully update the firmware of this card. Only modification was I did not erase the existing firmware but instead updated. In case anyone needs to do this in the future, here are the steps I took: Download Required Files 1) Obtain sas3flash for Linux (https://docs.broadcom.com/docs/Installer_P16_for_Linux.zip_p) 2) Obtain the v16.00.12.00 firmware and v08.37.02.00 bios from (https://docs.broadcom.com/docs/9305_24i_Pkg_P16.12_IT_FW_BIOS_for_MSDOS_Windows.zip) Extract and Prep Files 1) Extract Installer_P16_for_Linux.zip 2) Extract 9305_24i_Pkg_P16.12_IT_FW_BIOS_for_MSDOS_Windows.zip 3) Make a directory called hba_update 4) Copy sas3flash from Installer_P16_for_Linux\sas3flash_linux_x64_rel to hba_update 5) Copy SAS9305_24i_IT_P.bin from 9305_24i_Pkg_P16.12_IT_FW_BIOS_for_MSDOS_Windows\Firmware\SAS9305_24i_IT_P to hba_update 6) Copy mptsas3.rom from 9305_24i_Pkg_P16.12_IT_FW_BIOS_for_MSDOS_Windows\sasbios_rel to hba_update Your hba_update folder should now contain the following files: mptsas3.rom sas3flash SAS9305_24i_IT_P.bin Upload to UNRAID 1) Copy the hba_update directory to /tmp/ - This puts the directory in memory and allows the sas3flash to be executable since UNRAID no longer allows files on the flash drive to have the execute permission. 2) Perform the following permission modifications: chown root:root sas3flash chmod 755 sas3flash chmod +x sas3flash chmod 644 SAS9305_24i_IT_P.bin chmod 644 mptsas3.rom Backup Critical Information 1) Run ./sas3flash -listall - keep the output somewhere 2) Run ./sas3flash -list - keep the output somewhere 3) Run ./sas3flash -o -listsasadd - keep the output somewhere 4) You can try to run a backup of the firmware using this command: ./sas3flash -c 0 -backup firmware_backup.bin - note: the sas3flash may not always have this functionality Do this after performing the UNRAID Actions below if desired 4) Take a screenshot of all Array / Pool setups with drive assignments / serial numbers - this is in case the update wipes the data UNRAID Actions 1) Stop the UNRAID Array 2) Disable Docker 3) Disable VM Manager Run Update 1) Run ./sas3flash -c 0 -o -f SAS9305_24i_IT_P.bin to update firmware without erasing If this fails, updating with erasing the firmware may be needed 2) Run ./sas3flash -c 0 -o -b mptsas3.rom to update the bios (if desired) Verify Update 1) Run ./sas3flash -list Look for the output that is similar to the following: Firmware Version : 16.00.12.00 Firmware Product ID : IT SAS Address still present (previously pulled from ./sas3flash -o -listsasadd) If SAS Address is missing, run the following command with your sas address previously obtained: ./sas3flash -c 0 -o -sasadd ADDRESS_HERE 2) Shutdown the UNRAID Server, waiting 5 minutes or drain power after shutdown 3) Power on the UNRAID Server 4) Once booted up, run: ./sas3flash -list to verify the new firmware is still shown 5) Double check drive assignments If drive assignments aren't accurate, create a new config under Tools. Match your previous drive assignments and check 'parity is valid' before continuing 6) Enable Docker 7) Enable VM Manager 8) Start UNRAID Array 9) Monitor the syslog for any errors using the command: tail -f /var/log/syslog Hope it helps!

Hello everyone, I'm currently on a firmware version which is known for dropping the drives connected to it under certain circumstances causing errors and wanted to upgrade to the 'latest' firmware to avoid this issue from happening again. The current firmware version I'm on is v16.00.01.00 and I plan on going to v16.00.12.00 The current bios version I'm on is: v08.37.00.00 and I plan on going to v08.37.02.00 I just needed a quick sanity check on updating this card to make sure I'm not missing anything important. Here are the steps I plan on doing: Preparation: 1) Obtain sas3flash for linux (https://docs.broadcom.com/docs/Installer_P16_for_Linux.zip_p) 2) Move sas3flash from sas3flash_linux_x64_rel to a /tmp/hba_update folder 3) Modify the permissions/ownership to make the sas3flash executable 4) Obtain the v16.00.12.00 firmware and v08.37.02.00 bios from (https://docs.broadcom.com/docs/9305_24i_Pkg_P16.12_IT_FW_BIOS_for_MSDOS_Windows.zip) 4) Move the SAS9305_24i_IT_P.bin from the Firmware/SAS9305_24i_IT_P folder and mptsas3.rom from the sasbios_rel folder to the /tmp/hba_update folder 5) Modify the permissions/ownership if needed of each file 6) Obtain and write down the SAS adapter address by running sas3flash -o -listsasadd 7) Screenshot the existing array with all disk assignments and serial numbers Performing: 1) Stop the array and ensure all activity is halted 2) Erase the IT firmware with command: sas3flash -o -e 6 3) Flash the IT firmware with command: sas3flash -o -f SAS9305_24i_IT_P.bin 4) Flash the BIOS with command: sas3flash -b mptsas3.rom 5) Re-program the SAS Address with command: sas3flash -o -sasadd <sasaddress> 6) Re-check the updates by performing command: sas3flash -listall 7) Reboot Additional Steps (if needed) since I am on an old firmware: 1) Create a new array config 2) Assign all disks exactly as shown from Prep Step 7 3) Check 'Parity is already valid' 4) Start Array Appreciate it!

Build looks good, the only concern I'd call out is you might want to add a second cache for the Arr stack to keep the writes lower / avoid any issues with your docker containers.

Your PCPartPicker list has been set to private so we are unable to see it. Can you set it to public or list out the hardware?

Not sure if it will work for the X11 board, but I have an X10DRi-T Supermicro motherboard and use this. (If you can get IPMI working that is) First, I installed ipmitool-1.8.18-x86_64-1_SBo_nerdtools.txz from nerd tools (running v6.12.15 on unRAID currently) --- Note: I know nerdtools is depreciated, so what I did was copy the installed txz from /flash/extra out, then uninstalled nerdtools, and then put the file back in place. Once the file was back in place, I ran the command: upgradepkg --install-new /boot/extra/ipmitool-1.8.18-x86_64-1_SBo_nerdtools.txz to re-add it without rebooting. Then I found a script online (long time ago) and placed it in a user script to trigger at start of the array: #!/bin/bash #set fans to full speed ipmitool raw 0x30 0x45 0x01 0x01 sleep 10 #set 'system' fan zone to 30% ipmitool raw 0x30 0x70 0x66 0x01 0x00 0x1E sleep 10 #set 'peripheral' fan zone to 30% ipmitool raw 0x30 0x70 0x66 0x01 0x01 0x1E That sets my fan zones to 30%. If you want something different, you can change the first set 0x30 to something else. PS: I found an updated ipmitool v1.8.19 which is intended for unRAID v7.0 but I haven't upgraded my system yet to try it out.

Your current motherboard does not have any video ports on the I/O so it expects a discrete GPU in order to be used. The VGA does have a 'bypass' option to allow it to boot up without verifyiing the presense of a GPU, but that's about it. You won't be able to adjust the BIOS to use both, since the BIOS isn't programmed and the motherboard likely doesn't have the traces for utilizing the iGPU. The Supermicro board is nice, however there are a couple of things to note: 1) Online searches quote the CPU you have at 125W TPD however Intel lists a base / high power instead of the TDP for this processor. The high power exceeds 150W TPD quoted on the supermicro site for that board, this may or may not be a problem. If it is a problem, you just have to disable turbo to stay under the power requirements would be my guess 2) Intel 2.5GbE 225/226 chipsets often have connectivity problems when set to use a 2.5GbE network. These work fine when limited down to 1GbE speeds. This issue would likely occur on any board with a 225/226 intel 2.5GbE chipset Going with a Supermicro board, you'd gain IPMI support which might be useful if you don't want to be in front of it in order to control / see what's going on.

After searching the internet for a similar sound problem with my supermicro X10 board, I found and implemented the following script after using nerdtools to install ipmi tools.

I use a supermicro setup myself, no issues. Beefy AF for whatever I decide to mess around with.

- 2 errors: issue You can just delete the nextcloud.log in your data folder and it will clear the error - no maintenance window issue: Add something like: 'maintenance_window_start' => 1, to your config.php file in www\nextcloud\config - mimetype issue: launch console for your nextcloud docker container and run occ maintenance:repair --include-expensive - this is safe to run. - HSTS header issue: you'll need to change this for the ssl.config instance in the nginx folder of the nextcloud instance. (Just remove the # in front of the add_header line under HSTS. If you are putting this behind another container like SWAG, you'll need to do the same for it's ssl.config as well. - missing optional indices issue: Launch console for your nextcloud docker container and run occ db:add-missing-indices - this is safe to run. - no default phone region issue: add 'default_phone_region' => 'us', to your config.php file in www\nextcloud\config. Change the region to whatever your region might be. - email configuration issue: Set your user account email in the profile section first, then set the mail configuration in basic settings.

I used my onboard 10G x2. The only time I've chosen not to use onboard is when there was a driver issue in one of the unRAID v6.xx updates. Then I switched to a 10G PCIe card.

They're using NSIS (Nullsoft Scriptable Install System) which certain AVs and newer threat detection companies (Crowdstrike, Sentinel One, etc) don't like. They see it as a threat even when it's not. Some will see it's digitally signed and ignore it, others won't. You can always use the old manual method if you want to be safe. https://docs.unraid.net/unraid-os/getting-started/manual-install-method/

FileZaill has 'sponsored' content in the setup executible if you download direct from the main homepage. This 'sponsored' content is flagged by many security products. However if you download from the 'show more downloads' page, it is sponsored content free: https://filezilla-project.org/download.php?show_all=1

Who is your internet provider? It might be a CGNAT situation.