You are not logged in.
I used Virtualbox on a Windows host to install Arch onto a usb stick. I can boot into the os on virtualbox just fine (after creating a virtual harddrive that points to the usb stick), but **not** on actual hardware. Syslinux works fine, but it can't find the root partition during early boot.
Both syslinux.cfg and fstab are using PARTUUID labels to find the root partition. Is it possible that PARTUUID is different on virtualbox than actual hardware?
Last edited by AaronBP (2015-10-11 20:20:52)
Offline
Um I doubt that but for fstab I do
genfstab /mnt >> /mnt/etc/fstab
Also how did you install it ?
Offline
Hmmm...you may have to mkinitcpio out of virtualbox since it does use different /dev entries.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Um I doubt that but for fstab I do
genfstab /mnt >> /mnt/etc/fstabAlso how did you install it ?
IIRC, genfstab used UUID, and I switched to PARTUUID when that didn't work. I didn't write down all the commands I used, but I go pretty much by the book.
Hmmm...you may have to mkinitcpio out of virtualbox since it does use different /dev entries.
Hum. Syslinux is able to find and load the kernel. It's early boot that fails. Should it matter? I don't have /dev entries in fstab or syslinux.cfg. If you think so, it will take awhile before I can try this solution, but if I get a chance I'll report back if it works.
Note that when boot fails, it says that it can't find /dev/by-partuuid/$partuuid (should have mentioned before).
Offline
it worked! This begs the question -- for my curiosity more than any real need -- how would I install arch so that it will run on both actual hardware and virtualbox? The install iso does, after all.
Offline