The first symptom that I have observed is that dhcpcd isn't able to update /etc/resolv.conf
I am going to provide as much relevant info so you can tell me what to look for
1. Installed from december iso on newly created GPT ext4 partitions
2. Bootloader GRUB2 x86_64
3. Did a systemctl mask tmpfs as I am mounting a disk partition on /tmp from fstab
4. Double checked 2-3 times that all my mounts are rw in fstab
5. Once logged, I have no problem doing "mount -o remount,rw /"
6. I have removed the ro kernel parameter option in grub.cfg (BTW, why is this used at all? I'm a little bit ignorant about Linux booting good practices). By doing so rootfs still remains ro.
I am suspecting either systemd or the content of the initramfs. Until now, those are still black boxes to me. What should I look at to resolve my rootfs ro problem?
thank you very much!
(A new Arch user and extremely happy to have found and tried your distribution!)
Last edited by lano1106 (2012-12-03 18:21:16)
I'm not totally ruling out that there is a problem with my fstab but I haven't forgetten that step.
Would the command 'mount -a' eliminate that potential cause?
See point #4 in the initial post.
I have about 7 entries in my fstab
networked CIFS drive
/dev/sda1 being the 2MB bios_grub partition required for GPT boot from BIOS.
The weird thing is that all partitions are ext4 with the same basic options generated by genfstab: rw,relatime
and only / is ro at boot.
Last edited by lano1106 (2012-12-03 18:43:16)
/tmp is no longer needed.
Maybe there is a fs error on /. Usually / takes the option errors=remount-ro in fstab so this will happen if a problem is found.
I have finally found my problem. I have messes around with systemd and eventually, I wasn't able to get to the login prompt. At that point, I have decided to redo the installation from scratch.
My goal on the second attempt was to get something up and running fast hence, I have left to later all the small tweaking that I have set up on my first attempt.
One of the thing is that I wanted is to have a disk partition mounted on /tmp rather than having a tmpfs mount so I followed the recommendation in the Beginners guide that says to do:
systemctl mask tmp.mount
as soon as you do that and reboot it has the side effect that systemd do not remount the rootfs with the options specified in /etc/fstab (in my case rw)
to fix the problem, I just did
systemctl unmask tmp.mount
It seems that just specifying another partition for /tmp, it is enough for systemd to not use tmpfs.
On a modern setup with initramfs and the 'fsck' enabled in the default mkinitcpio.conf, you can simply use 'rw' on the kernel command line. Bonus: Faster boot time with 'systemctl mask systemd-remount-fs.service'.