You are not logged in.

#1 2014-10-01 12:45:38

nstgc
Member
Registered: 2014-03-17
Posts: 393

kernel: Read-error on swap-device (8:0:2778448)

Last night I started par2 to repairing part of a large collection of file to make sure that the set of recovery data was good. This morning I was checking on it and saw "bus error (core dump)". I checked the systemd journal and saw the following.

Oct 01 00:12:10 {computer-name} systemd-timesyncd[513]: interval/delta/delay/jitter/drift 2048s/-0.005s/0.083s/0.005s/+6ppm
Oct 01 00:36:39 {computer-name} kernel: ata2.00: exception Emask 0x0 SAct 0x36c SErr 0x0 action 0x0
Oct 01 00:36:59 {computer-name} kernel: ata2.00: irq_stat 0x40000008
Oct 01 00:36:59 {computer-name} kernel: ata2.00: failed command: READ FPDMA QUEUED
Oct 01 00:36:59 {computer-name} kernel: ata2.00: cmd 60/38:40:48:65:2a/00:00:00:00:00/40 tag 8 ncq 28672 in
                                           res 41/40:00:48:65:2a/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Oct 01 00:36:59 {computer-name} kernel: ata2.00: status: { DRDY ERR }
Oct 01 00:37:00 {computer-name} kernel: ata2.00: error: { UNC }
Oct 01 00:37:00 {computer-name} kernel: ata2.00: configured for UDMA/133
Oct 01 00:37:00 {computer-name} kernel: sd 1:0:0:0: [sda] Unhandled sense code
Oct 01 00:37:00 {computer-name} kernel: sd 1:0:0:0: [sda]  
Oct 01 00:37:00 {computer-name} kernel: Result: hostbyte=0x00 driverbyte=0x08
Oct 01 00:37:00 {computer-name} kernel: sd 1:0:0:0: [sda]  
Oct 01 00:37:00 {computer-name} kernel: Sense Key : 0x3 [current] [descriptor]
Oct 01 00:37:00 {computer-name} kernel: Descriptor sense data with sense descriptors (in hex):
Oct 01 00:37:00 {computer-name} kernel:         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Oct 01 00:37:00 {computer-name} kernel:         00 2a 65 48 
Oct 01 00:37:00 {computer-name} kernel: sd 1:0:0:0: [sda]  
Oct 01 00:37:00 {computer-name} kernel: ASC=0x11 ASCQ=0x4
Oct 01 00:37:00 {computer-name} kernel: sd 1:0:0:0: [sda] CDB: 
Oct 01 00:37:00 {computer-name} kernel: cdb[0]=0x28: 28 00 00 2a 65 48 00 00 38 00
Oct 01 00:37:00 {computer-name} kernel: end_request: I/O error, dev sda, sector 2778440
Oct 01 00:37:00 {computer-name} kernel: Read-error on swap-device (8:0:2778448)
Oct 01 00:37:01 {computer-name} kernel: Read-error on swap-device (8:0:2778456)
Oct 01 00:37:01 {computer-name} kernel: Read-error on swap-device (8:0:2778464)
Oct 01 00:37:01 {computer-name} kernel: Read-error on swap-device (8:0:2778472)
Oct 01 00:37:01 {computer-name} kernel: Read-error on swap-device (8:0:2778480)
Oct 01 00:37:01 {computer-name} kernel: Read-error on swap-device (8:0:2778488)
Oct 01 00:37:02 {computer-name} kernel: Read-error on swap-device (8:0:2778496)
Oct 01 00:37:02 {computer-name} kernel: ata2: EH complete
Oct 01 00:36:56 {computer-name} systemd-coredump[2139]: Coredump of 667 (par2) is larger than configured processing limit, refusing.
Oct 01 00:36:57 {computer-name} systemd-coredump[2139]: Process 667 (par2) of user 1000 dumped core.
Oct 01 00:46:18 {computer-name} systemd-timesyncd[513]: interval/delta/delay/jitter/drift 2048s/+0.000s/0.071s/0.005s/+6ppm

A quick Google search lead to the assumption that this is due to a bad block, however I just tested it for bad block a few months ago. I'll check it again this after noon after work, but for now I wanted to get some other opinions. See if there is some other explanaition beyound a bad block.

[edit] The result of "smartctl -a /dev/sda". It looks like I might have an issue with my cable or something from the UDMA count.

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital VelociRaptor
Device Model:     WDC WD6000HLHX-01JJPV0
Serial Number:    {redacted}
LU WWN Device Id: 5 0014ee 658312eaa
Firmware Version: 04.05G04
User Capacity:    600,127,266,816 bytes [600 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    10000 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, 6.0 Gb/s
Local Time is:    Wed Oct  1 15:29:50 2014 EDT
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:                ( 7860) 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:        (  84) minutes.
Conveyance self-test routine
recommended polling time:        (   5) minutes.
SCT capabilities:              (0x303d) SCT Status supported.
                                        SCT Error Recovery Control 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   234   232   021    Pre-fail  Always       -       3291
  4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       1120
  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       -       3963
 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   099   099   000    Old_age   Always       -       1060
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       120
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       999
194 Temperature_Celsius     0x0022   120   114   000    Old_age   Always       -       30
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       -       10
200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       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 without error       00%         5         -
# 2  Extended offline    Aborted by host               90%         4         -
# 3  Conveyance offline  Aborted by host               90%         4         -
# 4  Short offline       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.

[edit2] Just to make sure, I checked and found that none of the other drives have UDMA CRC errors, even the one that shares the same controller.
[edit3] Badblocks came back negative, and the previous time I tried this, just the night before, I didn't have any issues. I forgot to mention that last bit.

Last edited by nstgc (2014-10-01 20:02:58)

Offline

#2 2014-10-01 12:55:30

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,541

Re: kernel: Read-error on swap-device (8:0:2778448)

Try smartctl to see if it is showing anything.


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#3 2014-10-01 13:21:00

nstgc
Member
Registered: 2014-03-17
Posts: 393

Re: kernel: Read-error on swap-device (8:0:2778448)

nomorewindows wrote:

Try smartctl to see if it is showing anything.

I will when I get home.

I just remembered that I have another thread on these forums about my Steam library disappearing. My steam library is on a raid0 btrfs volume that does not include the drive that the swap partition is on. The point being that if this is a drive issue, it is unrelated to the previous problem. if its a different hardware issue or a software issue, it could still be related.

[edit] The SMART information is in the opening thread now. It looks like it may be a cable issue.

[edit2] Just to make sure, I checked and found that none of the other drives have UDMA CRC errors, even the one that shares the same controller.
[edit3] Badblocks came back negative, and the previous time I tried this, just the night before, I didn't have any issues. I forgot to mention that last bit.

Last edited by nstgc (2014-10-01 20:03:09)

Offline

Board footer

Powered by FluxBB