I don't know if it was able to mount root. Gummiboot was probably fine with the PARTUUID. The problem was in fstab. At any rate, have you heard of seclabel? Have you tried switching your fstab to PARTUUIDs? I was wrong about this being in the beginner's guide (it's actually on the fstab page), but I'm curious if it'll work. On Thu, Nov 6, 2014, at 05:39 AM, Damien Robert wrote: > vixsomnis wrote in message > <1415255453.3685895.187687373.7A25E4C3@xxxxxxxxxxxxxxxxxxxxxxxxxxx>: > > Weird issues with genfstab: > > - When I run with the -U option, no UUIDs are placed in fstab. > > With the -L option, no labels. Am I correct in thinking that the > > "/dev/sdX" should be replaced with UUIDs and labels, respectively? > > Yes. > > > Also, on following the Arch Wiki's advice in the beginner's guide: I > > used PARTUUIDs in my fstab and gummiboot entries. My system wasn't able > > to boot with these, which I had gotten from "blkid". > > Where did it fails exactly? Was the initrd able to mount your slash? > > > When I switched > > them out for regular UUIDs, I had no problems, and my system booted > > flawlessly. If someone could confirm that we should be using UUIDs, I'll > > change this on the wiki. If PARTUUIDs *should* work, can someone please > > explain why? Or maybe just vouch that they work on your system? I've > > never had success with them. I'll edit the wiki once this is verified, > > or otherwise resolved. > > For gummiboot I use > title Arch Linux > linux /vmlinuz-linux > initrd /initramfs-linux.img > options root=PARTUUID="986178da-85b0-4a7c-a0ec-600adfa32be7" > and it works well. > > My fstab uses UUID though because I generate it with genfstab -U; but for > mounting slash only the linux kernel options should matter at the initrd > stage; up to the normal boot where slash will be remounted by > systemd-remount-fs if it is in the fstab.
