[SOLVED] new install keeps getting corrupted

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
albertdh

[SOLVED] new install keeps getting corrupted

Post by albertdh »

Running Mint 19 Cinnamon ver.2 with kernel 4.15.0.38 on a Lenovo Thinkpad T420. Tested Mint on it for a bit with a USB. However, ever since installing it every other boot fails leaving me with Busybox. I get it back up running a command line with the USB and doing the FSCK thing. Sometimes it's good for a couple of boots, sometimes it fails while running. FSCK always shows "Error reading block" whatever and then Inode issues. Runs fine but keeps happening. I had problems with the laptop's Windows but eventually it was booting okay, just very slowly. Not sure if the hard drive is the issue or some compatability. Wonder if a different distro would run better. Any help would be appreciated.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
WharfRat

Re: new install keeps getting corrupted

Post by WharfRat »

Hello albertdh Image

Welcome to Linux Mint and the Linux Mint forum :)

It sounds like you might have a problem with that disk.

Install smartmontools then run sudo smartctl -a /dev/sda, assuming your disk is sda, and check for a high error counts.
albertdh

Re: new install keeps getting corrupted

Post by albertdh »

Thanks for responding. I've done as suggested but not sure how to interpret results. Had to run FSCK first so this was run on a fresh, clean boot. Should I send results?
WharfRat

Re: new install keeps getting corrupted

Post by WharfRat »

albertdh wrote: Fri Nov 16, 2018 11:18 am Thanks for responding. I've done as suggested but not sure how to interpret results. Had to run FSCK first so this was run on a fresh, clean boot. Should I send results?
Paste it back enclosed in the code tag like this

Code: Select all

Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   150   145   021    Pre-fail  Always       -       11466
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       900
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0032   083   083   000    Old_age   Always       -       12811
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       900
 16 Unknown_Attribute       0x0022   150   050   000    Old_age   Always       -       2644991733904
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       93
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       806
194 Temperature_Celsius     0x0022   107   099   000    Old_age   Always       -       45
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       4
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0
albertdh

Re: new install keeps getting corrupted

Post by albertdh »

Odd thing is that now I'm trying to run the smartctl command again to do this but it asks for my passcode and when I try to type it in the keyboard doesn't respond! Any thoughts? I did copy the results the first time but used a format where the columns aren't correct. sorry.
WharfRat

Re: new install keeps getting corrupted

Post by WharfRat »

albertdh wrote: Fri Nov 16, 2018 12:01 pm Odd thing is that now I'm trying to run the smartctl command again to do this but it asks for my passcode and when I try to type it in the keyboard doesn't respond! Any thoughts? I did copy the results the first time but used a format where the columns aren't correct. sorry.
The only thing I can suggest is to try to boot the live media, install smartmontools then run sudo smartctl -a /dev/sda from there.

You won't be asked for a password in the live session.
User avatar
Flemur
Level 20
Level 20
Posts: 10096
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

Re: new install keeps getting corrupted

Post by Flemur »

albertdh wrote: Fri Nov 16, 2018 12:01 pmOdd thing is that now I'm trying to run the smartctl command again to do this but it asks for my passcode and when I try to type it in the keyboard doesn't respond! Any thoughts?
It doesn't show your password or provide any useful feedback, so people often think something is broken. It's probably not.

Try

Code: Select all

sudo ls
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?
albertdh

Re: new install keeps getting corrupted

Post by albertdh »

Thanks Flemur, indeed no response but took the passcode!

Code: Select all

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Black
Device Model:     WDC WD3200BEKT-08PVMT1
Serial Number:    WD-WX91CC1A3652
LU WWN Device Id: 5 0014ee 6020a16f4
Firmware Version: 02.01A02
User Capacity:    320,072,933,376 bytes [320 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Fri Nov 16 11:18:42 2018 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

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

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		( 6060) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  63) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x7037)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       11559
  3 Spin_Up_Time            0x0027   161   148   021    Pre-fail  Always       -       941
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       615
  5 Reallocated_Sector_Ct   0x0033   185   185   140    Pre-fail  Always       -       129
  7 Seek_Error_Rate         0x002f   100   253   051    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   083   083   000    Old_age   Always       -       12843
 10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       604
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       56
193 Load_Cycle_Count        0x0032   194   194   000    Old_age   Always       -       19527
194 Temperature_Celsius     0x0022   107   096   000    Old_age   Always       -       36
196 Reallocated_Event_Count 0x0032   195   195   000    Old_age   Always       -       5
197 Current_Pending_Sector  0x0032   200   199   000    Old_age   Always       -       37
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0
240 Head_Flying_Hours       0x0032   083   083   000    Old_age   Always       -       12633

SMART Error Log Version: 1
ATA Error Count: 18 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 18 occurred at disk power-on lifetime: 12803 hours (533 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 7f 70 de 03 e0  Error: UNC 127 sectors at LBA = 0x0003de70 = 253552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 7f 12 de 03 e0 00      00:01:02.482  READ DMA
  c8 00 7f 93 dd 03 e0 00      00:01:02.482  READ DMA
  c8 00 7f 14 dd 03 e0 00      00:01:02.481  READ DMA
  c8 00 7f 95 dc 03 e0 00      00:01:02.481  READ DMA
  c8 00 7f 16 dc 03 e0 00      00:01:02.480  READ DMA

Error 17 occurred at disk power-on lifetime: 12803 hours (533 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 7f 70 de 03 e0  Error: UNC 127 sectors at LBA = 0x0003de70 = 253552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 7f 12 de 03 e0 00      00:01:00.799  READ DMA
  c8 00 7f 93 dd 03 e0 00      00:01:00.799  READ DMA
  c8 00 7f 14 dd 03 e0 00      00:01:00.798  READ DMA
  c8 00 7f 95 dc 03 e0 00      00:01:00.798  READ DMA
  c8 00 7f 16 dc 03 e0 00      00:01:00.797  READ DMA

Error 16 occurred at disk power-on lifetime: 12803 hours (533 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 7f 70 de 03 e0  Error: UNC 127 sectors at LBA = 0x0003de70 = 253552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 7f 12 de 03 e0 00      00:00:59.153  READ DMA
  c8 00 7f 93 dd 03 e0 00      00:00:59.152  READ DMA
  c8 00 7f 14 dd 03 e0 00      00:00:59.150  READ DMA
  c8 00 7f 95 dc 03 e0 00      00:00:59.150  READ DMA
  c8 00 7f 16 dc 03 e0 00      00:00:59.149  READ DMA

Error 15 occurred at disk power-on lifetime: 12802 hours (533 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 7f 70 de 03 e0  Error: UNC 127 sectors at LBA = 0x0003de70 = 253552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 7f 12 de 03 e0 00      00:10:39.248  READ DMA
  c8 00 7f 93 dd 03 e0 00      00:10:39.247  READ DMA
  c8 00 7f 14 dd 03 e0 00      00:10:39.247  READ DMA
  c8 00 7f 95 dc 03 e0 00      00:10:39.246  READ DMA
  c8 00 7f 16 dc 03 e0 00      00:10:39.245  READ DMA

Error 14 occurred at disk power-on lifetime: 12802 hours (533 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 7f 70 de 03 e0  Error: UNC 127 sectors at LBA = 0x0003de70 = 253552

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 7f 12 de 03 e0 00      00:10:37.557  READ DMA
  c8 00 7f 93 dd 03 e0 00      00:10:37.557  READ DMA
  c8 00 7f 14 dd 03 e0 00      00:10:37.556  READ DMA
  c8 00 7f 95 dc 03 e0 00      00:10:37.556  READ DMA
  c8 00 7f 16 dc 03 e0 00      00:10:37.555  READ DMA

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Vendor (0x50)       Completed without error       00%     10001         -
# 2  Short offline       Completed without error       00%     10000         -
# 3  Vendor (0x50)       Completed without error       00%         0         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Last edited by albertdh on Fri Nov 16, 2018 12:35 pm, edited 1 time in total.
Reason: Added code tag
WharfRat

Re: new install keeps getting corrupted

Post by WharfRat »

I would say with a Raw_Read_Error_Rate of 11559 that the disk is on the brink of total failure.

It makes no sense to keep running fsck as it will only get worse very soon.

Time for a new HDD :wink:
albertdh

[SOLVED] new install keeps getting corrupted

Post by albertdh »

Or a new laptop, I guess. Thanks so much for your assistance!
Locked

Return to “Installation & Boot”