You are not logged in.
During installation step 7 (Install bootloader), I get the error message:
Title: "No grub?"
Msg: "Error: couldn't find /mnt/boot/grub/menu.lst. Is GRUB installed?"
All previous steps succeeded. Network is correctly configured.
I selected GRUB as my bootloader in an earlier step. I found a similar thread here and followed those steps in another TTY. I got the following:
#~ pacman -S grub
error: could not open file /var/lib/pacman/sync/etra.db: Failed to open ...
(same message for core.db, community.db, four times each).
This is a net install on i686 architecture. I verified both md5 and sha1 sums after downloading. I am installing on VirtualBox. I am following the advice from this post and using a VHA. I did not do any special configuration for it. Should I have?
Sorry for asking such a noob question...
Last edited by blacksheep (2012-07-23 11:47:40)
Offline
Same problem here. I jumped the gun and basically reproduced this thread (sorry to admin). I think this has something to do with the recent switch from grub to grub2 (since I don't think grub2 uses menu.lst). I'll poke around and let you know what I come up with (but don't get your hopes up, I'm no linux guru at all).
Offline
Offline
This is a really helpful wiki entry, thanks for helping me out. However, I ran into problems when I followed the instructions. After I configured the network and mounted all the right components, I chrooted. I then upgraded pacman's db, and tried to sync. Didn't work. Specifically on this command:
pacman -Syy
I also cannot ping any devices on my network in the chroot jail. However when I exit the chroot jail, I can ping any device on my network. What could be causing this?
Offline
Did you copy your /etc/resolv.conf to the mounted partition before chrooting? Not doing so breaks the network inside the chroot.
Offline
Grub is no longer in the repos, which is why this is breaking most likely. New installation media is coming soon to fix issues like this.
I suggest using syslinux instead.
Offline
Did you copy your /etc/resolv.conf to the mounted partition before chrooting? Not doing so breaks the network inside the chroot.
Yup, I feel stupid. This solved my issue. tyvm
Offline
Please remember to mark your thread as [Solved].
Offline