Filesystem is all of a sudden read only

[Andy Proctor]

On Thu, 2021-01-21 at 18:35 -0800, Noah wrote:
> 
> Hi there,
> 
> I ubuntu 20.04 running on an intel NUC
> and I cant seem to figure out after a few days the file system
> announces 
> to me when I attempt to ssh that it is read-only and i am immediately
> logged out when I try to ssh to it.
> 
> Any clues what causes this?  Here is an example of an ssh session.
> I will try to log in locally next time this happens.
> 
> Cheers,
> Noah
> 
> 
> ❯ ssh nuc2
> Welcome to Ubuntu 20.04.1 LTS (GNU/Linux 5.4.0-62-generic x86_64)
> 
>   * Documentation:  https://help.ubuntu.com
>   * Management:     https://landscape.canonical.com
>   * Support:        https://ubuntu.com/advantage
> 
>    System information as of Tue Jan 19 02:52:11 UTC 2021
> 
>    System load:                      0.05
>    Usage of /:                       30.3% of 1.83TB
>    Memory usage:                     4%
>    Swap usage:                       0%
>    Temperature:                      70.0 C
>    Processes:                        449
>    Users logged in:                  1
> 
> 
>   * Introducing self-healing high availability clusters in MicroK8s.
>     Simple, hardened, Kubernetes for production, from RaspberryPi to
> DC.
> 
>       https://microk8s.io/high-availability
> 
> 14 updates can be installed immediately.
> 6 of these updates are security updates.
> To see these additional updates run: apt list --upgradable
> 
> 
> You have mail.
> Last login: Tue Jan 19 02:52:11 2021 from <IP>
> (anon):184: read-only file system: 
> /tmp/p10k-instant-prompt-output-noah-1152335
> (anon):13: read-only file system: 
> /tmp/gitstatus.POWERLEVEL9K.1000.1152335.1611277454.1.lock
> 
> [ERROR]: gitstatus failed to initialize.
> 
>    Your Git prompt may disappear or become slow.
> 
>    Add the following parameter to ~/.zshrc for extra diagnostics on
> error:
> 
>      GITSTATUS_LOG_LEVEL=DEBUG
> 
>    Restart Zsh to retry gitstatus initialization:
> 
>      exec zsh
> /home/noah/.jenv/libexec/jenv-refresh-plugins: line 43: 
> /home/noah/.jenv/jenv.version: Read-only file system
> zsh: locking failed for /home/noah/.zsh_history: read-only file
> system: 
> reading anyway
> Connection to <IP> closed.
> 

Hi Noah, not a solution but I had this with 20.04 locally, it started
to happen regularly and I suspected a HDD starting to fail. Many hours
of testing and diagnostics kept showing bad file systems not hard disk,
I did a complete reinstall of 20.04 more than once, but after a period
of time, I did correlate it in a course manner with use of Chrome which
also seemed odd. I'm not an expert so reading logs is not my forte btw.

I moved to 20.10 as soon as it came out, I no longer have the problem.
I have a relatively old desktop machine with a 1TB HDD and a 360GB SDD,
dual booted with Windoze. When I installed 20.10 I reformatted the
whole disk, repartitioned everything, reinstalled Windoze (I hate UEFI)
and Ubuntu. 

Not sure if relevant but I use ubuntu base with cinammon desktop. 

It may be some comfort that you are not the only one. 

Andy