ech0chamber

Can the pools be recreated with data intact? I have not formatted the drives yet

I am still pretty new to ZFS pools. Long story short I added a new drive to one of my ZFS pools. I had a Pool just for linux ISOs. It had only a single 26 TB drive in it with the intention of adding another 26TB drive at a later date. That day was today. I realized the ZFS pool was setup for Mirror with a single drive and for some reason I couldn't add a new drive to the pool. So, I took a screenshot of my pools like and stupidly went to Tool > New config like I have always done with the Array and cache drives when I needed to create it. I didn't understand once you destroy a ZFS pool, this essentially destroys it forever. I lost 3 pools. An Appdata mirror pool with 2 2TB NVMEs, as well as a ZFS pool with 3 16TB drives in RZ1 and a 3rd pool just for Linux ISOs that had a single 26TB drive I was adding another 26TB drive to today/ Luckily I think most of it is recoverable. It'll just take me months. Only thing I need to figure out is photos I had on Immich. I think most of that is backed up elsewhere also but I'll need to see. That is my main worry right now. Can the pools be recreated with data intact? I have not formatted the drives yet State of server right now:

Okay so swapping the drive to a 990 Pro solved my issues with the system crashing and shares disappearing. Still haven't fixed the drive ID issue but since my uptime has skyrocketed and the issue resolves itself after a reboot I can live with that for now.

Funny you mention this. This just occurred to me the drive was dropping offline as I have noticed for a couple months now whenever I reboot the server, the drive would not mount and only fix is to completely poweroff the server and power back on. Frustrating as this is a brand new drive I bought in November but I think the drive is known to have Firmware issues. It is a HP FX900 Pro 4TB and only reason I bought it is cause I got it for $215. I'll try this fix and see if it fixes it but if not I am replacing the drive. Already have a Samsung Evo Plus 4TB ordered for $249 and should arrive tomorrow. My Temp fix atm the moment is a user script I wrote that tries to write a text file to one of my shares and remove it every 15 minutes and it fails, reboot the server.

Shares dropped again. New log tower-diagnostics-20250308-0817.zip

Just fixed the container issue. It was Mellisearch that was continuously crashing. Will keep an eye on the system and see if I have any issues. For some reason my Disk IDs have not changed since I created this post despite editing my boot grub line days before making this post. But I'll take the win

Okay here's another log where shares dropped off middle of the night. I'll look for the container and I may disconnect the UPS tonight so I can give you cleaner logs tomorrow tower-diagnostics-20250306-0855.zip

The .230 is my Desktop PC I don't sorry. Here's another log with the shares dropping again. I just rebooted the server again. They seem to drop every 12 hours or so. It's 5p EST here I'll check again in the morning and if it's dropped off that'll give us a general idea tower-diagnostics-20250305-1621.zip

Haven't gotten the drive IDs to change yet which is weird cause it usually does it every 2-3 reboots. But here is diagnostics after the shares disappeared tower-diagnostics-20250304-1102.zip

Thanks I'll pull fresh logs here in little bit. Rebooting the server a couple times so I can get the issues to appear. It's pretty consistent

Also just noticed my Shares keep disappearing since the 7.0 update. They come back after a reboot. If I need to reboot and attach a new diagnotics let me know. I am also having an issue with one of my NVME drives dropping off after a reboot and only way to bring it back is a complete power off of the server and manual power on lsusb -vt /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/3p, 20000M/x2 ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 10000M ID 2109:0822 VIA Labs, Inc. |__ Port 002: Dev 003, If 0, Class=Mass Storage, Driver=usb-storage, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor |__ Port 003: Dev 004, If 0, Class=Hub, Driver=hub/4p, 10000M ID 2109:0822 VIA Labs, Inc. |__ Port 001: Dev 005, If 0, Class=Mass Storage, Driver=usb-storage, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor |__ Port 003: Dev 006, If 0, Class=Mass Storage, Driver=usb-storage, 10000M ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 002: Dev 002, If 0, Class=Human Interface Device, Driver=[none], 12M ID 0764:0601 Cyber Power System, Inc. PR1500LCDRT2U UPS |__ Port 003: Dev 003, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M ID 10c4:8a2a Silicon Labs |__ Port 003: Dev 003, If 1, Class=Vendor Specific Class, Driver=cp210x, 12M ID 10c4:8a2a Silicon Labs |__ Port 004: Dev 004, If 0, Class=Hub, Driver=hub/4p, 480M ID 2109:2822 VIA Labs, Inc. |__ Port 003: Dev 006, If 0, Class=Hub, Driver=hub/4p, 480M ID 2109:2822 VIA Labs, Inc. |__ Port 010: Dev 005, If 0, Class=Wireless, Driver=btusb, 12M ID 8087:0032 Intel Corp. AX210 Bluetooth |__ Port 010: Dev 005, If 1, Class=Wireless, Driver=btusb, 12M ID 8087:0032 Intel Corp. AX210 Bluetooth /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M ID 1d6b:0003 Linux Foundation 3.0 root hub |__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive syslog-previous tower-diagnostics-20250301-1107.zip

Okay so I have actually read another post or 2 saying that this is a know bug in Unraid 7 due to a storage driver change. I have actually already tried the fix that was posted for this that is supposed to keep the hardware IDs from changing: Edit my boot line to this: kernel /bzimage append initrd=/bzroot usb_storage.quirks=2109:0715:u USB IDs: Bus 001 Device 001 Port 1-0ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001 Port 2-0ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002 Port 2-1ID 2109:0822 VIA Labs, Inc. USB3.1 Hub Bus 002 Device 003 Port 2-1.2ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor Bus 002 Device 004 Port 2-1.3ID 2109:0822 VIA Labs, Inc. USB3.1 Hub Bus 002 Device 005 Port 2-1.3.1ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor Bus 002 Device 006 Port 2-1.3.3ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor Bus 003 Device 001 Port 3-0ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002 Port 3-2ID 0764:0601 Cyber Power System, Inc. PR1500LCDRT2U UPS Bus 003 Device 003 Port 3-3ID 10c4:8a2a Silicon Labs HubZ Smart Home Controller Bus 003 Device 004 Port 3-4ID 2109:2822 VIA Labs, Inc. USB2.0 Hub Bus 003 Device 005 Port 3-10ID 8087:0032 Intel Corp. AX210 Bluetooth Bus 003 Device 006 Port 3-4.3ID 2109:2822 VIA Labs, Inc. USB2.0 Hub Bus 004 Device 001 Port 4-0ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 002 Port 4-1ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive JBOD: Bus 002 Device 005 Port 2-1.3.1ID 2109:0715 VIA Labs, Inc. VL817 SATA Adaptor Hardware: MINISFORUM MS-01 Yottamaster 5 Bay RAID Hard Drive Enclosure in JBOD mode

I guess I can try but I know from prior instances, server really hates Macvlan

I'm using directory. Not an image

Issue came back with a single container running. IDK what's going on!