Search results

And again, I figured it out. The dd and resulting .raw image was fine, all that was needed extra was to set the cache mode as "write-through" or "write-back" for the VM's hard disk file in the VM's configuration (something that was not needed when using a zvol).

I tried the below command to convert a VM's zvol to a .raw file, however when trying to boot using that .raw file, the system says there are no bootable devices. dd if=/dev/zvol/flashpool/vm-101-disk-1 of=/flashpool/vm-101-disk-1.raw bs=1M Upon further inspection, I have discovered more than...

After a bit of digging around I solved the issue. ZVols are block devices - file level access isn't possible. Instead what one must do if wishing to share a VM drive over NFS is to convert the zvol to a disk image, in my case I chose .raw. This can be accomplished using the dd utility: dd...

Hello all, I'm hoping you maybe able to help me as I seem a bit in over my head this time. I have three physical servers that I am working to build into an HA cluster. Two of those servers will be the processing power (hereafter referred to as P1 and P2) of the cluster and one is the storage...

Okay so when running with the udev.log-priority tag in the kernel entry, the system boots to: "Unloaded link configuration context. Unloaded link configuration context. Unloaded link configuration context..." Repeated over and over, and then, "worker [403] exited" With all of the number...

Sorry for the wait there. So what I ended up doing was to run a fresh install on the server - then upgrade it through apt-get, reboot, and then run dist-upgrade to pull in the new kernel again. Interestingly enough, I still have to manually import the rpool and it still hangs at the same point...

Okay, even though I've already settled for just restoring from backup, I'd like to get you what you need to look at in case it maybe of help to others. What would be the best way to do that? Sorry for the noob question, would a boot.log or a journalctl dump be appropriate?

Thanks for your reply Fabian, I'm sorry that I've been unclear. :E On either of the servers, under the new kernel I cannot boot successfully even if I manually import the pool. It always hangs at the point shown in the screenshot - I've left it running for over an hour and nothing changed. The...

I've given up for the moment, I have 24 hours before I'll need to use these servers. My solution has been to have the system always boot with the old kernel for the time being - at least until the dev's have had time to realize the issues this is causing some people and cook up the appropriate...

Mike, have you tried running initramfs-update -u? While it didn't work for me, considering you are able to completely boot after manually importing the pool this may be worth a try for you, as well as the rootdelay option in grub (hit "e" when grub shows, manually append "rootdelay=30" to the...

Same here, I have two servers that have the same issue. On one of them when I went to manually import the rpool it notified me that I needed to upgrade the pool - being an idiot, I did (zpool upgrade rpool). So after importing the pool manually and continuing the boot process, the boot hangs...