JonathanM

Attach the diagnostics zip file to your next post in this thread.

Almost, make sure you put the key file from the config folder into the correct drive. So you will be copying the config folder complete except for the key file.

In theory it should be pretty straight forward, but it will have to be done with the server shut down. Make a backup of the config folder on the flash drive, then remove all existing partitions using gnome-disk-utility, create a single partition, format it FAT32 and label it UNRAID, copy the latest release of Unraid onto the partition, run the linux make bootable script, copy your config folder back to the drive. Theoretically that's how it should work, however there are plenty of things to go wrong along the way, so if I were you I'd prepare a second drive exactly as I outlined, instead of erasing your working one. Test boot from the new drive, it will complain about the key being invalid, but don't transfer it, just shut down. Then you can go through the process with your original boot drive, and if it goes horribly wrong you can always use the new one and transfer your license. The make bootable script in linux can be problematic depending on how your specific linux auto mounts USB drives, there is a thread somewhere on here about how to force it to work if it errors out.

Tools, new config, be VERY VERY SURE that the drive you put in parity slots are correct. Parity assigned drives WILL be permanently overwritten, so if you are at all unsure about it, don't put any drives at all in the parity slots until you confirm the rest of your data drives are correct. You can start the array with data drives only and check the contents.

Says the fanciest pumpkin ever!

Perhaps add a cheap SATA controller card and pass the whole card through?

LOL. Not an unreasonable worry. 🤣 Honestly I have no idea, but this release cycle "feels" shorter to me, simply because of the lack of feature creep in 6.11 vs. previous versions.

No, because Unraid doesn't install on a USB, it installs itself into RAM from archives on the USB at boot time. It uses the USB as persistent storage for configuration changes, and licensing, but it installs and runs purely in RAM.

My personal opinion is if you waited this long, wait a little longer for 6.11 to go stable for a week or two and reevaluate then. 6.10 feels like a wrap up of necessary updates for many of the new features with the myservers addon, while 6.11 seems to be not about adding features but getting all the back end stuff in order, kind of a deep breath before pushing ahead with new features again. I'm hoping 6.11 will turn out to be a good spot to upgrade to for "annual server maintenance" as you put it.

If you have 4 sticks of RAM, 3200 may be an overclock. It's not the RAM speed that limits it, it's the motherboard and CPU.

Logging?

This. After the speaker leads are reconnected, do the PW short test again, and see if you get POST codes. They're handy to have if you play with PC's, but if it's only for this exercise, I don't think you need one at this point.

Yep, it means the motherboard is correctly telling the power supply to go from standby to normal output. Without POST codes, it means very little. When you momentarily short the PW pins, correct behaviour would be to spin the CPU fan continuously, possibly changing speeds to clear dust. Momentarily short the pins again while the fan is running, and it should spin down the CPU fan. 99% of boards that I've dealt with either have on board piezo speakers, or just the pins. Are there any 4 position connectors labeled speak or something similar in the case front panel bundle with the power, reset, and LED connectors? Is the picture you posted 100% the same as your board? I don't see any piezo drivers on the picture you attached. Here's a picture of the part by itself, Here's a picture of a corner of a motherboard with one on it, upper right quadrant.

Speaker connected? Without it, you are flying blind.

Most scanners I've dealt with that have email also can use FTP. That may be the easiest answer if available.

mirror is NOT backup. Backups can be restored to fix things like file corruption and accidental deletion. Mirror keeps the files identical in realtime, so if a file is deleted, it's gone everywhere. mirror is NOT backup. mirrors perform best with identical drives, but can be forced to use vastly different capacities and speeds, typically you will be restricted to the limits of the slower and smaller of the disparate drives.

Do you care which drive number slots have specific shares on them? If not, you don't have to do nearly as much work. In a nutshell, copy one of the ReiserFS drives to one of your empty XFS drives. Compare the content, as thoroughly as you wish, cursory examination or binary file by file, whichever fits your risk profile. Format the source of the copy to XFS. Repeat until all ReiserFS drives have been formatted to XFS. Parity stays valid the entire time, no need to mess with new config and possibly rebuilding parity.

If the docker menu item is still available, you didn't disable the docker service.

Unraid runs in RAM and is installed clean on every boot, any modifications have to be scripted. So, as long as you remove any traces from /boot/extra and reboot, it's uninstalled.

Lower quality UPS's can have issues running on some generators, but with high quality equipment, both UPS and gensets, it can be ok. Have you run your IT stack for any significant time on genny? I'm asking just to make sure you aren't making assumptions that because the genny salesman said it would be fine but you haven't actually tried it, if that's the case I'd do dry runs with all your actual computers and servers unplugged and dummy loads on the UPS's to see how they behave. I've seen some nasty bangs as a result of unhappy electrics.

Depending on the board it may well be shipped in RAID (IR) mode, but many can be flashed to IT mode so it will work without issues. Google flash lsi 2308 it mode with your specific board and see if you can find instructions similar to this https://blog.widodh.nl/2014/10/flash-lsi-2308-to-it-mode-on-a-supermicro-x10sl7-f-mainboard/

Form view is sort of broken, it tries to ensure the XML code is valid, but it doesn't know all the acceptable entries, so if you make a change in XML that it doesn't understand, it wipes it out or errors. Stay in XML view once you customize a VM using XML. Take a look at all the options and combinations available, and you'll have a sense of why things are as they are. Form view is there to give a good base, hopefully 90% of VM's can be run from there, but the customizations available in the raw XML are almost endless. https://libvirt.org/formatdomain.html

To clarify, you do need the PSU connected to the motherboard. So, the only components involved would be PSU, MB, CPU heatsink and fan, and since your board doesn't appear to have an onboard speaker of any sort, you need one connected to the pins labeled SPEAK+ and SPEAK- to hear POST beeps. Once things are connected, you use a metal screwdriver or knife blade to momentarily connect the 2 pins labeled PW + and PW -, and you should get beep codes indicating RAM failure (since there is none) accompanied by the CPU fan spinning up. No beeps, bad board or CPU, typically board. If you are removing the MB from the case to do this, be sure it's on a non-conductive surface, and be careful about static electricity.

36 is fine. Start a parity check and see where it settles out.

Fairly easy to do with a container, I use