You are not logged in.
Hello,
I was inspired by the arch beginners installation wiki to make a seperate boot partition. I did this.
However, after setting up my fstab, i tried rebooting and my system complained it couldn't find my boot files.
So i put the boot dir back on my root partition and it works.
If i have to keep a boot dir on my root partition, whats the point of a seperate boot partition?
Or am i doing something wrong?
Last edited by fawkes5 (2013-04-24 21:11:01)
Offline
Yes you are doing something wrong. If you have a separate boot, did you make sure that your bootloader (grub or syslinux) knows about it ?
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
Partitions (etc.) need to be mounted to directories. So you need a directory (preferably empty) named boot at / if you want to use a separate boot partition.
Edit: Oops, I think Inxsible's grasp of the situation is probably better than mine...
Last edited by alphaniner (2013-04-24 21:24:40)
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
Yes you are doing something wrong. If you have a separate boot, did you make sure that your bootloader (grub or syslinux) knows about it ?
No i did not. Only my fstab knows about it.
I'm using syslinux. I'll check it out. Post back if i have any problems. Thank you both!
Offline
the only diff is partition if no sepparatte partition is specified it will make a folder in / if a partition is specified it will mount it to the folder. fstab is looked at at boot. the only other seperate partion or linked file system that needs consideration is usr which needs a hook in mkinitcpio. syslinux.cfg needs to point to / either uuid or path.
--------------------------------------
alcoves wonder creates the wonder unto the ages; never lose that.
Offline
syslinux.cfg may only need to point to the real root, but the MBR code needs to point to the boot partition. fstab, mkinitcpio, and all such things are irrelevant if the MBR isn't pointing to a bootable kernel image.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Syslinux uses the "bootable" flag. You need to change that to be the new boot partition.
Offline
I should of mentioned that i'm using GPT.
Offline
i think ill just reinstall syslinux. According to the arch wiki, the automatic install should take care of everything when my /boot partition is actually mounted [which it wasn't when i set up syslinux]
https://wiki.archlinux.org/index.php/Syslinux
Offline
There is still a boot bit flag and "mbr code" (gptmbr).
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline