JorgeB

GUI SMART tests don't work with SAS devices, you need to run them manually.

Device is currently at 114% estimated life, I believe some Intel SSDs went read only when they reach 100% expected life, so looks like it's not the case with that model, I would just keep using it, I have one NVMe device currently at 180% expected life (1.05PB written) and still going strong, just make sure you have up to date backups.

Apr 16 19:47:38 Cortana kernel: BTRFS info (device sdb1): bdev /dev/sdb1 errs: wr 169216630, rd 124947440, flush 2261207, corrupt 988649, gen 0 The large number of read and write errors suggest this device dropped offline some time earlier, you should run a scrub and make sure all errors are correctable, then suggest you monitor the pool for future issues, bore info below: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582

See if this applies to you, if yes, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Apr 12 08:43:22 SPFBACKUP kernel: ata6.00: disabled Apr 12 08:43:22 SPFBACKUP kernel: ata6.00: detaching (SCSI 6:0:0:0) ... Apr 12 08:44:31 SPFBACKUP kernel: ata1.00: disabled Apr 12 08:44:31 SPFBACKUP kernel: ata1.00: detaching (SCSI 1:0:0:0) Both disks dropped offline in the space of a minute, this is usually a power/connection problem, start by checking if they share anything in common, like a splitter.

Enable disk shares and try transferring directly to that, user shares usually have some extra overhead.

Enable the syslog server and post that after a crash.

Long test never completed, but drive looks OK, disable spin down for that drive, it should get rid of most of the log errors, then post new diags if there are still more.

You can use the UD plugin to mount Synology SMB shares on Unraid.

Disk looks healthy, assuming the emulated disk is mounting and contents look correct you can rebuild on top: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

Most of the GUI uses SI units, but the VMs are created with binary units, if you want the vdisk to have 60GB create one with 55.88GiB.

Because it's a different problem, you have an actual missing device: Apr 18 18:05:26 NAS emhttpd: /mnt/cache uuid: c0604d95-a95d-4473-b590-5d657cf45624 Apr 18 18:05:26 NAS emhttpd: /mnt/cache found: 2 Apr 18 18:05:26 NAS emhttpd: /mnt/cache extra: 0 Apr 18 18:05:26 NAS emhttpd: /mnt/cache missing: 0 Apr 18 18:05:27 NAS emhttpd: /mnt/cache warning, device 2 is missing Apr 18 18:05:27 NAS emhttpd: /mnt/cache Label: none uuid: c0604d95-a95d-4473-b590-5d657cf45624 Apr 18 18:05:27 NAS emhttpd: /mnt/cache Total devices 3 FS bytes used 429.72GiB Apr 18 18:05:27 NAS emhttpd: /mnt/cache devid 1 size 953.87GiB used 698.03GiB path /dev/nvme0n1p1 Apr 18 18:05:27 NAS emhttpd: /mnt/cache *** Some devices missing Apr 18 18:05:27 NAS emhttpd: /mnt/cache mount error: Invalid pool config No valid btrfs filesystem is being detected on the other NVMe device, and whatever happened it did before the diags posted, since no fs was detected on boot, if the device was wiped with wipefs you should be able to restore it with: btrfs-select-super -s 1 /dev/nvme1n1p1 If the command completes successfully then you need to reset the pool, to do that unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), start array, if it still doesn't mount please start a new thread in the general support forum and post new diags.

https://wiki.unraid.net/Manual/Storage_Management#Replacing_disks

Unraid disables a disk if there's a write error, doesn't mean the problem was caused by the disk, but after it gets disable you need to rebuild to re-enable, assuming the emulated disk is mounting and contents look correct you can rebuild on top: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

It's what I would do, unless you have another HBA you can try with.

It can be, it could even be neither, it could be for example a PSU problem, but since there are also CRC errors and those can basically only be from the controller, cables or backplane and the other disk issues are likely related it should be one of them, backplane more likely but HBA is also a possibility, especially if it's a Chinese fake, unfortunately no way of knowing for sure until you rule one of them out, either by using a different HBA or connecting the disks directly bypassing the backplane (or using a different one).

They did, and the board shouldn't let you select CSM boot when using an iGPU, Asus boards for example don't.

What you see in the emulated disk with or without an assigned disk is what will be there after the rebuild completes. Again, what you see now is what will be there once it finishes rebuilding. That was the emulated disk, and due to the filesystem corruption some (or all) data was moved to lost+found.

A full disk write might fix it for now, but likely there would be new read errors soon, the other disk is fine for now but if the mentioned attributes keep climbing will likely also generate more read errors.

Not booting with CSM enable looks like a board issue, but the LSI should still work in UEFI mode, so two different issues.

It's only mentioned if one is detected, in your case it isn't, if it was it would visible in the syslog and lspci.txt, also in the GUI like mentioned.

-For normal forum browsing the above setting works, i.e., I click on the thread title and it takes me to the first unread post, no need to click on the ball -Previously when I used the "all activity" feed to catch up I also didn't need to click on the ball since all posts for the same thread were visible so I just went bottom up to catch up -Now all posts from the same thread are grouped together in the "all activity" feed, so if I click on the title it takes to the last post, no the first unread one, so I guess I need to get used to click on the ball instead of the title, at least when I'm on the feed, it still works for normal browsing.

Diags show the filesystem corruption, but unfortunately not the reason why it happened, might have been caused by all the errors you were getting on the newer kernel, but it's just a guess, assuming it was stable before on v6.9 and continues to run stable now.

Then it's likely dead, you can try it in a different PC to confirm if you have one.

Check filesystem on disk3.