JorgeB

Never had any of that model but that would be the most likely explanation, I do have some Seagate Archive drives that make a clicking sound every few seconds or minutes.

Note: Moved from the FAQ thread, @ReidSFAQ thread isn't for asking questions, there's a FAQ feedback thread but this seams more like a general forum question.

https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive

Yep, that will do it.

Dashboard only reports the more common SMART attributes, it doesn't check SMART tests.

That disk has been failing the extended test for some time: SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 10% 3775 4296582856 # 2 Extended offline Completed: read failure 20% 3743 4296582856 # 3 Extended offline Aborted by host 80% 3738 - # 4 Extended offline Completed: read failure 10% 3731 4296582856 # 5 Short offline Completed: read failure 10% 3716 4296582856 # 6 Extended offline Completed: read failure 20% 1600 4296582848 # 7 Short offline Completed without error 00% 1595 - # 8 Short offline Completed: read failure 10% 1509 4296582848 # 9 Extended offline Completed: read failure 20% 1481 4296582848 #10 Short offline Completed without error 00% 1449 - You should replace it, or try preclearing, it might turn good, though it's more likely to fail again in the near future.

https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.0-x86_64.zip Note that v6.8.0 has known security issues.

Any LSI with a SAS2008/2308/3008/3408 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, 9400-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed.

When doing this also a good idea to swap the power cable, just to rule it out as well.

If another disk goes missing array won't start and warn about it, in that case just power down and swap cables back.

Disk isn't initializing correctly: Feb 12 16:54:34 BargeTower kernel: ata6: SATA link down (SStatus 0 SControl 300) Feb 12 16:54:38 BargeTower kernel: ata6: limiting SATA link speed to 1.5 Gbps Feb 12 16:54:39 BargeTower kernel: ata6: SATA link down (SStatus 0 SControl 310) Feb 12 16:54:42 BargeTower kernel: ata6: SATA link down (SStatus 0 SControl 300) Feb 12 16:55:03 BargeTower kernel: ata6: limiting SATA link speed to 1.5 Gbps Feb 12 16:55:04 BargeTower kernel: ata6: SATA link down (SStatus 0 SControl 310) Feb 12 16:55:07 BargeTower kernel: ata6: SATA link down (SStatus 0 SControl 300) Feb 12 16:55:07 BargeTower kernel: ata6: limiting SATA link speed to 1.5 Gbps Feb 12 16:55:09 BargeTower kernel: ata6: SATA link down (SStatus 0 SControl 310) Try swapping SATA cable with another one, just on the disk, so it also uses a different SATA port, if still the same disk is likely dead.

That would be the recommended thing to do.

Read the 1st couple of posts on the thread below, then post there if you still have doubts.

Disk looks fine, replace/swap cables just to rule them out and re-sync parity.

Please post the diagnostics: Tools -> Diagnostics

That is weird, but I can almost guarantee that if you connect the 4TB disk tot eh onboard controller it will work correctly, no idea why the 6TB is working, it shouldn't.

That's because you're replacing a disk, not adding one, current diags start with that disk already disable so can't see what happened but I would guess the smaller disk was not removed correctly. Disk is showing as 2.2TB because it's on a controller that doesn't support larger disks, also likely why it's failing to format, though it shouldn't, but same happened recently to another user.

Correct It's not just SMART, disk isn't being detected correctly, so that's why I believe not many options besides using data recovery services.

I believe so, but it won't hurt to try other things before, just to make sure.

I don't see how any of these will work because the disk isn't initializing correctly, very unlikely you can mount it with any OS, yes at some point it appeared under UD, but if you check no partition was detected, so not possible to mount.

The VirtIO driver should be in every virtio ISO, I remember a user recently that was having a similar issue and the problem was the Windows ISO, you can try redownloading it from MS website.

Yep, missed that part, I have a very old Win10 VM and speeds are normal and constant for years now, so not a general problem, maybe a Windows problem.

Was it performing better with an older Unraid release, i.e., did it slow down after a recent upgrade? If yes see if downgrading to the older release brings it back to normal speed.

Swapping just the PCB isn't usually enough with current drives, you need to swap the ROM chip from the old drive to the new PCB.

Connect one of the USB drives to a SATA port, if the error is the one above stop the array, unassign that disk, start array, if the emulated disk mounts correctly you can rebuild on top, just stop the array again, re-assign the disk and start array to begin rebuild, then repeat for the other disks.