On Tue, Sep 17, 2013 at 03:52:57AM -0000, Joseph Yasi wrote:
> /proc/cmdline is:
> BOOT_IMAGE=/boot/vmlinuz-3.11.1-customatom root=UUID=708b3ba8-c42a-4adf-a195-c0fb8d8f8dd3 ro
> So, none of those options are passed to the kernel. Mountall is
> starting, and everything but the NFS mounts are mounting fine. When NFS
> fails to mount without those lines, mountall is still running after boot
> and frozen. When I remove those lines, everything mounts and mountall
> finishes so it is no longer running after boot. It is very strange.
Ok. If you *do* boot with --verbose on the kernel commandline, do you get a
/var/log/upstart/mountall.log file? Can you attach the contents?
Also, would you mind filing a separate bug report on the mountall package
for this regression?
On Tue, Sep 17, 2013 at 03:52:57AM -0000, Joseph Yasi wrote: /boot/vmlinuz- 3.11.1- customatom root=UUID= 708b3ba8- c42a-4adf- a195-c0fb8d8f8d d3 ro
> /proc/cmdline is:
> BOOT_IMAGE=
> So, none of those options are passed to the kernel. Mountall is
> starting, and everything but the NFS mounts are mounting fine. When NFS
> fails to mount without those lines, mountall is still running after boot
> and frozen. When I remove those lines, everything mounts and mountall
> finishes so it is no longer running after boot. It is very strange.
Ok. If you *do* boot with --verbose on the kernel commandline, do you get a upstart/ mountall. log file? Can you attach the contents?
/var/log/
Also, would you mind filing a separate bug report on the mountall package
for this regression?