fsck from grub menu, no longer working

Liam Proven lproven at gmail.com
Wed Nov 21 10:15:44 UTC 2018


On Wed, 21 Nov 2018 at 00:51, Udvarias Ur <udvarias1 at gmail.com> wrote:
>
> 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?

For a Unix system to be functioning, it must have a mounted root file system.

Always. This has been the case since Unix was developed at the end of
the 1960s.

Which root FS can change -- the ``chroot'' command can do this, for instance.

However, it need not be mounted read-write. It can be mounted
read-only. You can fsck a filesystem which is mounted RO. This is
normal in maintenance mode.

``dpkg'' on its own does nothing useful.

``clean'' is not a Unix command, TTBOMK.

Finally: please bottom-post on mailing lists.

-- 
Liam Proven - Profile: https://about.me/liamproven
Email: lproven at cix.co.uk - Google Mail/Hangouts/Plus: lproven at gmail.com
Twitter/Facebook/Flickr: lproven - Skype/LinkedIn: liamproven
UK: +44 7939-087884 - ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053



More information about the ubuntu-users mailing list