Failed to write entry journal error Linux Mint 19

Questions about other topics - please check if your question fits better in another category before posting here
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Auerilas
Level 1
Level 1
Posts: 45
Joined: Fri Nov 18, 2016 1:26 pm

Failed to write entry journal error Linux Mint 19

Post by Auerilas »

Hi all,
I recently did a clean reinstall of Linux Mint 19. Everything was working swimmingly before the reinstall (except for when I accidentally deleted a whole bunch of stuff), as well as on my other computer. However, after my reinstall I'm having weird issues. If I log out (not restart), and leave the computer sit for a while, I get strange behavior. Sometimes when I come back to log back in, I get a black screen with no prompt, no nothing, just a blinking cursor. Most recently, I received the errors in the image below:
IMG_20181009_130828.jpg
I don't know what these errors mean, how to diagnose them, or basically anything except they're probably not good. The odd part is that Linux Mint seems to reboot and start up just fine if I don't log out and leave it on. I've attached my boot log and dmesg in a tarball, in case those help. I don't really know what to look for.

I logged in using a LiveUSB and used Disks to check /dev/sda1 and /dev/sda2 and found no errors. Furthermore:

Code: Select all

sudo fsck /dev/sda2
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sda2: clean, 740064/122068992 files, 145868445/488247296 blocks
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Laurent85
Level 17
Level 17
Posts: 7081
Joined: Tue May 26, 2015 10:11 am

Re: Failed to write entry journal error Linux Mint 19

Post by Laurent85 »

Auerilas wrote: Tue Oct 09, 2018 3:42 pm I logged in using a LiveUSB and used Disks to check /dev/sda1 and /dev/sda2 and found no errors. Furthermore:
Check the drive health status, in the live session install smartmontools:

Code: Select all

apt install smartmontools
Post the drive's SMART attributes:

Code: Select all

sudo smartctl -s on -iHA --log=error -f brief -q noserial /dev/sda
Image
Auerilas
Level 1
Level 1
Posts: 45
Joined: Fri Nov 18, 2016 1:26 pm

Re: Failed to write entry journal error Linux Mint 19

Post by Auerilas »

Here it is:

Code: Select all

sudo smartctl -s on -iHA --log=error -f brief -q noserial /dev/sda
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-20-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Desktop SSHD
Device Model:     ST2000DX001-1NS164
Firmware Version: CC41
User Capacity:    2,000,398,934,016 bytes [2.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Oct  9 22:16:40 2018 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR--   115   099   006    -    88131768
  3 Spin_Up_Time            PO----   096   095   000    -    0
  4 Start_Stop_Count        -O--CK   100   100   020    -    209
  5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    0
  7 Seek_Error_Rate         POSR--   075   060   030    -    39538632
  9 Power_On_Hours          -O--CK   089   089   000    -    9700
 10 Spin_Retry_Count        PO--C-   100   100   097    -    0
 12 Power_Cycle_Count       -O--CK   100   100   020    -    210
183 Runtime_Bad_Block       -O--CK   092   092   000    -    8
184 End-to-End_Error        -O--CK   100   100   099    -    0
187 Reported_Uncorrect      -O--CK   100   100   000    -    0
188 Command_Timeout         -O--CK   100   099   000    -    0 0 1
189 High_Fly_Writes         -O-RCK   093   093   000    -    7
190 Airflow_Temperature_Cel -O---K   065   061   045    -    35 (Min/Max 32/35)
191 G-Sense_Error_Rate      -O--CK   100   100   000    -    0
192 Power-Off_Retract_Count -O--CK   100   100   000    -    43
193 Load_Cycle_Count        -O--CK   100   100   000    -    210
194 Temperature_Celsius     -O---K   035   040   000    -    35 (0 17 0 0 0)
197 Current_Pending_Sector  -O--C-   100   100   000    -    0
198 Offline_Uncorrectable   ----C-   100   100   000    -    0
199 UDMA_CRC_Error_Count    -OSRCK   200   200   000    -    0
240 Head_Flying_Hours       ------   100   253   000    -    10283h+17m+47.781s
241 Total_LBAs_Written      ------   100   253   000    -    9357375159
242 Total_LBAs_Read         ------   100   253   000    -    86112950025
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

SMART Error Log Version: 1
No Errors Logged
Laurent85
Level 17
Level 17
Posts: 7081
Joined: Tue May 26, 2015 10:11 am

Re: Failed to write entry journal error Linux Mint 19

Post by Laurent85 »

Auerilas wrote: Tue Oct 09, 2018 6:18 pm 183 Runtime_Bad_Block -O--CK 092 092 000 - 8
The drive has bad blocks with data stored at this location the system can no loger access, resulting in input output errors. That type of failure does not mean the drives will die soon but the data stored on those blocks is unrecoverable. You may have to reinstall LM, the drive's firmware should reallocate those blocks to a spare area.
Image
Auerilas
Level 1
Level 1
Posts: 45
Joined: Fri Nov 18, 2016 1:26 pm

Re: Failed to write entry journal error Linux Mint 19

Post by Auerilas »

Ah ok. Well I'd already done a full reinstall anyway. Hopefully that resolves the issue.

Thanks!
Locked

Return to “Other topics”