Kilrah

Logging is for knowing what's happening, it won't change anything and shouldn't be left on once the issue is found.

Check filesystem on the cache.

But in your case it's kinda useless, setting it high enough would mean you would never use cache for that share. Best to write those to an array-only share.

Ah the 10TB doesn't need to be rebuilt, so then yes you can do it in one go, do New Config, assign all the drives as desired and let it build parity. Just won't have protection during that process.

Nope can't do it in one go. Does the 20TB drive still have data on it?

What's that "source" in the router? Might need to be empty or it'd only forward stuff coming from the address specified which will never happen.

Stopping Docker was not the reason, disk3 (is that the replacement?) has connection issues. Reseat/clean contacts/change cable. Oct 12 02:02:01 JimmiNas kernel: ata5.00: failed command: WRITE FPDMA QUEUED Oct 12 02:02:01 JimmiNas kernel: ata5.00: cmd 61/68:f0:38:62:e0/03:00:01:00:00/40 tag 30 ncq dma 446464 out Oct 12 02:02:01 JimmiNas kernel: res 43/84:01:01:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Oct 12 02:02:01 JimmiNas kernel: ata5.00: status: { DRDY SENSE ERR } Oct 12 02:02:01 JimmiNas kernel: ata5.00: error: { ICRC ABRT } Oct 12 02:02:01 JimmiNas kernel: ata5: hard resetting link Oct 12 02:02:02 JimmiNas kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Oct 12 02:02:02 JimmiNas kernel: ata5.00: configured for UDMA/133 Oct 12 02:02:02 JimmiNas kernel: sd 5:0:0:0: [sdf] tag#30 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Oct 12 02:02:02 JimmiNas kernel: sd 5:0:0:0: [sdf] tag#30 Sense Key : 0xb [current] Oct 12 02:02:02 JimmiNas kernel: sd 5:0:0:0: [sdf] tag#30 ASC=0x47 ASCQ=0x0 Oct 12 02:02:02 JimmiNas kernel: sd 5:0:0:0: [sdf] tag#30 CDB: opcode=0x2a 2a 00 01 e0 62 38 00 03 68 00 Oct 12 02:02:02 JimmiNas kernel: I/O error, dev sdf, sector 31482424 op 0x1:(WRITE) flags 0x0 phys_seg 109 prio class 0 Oct 12 02:02:02 JimmiNas kernel: md: disk3 write error, sector=31482360 Oct 12 02:02:02 JimmiNas kernel: md: disk3 write error, sector=31482368 Oct 12 02:02:02 JimmiNas kernel: md: disk3 write error, sector=31482376 Oct 12 02:02:02 JimmiNas kernel: md: disk3 write error, sector=31482384 Oct 12 02:02:02 JimmiNas kernel: md: disk3 write error, sector=31482392 Oct 12 02:02:02 JimmiNas kernel: md: disk3 write error, sector=31482400 Oct 12 02:02:02 JimmiNas kernel: md: disk3 write error, sector=31482408 Oct 12 02:02:02 JimmiNas kernel: md: disk3 write error, sector=31482416

Check that nothing in Docker or VM settings directly maps to /mnt/[poolname]/[share] but map to /mnt/user/share instead.

Seems that pool was a single drive, how would you expect that if you remove a single drive with data on it it'd magically appear on the new one? You need to manually copy the old drive contents to the new one.

It doesn't, if you want NUT you don't set up/disable the built-in thing but install the NUT plugin and set it up.

Use ZFS pools instead of the array, that's why that was introduced and the array became optional. Can't do TRIM with parity in a reasonable way, wouldn't put much hope into it.

It's the program that will have misidentified it as sqlite3, since you know it's a raw disk image rename it to img and try to mount it on a linux distro that has btrfs tools installed (assuming the image is the default btrfs format).

Yes, it's tied to the "start array" button, which now is pretty much "start Unraid services" but... name's still what it is.

No problem here. Do you have ancient hardware? If CPU is set as Host then that's reporting that your actual CPU doesn't support those.

DB runs on 3306 but you gave 8080 on the DB host line in the WP template.

Unassigned Devices is what you need to mount external drives yes. Might need Unassigned Devices Plus too for exfat. People often tend to assume everyone has those installed already

Stop array, unassign the disabled disk, start array, stop again, reassign it, start and let it rebuild. SMART is always from an actual disk.

Not seeing the real drive identifiers should have been an instant red flag

That backs up the container's data paths. If the container was incorrectly configured and there were none there was nothing for it to back up so it's gone.

Eh, that's dealt with by the template maintainer who still wants to edit the XML anyway, and unlike the container order the order of those is meaningless, no point wasting time on that IMO.

Drag/drop's been there for a long time, click the padlock and that makes the sliders appear.

1st you don't want Docker containers - they just set up a VM, better do it yourself in the Unraid VM system directly. 2nd MacOS is pain. Set up a MacOS VM for yourself and you'll see that unless you add a dedicated supported GPU for it it's unbearably slow and there are major hoops to go through get things like iMessage to work since those normally rely on Apple's security chip, which you mentioned as main purpose. The idea is cool, the implementation is often neither stable or safe without lots of effort.

These do need some airflow, they're meant to be actively cooled by the airflow a server chassis provides. It's pretty common to have heat-related issues, people often 3D print a mount and install a small fan.

Starts to sound like the HBA itself could be faulty. Rare that so many drives/cables would fail at the same time, but the common point connecting all of them... What is it, when you changed mobo could you maybe have changed things so it doesn't have proper cooling anymore?

Guessing you mean macOS instead of iOS... virtualizing macOS is a massive pain because Apple don't care for it and since they haven't made a new x86-based mac in years getting it to work in on current hardware is even more so. Windows works well for some, although as usual that's more complexity and more points of failure than a dedicated machine. For macOS you probably want to buy an M4 Mac Mini these days.