Could fstab default mount options be changed so that, unless otherwise
specified, failed mount attempts would skip that filesystem and keep
booting (logging an error), instead of dropping to an inaccessible
recovery console? This would let the fstab be fixed with minimal hassle
in a headless enviro
Thanks for your attention on this bug, Joseph. I'm compiling the new
kernel, now, and will let you know as soon as I have a test result.
As far as I know, all 16.04 kernel versions exhibit this problem; but I
haven't done any testing on Ubuntu 15.X.
--
You received this bug notification because
(New kernel is still compiling...)
I just did a test with a fully-patched, newly spun-up Ubuntu Server
14.04 AWS instance, and the behavior seems to be present with kernel
3.13.0-107. I can't verify all of the symptoms described by the
reporter, because I don't have physical access; but I get "co
I've tested this with kernel 4.10-rc3 in a local VirtualBox VM (Ubuntu
Server 16.04), with the same fstab error as above, and am able to
confirm most of the symptoms described by the reporter.
When attempting to 'mount -a', it presents the expected "wrong
filesystem type" error, but doesn't render
Hi, Tim.
I ran into this issue a few days ago on a local server where I'd made an
fstab mistake. The behavior seems un-changed from previous observations
(drops to the same recovery console). I believe this would still result
in an un-bootable cloud VM.
For those who are experiencing the issue
5 matches
Mail list logo
