JorgeB

Any way you like. See here for better pool monitoring. https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309

Apparently not, docker image is corrupt again, but because there are still issue with the pool filesystem, best bet is to backup and re-format the pool.

Thanks, entered the wrong link, corrected.

Both are failing to initialize: Dec 28 01:18:08 Server02 kernel: ata1: link is slow to respond, please be patient (ready=0) Dec 28 01:18:08 Server02 kernel: ata4: link is slow to respond, please be patient (ready=0) Dec 28 01:18:08 Server02 kernel: ata1: COMRESET failed (errno=-16) Dec 28 01:18:08 Server02 kernel: ata4: COMRESET failed (errno=-16) Dec 28 01:18:08 Server02 kernel: ata1: link is slow to respond, please be patient (ready=0) Dec 28 01:18:08 Server02 kernel: ata4: link is slow to respond, please be patient (ready=0) Dec 28 01:18:08 Server02 kernel: ata1: COMRESET failed (errno=-16) Dec 28 01:18:08 Server02 kernel: ata4: COMRESET failed (errno=-16) Dec 28 01:18:08 Server02 kernel: ata1: link is slow to respond, please be patient (ready=0) Dec 28 01:18:08 Server02 kernel: ata4: link is slow to respond, please be patient (ready=0) Dec 28 01:18:08 Server02 kernel: ata1: COMRESET failed (errno=-16) Dec 28 01:18:08 Server02 kernel: ata1: limiting SATA link speed to 3.0 Gbps Dec 28 01:18:08 Server02 kernel: ata4: COMRESET failed (errno=-16) Dec 28 01:18:08 Server02 kernel: ata4: limiting SATA link speed to 3.0 Gbps Dec 28 01:18:08 Server02 kernel: ata1: COMRESET failed (errno=-16) Dec 28 01:18:08 Server02 kernel: ata1: reset failed, giving up Try different cables, you can then just check if they are detected in the board BIOS, if they aren't they also won't be detected by Unraid.

Run another scrub and post the output.

If the errors started after adding it then yes.

You can try doing a new config, don't assign disk7, assign a new parity and re-sync parity, but if disk1 is also failing there will be some errors.

Try enabling turbo write.

Marvell controllers are not recommended, if possible it should be replaced, disk8 possibly has some real issues, you should run an extended SMART test.

That's the disks status, there is a filesystem problem: parent transid verify failed on 22183936 wanted 519 found 510 This error means some writes were missed due to unclean shutdown or device issues, and it's fatal, there are some recovery options here, btrfs restore (option 2) is the most likely to work for this.

Parity disk is showing some SMART warnings, you should run an extended SMART test.

Parity helps if you lose a disk, it can't help with filesystem corruption, any filesystem. Depends on the tool you use for the backup, if for example you use rsync you can still do it on a user share like any other filesystem, if you want to use snapshots then you can only do it disk by disk. There's a sticky in this forum on how to migrate from resier to xfs, the same principle applies to any filesystem conversion.

Shares work across disks, like any other filesystem.

OK, in that case you should be fine.

Goods news, please keeps us posted if you find anything different.

That is a RAID controller, it might still work or be flashable to IT mode, IT mode not always the same as JBOD, if you use a true HBA then it's plug'n play.

That script is very slow with recent Unraid releases, and the author has not been in the forums for a long time, but you can still do the procedure manually.

If they are the same run a correcting check, as along as no more future errors you should be fine.

It's viable, I use it, there's always some risk migrating or just moving a lot of data in general, also btrfs is not as robust as xfs against hardware issues, etc, so make sure you have good backups. You can use snapshots for backups but since each disk is an individual filesystem it needs to be done disks by disk, that is what I do, snapshot each disk then send/receive to an identical server.

HBA is failing to initialize: Dec 26 17:59:26 Tower kernel: mpt2sas_cm0: diag reset: SUCCESS Dec 26 17:59:26 Tower kernel: mpt2sas_cm0: _base_spin_on_doorbell_int: failed due to timeout count(10000), int_status(c0000000)! Dec 26 17:59:26 Tower kernel: mpt2sas_cm0: doorbell handshake int failed (line=5916) Dec 26 17:59:26 Tower kernel: mpt2sas_cm0: _base_get_ioc_facts: handshake failed (r=-14) Dec 26 17:59:26 Tower kernel: mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:10790/_scsih_probe()! Try re-flashing it or testing in a different board if available.

Make sure you try after booting in safe mode with all dockers disable to rule out any plugin/docker interference, it sill issues please post the diagnostics: Tools -> Diagnostics

Yes, but using a new disk.

Best bet is to ask for help in the existing support thread for that docker:

AFAIK no one has been able to make SMB multichannel work wit Unraid and multiple NICs, but note that you can't have them bonded like they are currently, also and IIRC for Samba multichannel they need to be on different IP subnets, unlike in Windows.

This was a problem with the onboard SATA controller: Dec 25 10:21:38 ChunksUnraid kernel: ahci 0000:02:00.1: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x00000000b4b3e000 flags=0x0000] Unfortunately this issue is quite common with Ryzen boards, BIOS update might help, as well as updating to the latest Unraid beta, or disabling IOMMU if not needed.