January 18, 20251 yr Hi Sorry if the writing below is a bit hectic, I'm a bit stressed at the moment... Let me cut right to the chase; I was an idiot while swapping my old Cache drive for a new one and I am currently trying to recover the situation. First of all this is the first time I have done something like this in Unraid so please consider me a noob. When swapping the drive I forgot to backup the appdata folder and now all my Docker containers are missing and my VMs cant start with an error message "Libvirt Service failed to start.". I thought I just could plug the old drive back in and assign it as Cache again, but when trying to do that, it prompts me to format the drive. Knowing that the data is still on there I aborted that idea. The next idea was to restore from a backup I had (although it was created in May 2024), but when trying to restore from that backup it just tells me "The selected source seems invalid". Feeling down I at least wanted to start my VMs again since I run my Home Assistant from that, but when attempting to start the VMs i get this error "Libvirt Service failed to start.". Ok, fine. Lets try and fix that... I go to settings and point to /mnt/user/system/libvirt/libvirt.img but I then discover that directory is also empty. Starting to panic a little bit. I dont want to spend 4 days setting up everything from scratch. Is there a way to reinstate the old drive as the cache drive and restore normal operations? tower-diagnostics-20250118-1559.zip
January 18, 20251 yr Disclaimer, I don't know much about this as I've yet to do it but since you are stressed, I'll give a suggestion. Libvirt is probably missing. Seems it's in the "System" share and if that was on your cache drive, that could be why your docker containers won't start. /mnt/usr/system/libvirt/libvirt.img /mnt/usr/system/docker/docker.img
January 18, 20251 yr Author 51 minutes ago, Mr.Grumpy said: Disclaimer, I don't know much about this as I've yet to do it but since you are stressed, I'll give a suggestion. Libvirt is probably missing. Seems it's in the "System" share and if that was on your cache drive, that could be why your docker containers won't start. /mnt/usr/system/libvirt/libvirt.img /mnt/usr/system/docker/docker.img Thanks for tuning in. I eventually found out that the libvirt.img file didn't get restored because in my panic I forgot to set the file size in the settings. Still need to restore the VMs. Some of them was on my array, but it seems my Home Assistant VM was on the cache drive only (idk why).
January 18, 20251 yr Community Expert 5 minutes ago, uptivuptiz said: Some of them was on my array, but it seems my Home Assistant VM was on the cache drive only (idk why) You ultimately want those shares (appdata, system, domains) on cache. Would have been better if you just disabled Docker and VM Manager until you got cache going again.
January 18, 20251 yr Author 51 minutes ago, trurl said: You ultimately want those shares (appdata, system, domains) on cache. Would have been better if you just disabled Docker and VM Manager until you got cache going again. When doing the initial swap I did turn off Docker and VMs in the Settings. Although in my panic to fix the mess I created I turned on VMs and Docker to assess the situation. Still searching for a way to make Unraid accept the old cache drive so I can recover the files.
January 18, 20251 yr Community Expert 21 minutes ago, uptivuptiz said: When doing the initial swap I did turn off Docker and VMs in the Settings. Although in my panic to fix the mess I created I turned on VMs and Docker to assess the situation. Still searching for a way to make Unraid accept the old cache drive so I can recover the files. If the drive is OK and it’s file system is intact then it should mount under Unassigned Devices.
January 18, 20251 yr Author 54 minutes ago, itimpi said: If the drive is OK and it’s file system is intact then it should mount under Unassigned Devices. That was what I thought too, but when I went to mount it, I could only format before mounting... Pulling the drive out and attaching to one of my other Linux boxes showed that the drive is unformatted for some reason. I dont understand how that could happen as I never formatted the drive after swapping it.
January 19, 20251 yr Author 2 hours ago, JorgeB said: Post the output of fdisk -l /dev/sdX for the old cache drive fdisk -l /dev/sdi gives me the following: Disk /dev/sdi: 223.57 GiB, 240057409536 bytes, 468862128 sectors Disk model: NV-C01 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes The disk model is incorrect because I re-attached the drive through a USB adapter. The drive is a Corsair MP510 SSD.
January 19, 20251 yr Community Expert 9 minutes ago, uptivuptiz said: The disk model is incorrect because I re-attached the drive through a USB adapter. The drive is a Corsair MP510 SSD. Sounds as if the issue if the USB adapter is not passing through all the correct information to Unraid. This is a common problem with USB adapters.
January 19, 20251 yr Community Expert That confirms the partition was deleted, assuming that USB bridge is transparent, type sfdisk /dev/sdi then type 2048 and hit enter, don't do anything else, just post the output from that
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.