Bug#812589: fsck -M has stopped working

2016-01-25 Thread sacrificial-spam-address
>> The "802" is the root= argument passed to the kernel by the boot loader. >> Major device 8, minor 2. What I don't understand is why libmount thinks >> it's a file name (in $PWD, no less). > The boot loader should be passing "/dev/sda2", not "802". Are you using > an ancient boot loader (

Bug#812589: fsck -M has stopped working

2016-01-25 Thread sacrificial-spam-address
> Thanks for your bug report, but I'm not able to reproduce it and > it lacks information needed to investigate it. (Tagged as such > in a separate email to the bug tracking system.) Sorry, I tried to include pretty much everything. > Also adding -V (for verbose) would give some additional

Bug#812589: fsck -M has stopped working

2016-01-25 Thread Phil Susi
On 1/25/2016 11:16 AM, sacrificial-spam-addr...@horizon.com wrote: > The "802" is the root= argument passed to the kernel by the boot loader. > Major device 8, minor 2. What I don't understand is why libmount thinks > it's a file name (in $PWD, no less). The boot loader should be passing

Bug#812589: fsck -M has stopped working

2016-01-25 Thread sacrificial-spam-address
Package: util-linux Version: 2.27.1-1 Architecture: i386 (libmount1 and libblkid1 are also 2.27.1.) My most recent reboot (and it's been a while, so it may be some dependent library or new 4.4 kernel or something) failed in checkfs.sh. Upon debugging, it appeared that the invocation of "fsck -C