After update, pxe client does not remount root rw anymore

[sidamos]

HI!

After I updated my PXE diskless client today, it won't boot anymore. I updated only packages, not the kernel.

I get errors like
* Skipping /etc/mtab initialization (ro root?)
* Updating modules.dep
FATAL: Could not open ...../modules.dep.temp for writing: Read-only file system
rm: Cannot remove /fastboot: File system is read-only

These messages lead me to the conclusion, that the root fs is not being remounted rw anymore.

/etc/exports on the server and /etc/fstab on the client should be OK, because it worked before the update.

I tried adding "mount -n -o remount,rw -" to /etc/init.d/checkroot, as suggested here: https://forums.gentoo.org/viewtopic-t-719501-highlight-nfs+remount.html

I also tried patching /usr/share/genkernel/generic/linuxrc with the patch from https://bugs.gentoo.org/show_bug.cgi?id=246759.

Both did not help. Or should I have rebuilt the current kernel to make the 2nd solution working?

Any help would be greatly appreciated.

Thanks!

Thomas

These are the packages, that have been updated:

[sidamos]

I got some more info:

During boot, I am missing this message:
Remounting root filesystem read/write

So, it even does not try to remount the root fs rw.

Searching around the Internet, I think maybe this update has caused the problem:
sys-apps/util-linux, 2.13.1.1 -> 2.14.1

But is it a bug? Then how to workaround? Or is it a new feature? Then how to configure?

BTW: During this update, I also switched from profile 2007.0 to 2008.0. But that did not cause many rebuilds.

This is the filesystem in /etc/exports:
/pxe/frontend 192.168.0.5(rw,sync,no_root_squash)

This is /etc/fstab on the client:
192.168.0.7:/pxe/frontend / nfs nfsvers=3,tcp,intr,rw,nolock,rsize=8192,wsize=8192 0 0

These are the boot options in pxelinux.cfg:
append initrd=initramfs-genkernel-x86-2.6.25-gentoo-r8 ip=dhcp real_root=/dev/nfs nfsroot=192.168.0.7:/pxe/frontend vga=791 splash=silent,theme:livecd-2007.0 console=tty1 quiet


Thanks for any hints.

[sidamos]

Upon further investigation, I found out, that mount behaves differently in the newer util-linux, which causes /etc/init.d/checkroot to act differently.

checkroot: