Now have a look at the attached picture. You can see that the output from mountall.conf contains the wrong date.
At the very bottom I had tune2fs print out the last mount time and it's indeed the wrong one. Thus leading to an fsck error on next reboot. If I don't do a reboot but a shutdown instead, the error won't show up on next boot, because the time would be wrong again.
Also notice that 'date' spits out the correct time after I was able to login.
An installation on my physical machine has the issue, too. But it happens pretty randomly there and I haven't found a regularity (such as 'after each shutdown') as with VirtualBox.
I changed /etc/init/ mountall. conf to print out the current time before it execs mountall:
--- snip ---
console output
script mountall. conf: `date`"
echo "/etc/init/
. /etc/default/rcS
--- /snip ---
Now have a look at the attached picture. You can see that the output from mountall.conf contains the wrong date.
At the very bottom I had tune2fs print out the last mount time and it's indeed the wrong one. Thus leading to an fsck error on next reboot. If I don't do a reboot but a shutdown instead, the error won't show up on next boot, because the time would be wrong again.
Also notice that 'date' spits out the correct time after I was able to login.
An installation on my physical machine has the issue, too. But it happens pretty randomly there and I haven't found a regularity (such as 'after each shutdown') as with VirtualBox.