ksw10292

I tried 4 more things. The drive still never appears in UnRaid. (Still works fine in Windows 10, though) 1. Covered pin #3 with tape. 2. Covered pins 1,2,3 with tape. 3. Removed all tape and physically ripped out pin #3 at the back of the drive. 4. Physically removed pin 3, and covered pins 1-2 with tape. Someone really changed the standard and said "gee, let's use pin #3 for some different purpose and cause all drives that use it, to never spin up again"? Wouldn't that cause millions of drives to have problems? (And their existing data)

How do you "power with a SATA connector"? All the drives slide right into the backplane that supplies all power and all SATA connections. I never touch cables. Other than this 1 drive, all the cables properly power any drive and all data flows without any problems. Do certain "odd" drives need 3.3v pins... but none of my other assorted drive do?

A wide variety of drives always work in any bay I put them in. This 1 Seagate drive doesn't work in ANY of the bays I've tried so far. Could the drive be formatted/partitioned/initialized in a strange way that Unraid/UnassignedDevices can never see? Or should that not matter? Does Unraid just see "any drive, from any prior use case" as immediately available as "a drive for reuse in Unraid"?

I tried several different of the hot-swappable bays. So I know that not all of them could be doing the "share with nvme slot" thing. Other drives work, but never the Seagate ST4000LM016. It also rules out "cable problems" because I know so many bays can't all be having "bad cable" problems.... but only with this 1 magical drive. Could it just be "a bad drive"? But I can't explain why it works 100% under Windows 10 and a USB external case.

Would it be possible to upload just 1-2 of the diagnostic files? (The 1 that pertains to 'recognizing newly installed drives') The whole set is huge and contains WAY too much info for me to be posting it publicly. Even when "anonymize" I see it contains full VM machine names (our user's first and last names), etc. And info that has nothing to do with "unassigned drives" or "newly added drives".

My Unassigned Devices have always work with any drive I've ever connected to my UnRaid server over the past few years. A wide variety of various brands, models, sizes, speeds, age, etc. Some are new, some 5-12 years old, some are SSDs, some are mechanical drives, SATA and SAS, 2.5" and 3.5". Except this 1 drive. It's a Seagate 4TB SATA ST4000LM016 2.5". (Commonly found 5 years ago) I connect it to UnRaid... and it never appears in my Unassigned Devices list. I've tried several different slots in my hot-swappable drive bays. The green LED light is on. The drive is getting power. Tried hitting the "refresh" button near Unassigned Device. If I remove it from UnRaid, and connect the drive (via a USB enclosure) to a Windows 10 computer... it works fine. I can DiskPart-Clean it, format it with Disk Management, partition it, read/write data to it, anything. But when I move it back to UnRaid, it never appears in Unassigned, nor even as "pick a drive choice" when the array is stopped. I tried connecting it to UnRaid while the drive was empty, or full, formatted or not, FAT32 or NTFS, 1 partition or multiple, DiskPart-Cleaned (raw), etc. Are there some brands/models of drives that just plain "never work with Unassigned Devices"? (Thank God I only bought 1 of these drives, and not 10) Does UnAssigned Devices do any kind of filtering, blocking drives based on brand, model, age, or prior formatting, etc?

> In order to benchmark SSD's, they must be mounted in UNRAID and a mapping configured in the DiskSpeed Docker settings. Can someone explain *HOW* (not just "what") I need to do, step-by-step? Click-by-click, how do I "mount", how do I "map", how do I "configure"?