Nads

Thank you so much for all your help and everything you do. You're a gem!

Completed the abovementioned steps. Docker image recreated, Docker containers reinstalled, and it works! As for Libvert, it still doesn't work. I don't have a backup and that's fine by me because I plan to start from scratch to create new VMs. Would I be setting "Enable VMs" to No, click Apply, check off the "Delete Image File" box for Libvert, click Apply, and then setting "Enable VMs" to Yes", click Apply?

Went into my first NVMe drive and clicked Scrub. These are the results below

Hello! Can someone take a look at my file, I'm having the same issue with Docker Service failed to start. unraid-tower-diagnostics-20251204-0034.zip

I recently got rid of my Windows VM which was running off of a SATA SSD drive. I removed the drive after I safely shutdown my server. After booting it up, my Docker tab now says "Docker Service failed to start" and VMS tab says "Libvirt Service failed to start". The VMS tab I don't care about cause I am no longer using VMs on my Unraid Server. I did not want to act out or attempt anything that's why I'm here asking the best first steps to resolve and restore my Docker containers. unraid-tower-diagnostics-20251204-0034.zip

Here's the diagnostics. I hope you're able to determine the cause so I won't have to deal with this issue again. Cheers! unraid-tower-diagnostics-20250618-0000.zip

@JorgeB Sorry for the delayed response, I was out of town for a while. Great news! As of a few minutes ago, the backup I had made back in March 2025 of 7.0.1 worked! I restored to 7.0.1, and nothing else was needed in terms of a new config. All photos and videos are present, and Plex is up and running. I'm gonna stick to 7.0.1 for a while and not get trigger-happy updating to the latest stable build. Thank you for your help and dedication; it helped me get here. I'm not sure why or how things broke in 7.1.2, but hopefully this won't happen again if/when I update down the road.

It's still running...

With the array stopped, I entered the commands, and this is what I got (see screenshot). I tried that command for my 4 TB drive to test, it worked fine. I do see a single line output, but not the case for the 14 TB & 12 TB. The 14 TB drive (sdf) is in XFS, but the partition format is "custom" vs the 4 TB drive is "4KiB-aligned". Not sure if that matters. Also, when I set up this Unraid server a couple of months ago, I formatted the drives in XFS in Unraid. I'm not sure how or why it says 'Windows formatted disk.' Maybe it was formatted in Windows once before? Would restoring 7.0.1 using the zip file put the drives' config back or would it not matter cause it's now a Windows formatted disk?

Understood. Just a side note, I have a 7.0.1 (back when everything worked normally) flash backup zip file. If I were to restore using that, would it restore my original device config, as I already did a "new config" mentioned above, and be able to access my files in the 12 & 14 TB normally? I'm just having trouble mounting; it's greyed out. I've looked into other forum posts for solutions.

root@Unraid-Tower:~# fdisk -l /dev/sdf Disk /dev/sdf: 12.73 TiB, 14000519643136 bytes, 27344764928 sectors Disk model: ST14000NM001G-2K Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: E7BE130F-2699-49F7-866F-587D5C058DC6 Device Start End Sectors Size Type /dev/sdf1 2048 27344762879 27344760832 12.7T Microsoft basic data root@Unraid-Tower:~# fdisk -l /dev/sdc Disk /dev/sdc: 10.91 TiB, 12000138625024 bytes, 23437770752 sectors Disk model: ST12000NM000J-2T Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 16773120 bytes Disklabel type: gpt Disk identifier: 29218FE3-6CB2-4F70-AB68-D7FED1605C55 Device Start End Sectors Size Type /dev/sdc1 2048 23437768703 23437766656 10.9T Microsoft basic data root@Unraid-Tower:~#

I just did it. Stopped the array, entered the command one by one, but no output was generated.

unraid-tower-diagnostics-20250511-2036.zip Latest Diag

root@Unraid-Tower:~# lsblk -lo TYPE,PARTN,NAME,START,SIZE,PTTYPE,PARTTYPE,FSTYPE,LABEL,SERIAL TYPE PARTN NAME START SIZE PTTYPE PARTTYPE FSTYPE LABEL SERIAL loop loop0 579.7M squashfs loop loop1 169.8M squashfs loop loop2 20G btrfs loop loop3 1G btrfs disk sda 14.4G dos F46D0461E280F1A0A94D0187 part 1 sda1 2048 14.4G dos 0xc vfat UNRAID disk sdb 3.6T gpt WD-WCC7K5TY8K0Y part 1 sdb1 64 3.6T gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 xfs disk sdc 10.9T gpt ZRT1HFF4 part 1 sdc1 2048 10.9T gpt ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 disk sdd 14.6T gpt ZR59J2JK part 1 sdd1 64 14.6T gpt 0fc63daf-8483-4772-8e79-3d69d8477de4 disk sde 931.5G gpt S59VNJ0NA00987F part 1 sde1 2048 100M gpt c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat part 2 sde2 206848 16M gpt e3c9e316-0b5c-4db8-817d-f92df00215ae part 3 sde3 239616 930.6G gpt ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs part 4 sde4 1951932416 775M gpt de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs disk sdf 12.7T gpt ZTM0ME8H part 1 sdf1 2048 12.7T gpt ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 md md1p1 12.7T md md2p1 10.9T md md3p1 3.6T disk nvme0n1 931.5G dos 2325E6E73C78 part 1 nvme0n1p1 2048 931.5G dos 0x83 btrfs root@Unraid-Tower:~# wipefs /dev/sdc1 wipefs: error: /dev/sdc1: probing initialization failed: No such file or directory root@Unraid-Tower:~# wipefs /dev/sdf1 wipefs: error: /dev/sdf1: probing initialization failed: No such file or directory root@Unraid-Tower:~# wipefs /dev/sdc DEVICE OFFSET TYPE UUID LABEL sdc 0x200 gpt sdc 0xae9fffffe00 gpt sdc 0x1fe PMBR root@Unraid-Tower:~# wipefs /dev/sdf DEVICE OFFSET TYPE UUID LABEL sdf 0x200 gpt sdf 0xcbbbffffe00 gpt sdf 0x1fe PMBR root@Unraid-Tower:~# Sorry, this should be more accurate. SDC1 is 12 TB, SDF1 is 14 TB.