JorgeB

Not seeing any attempt to start or enable the VM service, you can try editing domain.cg on the flashdrive's config folder and change SERVICE="disable" to "enable", then reboot.

Please post the diagnostics: Tools -> Diagnostics (after toggling VM manager)

Try toggling the UPS service enable/disable setting on the GUI, if that doesn't work edit config/plugins/dynamix.apcupsd/dynamix.apcupsd.cfg on you flash drive and change SERVICE="enable" to "disable", then reboot, UPS service should stay off.

Possibly related to the USB bridge, USB is prone to disconnects and very bad a error handling, try connecting directly to a SATA port if possible, you can also run a filesystem check. The duplicate UUID is also related, it's because the filesystem it's not correctly unmounting.

With 4 DIMMs they should be set 1866 or 2133Mhz depending if they are single or dual rank, doesn't mean it can't be stable at higher speeds, but you should start at non overclocked speeds (same for CPU) and only if stable try overclocking, though IMHO file servers are not for overclocking.

IIRC the issue is mostly for anyone using a Samsung drive because they have a different NAND erase block size and partitions starting on sector 64 aren't optimal. https://forums.unraid.net/topic/58381-large-copywrite-on-btrfs-cache-pool-locking-up-server-temporarily/?do=findComment&comment=641245 also posting the post he links to since it's not going directly there: https://forums.unraid.net/topic/44104-unassigned-devices-managing-disk-drives-and-remote-shares-outside-of-the-unraid-array/?do=findComment&comment=640178

Merged your other thread here since it's related, please don't double post.

Check filesystem on disk8: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Remove -n (no modify) or nothing will be done, if it asks for -L use it.

Still, and I realized this after posting, it should boot legacy BIOS, since you had that as the 2nd boot option, but glad it's working.

This would suggest filesystem corruption, and that can still be present on a rebuilt drive, you should check filesystem on that drive, if more helped is needed please start a new thread on the general support forum and post the diagnostics.

Please post the diagnostics: Tools -> Diagnostics

Diagnostics are just after a reboot so not much to see, you can try mirroring the syslog to flash, then post it after a crash: Settings -> Syslog Server. Also, and though there's some debate if this is still needed for 2nd gen Ryzen, check your bios for "Power Supply Idle Control" (or similar) and set it to "typical current idle" (or similar), and make sure the RAM is not overclocked, it's known to cause issues with some Ryzen servers.

It's safe and you can always revert to an earlier release if there is an issue with your config and v6.8.

Did you enabled UEFI boot on the USB flash creator tool? I believe it still defaults to disable (you need to click on "Customize" first)

That is part of the Marvell controller, it's a virtual device, normal and nothing to worry about, just don't use those 4 ports (1st 4 white ports) for devices as they are a known problem on those boards and tend to drop drives.

They are not all large capacity disks, most are 3TB and lately I've been buying 6TB.

Most likely, I've buying Toshibas lately since they are very competitively priced and no issues so far, have more than 50 currently.

There's some issue with the USB3 controller: Nov 21 20:49:37 tbmaindoma kernel: xhci_hcd 0000:03:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0000 address=0xfff9d000 flags=0x0000] Nov 21 20:49:37 tbmaindoma kernel: xhci_hcd 0000:03:00.0: WARNING: Host System Error Nov 21 20:49:37 tbmaindoma kernel: xhci_hcd 0000:03:00.0: Host halt failed, -110 Nov 21 20:49:37 tbmaindoma kernel: xhci_hcd 0000:03:00.0: xHCI host not responding to stop endpoint command. Nov 21 20:49:37 tbmaindoma kernel: xhci_hcd 0000:03:00.0: Host halt failed, -110 Nov 21 20:49:37 tbmaindoma kernel: xhci_hcd 0000:03:00.0: xHCI host controller not responding, assume dead Nov 21 20:49:37 tbmaindoma kernel: xhci_hcd 0000:03:00.0: HC died; cleaning up You might try with IOMMU disabled if not needed, also look for a bios update.

Threshold is 50 and it's at 48, at some point in the past it was even lower at 31

No, SMART is failing. Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 7 Seek_Error_Rate PO-R-- 048 031 050 NOW 0

Duplicate UUID is expected if the drive was replaced on the same system, it can be changed for the unassigned device with: xfs_admin -U generate /dev/sdX1

In this case yes, since they have the exact same ID, they don't even have a valid serial number, Unraid requires that each device has a different ID, since that is used to track them. Device Model: OOS3000G Serial Number: 00000000

OK, I see the problem now, disk2 has the same ID as disk3: Nov 21 18:06:38 Petere kernel: ata10.00: ATA-10: OOS3000G, 00000000, 0001OOS1, max UDMA/133 Nov 21 18:06:38 Petere kernel: ata9.00: ATA-10: OOS3000G, 00000000, 0001OOS1, max UDMA/133 You can only use one of these with Unraid, and these are no standard Seagate drives, maybe white label?

It's not being detected as a standard hard drive, try to get and post a SMART report.

Use standard hard drives, from WD (HGST), Toshiba or Seagate.