`Read only file system` after upgrading to nixos 22.11

Hello. For the last 4 years I have been mounting my drive with:

  fileSystems."/mnt/samsung" =
    { device = "/dev/sda1";
      fsType = "ext4";
      options = ["nofail"];
    };

And I have a bunch of symlinks in my home directory to access all data in /mnt/samsung. Now I just upgraded to nixos 22.11, and the fs is read only:

touch: hello: Read-only file system
1 Like

Have you checked boot logs? It may have backed off to a read-only state due to problems with the fs.

2 Likes

Thank you tejing. It’s fixed with no intervention after a few restarts.

It came back. Now it didn’t mount (after restarting when facing the read-only problem again)

Any idea? The startup process is very fast and I can’t read anything. Here is the log (journalctl -b 0): gist:c8b28b62e4ef69ef9067ff916580d4c3 · GitHub

Dec 29 21:25:43 <name> systemd-fsck[818]: fsck.ext4: Superblock checksum does not match superblock while trying to re-open /dev/sda1
Dec 29 21:25:43 <name> systemd-fsck[818]: /dev/sda1: ********** WARNING: Filesystem still has errors **********
Dec 29 21:25:43 <name> systemd-fsck[816]: fsck failed with exit status 12.
Dec 29 21:25:43 <name> systemd[1]: systemd-fsck@dev-sda1.service: Main process exited, code=exited, status=1/FAILURE
Dec 29 21:25:43 <name> systemd[1]: systemd-fsck@dev-sda1.service: Failed with result 'exit-code'.
Dec 29 21:25:43 <name> systemd[1]: Failed to start File System Check on /dev/sda1.
Dec 29 21:25:43 <name> systemd[1]: Dependency failed for /mnt/samsung.

Your file system is corrupted.

2 Likes
Hosted by Flying Circus.