New Question

Nano server won't boot

asked 2017-05-18 12:28:22 +0300

johan-borch gravatar image


I created a Nano server image for KVM using the offline tools and this guide:

After uploading the image and launching an instance it fails on: "Inaccessible Boot Device"

I got the same problem when trying to create a windows2016 image using Cloudbase tools, and it seems like the tools somehow fails to inject the correct disk drivers?

I got the windows 2016 to run using virt-manager and installing manually, but I would rather use Cloudbase tools for nano server.

So my question is, are the disk drivers not injected correly or am I missing something?

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted

answered 2017-05-18 13:19:00 +0300

avladu gravatar image


Can you check in the mounted nano disk that the VirtIO drivers have been correctly installed? You can do that by checking if:

ls mount_point:\windows\inf\oem* returns a list of virtio drivers inf files.

Also, can you provide the nano image generation log in a pastebin, if possible? It would help a lot.

Thank you,
Adrian Vladu

edit flag offensive delete link more


Here is the log Can't find any files that starts with oem: ---- J:\Windows\INF>dir oem* Volume in drive J has no label. Volume Serial Number is Directory of J:\Windows\INF File Not Found -----

johan-borch gravatar imagejohan-borch ( 2017-05-18 16:51:21 +0300 )edit

Hello, from what I see you are not using our tools to generate the nano image. Please use the repository, where you can find in the Readme the how-to's necessary to generate the image.

avladu gravatar imageavladu ( 2017-05-18 17:48:51 +0300 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2017-05-18 12:28:22 +0300

Seen: 454 times

Last updated: May 18 '17