* FC2-re0127.3 * initscripts-7.43-2 anaconda reports an fatal error installing initscripts. Happening on all installs. VC1 shows a bunch of errors from rpmdb like rpmdb: /var/lib/rpm/Triggername: unable to flush: Read-only file system (repeat for various rpm related files)
What is the error?
Created attachment 97307 [details] output of rpm on VC2 this is the output of running % rpm --root /mnt/sysimage -ivh /mnt/source/Fedora/RPMS/initscripts-..... There are a bunch of errors about being unable to create files. Somehow /mnt/sysimage managed to get remounted as read-only. So, probably not an initscripts bug (unless initscripts did the remount). Not really sure where problem is coming from....
The first warning is just a key thing. The %pre failed presumably because of the read-only filesystem. Punting to anaconda.
This was the first kernel bug that we hit last night. sct has a fix for it, but then we hit more :/
Created attachment 97311 [details] log of /proc/mounts and install.log during install This log shows the output of: - date - grep /mnt/sysimage /proc/mounts - tail -n 3 /mnt/sysimage/root/install.log during the course of the install. As you can see, /mnt/sysimage is mounted read-write until anaconda begins installing initscripts. At that point: - /mnt/sysimage shows up as being mounted read-only - the tail of install.log contains only null characters
I am no longer seeing these symptoms in the installer. Is this bug fixed in the kernel, or has Jeremy implemented a workaround in the installer? If the former, please close.
Just worked around for now (we're not doing selinux stuff for test1 :()
did this ever get fixed properly ?