fsck from grub menu, no longer working

Udvarias Ur udvarias1 at gmail.com
Tue Nov 20 23:49:41 UTC 2018


Folks,

First, thank you for the suggestions and attention to this issue.

I may have gotten caught up in the details, so here's the crux of the 
matter.

In the past I ran 'fsck,' 'dpkg,' and 'clean' (in that order) in 
'recovery mode.' (From the menu I mention below.)

I had to run 'fsck' first because 'dpkg,' and 'clean' both mounted the 
root partition. (So I concluded that the root partition is NOT mounted 
when the system is booted into 'recovery mode.')

Now, suddenly, I can no longer run 'fsck' from 'recovery mode.'

Have things changed such that this no longer works?



On 2018-11-20 6:26 a.m., Tom H wrote:

> 3) _IF_ "fsck from grub menu" means selecting to fsck "/" from the 
> friendly-recovery menu that's displayed in single-user mode fails 
> because "/" is mounted, then there's a bug in that package. (I don't 
> use it so I can't check.)
>
On 2018-11-19 3:09 p.m., Udvarias Ur wrote:

> Folks,
>
> I've been using the 'Advanced options for Ubuntu' to select the 
> '(recovery mode)' of the current kernel in order to run 'fsck,' 
> 'dpkg,' and 'clean.'
>
{snip}

-- 
Udvarias Ur

This letter was generated and sent from Thunderbird 52.7.0 on Ubuntu Linux 16.04.5 LTS.

Cette lettre a été générée et envoyée à partir de Thunderbird 52.7.0 sur Ubuntu Linux 16.04.5 LTS.




More information about the ubuntu-users mailing list