LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page is my harddisk dying?
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-16-2010, 09:32 AM   #1
kite
Member
 
Registered: Aug 2003
Location: Shenzhen, China
Distribution: Slackware
Posts: 306

Rep: Reputation: 47
is my harddisk dying?

This is a block of dmesg:

Code:
ata4.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
ata4.00: irq_stat 0x40000008
ata4.00: failed command: READ FPDMA QUEUED
ata4.00: cmd 60/08:10:47:97:85/00:00:09:00:00/40 tag 2 ncq 4096 in
         res 41/40:00:48:97:85/00:00:09:00:00/40 Emask 0x409 (media error) <F>
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: configured for UDMA/133
ata4: EH complete
ata4.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
ata4.00: irq_stat 0x40000008
ata4.00: failed command: READ FPDMA QUEUED
ata4.00: cmd 60/08:00:47:97:85/00:00:09:00:00/40 tag 0 ncq 4096 in
         res 41/40:00:48:97:85/00:00:09:00:00/40 Emask 0x409 (media error) <F>
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: configured for UDMA/133
ata4: EH complete
ata4.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
ata4.00: irq_stat 0x40000008
ata4.00: failed command: READ FPDMA QUEUED
ata4.00: cmd 60/08:10:47:97:85/00:00:09:00:00/40 tag 2 ncq 4096 in
         res 41/40:00:48:97:85/00:00:09:00:00/40 Emask 0x409 (media error) <F>
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: configured for UDMA/133
ata4: EH complete
ata4.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
ata4.00: irq_stat 0x40000008
ata4.00: failed command: READ FPDMA QUEUED
ata4.00: cmd 60/08:00:47:97:85/00:00:09:00:00/40 tag 0 ncq 4096 in
         res 41/40:00:48:97:85/00:00:09:00:00/40 Emask 0x409 (media error) <F>
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: configured for UDMA/133
ata4: EH complete
ata4.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
ata4.00: irq_stat 0x40000008
ata4.00: failed command: READ FPDMA QUEUED
ata4.00: cmd 60/08:10:47:97:85/00:00:09:00:00/40 tag 2 ncq 4096 in
         res 41/40:00:48:97:85/00:00:09:00:00/40 Emask 0x409 (media error) <F>
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: configured for UDMA/133
ata4: EH complete
ata4.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
ata4.00: irq_stat 0x40000008
ata4.00: failed command: READ FPDMA QUEUED
ata4.00: cmd 60/08:00:47:97:85/00:00:09:00:00/40 tag 0 ncq 4096 in
         res 41/40:00:48:97:85/00:00:09:00:00/40 Emask 0x409 (media error) <F>
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: configured for UDMA/133
sd 3:0:0:0: [sda] Unhandled sense code
sd 3:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 3:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
        09 85 97 48 
sd 3:0:0:0: [sda] ASC=0x11 ASCQ=0x4
sd 3:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 09 85 97 47 00 00 08 00
end_request: I/O error, dev sda, sector 159749960
Buffer I/O error on device sda1, logical block 159749897
Buffer I/O error on device sda1, logical block 159749898
Buffer I/O error on device sda1, logical block 159749899
Buffer I/O error on device sda1, logical block 159749900
Buffer I/O error on device sda1, logical block 159749901
Buffer I/O error on device sda1, logical block 159749902
Buffer I/O error on device sda1, logical block 159749903
ata4: EH complete
ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
ata4.00: irq_stat 0x40000008
ata4.00: failed command: READ FPDMA QUEUED
ata4.00: cmd 60/07:00:48:97:85/00:00:09:00:00/40 tag 0 ncq 3584 in
         res 41/40:00:48:97:85/00:00:09:00:00/40 Emask 0x409 (media error) <F>
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: configured for UDMA/133
ata4: EH complete
ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
ata4.00: irq_stat 0x40000008
ata4.00: failed command: READ FPDMA QUEUED
ata4.00: cmd 60/07:00:48:97:85/00:00:09:00:00/40 tag 0 ncq 3584 in
         res 41/40:00:48:97:85/00:00:09:00:00/40 Emask 0x409 (media error) <F>
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: configured for UDMA/133
ata4: EH complete
ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
ata4.00: irq_stat 0x40000008
ata4.00: failed command: READ FPDMA QUEUED
ata4.00: cmd 60/07:00:48:97:85/00:00:09:00:00/40 tag 0 ncq 3584 in
         res 41/40:00:48:97:85/00:00:09:00:00/40 Emask 0x409 (media error) <F>
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: configured for UDMA/133
ata4: EH complete
ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
ata4.00: irq_stat 0x40000008
ata4.00: failed command: READ FPDMA QUEUED
ata4.00: cmd 60/07:00:48:97:85/00:00:09:00:00/40 tag 0 ncq 3584 in
         res 41/40:00:48:97:85/00:00:09:00:00/40 Emask 0x409 (media error) <F>
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: configured for UDMA/133
ata4: EH complete
ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
ata4.00: irq_stat 0x40000008
ata4.00: failed command: READ FPDMA QUEUED
ata4.00: cmd 60/07:00:48:97:85/00:00:09:00:00/40 tag 0 ncq 3584 in
         res 41/40:00:48:97:85/00:00:09:00:00/40 Emask 0x409 (media error) <F>
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: configured for UDMA/133
ata4: EH complete
ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
ata4.00: irq_stat 0x40000008
ata4.00: failed command: READ FPDMA QUEUED
ata4.00: cmd 60/07:00:48:97:85/00:00:09:00:00/40 tag 0 ncq 3584 in
         res 41/40:00:48:97:85/00:00:09:00:00/40 Emask 0x409 (media error) <F>
ata4.00: status: { DRDY ERR }
ata4.00: error: { UNC }
ata4.00: configured for UDMA/133
sd 3:0:0:0: [sda] Unhandled sense code
sd 3:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
sd 3:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
        09 85 97 48 
sd 3:0:0:0: [sda] ASC=0x11 ASCQ=0x4
sd 3:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 09 85 97 48 00 00 07 00
end_request: I/O error, dev sda, sector 159749960
Buffer I/O error on device sda1, logical block 159749897
Buffer I/O error on device sda1, logical block 159749898
Buffer I/O error on device sda1, logical block 159749899
Buffer I/O error on device sda1, logical block 159749900
Buffer I/O error on device sda1, logical block 159749901
Buffer I/O error on device sda1, logical block 159749902
Buffer I/O error on device sda1, logical block 159749903
ata4: EH complete
 
Old 10-16-2010, 09:52 AM   #2
ozanbaba
Member
 
Registered: May 2003
Location: İzmir
Distribution: Slackware64 15.0 Multilib
Posts: 778

Rep: Reputation: 135Reputation: 135
It looks it does. What SMART says? (smartctl [Dev Name]). And is your harddisk securely placed? Small vibrations may cause reading instabilities but that's really unlikely. Back up your data. How old is the harddisk?.
 
Old 10-16-2010, 10:34 AM   #3
kite
Member
 
Registered: Aug 2003
Location: Shenzhen, China
Distribution: Slackware
Posts: 306

Original Poster
Rep: Reputation: 47
My harddisk is well placed. And I have tried to replace the cable without help. I bought this new harddisk about 4 months ago.

here is the result of smartctl --all /dev/sda

Code:
smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD10EARS-00Y5B1
Serial Number:    WD-WCAV57518085
Firmware Version: 80.00A80
User Capacity:    1,000,204,886,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Sat Oct 16 23:24:41 2010 CST
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:  (0x84)	Offline data collection activity
					was suspended by an interrupting command from host.
					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: 		 (18960) 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: 	 ( 219) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3031)	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       -       1951
  3 Spin_Up_Time            0x0027   129   127   021    Pre-fail  Always       -       6550
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       548
  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   097   097   000    Old_age   Always       -       2536
 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       -       544
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       75
193 Load_Cycle_Count        0x0032   154   154   000    Old_age   Always       -       139120
194 Temperature_Celsius     0x0022   111   096   000    Old_age   Always       -       36
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       80
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       127
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      -       156

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  Conveyance offline  Completed without error       00%      1818         -
# 2  Short offline       Completed without error       00%      1798         -

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.
 
Old 10-16-2010, 11:00 AM   #4
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
Now, you have 127 bad sectors and 80 sectors suspected to be damaged. It's time to seriously think about a full backup and buying a new hard drive. Sorry!
 
Old 10-16-2010, 11:22 AM   #5
ozanbaba
Member
 
Registered: May 2003
Location: İzmir
Distribution: Slackware64 15.0 Multilib
Posts: 778

Rep: Reputation: 135Reputation: 135
Quote:
Originally Posted by Darth Vader View Post
Now, you have 127 bad sectors and 80 sectors suspected to be damaged. It's time to seriously think about a full backup and buying a new hard drive. Sorry!
And do it quickly. HDDs dies in radom intervals. It can go kaput at any given time now. Don't loose any time.
 
Old 10-16-2010, 12:31 PM   #6
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
Try a smartctl long test: 'smartctl -t long /dev/sda'
 
Old 10-16-2010, 07:56 PM   #7
kite
Member
 
Registered: Aug 2003
Location: Shenzhen, China
Distribution: Slackware
Posts: 306

Original Poster
Rep: Reputation: 47
Thanks for pointing out. This is really horrible considering that it is a new hard disk.

I ran a a smartctl long test: 'smartctl -t long /dev/sda', but do not know where to collect the output/result.
 
Old 10-16-2010, 08:13 PM   #8
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
Just do a dump of "smartctl --all /dev/sda" for our eyes pleasure.

BTW, the long test don't fix anything and will abort on first problem. Consider to buy a new hard drive quickly.
 
Old 10-16-2010, 08:15 PM   #9
SuperTico
LQ Newbie
 
Registered: Sep 2010
Location: Costa Rica
Distribution: SalineOS 1.5
Posts: 20

Rep: Reputation: 1
Just get another drive. These daze they are chump change.
 
Old 10-17-2010, 04:21 AM   #10
kite
Member
 
Registered: Aug 2003
Location: Shenzhen, China
Distribution: Slackware
Posts: 306

Original Poster
Rep: Reputation: 47
Thanks for everyone. I have bought another harddisk.
 
Old 10-17-2010, 05:13 AM   #11
ozanbaba
Member
 
Registered: May 2003
Location: İzmir
Distribution: Slackware64 15.0 Multilib
Posts: 778

Rep: Reputation: 135Reputation: 135
Quote:
Originally Posted by kite View Post
Thanks for everyone. I have bought another harddisk.
Was the original HDD in the guarantee? They may give you a nice disk.
 
Old 10-17-2010, 05:30 AM   #12
kite
Member
 
Registered: Aug 2003
Location: Shenzhen, China
Distribution: Slackware
Posts: 306

Original Poster
Rep: Reputation: 47
Yes, I think so. I bought the old one in March 2010. Then I will have an extra harddisk for backup purpose. thanks a lot.
 
Old 10-17-2010, 06:29 AM   #13
hughetorrance
Member
 
Registered: Aug 2009
Location: London North West
Distribution: x86_64 Slack 13.37 current : +others
Posts: 459

Rep: Reputation: 59
I would have used spinrite on it and see if it can sort it out... ! Google for the free one.
 
  


Reply

Tags
harddisk



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Is my harddisk dying ? mfred Linux - Hardware 2 12-31-2005 08:20 AM
monitor dying? SlipAway172 Linux - Hardware 3 07-29-2005 10:37 PM
dhclient keeps dying! chanys Linux - Networking 0 12-21-2004 02:43 AM
Low Harddisk space. Can I just transfer the entire Linux to a bigger harddisk? davidas Linux - Newbie 12 04-13-2004 02:03 AM
Dying disk???? Mux Linux - Hardware 2 10-22-2002 06:27 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:44 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration