JorgeB

Feb 8 09:57:39 MOTHER emhttpd: device /dev/sdb problem getting id Note that USB is not recommended for array or pools devices, but the problem is that both devices have the same identifier, Unraid requires a unique identifier to be able to track the devices, you'd need to use a different USB bridge for one of them.
 

Try this first:
https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009
 

Do a new config, it's still works without parity.

Looks like the USB controller where you have the flash drive:
 
0d:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] Subsystem: Gigabyte Technology Co., Ltd Matisse USB 3.0 Host Controller [1458:5007] Kernel driver in use: xhci_hcd  
Is being passed-through to the Windows 11 VM, so when it starts you lose access to the flash drive, adjust that, note that device IDs can change if you add or remove any hardware.

Once a drive gets disabled it must be rebuilt, diags before rebooting could give a clue on why it got disabled.

Next time please post the complete diags but based on that looks more like a power/connection problem, replace/swap both cables/slot and try again, if the problem follows the disk it's likely a disk problem.

comprueba esto para cada share
 

Disable array auto start and boot in safe mode.

No need to balance for now, and the devices look OK, more likely it was a cable/connection problem, keep monitoring the stats, and you need to recreate the docker image.

With the array stopped post the output of:
btrfs-select-super -s 1 /dev/nvme0n1p1 after doing that post again
btrfs fi show  

Looks like there's only one corrupt file:
path: appdata/plex/Library/Application Support/Plex Media Server/Metadata/Movies/b/7fb89a93954dc1f26aaf78a08480ef359c86b9c.bundle/Contents/_combined/posters/tv.plex.agents.movie_d5f0b5612818688ae3c84b27db7d760ad1e40609)  
Delete/restore from backup then run another scrub.

Earlier diags didn't show the begging of the problem because of all the spam, NVMe device is not dropping offline, it's being passed-through to a VM, disable that and run another scrub.

UDMA CRC errors are usually a bad SATA cable, but a single error is no reason for concern, acknowledge it and if you get more replace the SATA cable.

Start here:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
 

Feb 5 23:10:31 devoraid kernel: BTRFS warning (device sdc1): chunk 4163153952768 missing 1 devices, max tolerance is 0 for writable mount This means your pool was not redundant, so it cannot mount read/write with a missing device, you can manually mount it degraded and read only but most files will likely be damaged or incomplete, if you want to try see how to mount manually below:
 
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490
 
You'd need to use degraded,ro as mount options.

Script is here, note that some users have complained of very slow clear speed with this script and more recent Unraid releases, you can also do it manually.
 
 
@SpencerJany way these old links could keep redirecting? It broke a lot of forum and wiki links.

You cannot replace disk1 with a 16TB drive while parity is 12TB, would need to upgrade parity first, remove parity2, then replace disk1.

Those should be harmless, just reboot.

Run it again without -n or nothing will be done, if it asks for -L use, then post new diags after array start in normal mode.

Change the NIC to e1000

Check filesystem on disk1

That's a known issue with some USB enclosures, and one of the reasons we don't recommend using USB for array/pool devices.

With all the config changes you've made the drive was wiped with wipefs, you can try running xfs_repair to see if it can recover from a backup superblock:
 
xfs_repair -v /dev/sdf1  
Note the one in the end

Cache disk need to be replaced, the missing shares should come back one you remove that drive and reboot, then restore your appdata backup and re-create the docker image.