You are not logged in.

#1 2020-09-11 20:47:39

Sector11
Conky 1.9er Mod Squid
From: Upstairs
Registered: 2015-08-20
Posts: 6,401

[SOLVED] - PC Locked-up - now with BOOT problems.

Solved ... it was a loose cable????
------------------------
Earlier today I had Thunar open renaming images.

Computer locked.

Tried exiting thunar, exiting the renaming window, etc and even [Exit]
STUCK!
then things started going crazy with [not responding popups]

Finally I forced a shutdown.

I tried everything ... finally after a few minutes waiting at the bios screen, I get the boot menu - VERY slow

booted rescue mode --- super slow with errors .....

~/.xsession-errors

is 3MB and I cannot read it.
Says it cannot detect file encoding.  Was always UTF8 I think.

 11 Sep 20 @ 17:39:08 ~
   $ sudo smartctl --attributes -H /dev/sda
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-10-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

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

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       -       0
  3 Spin_Up_Time            0x0027   183   170   021    Pre-fail  Always       -       1841
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       322
  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   095   095   000    Old_age   Always       -       4377
 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       -       322
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       26
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       365
194 Temperature_Celsius     0x0022   109   099   000    Old_age   Always       -       34
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       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

 
 11 Sep 20 @ 17:40:06 ~
   $ 

OK HDD is OK - except for that Old Age!  ?????

lern.log is 12152 lines long....
kern.log entry for just today is 4135 lines long.  No idea what all that means.
but this stuff doesn't look good at all:

Sep 11 16:59:20 sector11 kernel: [   37.848057] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 11 16:59:20 sector11 kernel: [   37.848115] ata5.00: failed command: FLUSH CACHE EXT
Sep 11 16:59:20 sector11 kernel: [   37.848152] ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 27
Sep 11 16:59:20 sector11 kernel: [   37.848152]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Sep 11 16:59:20 sector11 kernel: [   37.848235] ata5.00: status: { DRDY }
Sep 11 16:59:20 sector11 kernel: [   37.848262] ata5: hard resetting link
Sep 11 16:59:20 sector11 kernel: [   47.860377] ata5: softreset failed (device not ready)
Sep 11 16:59:20 sector11 kernel: [   47.860421] ata5: hard resetting link
Sep 11 16:59:20 sector11 kernel: [   57.872388] ata5: softreset failed (device not ready)
Sep 11 16:59:20 sector11 kernel: [   57.872433] ata5: hard resetting link
Sep 11 16:59:20 sector11 kernel: [   68.428536] ata5: link is slow to respond, please be patient (ready=0)
Sep 11 16:59:20 sector11 kernel: [   77.488375] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 11 16:59:20 sector11 kernel: [   77.491685] ata5.00: failed to read native max address (err_mask=0x1)
Sep 11 16:59:20 sector11 kernel: [   77.491688] ata5.00: HPA support seems broken, skipping HPA handling
Sep 11 16:59:20 sector11 kernel: [   77.491898] ata5.00: failed to enable AA (error_mask=0x1)
Sep 11 16:59:20 sector11 kernel: [   77.492775] ata5.00: failed to enable AA (error_mask=0x1)
Sep 11 16:59:20 sector11 kernel: [   77.492797] ata5.00: configured for UDMA/100 (device error ignored)
Sep 11 16:59:20 sector11 kernel: [   77.492798] ata5.00: retrying FLUSH 0xea Emask 0x4
Sep 11 16:59:20 sector11 kernel: [   77.492942] ata5.00: FLUSH failed Emask 0x1
Sep 11 16:59:20 sector11 kernel: [   77.492943] ata5.00: device reported invalid CHS sector 0
Sep 11 16:59:20 sector11 kernel: [   77.492956] ata5: EH complete
Sep 11 16:59:20 sector11 kernel: [   77.508079] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 11 16:59:20 sector11 kernel: [   77.508130] ata5.00: irq_stat 0x40000001
Sep 11 16:59:20 sector11 kernel: [   77.508158] ata5.00: failed command: FLUSH CACHE EXT
Sep 11 16:59:20 sector11 kernel: [   77.508195] ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 8
Sep 11 16:59:20 sector11 kernel: [   77.508195]          res 61/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
Sep 11 16:59:20 sector11 kernel: [   77.508281] ata5.00: status: { DRDY DF ERR }
Sep 11 16:59:20 sector11 kernel: [   77.508309] ata5.00: error: { ABRT }
Sep 11 16:59:20 sector11 kernel: [   77.516921] ata5.00: failed to enable AA (error_mask=0x1)
Sep 11 16:59:20 sector11 kernel: [   77.517805] ata5.00: failed to enable AA (error_mask=0x1)
Sep 11 16:59:20 sector11 kernel: [   77.517830] ata5.00: configured for UDMA/100 (device error ignored)
Sep 11 16:59:20 sector11 kernel: [   77.517832] ata5.00: device reported invalid CHS sector 0
Sep 11 16:59:20 sector11 kernel: [   77.517845] ata5: EH complete
Sep 11 16:59:20 sector11 kernel: [   77.540062] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 11 16:59:20 sector11 kernel: [   77.540100] ata5.00: irq_stat 0x40000001
Sep 11 16:59:20 sector11 kernel: [   77.540124] ata5.00: failed command: FLUSH CACHE EXT
Sep 11 16:59:20 sector11 kernel: [   77.540162] ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 26
Sep 11 16:59:20 sector11 kernel: [   77.540162]          res 61/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
Sep 11 16:59:20 sector11 kernel: [   77.540248] ata5.00: status: { DRDY DF ERR }
Sep 11 16:59:20 sector11 kernel: [   77.540276] ata5.00: error: { ABRT }
Sep 11 16:59:20 sector11 kernel: [   77.540956] ata5.00: failed to enable AA (error_mask=0x1)
Sep 11 16:59:20 sector11 kernel: [   77.541800] ata5.00: failed to enable AA (error_mask=0x1)
Sep 11 16:59:20 sector11 kernel: [   77.541829] ata5.00: configured for UDMA/100 (device error ignored)
Sep 11 16:59:20 sector11 kernel: [   77.541831] ata5.00: device reported invalid CHS sector 0
Sep 11 16:59:20 sector11 kernel: [   77.541842] ata5: EH complete
Sep 11 16:59:20 sector11 kernel: [   77.556093] ata5.00: NCQ disabled due to excessive errors
Sep 11 16:59:20 sector11 kernel: [   77.556097] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 11 16:59:20 sector11 kernel: [   77.556147] ata5.00: irq_stat 0x40000001
Sep 11 16:59:20 sector11 kernel: [   77.556175] ata5.00: failed command: FLUSH CACHE EXT
Sep 11 16:59:20 sector11 kernel: [   77.556212] ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 13
Sep 11 16:59:20 sector11 kernel: [   77.556212]          res 61/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
Sep 11 16:59:20 sector11 kernel: [   77.556298] ata5.00: status: { DRDY DF ERR }
Sep 11 16:59:20 sector11 kernel: [   77.556327] ata5.00: error: { ABRT }
Sep 11 16:59:20 sector11 kernel: [   77.557012] ata5.00: failed to enable AA (error_mask=0x1)
Sep 11 16:59:20 sector11 kernel: [   77.557845] ata5.00: failed to enable AA (error_mask=0x1)
Sep 11 16:59:20 sector11 kernel: [   77.557872] ata5.00: configured for UDMA/100 (device error ignored)
Sep 11 16:59:20 sector11 kernel: [   77.557874] ata5.00: device reported invalid CHS sector 0
Sep 11 16:59:20 sector11 kernel: [   77.557885] ata5: EH complete
Sep 11 16:59:20 sector11 kernel: [   77.572379] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 11 16:59:20 sector11 kernel: [   77.572430] ata5.00: irq_stat 0x40000001
Sep 11 16:59:20 sector11 kernel: [   77.572458] ata5.00: failed command: FLUSH CACHE EXT
Sep 11 16:59:20 sector11 kernel: [   77.572495] ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Sep 11 16:59:20 sector11 kernel: [   77.572495]          res 61/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
Sep 11 16:59:20 sector11 kernel: [   77.572581] ata5.00: status: { DRDY DF ERR }
Sep 11 16:59:20 sector11 kernel: [   77.572610] ata5.00: error: { ABRT }
Sep 11 16:59:20 sector11 kernel: [   82.620376] ata5.00: qc timeout (cmd 0xec)
Sep 11 16:59:20 sector11 kernel: [   82.620389] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x5)
Sep 11 16:59:20 sector11 kernel: [   82.620391] ata5.00: revalidation failed (errno=-5)
Sep 11 16:59:20 sector11 kernel: [   82.620435] ata5: hard resetting link
Sep 11 16:59:20 sector11 kernel: [   92.632362] ata5: softreset failed (device not ready)
Sep 11 16:59:20 sector11 kernel: [   92.632408] ata5: hard resetting link
Sep 11 16:59:20 sector11 kernel: [  102.644362] ata5: softreset failed (device not ready)
Sep 11 16:59:20 sector11 kernel: [  102.645358] ata5: hard resetting link
Sep 11 16:59:20 sector11 kernel: [  113.196361] ata5: link is slow to respond, please be patient (ready=0)
Sep 11 16:59:20 sector11 kernel: [  137.676372] ata5: softreset failed (device not ready)
Sep 11 16:59:20 sector11 kernel: [  137.677350] ata5: limiting SATA link speed to 3.0 Gbps
Sep 11 16:59:20 sector11 kernel: [  137.677352] ata5: hard resetting link
Sep 11 16:59:20 sector11 kernel: [  137.991873] ata5: SATA link down (SStatus 0 SControl 320)
Sep 11 16:59:20 sector11 kernel: [  138.129447] ata5: hard resetting link
Sep 11 16:59:20 sector11 kernel: [  141.304376] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Sep 11 16:59:20 sector11 kernel: [  141.330819] ata5.00: configured for UDMA/100
Sep 11 16:59:20 sector11 kernel: [  141.330822] ata5.00: device reported invalid CHS sector 0
Sep 11 16:59:20 sector11 kernel: [  141.330829] ata5: EH complete

Anyone got an idea what is happening.

Need more info tell me how to get it and I'll get it.

Last edited by Sector11 (2020-09-12 15:40:55)


The sun will never set if you keep walking towards it. - my son
Being positive doesn't understand physics.
_______________________________
Debian 10 Buster = SharpBang ♯!

Offline

#2 2020-09-11 22:56:55

trilobite
Member
From: Saskatchewan, Canada
Registered: 2017-06-27
Posts: 28

Re: [SOLVED] - PC Locked-up - now with BOOT problems.

Pop in a live USB and boot from that, having a look at your HD.  I'm no genius about these things, but the SATA stuff does suggest an unhappy HD to me.


{Linux-using people I haven't met are friends yet to be made.}

Offline

#3 2020-09-12 00:50:39

Sector11
Conky 1.9er Mod Squid
From: Upstairs
Registered: 2015-08-20
Posts: 6,401

Re: [SOLVED] - PC Locked-up - now with BOOT problems.

Greeting from another Canuck.

Yea, it died about 45 minutes after writing that post.
The HDD is "maybe" a year old I am NOT happy.

Currently have a Live-USB stick plugged in and I loaded the whole stsyem into RAM.

That goodness for backups.
I am least up and running with all my old configs more or less and have email.


The sun will never set if you keep walking towards it. - my son
Being positive doesn't understand physics.
_______________________________
Debian 10 Buster = SharpBang ♯!

Offline

#4 2020-09-12 07:26:00

unklar
Member
Registered: 2015-10-31
Posts: 1,257

Re: [SOLVED] - PC Locked-up - now with BOOT problems.

^Unfortunately it is always so that one must concern oneself only with errors with the aforementioned problem.
That does not go me differently.  big_smile

In short, I don't think that the values you published are caused by a defect of the HDD. This smells like a cable fault.

Please test another cable/fixed cable connection before you throw away the disk.   wink
The smartctl values are ok for me.

Offline

#5 2020-09-12 15:38:30

Sector11
Conky 1.9er Mod Squid
From: Upstairs
Registered: 2015-08-20
Posts: 6,401

Re: [SOLVED] - PC Locked-up - now with BOOT problems.

unklar wrote:

^Unfortunately it is always so that one must concern oneself only with errors with the aforementioned problem.
That does not go me differently.  big_smile

In short, I don't think that the values you published are caused by a defect of the HDD. This smells like a cable fault.

Please test another cable/fixed cable connection before you throw away the disk.   wink
The smartctl values are ok for me.

I have no idea why you thought it was a cable.
For a desktop that never moves I have no idea how a cable can become loose but here it is all back in it's glory.
-----
Ich habe keine Ahnung, warum Sie dachten, es sei ein Kabel.
Bei einem Desktop, der sich nie bewegt, habe ich keine Ahnung, wie sich ein Kabel lösen kann, aber hier ist alles wieder in Ordnung.

2020-09-12_124442_S11.th.jpg

Smartctl seems the same though:
------
Smartctl scheint jedoch dasselbe zu sein:

 12 Sep 20 @ 12:30:32 ~
   $ sudo smartctl -a /dev/sda
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-10-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Blue
Device Model:     WDC WD10EZEX-08WN4A0
Serial Number:    WD-WCC6Y3UV88Y3
LU WWN Device Id: 5 0014ee 2662919f5
Firmware Version: 02.01A02
User Capacity:    1,000,204,886,016 bytes [1.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-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Sep 12 12:32:00 2020 -03
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:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
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: 		(10920) 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: 	 ( 114) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3035)	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       -       0
  3 Spin_Up_Time            0x0027   183   170   021    Pre-fail  Always       -       1833
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       323
  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   095   095   000    Old_age   Always       -       4378
 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       -       323
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       27
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       365
194 Temperature_Celsius     0x0022   112   099   000    Old_age   Always       -       31
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       -       0
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 2012 (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 2012 occurred at disk power-on lifetime: 4375 hours (182 days + 7 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
  -- -- -- -- -- -- --
  04 61 08 50 2d 69 e4  Device Fault; Error: ABRT at LBA = 0x04692d50 = 74001744

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ca 00 08 50 2d 69 e4 08      00:02:01.180  WRITE DMA
  ef 10 02 00 00 00 a0 08      00:02:01.180  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      00:02:01.179  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 08      00:02:01.179  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 08      00:02:01.179  SET FEATURES [Enable SATA feature]

Error 2011 occurred at disk power-on lifetime: 4375 hours (182 days + 7 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
  -- -- -- -- -- -- --
  04 61 02 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 10 02 00 00 00 a0 08      00:02:01.180  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      00:02:01.179  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 08      00:02:01.179  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 08      00:02:01.179  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      00:02:01.179  IDENTIFY DEVICE

Error 2010 occurred at disk power-on lifetime: 4375 hours (182 days + 7 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
  -- -- -- -- -- -- --
  04 61 45 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 03 45 00 00 00 a0 08      00:02:01.179  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 08      00:02:01.179  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      00:02:01.179  IDENTIFY DEVICE
  ca 00 18 80 2d 69 e4 08      00:02:01.160  WRITE DMA
  ef 10 02 00 00 00 a0 08      00:02:01.160  SET FEATURES [Enable SATA feature]

Error 2009 occurred at disk power-on lifetime: 4375 hours (182 days + 7 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
  -- -- -- -- -- -- --
  04 61 02 00 00 00 a0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ef 10 02 00 00 00 a0 08      00:02:01.179  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      00:02:01.179  IDENTIFY DEVICE
  ca 00 18 80 2d 69 e4 08      00:02:01.160  WRITE DMA
  ef 10 02 00 00 00 a0 08      00:02:01.160  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      00:02:01.159  IDENTIFY DEVICE

Error 2008 occurred at disk power-on lifetime: 4375 hours (182 days + 7 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
  -- -- -- -- -- -- --
  04 61 18 80 2d 69 e4  Device Fault; Error: ABRT at LBA = 0x04692d80 = 74001792

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ca 00 18 80 2d 69 e4 08      00:02:01.160  WRITE DMA
  ef 10 02 00 00 00 a0 08      00:02:01.160  SET FEATURES [Enable SATA feature]
  ec 00 00 00 00 00 a0 08      00:02:01.159  IDENTIFY DEVICE
  ef 03 45 00 00 00 a0 08      00:02:01.159  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 08      00:02:01.159  SET FEATURES [Enable SATA feature]

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

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.

 
 12 Sep 20 @ 12:32:00 ~
   $ 

I have NO idea what all that means.  Especially that "Old_age"
-----
Ich habe KEINE Ahnung, was das alles bedeutet.  Besonders dieses "Old_age" ("Alt_Alter")


========================
Mrs. unklar please give unklar a big hug from me.  He saved my day!
a big hug
-----
Frau unklar, bitte umarmen Sie unklar von mir.  Er hat meinen Tag gerettet!
eine große Umarmung

Last edited by Sector11 (2020-09-12 15:47:34)


The sun will never set if you keep walking towards it. - my son
Being positive doesn't understand physics.
_______________________________
Debian 10 Buster = SharpBang ♯!

Offline

#6 2020-09-12 18:11:23

PackRat
jgmenu user Numero Uno
Registered: 2015-10-02
Posts: 1,277

Re: [SOLVED] - PC Locked-up - now with BOOT problems.

S11 wrote:

I have no idea why you thought it was a cable.

Cables and motherboards fail too; I've a couple cables go in the past.

S11 wrote:

Especially that "Old_age"

Old age, or usage Attributes, are ones which indicate end-of-product life from old-age or normal  aging and wearout,


You must unlearn what you have learned.
    -- yoda

Offline

#7 2020-09-12 18:13:05

unklar
Member
Registered: 2015-10-31
Posts: 1,257

Re: [SOLVED] - PC Locked-up - now with BOOT problems.

Sector11 wrote:

I have no idea why you thought it was a cable.

I have no other picture here in a hurry...  (the 13th is tomorrow)  big_smile wink
(the speech bubbles are not important)

DSC_0032.th.jpg
I mean these red, flat cables that are plugged into the HDD on the back (of the picture) and on the other side to the Mobo.

Sector11 wrote:

I have NO idea what all that means.  Especially that "Old_age"

https://de.wikipedia.org/wiki/Self-Moni … _Parameter
https://en.wikipedia.org/wiki/S.M.A.R.T … attributes
https://wiki.debianforum.de/Festplatten … _Reparatur    glasses  big_smile  tongue

Last edited by unklar (2020-09-12 18:17:59)

Offline

#8 2020-09-12 18:38:58

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 661

Re: [SOLVED] - PC Locked-up - now with BOOT problems.

Smart log is not easy to read. I use to look for "Current_Pending_Sector" and "Offline_Uncorrectable", they had good figures:

197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always  -  0
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline -  0

Run "badblocks" and you will se if there is any errors. Takes considerable time. If you want to run it in write-mode (mark bad blocks, not only list them), you shall not haeve partion mounted. Better boot live dist then.

Last edited by rbh (2020-09-12 18:41:06)


// Regards rbh

Offline

#9 2020-09-12 18:59:43

Sector11
Conky 1.9er Mod Squid
From: Upstairs
Registered: 2015-08-20
Posts: 6,401

Re: [SOLVED] - PC Locked-up - now with BOOT problems.

PackRat wrote:
S11 wrote:

I have no idea why you thought it was a cable.

Cables and motherboards fail too; I've a couple cables go in the past.

Well, I can't recall a cable ever failing - and this one turned out to be loose.
Which is REALLY strange.

Aaaaaan I have just unlearned whet I though I had learned.  big_smile
Thank you - I though it was "telling me" my HDD was OLD.  DUH!


The sun will never set if you keep walking towards it. - my son
Being positive doesn't understand physics.
_______________________________
Debian 10 Buster = SharpBang ♯!

Offline

#10 2020-09-12 19:17:48

Sector11
Conky 1.9er Mod Squid
From: Upstairs
Registered: 2015-08-20
Posts: 6,401

Re: [SOLVED] - PC Locked-up - now with BOOT problems.

unklar wrote:

I mean these red, flat cables that are plugged into the HDD on the back (of the picture) and on the other side to the Mobo.

Interesting, mine are all black round cables.  All being 3, 2 going to DVD player (collecting dust these days) and 1 HDD.

Interessant, meine sind alle schwarze Rundkabel.  Alle sind 3, 2 gehen zum DVD-Player (der heutzutage Staub sammelt) und 1 HDD.

OK, thank you time to read.
OK, danke für die Zeit zum Lesen.


The sun will never set if you keep walking towards it. - my son
Being positive doesn't understand physics.
_______________________________
Debian 10 Buster = SharpBang ♯!

Offline

#11 2020-09-12 19:48:19

Sector11
Conky 1.9er Mod Squid
From: Upstairs
Registered: 2015-08-20
Posts: 6,401

Re: [SOLVED] - PC Locked-up - now with BOOT problems.

rbh wrote:

Run "badblocks" and you will se if there is any errors. Takes considerable time. If you want to run it in write-mode (mark bad blocks, not only list them), you shall not haeve partion mounted. Better boot live dist then.

Thank you - will consider that later.  Learning good stuff here.
For now ({snipped out common elements}):

 12 Sep 20 @ 16:45:38 ~
   $ sudo smartctl -H /dev/sda1
[sudo] password for sector11: 
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.19.0-10-amd64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
 
 12 Sep 20 @ 16:46:01 ~
   $ sudo smartctl -H /dev/sda2
{snip}
SMART overall-health self-assessment test result: PASSED
 
 12 Sep 20 @ 16:46:07 ~
   $ sudo smartctl -H /dev/sda3
{snip}
SMART overall-health self-assessment test result: PASSED
 
 12 Sep 20 @ 16:46:10 ~
   $ sudo smartctl -H /dev/sda4
{snip}
SMART overall-health self-assessment test result: PASSED
 
 12 Sep 20 @ 16:46:13 ~
   $ sudo smartctl -H /dev/sda5
{snip}
SMART overall-health self-assessment test result: PASSED
 
 12 Sep 20 @ 16:46:17 ~
   $ sudo smartctl -H /dev/sda6
{snip}
SMART overall-health self-assessment test result: PASSED
 
 12 Sep 20 @ 16:46:22 ~
   $ sudo smartctl -H /dev/sda7
{snip}
SMART overall-health self-assessment test result: PASSED
 
 12 Sep 20 @ 16:46:25 ~
   $ 

is acceptable.


The sun will never set if you keep walking towards it. - my son
Being positive doesn't understand physics.
_______________________________
Debian 10 Buster = SharpBang ♯!

Offline

#12 2020-09-12 22:22:55

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 661

Re: [SOLVED] - PC Locked-up - now with BOOT problems.

I have got "PASSED" on disks with high numbers of "Current_Pending_Sector" and "Offline_Uncorrectable".

You have enabled periodic offline testing? else you must issue new test before printing health report.


// Regards rbh

Offline

#13 2020-09-12 23:02:02

rbh
Member
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 661

Re: [SOLVED] - PC Locked-up - now with BOOT problems.

Sector11 wrote:

   $ sudo smartctl -H /dev/sda1

I was not paying enough attention to the text first.

From "man smartctl":

The user must specify the device to be controlled or interrogated as the final argument to smartctl. 

You shall not specify partitions! "smartctl -i /dev/sda1|sda2 gives the same ibformation as *sda.

Last edited by rbh (2020-09-12 23:02:53)


// Regards rbh

Offline

#14 2020-09-13 00:49:54

Sector11
Conky 1.9er Mod Squid
From: Upstairs
Registered: 2015-08-20
Posts: 6,401

Re: [SOLVED] - PC Locked-up - now with BOOT problems.

@ rbh

You're right sda1|2|3 is not correct /dev/sda, dev/sdb, etc are.
OOPS!  Thank you


The sun will never set if you keep walking towards it. - my son
Being positive doesn't understand physics.
_______________________________
Debian 10 Buster = SharpBang ♯!

Offline

Board footer

Powered by FluxBB