Problem seems to be SOLVED!
Am 22.02.2013 14:39, schrieb sf...@users.sourceforge.net:
> These outputs are totally wrong.
> I am afraid your "/bin/mount --move /proc ${TARGET}/proc" doesn't work,
> or if it really works then traversing mount tree is broken.
> I'd suggest you to try these instead of "mount --move"
> - mount --bind /proc ${TARGET}/proc
> or
> - mount -t proc ${TARGET}/proc
After changing the lines moving /proc and /sys to just unmounting and
mounting again at the new mount point the problem is gone:
# Move virtual filesystems over to the real filesystem
#/bin/mount --move /sys ${TARGET}/sys
#/bin/mount --move /proc ${TARGET}/proc
umount /proc
/bin/mount -t proc -o nodev,noexec,nosuid none ${TARGET}/proc
umount /sys
/bin/mount -t sysfs -o nodev,noexec,nosuid none ${TARGET}/sys
I will finish checking the script on Thursday, trying to switch back to
using the busybox mount and checking if the problem comes back with the
"/bin/mount --move" just to make sure that these really have been the
problem. I will give you the results and post the functioning initramfs
init script.
Please let me apologize for not seeing the obvious, the script had been
evolving for a long time, with the part with the "/bin/move --move"
being considered stable by me. One should always be able to rethink
everything.
I must admit, though, that I do not understand the internal workings of
this error. It seems as if these "mount --move" are more fragile than
regular mounts, but still they are working for the other mounts. Or did
I miss some required files for mount in the initramfs?
Whatever it may be, I am very grateful for this problem to be solved, it
has been plagueing me for several weeks now. I could not solve it
myself, thank you very much for helping me.
Eibo Thieme
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
