You are not logged in.

Pages: 1

#1 2016-11-02 06:35:49

MrSatchmoo
Member
Registered: 2016-11-02
Posts: 3

hd broken?

Hi all,

after booting and logging in to gnome my system kind of freezes for about 20 seconds. gnome shell works but if i want to start a program nothing happens. After searching around I found that dmsg gives me this:

[   42.776558] ata2.00: invalid checksum 0x89 on log page 10h
[   42.776561] ata2.00: exception Emask 0x0 SAct 0x1f800000 SErr 0x0 action 0x0
[   42.776563] ata2.00: irq_stat 0x40000008
[   42.776565] ata2.00: failed command: READ FPDMA QUEUED
[   42.776567] ata2.00: cmd 60/00:b8:e0:c5:5e/01:00:18:00:00/40 tag 23 ncq dma 131072 in
                        res 51/40:b8:c0:c6:5e/00:00:18:00:00/40 Emask 0x409 (media error) <F>
[   42.776568] ata2.00: status: { DRDY ERR }
[   42.776569] ata2.00: error: { UNC }
[   42.795050] ata2.00: configured for UDMA/133
[   42.795057] sd 1:0:0:0: [sdb] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   42.795059] sd 1:0:0:0: [sdb] tag#23 Sense Key : 0x3 [current] 
[   42.795059] sd 1:0:0:0: [sdb] tag#23 ASC=0x11 ASCQ=0x4 
[   42.795060] sd 1:0:0:0: [sdb] tag#23 CDB: opcode=0x28 28 00 18 5e c5 e0 00 01 00 00
[   42.795061] blk_update_request: I/O error, dev sdb, sector 408864448
[   42.795079] ata2: EH complete
[   44.758675] ata2.00: invalid checksum 0x27 on log page 10h
[   44.758677] ata2.00: exception Emask 0x0 SAct 0xfc003c SErr 0x0 action 0x0
[   44.758684] ata2.00: irq_stat 0x40000008
[   44.758688] ata2.00: failed command: READ FPDMA QUEUED
[   44.758692] ata2.00: cmd 60/00:28:e0:c6:5e/01:00:18:00:00/40 tag 5 ncq dma 131072 in
                        res 51/40:28:e0:c6:5e/00:00:18:00:00/40 Emask 0x409 (media error) <F>
[   44.758698] ata2.00: status: { DRDY ERR }
[   44.758701] ata2.00: error: { UNC }
[   44.776760] ata2.00: configured for UDMA/133
[   44.776775] sd 1:0:0:0: [sdb] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   44.776776] sd 1:0:0:0: [sdb] tag#5 Sense Key : 0x3 [current] 
[   44.776777] sd 1:0:0:0: [sdb] tag#5 ASC=0x11 ASCQ=0x4 
[   44.776778] sd 1:0:0:0: [sdb] tag#5 CDB: opcode=0x28 28 00 18 5e c6 e0 00 01 00 00
[   44.776779] blk_update_request: I/O error, dev sdb, sector 408864480
[   44.776799] ata2: EH complete
[   46.815364] ata2.00: invalid checksum 0x14 on log page 10h
[   46.815368] ata2.00: exception Emask 0x0 SAct 0x400 SErr 0x0 action 0x0
[   46.815380] ata2.00: irq_stat 0x40000008
[   46.815386] ata2.00: failed command: READ FPDMA QUEUED
[   46.815394] ata2.00: cmd 60/08:50:c0:c6:5e/00:00:18:00:00/40 tag 10 ncq dma 4096 in
                        res 51/40:50:c0:c6:5e/00:00:18:00:00/40 Emask 0x409 (media error) <F>
[   46.815406] ata2.00: status: { DRDY ERR }
[   46.815410] ata2.00: error: { UNC }
[   46.833292] ata2.00: configured for UDMA/133
[   46.833298] sd 1:0:0:0: [sdb] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   46.833299] sd 1:0:0:0: [sdb] tag#10 Sense Key : 0x3 [current] 
[   46.833300] sd 1:0:0:0: [sdb] tag#10 ASC=0x11 ASCQ=0x4 
[   46.833301] sd 1:0:0:0: [sdb] tag#10 CDB: opcode=0x28 28 00 18 5e c6 c0 00 00 08 00
[   46.833302] blk_update_request: I/O error, dev sdb, sector 408864448
[   46.833317] ata2: EH complete
[   48.772623] ata2.00: invalid checksum 0x65 on log page 10h
[   48.772631] ata2.00: exception Emask 0x0 SAct 0x80000 SErr 0x0 action 0x0
[   48.772654] ata2.00: irq_stat 0x40000008
[   48.772668] ata2.00: failed command: READ FPDMA QUEUED
[   48.772687] ata2.00: cmd 60/08:98:c0:c6:5e/00:00:18:00:00/40 tag 19 ncq dma 4096 in
                        res 51/40:98:c0:c6:5e/00:00:18:00:00/40 Emask 0x409 (media error) <F>
[   48.772712] ata2.00: status: { DRDY ERR }
[   48.772723] ata2.00: error: { UNC }
[   48.790913] ata2.00: configured for UDMA/133
[   48.790930] sd 1:0:0:0: [sdb] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   48.790934] sd 1:0:0:0: [sdb] tag#19 Sense Key : 0x3 [current] 
[   48.790938] sd 1:0:0:0: [sdb] tag#19 ASC=0x11 ASCQ=0x4 
[   48.790941] sd 1:0:0:0: [sdb] tag#19 CDB: opcode=0x28 28 00 18 5e c6 c0 00 00 08 00
[   48.790944] blk_update_request: I/O error, dev sdb, sector 408864448
[   48.790999] ata2: EH complete
[   81.359150] ata2.00: exception Emask 0x0 SAct 0x1c008 SErr 0x0 action 0x6 frozen
[   81.359179] ata2.00: failed command: READ FPDMA QUEUED
[   81.359200] ata2.00: cmd 60/08:18:c0:c6:5e/00:00:18:00:00/40 tag 3 ncq dma 4096 in
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   81.359225] ata2.00: status: { DRDY }
[   81.359236] ata2.00: failed command: WRITE FPDMA QUEUED
[   81.359253] ata2.00: cmd 61/28:70:78:84:b8/00:00:19:00:00/40 tag 14 ncq dma 20480 out
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   81.359282] ata2.00: status: { DRDY }
[   81.359292] ata2.00: failed command: READ FPDMA QUEUED
[   81.359309] ata2.00: cmd 60/08:78:08:ed:b8/00:00:18:00:00/40 tag 15 ncq dma 4096 in
                        res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[   81.359331] ata2.00: status: { DRDY }
[   81.359341] ata2.00: failed command: READ FPDMA QUEUED
[   81.359357] ata2.00: cmd 60/08:80:b0:82:75/00:00:18:00:00/40 tag 16 ncq dma 4096 in
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   81.359380] ata2.00: status: { DRDY }
[   81.359393] ata2: hard resetting link
[   81.679533] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   81.689802] ata2.00: configured for UDMA/133
[   81.689809] ata2.00: device reported invalid CHS sector 0
[   81.689813] ata2.00: device reported invalid CHS sector 0
[   81.689816] ata2.00: device reported invalid CHS sector 0
[   81.689845] ata2: EH complete
[   83.629061] ata2.00: invalid checksum 0x80 on log page 10h
[   83.629069] ata2.00: exception Emask 0x0 SAct 0x500000 SErr 0x0 action 0x0
[   83.629094] ata2.00: irq_stat 0x40000008
[   83.629108] ata2.00: failed command: READ FPDMA QUEUED
[   83.629127] ata2.00: cmd 60/08:b0:c0:c6:5e/00:00:18:00:00/40 tag 22 ncq dma 4096 in
                        res 51/40:b0:c0:c6:5e/00:00:18:00:00/40 Emask 0x409 (media error) <F>
[   83.629152] ata2.00: status: { DRDY ERR }
[   83.629163] ata2.00: error: { UNC }
[   83.647108] ata2.00: configured for UDMA/133
[   83.647142] sd 1:0:0:0: [sdb] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   83.647147] sd 1:0:0:0: [sdb] tag#22 Sense Key : 0x3 [current] 
[   83.647150] sd 1:0:0:0: [sdb] tag#22 ASC=0x11 ASCQ=0x4 
[   83.647155] sd 1:0:0:0: [sdb] tag#22 CDB: opcode=0x28 28 00 18 5e c6 c0 00 00 08 00
[   83.647158] blk_update_request: I/O error, dev sdb, sector 408864448
[   83.647197] ata2: EH complete
[   85.594530] ata2.00: invalid checksum 0x5c on log page 10h
[   85.594537] ata2.00: exception Emask 0x0 SAct 0x40000 SErr 0x0 action 0x0
[   85.594559] ata2.00: irq_stat 0x40000008
[   85.594571] ata2.00: failed command: READ FPDMA QUEUED
[   85.594588] ata2.00: cmd 60/08:90:c0:c6:5e/00:00:18:00:00/40 tag 18 ncq dma 4096 in
                        res 51/40:90:c0:c6:5e/00:00:18:00:00/40 Emask 0x409 (media error) <F>
[   85.594609] ata2.00: status: { DRDY ERR }
[   85.594618] ata2.00: error: { UNC }
[   85.612572] ata2.00: configured for UDMA/133
[   85.612588] sd 1:0:0:0: [sdb] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   85.612593] sd 1:0:0:0: [sdb] tag#18 Sense Key : 0x3 [current] 
[   85.612596] sd 1:0:0:0: [sdb] tag#18 ASC=0x11 ASCQ=0x4 
[   85.612600] sd 1:0:0:0: [sdb] tag#18 CDB: opcode=0x28 28 00 18 5e c6 c0 00 00 08 00
[   85.612603] blk_update_request: I/O error, dev sdb, sector 408864448
[   85.612660] ata2: EH complete
[   87.535138] ata2.00: invalid checksum 0xcc on log page 10h
[   87.535145] ata2.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x0
[   87.535164] ata2.00: irq_stat 0x40000008
[   87.535176] ata2.00: failed command: READ FPDMA QUEUED
[   87.535192] ata2.00: cmd 60/08:10:c0:c6:5e/00:00:18:00:00/40 tag 2 ncq dma 4096 in
                        res 51/40:10:c0:c6:5e/00:00:18:00:00/40 Emask 0x409 (media error) <F>
[   87.535214] ata2.00: status: { DRDY ERR }
[   87.535223] ata2.00: error: { UNC }
[   87.553115] ata2.00: configured for UDMA/133
[   87.553129] sd 1:0:0:0: [sdb] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   87.553133] sd 1:0:0:0: [sdb] tag#2 Sense Key : 0x3 [current] 
[   87.553136] sd 1:0:0:0: [sdb] tag#2 ASC=0x11 ASCQ=0x4 
[   87.553140] sd 1:0:0:0: [sdb] tag#2 CDB: opcode=0x28 28 00 18 5e c6 c0 00 00 08 00
[   87.553142] blk_update_request: I/O error, dev sdb, sector 408864448
[   87.553662] ata2: EH complete
[   89.608440] ata2.00: invalid checksum 0x80 on log page 10h
[   89.608448] ata2.00: exception Emask 0x0 SAct 0x400000 SErr 0x0 action 0x0
[   89.609067] ata2.00: irq_stat 0x40000008
[   89.611118] ata2.00: failed command: READ FPDMA QUEUED
[   89.613571] ata2.00: cmd 60/08:b0:c0:c6:5e/00:00:18:00:00/40 tag 22 ncq dma 4096 in
                        res 51/40:b0:c0:c6:5e/00:00:18:00:00/40 Emask 0x409 (media error) <F>
[   89.618481] ata2.00: status: { DRDY ERR }
[   89.620883] ata2.00: error: { UNC }
[   89.633419] ata2.00: configured for UDMA/133
[   89.633433] sd 1:0:0:0: [sdb] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[   89.633436] sd 1:0:0:0: [sdb] tag#22 Sense Key : 0x3 [current] 
[   89.633439] sd 1:0:0:0: [sdb] tag#22 ASC=0x11 ASCQ=0x4 
[   89.633443] sd 1:0:0:0: [sdb] tag#22 CDB: opcode=0x28 28 00 18 5e c6 c0 00 00 08 00
[   89.633446] blk_update_request: I/O error, dev sdb, sector 408864448
[   89.633969] ata2: EH complete

I have to say that I don't have any idea what that means. Is my sdb broken?

Thank you in advance!

Offline

#2 2016-11-02 06:46:24

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: hd broken?

What does smartctl say?

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2016-11-02 19:21:17

MrSatchmoo
Member
Registered: 2016-11-02
Posts: 3

Re: hd broken?

Hello. Here's the result: 

$ sudo smartctl -H /dev/sdb
[sudo] Passwort für satch: 
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.8.4-1-ARCH] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

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

I'm still running the long test and I will post differing results in an hour.
Thank you for your fast answer!

Offline

#4 2016-11-02 20:35:54

seth
Member
Registered: 2012-09-03
Posts: 50,931

Re: hd broken?

You probably don't require the test, "sudo smartctl -a /dev/sdb" will usually know whether there're uncorrectable errors or pending sectors and stuff.
Avoid burdening the device - if it's bad, you might add the final call this way (loosing your data which you should rather secure)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#5 2016-11-02 20:49:58

MrSatchmoo
Member
Registered: 2016-11-02
Posts: 3

Re: hd broken?

OK, here we go:

 $ sudo smartctl -a /dev/sdb
[sudo] Passwort für satch: 
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.8.4-1-ARCH] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint P120
Device Model:     SAMSUNG SP2504C
Serial Number:    S09QJ1UL304014
Firmware Version: VT100-33
User Capacity:    250.058.268.160 bytes [250 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA/ATAPI-7 T13/1532D revision 4a
Local Time is:    Wed Nov  2 21:47:47 2016 CET

==> WARNING: May need -F samsung3 enabled; see manual for details.

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:      ( 121)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		( 4866) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 (  81) minutes.

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     0x000f   253   100   051    Pre-fail  Always       -       2
  3 Spin_Up_Time            0x0007   100   100   025    Pre-fail  Always       -       5824
  4 Start_Stop_Count        0x0032   090   090   000    Old_age   Always       -       10419
  5 Reallocated_Sector_Ct   0x0033   253   253   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   253   253   051    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0025   253   253   015    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       27213
 10 Spin_Retry_Count        0x0033   253   253   051    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x0012   253   002   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   096   096   000    Old_age   Always       -       4839
190 Airflow_Temperature_Cel 0x0022   142   103   000    Old_age   Always       -       32
194 Temperature_Celsius     0x0022   142   103   000    Old_age   Always       -       32
195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       -       171097
196 Reallocated_Event_Count 0x0032   253   253   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0012   096   096   000    Old_age   Always       -       44
198 Offline_Uncorrectable   0x0030   253   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x000a   100   100   000    Old_age   Always       -       0
201 Soft_Read_Error_Rate    0x000a   253   100   000    Old_age   Always       -       0
202 Data_Address_Mark_Errs  0x0032   253   253   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%     27212         -
# 2  Extended offline    Completed: read failure       90%     27212         -
# 3  Short offline       Completed: read failure       90%     27212         -

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 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.

Offline

#6 2016-11-02 20:58:19

Potomac
Member
Registered: 2011-12-25
Posts: 526

Re: hd broken?

the problem has begun since a recent "pacman -Syu" ?

did you try with another kernel, like linux-lts ?

Offline

#7 2016-11-02 21:02:33

seth
Member
Registered: 2012-09-03
Posts: 50,931

Re: hd broken?

> 197 Current_Pending_Sector  0x0012   096   096   000    Old_age   Always       -       44

Weary. Ensure this value doesn't raise.

> # 1  Extended offline    Completed: read failure       90%     27212         -
Not good and you've 2 read errors.

The disk is not dead, but the reading problems are not in software.
Could be (bad) powersaving or bad cable/connectors. - sdb is an external disk? usb?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#8 2016-11-02 21:07:29

frostschutz
Member
Registered: 2013-11-15
Posts: 1,417

Re: hd broken?

Pending sectors are sectors the HDD can not read anymore. That's the number of them the disk knows about - there could be more. If there was valuable data in those sectors, it is lost. Never mind that filesystems and programs are not prepared to handle read errors and all those scary error messages you got - do you want to trust a disk that already lost you data?

I prefer to replace such disks or put them to tasks where data loss and system instability is acceptable. Other people claim this is normal behaviour. They write new data (low level format, raid resync, etc.) and happily keep using it in the hopes it won't happen again.

There's no way of knowing whether it's caused by a random fluke or if there is a serious mechanical error problem the disk.

Last edited by frostschutz (2016-11-02 21:08:41)

Offline

#9 2016-11-02 22:56:42

seth
Member
Registered: 2012-09-03
Posts: 50,931

Re: hd broken?

Pending sectors can (and very often are) due to a dying disc (and if the number raises constantly, you're in trouble) but can have other causes.
You can test the sector by writing it and it's then either remapped or "good" again, but if you keep pending sectors, there's something wrong in the setup.

See http://daemon-notes.com/articles/system … nt-pending

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

Pages: 1

Board footer

Powered by FluxBB