Jump to content

Unraid VM's root disk is unbootable and shows no partitions available after config changes.

Go to solution Solved by Kilrah,

Check you're using the right vdisk, by default the vdisk is put in a folder with the vm name, if you renamed the VM it might not have followed /created a new one.

Hey, so I working on a VM which is running on an Unraid server. I powered the machine down using the Unraid controls (clean shutdown, no force stop) and changed the name, as well as removed the install ISO from the virtual CD-ROM (I'd forgotten to remove it after setting up the VM). The boot drive is still present in the config. Upon attempting to boot the VM, the system boots into BIOS since the disk doesn't have any partitions to boot from. I confirmed this by booting into a live Debian CD and using rescue mode. fdisk shows no partitions on the disk:

# fdisk -l
Disk /dev/sda: 70.98 GiB, some bytes, some sectors

Disk model: QEMU HARDDISK
Units: sectors of 1 * 512 = 512 bytes, Sector size, etc

 

shows no partitions, even though the virtual drive is showing up. I searched around for anything that might tip me off to what's going on, but I am at a loss. Hopefully someone here might know what is going on with this silly goose - I'll also provide other screenshots if needed. (edit: hope this is the right thread for something like this)

Screenshot 2024-05-17 100730.png

 

Screenshot 2024-05-17 102047.png

Link to comment
Share on other sites

Link to post
Share on other sites

Check you're using the right vdisk, by default the vdisk is put in a folder with the vm name, if you renamed the VM it might not have followed /created a new one.

F@H
Desktop: i9-13900K, ASUS Z790-E, 64GB DDR5-6000 CL36, RTX3080, 2TB MP600 Pro XT, 2TB SX8200Pro, 2x16TB Ironwolf RAID0, Corsair HX1200, Antec Vortex 360 AIO, Thermaltake Versa H25 TG, Samsung 4K curved 49" TV, 23" secondary, Mountain Everest Max

Mobile SFF rig: i9-9900K, Noctua NH-L9i, Asrock Z390 Phantom ITX-AC, 32GB, GTX1070, 2x1TB SX8200Pro RAID0, 2x5TB 2.5" HDD RAID0, Athena 500W Flex (Noctua fan), Custom 4.7l 3D printed case

 

Asus Zenbook UM325UA, Ryzen 7 5700u, 16GB, 1TB, OLED

 

GPD Win 2

Link to comment
Share on other sites

Link to post
Share on other sites

55 minutes ago, Kilrah said:

Check you're using the right vdisk, by default the vdisk is put in a folder with the vm name, if you renamed the VM it might not have followed /created a new one.

I went ahead and renamed the VM to its original name, which strangely, seemed to have restored the disk image in /mnt/user/domains/<domain>/vdisk1.img, but it still will not recognize it as bootable or show any partitions. I used "cat" to see if there was anything in the file, the disk image definitely contains the data for the VM - so that's good I suppose? I'm going to see if I can just recover the data out of the image and rebuild the VM. 

Link to comment
Share on other sites

Link to post
Share on other sites

Maybe your vdisk never was made properly bootable and you were able to boot only because the cdrom was still assigned?

F@H
Desktop: i9-13900K, ASUS Z790-E, 64GB DDR5-6000 CL36, RTX3080, 2TB MP600 Pro XT, 2TB SX8200Pro, 2x16TB Ironwolf RAID0, Corsair HX1200, Antec Vortex 360 AIO, Thermaltake Versa H25 TG, Samsung 4K curved 49" TV, 23" secondary, Mountain Everest Max

Mobile SFF rig: i9-9900K, Noctua NH-L9i, Asrock Z390 Phantom ITX-AC, 32GB, GTX1070, 2x1TB SX8200Pro RAID0, 2x5TB 2.5" HDD RAID0, Athena 500W Flex (Noctua fan), Custom 4.7l 3D printed case

 

Asus Zenbook UM325UA, Ryzen 7 5700u, 16GB, 1TB, OLED

 

GPD Win 2

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×