FCruz2489

That did the trick! Thank you very much for the help!

Long story short, I had to temporarily physically remove an M. 2 drive from my two-drive ZFS mirror pool. I started the array without the drive and none of the docker services started even though the other drive in the mirror was online and showing healthy but in a (expected) degraded state. Since the system wasn't operational with only one drive in the ZFS mirror, I powered down the system, popped the ORIGINAL drive back in the system, and powered it on. Before manually starting the array, I noticed the ZFS mirror pool was now only showing one disk/one drive slot. I added a slot to the pool and put the ORIGINAL m.2 drive back in the new slot. Unraid warned me the drive would be wiped when starting the array and I thought this was ok since it would need to resync the data between both drives. The pool is now showing healthy with two drives, both in the unraid main tab and ZFS master. The drive that was never removed shows green and the one that was taken out and put back in shows a blue 'new device' icon. I am not sure if this means the ZFS mirror is functional and both drives are in sync. In my silliness with this entire task, I am wondering if maybe their 'slots' got reversed, and that somehow messed up the zfs pool? Running the latest BETA 7.0.0-beta.3 Could someone please let me know if there's a command I have to run or something to get the mirror back to fully operational, or if it is operational at this point even with the blue new device indicator? Thank you!

Hi! Just wanted to provide an update - since I added the line you suggested to the config AND changing all my PCI-e and NVME slots to disable aspm in the bios, the drives have been solid for a week. I'll continue to monitor it, but this is very promising and I hope it did the trick. Thank you again!

Sadly, one of the drives disappeared with this setting enabled while i was running the cach pool BTRFS scrub/repair. But they are still connected via the Highpoint card so maybe I need to put them back into the M.2 slots with this new setting.

Thank you so much for the response! I added that to my flash config and am rebooting the server now. My docker and VM images are jacked again, so I will reconfigure them with this setting enabled and see if all drives can finally be reliable. If I wanted to add this to the GUI boot option as well, would it be the text below or do I need a comma? append initrd=/bzroot,/bzroot-gui nvme_core.default_ps_max_latency_us=0 pcie_aspm=off

Hi All, Sorry for the long post, but I have been experiencing some very strange SSD issues since I upgraded my platform from an i9-10900 to a i7-12700. Its been driving me mad. I had a stable Z490/DDR4/i9-10900 server which I migrated to B660/DDR5/i7-12700 and then W680/DDR5/i7-12700. I know SSDs are technically not supported in the array, but I am not using parity so I think its ok for my purposes (also understanding that my data is unprotected). ARRAY: TWO Intel P4510 8TB U.2 NVME drives - NO PARITY CACHE: TWO WD SN850X 1TB M.2 NVME drives - BTRFS RAID 1 ARRAY DRIVE ISSUES: Upon moving to the new platform (ASUS ROG STRIX B660-I) I started experiencing issues where the NVME drives would randomly drop out. CACHE drives were connected direct to the motherboard M.2 slots and ARRAY drives were connected via a Highpoint SSD7104 PCI-e 3.0 x16 RAID card with U.2 to M.2 adapters because of ITX motherboard limitation. CACHE drives were solid/stable, but the ARRAY drives would drop off randomly - only one at a time, never both. The server would also lock up and need a hard restart every few days. The motherboard was experiencing some coil whine as well so the entire situation drove me to replace the motherboard. CACHE DRIVE ISSUES: Now I have everything in a SUPERMICRO MBD-X13SAE-F-O W680 setup. The CACHE drives were connected straight to the motherboard via the M.2 slots and the ARRAY drives are now connected via U.2 to PCI-e 3.0 x4 adapters - got rid of the highpoint pci-e card since I have additional pci-e slots now. Memory in this system is NON-ECC Team T-Force Vulcan 32GB (2 x 16GB) DDR5 FLBD532G5600HC36BDC01. Everything seemed to be running fine and stable until after a few days the CACHE drives started disappearing and I was getting nvme drive btrfs errors in my system log. Only one drive would disappear, not both. I tried setting the pci-e link speed on the m.2 drives to 4.0 manually instead of AUTO - even though the slots on the motherboard and the drives are both 4.0. Worked fine for a bit and then one drive would drop out. Did some digging on the forum and people mentioned this could be memory related issue so I set the memory to default settings. Single CACHE drive dropped and error logs came back. At this point I figured it was something with the M.2 slots on the motherboard so I reintroduced the Highpoint SSD7104 into the system and put the CACHE drives on there. Again, everything worked fine for a bit and then one CACHE drive dropped off. I tried setting the PCI-e 5.0 slot on the motherboard to 3.0 manually to match the Highpoint SSD7104 card. Worked fine for a bit and single drive gone again. At this point I assume the Highpoint SSD7104 card might be the culprit since originally the ARRAY drives were dropping off connected to it (via the U.2 to M.2 adapters) and now the CACHE drives are dropping off connected to it. However, this doesn't explain why the CACHE drives were dropping off while connected to the M.2 slots on the SUPERMICRO MBD-X13SAE-F-O directly. As it stands, I don't know if I need to replace the Team Group DDR5 memory with some ECC memory/different memory or if the WD SN850X drives are not good as CACHE drives on this motherboard. I have had to reconfigure all my dockers and my docker image numerous times in the past few weeks. All of these drives are super expensive and have worked reliably in the past on the older DDR4 platform. I am hoping someone can take a look at my diagnostics and give me an idea of where to start on fixing this. I have done some research on ASPM to see if that could be causing issues with the NVME drives but I don't know what settings to change, if any. Thank you in advance for reading and any input at all! fc-unraid-diagnostics-20230215-1022.zip

I purchased it from Newegg in the past month and it came with 2.0 installed. I didn’t install a 13th gen CPU, but assume it would have worked. also, supermicro has some compatible ecc memory on their US online store. 32gb sticks were in store for about $160 last I checked.