JorgeB

Unlike CRC errors this is a disk problem. Perfectly normal without a fan on it, but still a normal safe operating temperature.

You could start by posting a SMART report, before or after running an extended SMART test.

Boot in safe mode, or before doing that make sure there's not any user script getting stuck at array start, same thing happended to more than one user.

It passed the last extended test, but if failed one a few hours before: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 20800 - # 2 Extended offline Completed: read failure 40% 20745 7337814160 This confirms it was a disk problem, it is fine for now but you'll want to keep an eye on it, it will likely fail again soon.

Some of the disks are formatted with a 520byte sector size, that's not supported, you can usually re-format to 512 with SGutils. P.S. HBA is in RAID mode, IT would be better.

Looks like a flash drive problem, see if running chkdsk helps.

FYI you need to be careful copying from a disk share to a user share and vice versa, but this points to a possible SMB problem, increase SMB logging: Go to Settings -> SMB -> SMB Extras and add: log level = 3 logging = syslog Then try another transfer from your desktop and post new diags.

Depends on how the old one looks, post current diags.

With some hardware the SAS2LP is known to cause always 5 sync errors after a reboot, just one of the reasons it's not recommended for a long time, you should replace it with an LSI controller.

Parity check was correct so errors are fixed, though parity check after an unclean shutdown should be non correct, unless it changed recently again. A couple more things: -there are many ATA errors on disks 3 and 4, likely a connection issue, check cables. -CPU is throttling down due to overheating, cooler likely needs cleaning.

It's not usually spontaneously, either an unclean shutdown or bad hardware are the most common reasons.

Click on the VM name (in blue), it will expand and allow to resize the vdisks.

sde isn't cache1, it's an unassigned disk that is still connect and not wiped, and has the same UUID as disk1, it's also confusing the cache pool code since Unraid thinks it's part of the pool (because it looks to btrfs like it's part of a pool).

Not sure if that's a duplicate UUID issue, please post complete diags or can't see which disk is which. Also please post output of blkid

Is this still the same sde disk? It's still causing problems. Encryption is outside my wheel house, but that error suggest it's not accepting/recognizing the key.

It basically is, but parity will have the same one if used with a single device array.

It's probably best to wipe disk2 before re-formatting: wipefs -a /dev/sdX1 then wipefs -a /dev/sdX

Yes, the pool is fine, the problem are the duplicated btrfs UUID, which are confusing Unraid: Feb 9 17:02:55 Tower root: WARNING: adding device /dev/sde1 gen 27591023 but found an existing device /dev/sdd1 gen 27591412 Feb 9 17:02:55 Tower root: ERROR: cannot scan /dev/sde1: File exists Feb 9 17:02:55 Tower root: WARNING: adding device /dev/sdf1 gen 27591023 but found an existing device /dev/sdd1 gen 27591412 Feb 9 17:02:55 Tower root: ERROR: cannot scan /dev/sdf1: File exists Feb 9 17:02:55 Tower root: WARNING: adding device /dev/md2 gen 27591023 but found an existing device /dev/md1 gen 27591412 Feb 9 17:02:55 Tower root: ERROR: cannot scan /dev/md2: File exists Feb 9 17:02:55 Tower root: Scanning for Btrfs filesystems Pool should mount correctly once you fix those, disconnecting or wiping sde and reformatting disk2 should do it.

It would be best to post the full diags, but it does look like a disk issue, run an extended SMART test.

You appear to have multiple disks with the same UUID, disconnect (or wipe) any disks currently no being used, like sde. It also looks like disks 1 and 2 have the same UUID, this won't work, you need to reformat one of them. After doing that post new diags (not just the syslog)

Something weird going on where the array devices are being considered part of the pool, am I right in understating that the array devices don't have any data are empty for now (disk1 and disk2)?

Try this, it might catch something.

Disk dropped offline: Feb 9 21:21:08 BargeTower kernel: ata6: SATA link down (SStatus 0 SControl 300) Feb 9 21:21:08 BargeTower kernel: ata6.00: link offline, clearing class 1 to NONE Feb 9 21:21:09 BargeTower kernel: ata6: SATA link down (SStatus 0 SControl 300) Feb 9 21:21:09 BargeTower kernel: ata6.00: link offline, clearing class 1 to NONE Feb 9 21:21:10 BargeTower kernel: ata6: SATA link down (SStatus 0 SControl 300) Feb 9 21:21:10 BargeTower kernel: ata6.00: disabled Feb 9 21:21:10 BargeTower kernel: ata6.00: detaching (SCSI 6:0:0:0) Check connections and post new diags.

Don't worry about that for now, first see if running is safe mode helps, if it doesn't it's not a plugin.

Running is safe mode will disable them all.