JorgeB

No more ideas sorry.

Then you might have a problem with the HBA, it's being detected in a weird way: 01:00.0 Mass storage controller [0180]: Broadcom / LSI 53c875J [1000:008f] (rev 05) Subsystem: Broadcom / LSI 53c875J [1000:008f] Typical 9207-8i looks like this: 01:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 [1000:0087] (rev 05) Subsystem: Broadcom / LSI 9207-8i SAS2.1 HBA [1000:3020] And I think that's why no driver is being loaded, it's being detected with a weird model and with a different vendor:device ID, try it in a different slot/PC if available to see it makes a difference, you can also try re-flashing the firmware.

That looks like a problem with the USb adapter.

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 11980 root 20 0 2381912 2.0g 23372 S 12.5 12.9 390:55.06 ffmpeg 11983 root 20 0 2293552 1.9g 23516 S 12.5 12.3 394:58.95 ffmpeg These appear to me the main culprits, are you doing video encoding?

Click on the disk and you can set a specific spin down time for that device.

^This

Why not? It should find any connected device.

Could be a bug, do you have any other computer or device you can access the web GUI to see if works there?

Since the device will have a new btrfs superblock and AFAIK it's would be very difficult to recover the old one, you could use a file recovery util like UFS explorer to try and recover the vdisk.

That's an option with the parity check plugin, and it can be configured there.

See here for better pool monitoring, so you know as soon as possible if more issues are found.

Oct 7 14:39:13 TOWER kernel: mpt2sas_cm0: SAS host is non-operational !!!! If using a different HBA didn't help it suggests to me that the board is the problem.

This is a strange one, please check if the permissions are correct after a reboot, if not stop all dockers/VMs and boot in safe mode, if now they are correct start enabling everything to try and find the culprit, if they are correct at boot again see if you can find if they go wrong after using some docker/VM, etc.

Parity is valid for current array, or at least as valid as we can make it, no need for anything else, just try with the other parity when you get the other disk to see if the results are better.

Never seen something like that, it can have fewer lanes, it won't change the PCIe generation.

Yes, it's the same issue, some quirks were added for v6.11.1, but LT can only add the ones that are reported, I added yours to the list, it should be added for the next release.

Some quirks were added for v6.11.1, but LT can only add the ones that are reported, I added yours to the list, it should be added for the next release.

Yes, since v6.10.3 you don't need to do anything extra, just update.

You can contact support, they will replace the flash drive for you.

That's not supported, looks like there was a way to make work before but not anymore, if you enable the GUI help it will show the supported characters.

Boot using the GUI mode, use the local browser then click the dropdown to assign a disk a take a photo, then please post it here.

That's good for now, of course we still don't know what caused the initial problem, use the server normally for a week or two and then run another check.

If you added the SSDs to an existing pool any that on the added devices would be deleted.

That's a good thing, so most data should be good, of course there can still be some corruption due to disk3 errors, but it will be small since 99.99% was recovered.

Was going to post about this earlier but forgot, turns out the corruption was already there on v6.9.2: Metadata CRC error detected at 0x47542a, xfs_sb block 0x0/0x200 Difference is that the newer kernel detected the corruption at mount time and prevented the filesystem from mounting, possibly to prevent further damaged, so it's a good thing, anyway xfs_repair fixed the problem and all is good now. /topic/129001-solved-6110-disk-is-not-recognized-after-upgrade-to-6110-from-692/?do=findComment&comment=1176260