Arch Linux

Veske

Member

Registered: 2015-01-13

Posts: 12

[SOLVED] Unable to boot freshly installed system

So I installed a new Arch system on Virtualbox and I am having a bit of trouble here.

When I try to boot the new system, I get this error:

Failed to load COM32 file boot/syslinux/chain.c32

So I figured that maybe I am missing the file indeed from my /boot/syslinux folder, and so it was. So I went on and did this: syslinux-install_update -i -a -m which created all the files needed into the folder and also it made the syslinux.cfg file.

Now booting again and the same problem appears. I copy the chain.c32 from /boot/syslinux/ to / and reboot, same problem but this time I type in chain.c32 and it actually seems to manage to load the file. But then another error appears:

Booting....
isolinux.bin missing or corrupt.
FATAL: INT18: BOOT FAILURE

Googling around it seems that the problem has occurred to people only when trying to install a Linux system on USB stick. But that is not the case here as I am installing it on a Virutalbox drive.

What could have gone wrong here?

Last edited by Veske (2015-02-18 16:21:26)

nullified

Member

From: Massachusetts, USA

Registered: 2013-12-09

Posts: 468

Re: [SOLVED] Unable to boot freshly installed system

What guide or guides did you follow, if any? Did you use this guide as well?

---

"We may say most aptly, that the Analytical Engine weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves." - Ada Lovelace

Veske

Member

Registered: 2015-01-13

Posts: 12

Re: [SOLVED] Unable to boot freshly installed system

Well I just went naturally. Made partitions(/, /home, swap, BIOS boot), formatted them, sources list, installed system,, fstab, locales, time, languages, GRUB install, root pw and user. The virtualbox guide does not give much more needed currently, I would worry about fancy guest additions and advanced mounting after I get the system running at least. Right now it is not even doing that.

I am not sure tough why is it trying to get into syslinux at all when I boot, I installed GRUB for my bootloader.
I uninstalled syslinux from my system and updates grub, installed it again and created the conf file for it. But when I boot to system, I still don't see the GRUB loader but the syslinux errors.

EDIT: I don't know what caused it but I just waited after the error for like 2 minutes and then it suddenly booted into the system and everything is working fine. It's just that everytime I reboot, it takes a long time to get into the system.

Last edited by Veske (2015-02-18 16:21:11)