[SOLVED] System crash - systemd-journald[354]: failed to write entry, ignoring: read-only file system

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
trope
Level 4
Level 4
Posts: 221
Joined: Tue Feb 19, 2013 1:10 pm

[SOLVED] System crash - systemd-journald[354]: failed to write entry, ignoring: read-only file system

Post by trope » Fri Feb 01, 2019 5:02 pm

Am using Mint 19, Tara, 64-bit, MATE. Had no problems with the OS and suddenly when trying to write some data in the terminal in taskwarrior, got an error message about not having permission. I closed all applications, logged out of Mint, got a message that something with virtualbox was not responding, I logged out anyway, and then I got the error message above:

Code: Select all

systemd-journald[354]: failed to write entry, ignoring: read-only file system
Variations of this kept repeating. Am linking a screenshot:
https://imgur.com/a/KeQNy9L

I rebooted and everything seems to work fine. My root did only have 3.4 GB free, I deleted 9 GB from root. Also I began using timeshift yesterday (but not saving in /), not sure if it is related.

Is this error message something I need to be concerned about? How do I troubleshoot it?
Last edited by trope on Tue Feb 12, 2019 7:48 pm, edited 1 time in total.

User avatar
WharfRat
Level 21
Level 21
Posts: 13440
Joined: Thu Apr 07, 2011 8:15 pm

Re: System crash - systemd-journald[354]: failed to write entry, ignoring: read-only file system

Post by WharfRat » Fri Feb 01, 2019 5:08 pm

What does sudo inxi -SCMm -t c -P -x show :?:
ImageImage

trope
Level 4
Level 4
Posts: 221
Joined: Tue Feb 19, 2013 1:10 pm

Re: System crash - systemd-journald[354]: failed to write entry, ignoring: read-only file system

Post by trope » Sun Feb 03, 2019 1:13 pm

The output is:

Code: Select all

System:    Host: Latitude-E5450 Kernel: 4.15.0-20-generic x86_64
           bits: 64 gcc: 7.3.0
           Desktop: MATE 1.20.1 (Gtk 3.22.30-1ubuntu1)
           Distro: Linux Mint 19 Tara
Machine:   Device: laptop System: Dell product: Latitude E5450 serial: 446B262
           Mobo: Dell model: 0DCPV1 v: A00 serial: /446B262/CN1296359M03FA/
           UEFI [Legacy]: Dell v: A18 date: 01/03/2018
CPU:       Dual core Intel Core i5-5300U (-MT-MCP-) 
           arch: Broadwell rev.4 cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9178
           clock speeds: max: 2900 MHz 1: 2167 MHz 2: 1446 MHz 3: 1898 MHz
           4: 2175 MHz
Memory:    Used/Total: 2383.9/7849.8MB
           Array-1 capacity: 16 GB devices: 2 EC: None
           Device-1: DIMM A size: 8 GB speed: 1600 MT/s type: DDR3
           part: HMT41GS6BFR8A-PB
           Device-2: DIMM B size: No Module Installed type: N/A
           Device-3: N/A size: N/A type: N/A
           Device-4: N/A size: N/A type: N/A
Partition: ID-1: / size: 29G used: 15G (55%) fs: ext4 dev: /dev/sda5
           ID-2: swap-1 size: 17.83GB used: 0.00GB (0%)
           fs: swap dev: /dev/sda6
Processes: CPU: % used - Memory: MB / % used - Used/Total: 2384.4/7849.8MB - top 5 active
           1: cpu: 10.3% command: java pid: 1199 mem: 605.71MB (7.7%)
           2: cpu: 7.7% command: brave pid: 3988 mem: 248.53MB (3.1%)
           3: cpu: 4.4% command: thunderbird pid: 3992 mem: 344.15MB (4.3%)
           4: cpu: 3.5% command: Xorg pid: 2503 mem: 89.52MB (1.1%)
           5: cpu: 2.8% command: brave pid: 4243 mem: 123.62MB (1.5%)
The error happened again so I do think it's something significant that I need to figure out.

gm10
Level 20
Level 20
Posts: 10153
Joined: Thu Jun 21, 2018 5:11 pm

Re: System crash - systemd-journald[354]: failed to write entry, ignoring: read-only file system

Post by gm10 » Sun Feb 03, 2019 2:05 pm

trope wrote:
Sun Feb 03, 2019 1:13 pm
The error happened again so I do think it's something significant that I need to figure out.
The filesystem goes read-only when file system errors are detected that cannot be fixed on the mounted filesystem. It's a security measure to prevent further data loss.

This can be caused by either hardware issues (i.e. your disk is failing, go Mint menu > Disks, select your disk and check the SMART data for your drive from the hamburger menu at the top, in particular bad/relocated sectors), or a software issue (e.g. the old kernel version you're running has some known ext4 bugs, you could start by applying some updates to that system, those are being offered for a reason).

trope
Level 4
Level 4
Posts: 221
Joined: Tue Feb 19, 2013 1:10 pm

Re: System crash - systemd-journald[354]: failed to write entry, ignoring: read-only file system

Post by trope » Mon Feb 04, 2019 1:26 pm

The SMART test showed that the "last self-test completed successfully" and the overall assessment is "Disk is OK". Can I rule out a disk problem with this, or does the test not cover all the segments? Will apply some updates.

gm10
Level 20
Level 20
Posts: 10153
Joined: Thu Jun 21, 2018 5:11 pm

Re: System crash - systemd-journald[354]: failed to write entry, ignoring: read-only file system

Post by gm10 » Mon Feb 04, 2019 2:08 pm

trope wrote:
Mon Feb 04, 2019 1:26 pm
The SMART test showed that the "last self-test completed successfully" and the overall assessment is "Disk is OK". Can I rule out a disk problem with this, or does the test not cover all the segments? Will apply some updates.
Can't rule it out but makes it much less likely. I'd do the updates first, that's the most likely solution.

trope
Level 4
Level 4
Posts: 221
Joined: Tue Feb 19, 2013 1:10 pm

Re: System crash - systemd-journald[354]: failed to write entry, ignoring: read-only file system

Post by trope » Tue Feb 12, 2019 7:47 pm

Has not occurred since I ran a bunch of updates. Am considered it solved.

Post Reply

Return to “Installation & Boot”