Ubuntu VM unbootable .img after reboot


Recommended Posts

ok, so i rebooted my Unraid server (not for the first time, more like 3rd time), and my ubuntu VM says that the img is no longer bootable? but the .img is still there.

 

i can not figure out how to fix it to get it to boot again

 

i cant think of any steps to take to try to fix it

Link to comment

Did you make any custom edits to the XML for your VM?  From your logs, I did see one particular line that stuck out:

 

2017-09-27 17:22:22.112+0000: 3531: error : virDomainDiskDefCheckDuplicateInfo:25575 : XML error: target 'hdc' duplicated for disk sources '/mnt/user/domains/Ubuntu/vdisk1.img' and '<null>'

 

I'm curious why you're using IDE as the bus type for the virtual storage on this VM as well (instead of VirtIO).

Link to comment

Another issue I see in the logs is a call trace relating to IRQs:

 

Sep 27 10:49:36 tower kernel: Call Trace:
Sep 27 10:49:36 tower kernel: <IRQ> 
Sep 27 10:49:36 tower kernel: [<ffffffff813a4a1b>] dump_stack+0x61/0x7e
Sep 27 10:49:36 tower kernel: [<ffffffff810864d1>] __report_bad_irq+0x2b/0xb4
Sep 27 10:49:36 tower kernel: [<ffffffff8108679a>] note_interrupt+0x1a0/0x22e
Sep 27 10:49:36 tower kernel: [<ffffffff81084384>] handle_irq_event_percpu+0x3d/0x46
Sep 27 10:49:36 tower kernel: [<ffffffff810843c3>] handle_irq_event+0x36/0x54
Sep 27 10:49:36 tower kernel: [<ffffffff810872e6>] handle_fasteoi_irq+0x90/0xf8
Sep 27 10:49:36 tower kernel: [<ffffffff81020585>] handle_irq+0x17/0x1b
Sep 27 10:49:36 tower kernel: [<ffffffff8101ffda>] do_IRQ+0x46/0xc2
Sep 27 10:49:36 tower kernel: [<ffffffff8167fec2>] common_interrupt+0x82/0x82
Sep 27 10:49:36 tower kernel: <EOI> 
Sep 27 10:49:36 tower kernel: handlers:
Sep 27 10:49:36 tower kernel: [<ffffffff814fa942>] usb_hcd_irq

 

Seems like you might have some bad hardware on your hands or something else.  What's not ringing any bells for me is the fact that you state nothing really changed before the VM stopped booting.   Also, did originally set this system up with or without a cache pool?  Did you add a cache pool later?  Anything at all you can think of that was changed close to the time the VM stopped working?

 

All the best,


Jon

Link to comment

as far as before and after the VM stopped working, I was going to be moving everything into a new case as the case it's in is the stock HP Z620 case and is limited to 3 Drives, so I got a new case that allows 8 drives and 2 SSDs', but upon starting to take it apart I realized that I was going to need to get a CPU backplate as the HP Z620 has one build into the case, so I put it all back together the same way, and that's when it stopped.

 

cache was there when the unraid was setup, and is still there today, i will be adding another SSD to it when i move it to a new case as well as more HDD's

Edited by cheabred
Link to comment

now, i did just get some more RAM for this, so i will be adding in another 2 sticks for a total of 24GB of ram as well. so i will be rebooting the main Unraid box yet again later this week

but i had a windows 8.1 VM that was set up the same day as the Ubuntu one, and it has and still is working, in fact, its the one I'm typing this one on right now haha

Edited by cheabred
Link to comment

So I've just run into a similar issue after newly passing through a USB controller. I followed SpaceInvaderOne's video to do this but when I passed it through an already working Ubuntu VM I got a similar message, see attached.

 

My solution was to switch from USB3.0 to USB2.0 which allowed me to boot and then I tried USB3.0 again and it worked.

 

I've also attached the VM's XML for both the working 2.0 and 3.0 setups if they make a difference.

 

Hope this helps!

 

errorMsg.png

ubuntuXMLusb2Passthrough.xml

ubuntuXMLusb3Passthrough.xml

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.