That makes sense, but I don't know how to do that. I tried disabling kdm start so I booted into a shell. I then enabled the /var/tmp line in fstab and ran mountall. In that case it seemed to mount /var/tmp okay, although it did hang. I had to press Ctrl-C to stop it. But the log showed nothing different, except it said /var/tmp was mounted successfully. A "mount" command confirmed that /var/tmp was mounted on tmpfs. Seemed to get way past that point in the log, which ended with the line
run_swapon: /dev/disk/by-uuid/900b83f8-4962-4652-a865-3d775b3af2ed: already activated
So I don't know how to make mountall fail in the log, since it only seems to fail during boot (presumably when upstart executes it). I considered changing the mountall command in /etc/init/mountall.conf and adding a --debug and redirecting the output to a file, but where can I write the file? Aren't all filesystems unmounted at that point?
So I need instructions on the getting log you want. Thanks for looking at this.
> I need to see it failing in the log ;-)
That makes sense, but I don't know how to do that. I tried disabling kdm start so I booted into a shell. I then enabled the /var/tmp line in fstab and ran mountall. In that case it seemed to mount /var/tmp okay, although it did hang. I had to press Ctrl-C to stop it. But the log showed nothing different, except it said /var/tmp was mounted successfully. A "mount" command confirmed that /var/tmp was mounted on tmpfs. Seemed to get way past that point in the log, which ended with the line by-uuid/ 900b83f8- 4962-4652- a865-3d775b3af2 ed: already activated
run_swapon: /dev/disk/
So I don't know how to make mountall fail in the log, since it only seems to fail during boot (presumably when upstart executes it). I considered changing the mountall command in /etc/init/ mountall. conf and adding a --debug and redirecting the output to a file, but where can I write the file? Aren't all filesystems unmounted at that point?
So I need instructions on the getting log you want. Thanks for looking at this.