Hoopster

Disks added to an unRAID array must be formatted in a supported format (xfs or btrfs). You can use New Config to get unRAID to forget any previous disk assignments and start over. When you add disks to the array in a new config, they will be formatted with the specified supported file system. You cannot simply add disks with media on them to the array; especially not NTFS disks as those are not supported by unRAID. Your choices with the NTFS disks and media are 1) - mount them as Unassigned Devices in your unRAID system and copy the data over to unRAID array disks, or 2) - backup the media you want to preserve from those disks, add those NTFS disks to the array and allow them to be formatted and then copy the media back to them from the backup location.

Oops, I missed that point. Have you tried running chkdsk on the disk file system? Would have to be mounted in Windows to do that.

Is it set to Read-only in the UD settings?

Yes, completely missing important bits would have caused that as well. 😁 Glad you got it sorted and working!

This often indicates corrupt audio codecs. Delete the Codecs (or rename) folder from [path to appdata Plex container]/Library/Application Support/Plex Media Server This will force the recreation of the folder and download again the audio codecs as needed. Could be another issue, but no harm in starting there.

Since new disks need to be formatted by unRAID to add them to the array, you cannot migrate the data to new drives before adding them to the array unless they were already formatted in unRAID. You have a few options I can think of. Perhaps there are other suggestions to come from others. 1. Create new array with new hardware and new disks (keep current USB but use the New Config option to add new disks to array), mount old disks as Unassigned Devices and migrate the data to the new disks in the array. or 2. in the current array, replace old disks one at a time with the new disks using the Replace a Data Drive procedure then transfer disks to the new hardware setup. Remember you cannot add a new data drive that is larger than the parity drive(s). or 3. Add new disks to the current array and migrate all data from old to new disks then use the Shrink Array procedure to remove the old disks. Then transfer everything including "new" disks which now contain all your data to the new hardware configuration.

Version 6.9.x sees cache drives in a different way. When you downgrade to 6.8.x it is not compatible and the drives must be reassigned as cache drives.

Have you enabled destructive mode?

You need the Unassigned Devices PLUS plugin. Not just Unassigned Devices. Sent from my iPhone using Tapatalk

No need to preclear SSDs. It's just unnecessary wear and tear for an SSD. If you are trying to mount the drive as an unassigned device, you must have the Unassigned Devices Plus plugin installed to enable destructive mode which allows you to format the SSD. This is documented in the Unassigned Devices support thread.

As far as I know, there has been no mention of this issue with the SuperMicro boards in any forums discussions.

Yep, same thing happened to me and I also needed to reflash the BMC with socflash.

As documented earlier in this thread, you likely need to do the 3.3v reset tape trick. Have you tried that? It's a common issue with WD drives shucked from external enclosures.

WD has started putting air filled drives in the external enclosures instead of the helium filled. Air filled drives run hotter. I have two 8TB EDAZ drives I shucked from external enclosures and they run about 5C hotter than the helium filled EMAZ drives when under constant heavy load and 2-3C hotter in normal operations. However, even when preclearing, they never got hotter than 47C. I remove them from the enclosures before preclearing so they have the case fans blowing on them. Anything under 60C is OK even over a long period. Lately, the concern about temperatures has been more about frequent swings in temperature from high temps to low temps and back to high, rather than a constant high temp. It is the fluctuations that seems to be bad for the drives more than highest temperature.

And on my system, I find 'sensors' provides better information on available sensors than 'sensors-detect' which is very verbose.

Sent from my iPhone using Tapatalk

Ubiquiti does not officially support the controller running in a docker container even though many run it that way without issue. Don't mention Docker. Just say you are running it on Linux if they ask for the OS. Officially, they support Windows, MacOS, Debian/Ubuntu, iOS, Android and, of course, their own Cloudkey. If you say Docker, they may try to blame that for whatever the problem is.

Check out both the NVENC and NVDEC lists and check the Consumer and Professional tabs for supported cards and limitations

It appears you do not have coretemp as a selection in the list. I have all the same versions of everything that you listed. Perhaps the coretemp driver did not properly load even though it was detected? Perhaps unload the drivers and try again? I don't know what else to tell you.

I have no idea what interface that is. Here is the setting in the unRAID web UI: This will change display of CPU, motherboard, HDD, SSD, NVMe, etc. temperatures in the unRAID GUI. Scrutiny is not part of unRAID so I cannot tell you how to change anything there,

Settings -- Display Settings --> Temperature Unit

All recent "entry-level" Xeons with an iGPU support Quick Sync Video. My E-2288G is roughly equivalent to an i9-9900K but with ECC support. Many of the current generation W-12xx Xeons also have an iGPU. The soon-to-be released W-13xx (11th generation) will also include many models with an iGPU The Bronze, Silver, Gold and Platinum lines do not have iGPU/QSV support.

Just edit your original post and put [SOLVED] in the title.

See the Unassigned Devices plugin and included sample rsync script for backup of shares to an external drive. Huh? I have been using Xeons for years in my unRAID server and it has no problems with Plex at all. Most of my content direct plays locally and even over the Internet in many cases. See my signature for server specs including ECC RAM.

You would need a Z590 (consumer) chipset based motherboard and a compatible Core i5, i7, i9 CPU The latest server/Xeon chipset is W480 which, currently only supports Comet Lake 10th generation Xeon W-12xx CPUs. However, it is expected to support the new Rocket Lake W-13xx CPUs when they are released.