LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
Reload this Page Pretty sure I am having hard drive problems...
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 07-21-2011, 01:43 AM   #1
Skillz
Member
 
Registered: Sep 2007
Posts: 252

Rep: Reputation: 32
Pretty sure I am having hard drive problems...

Code:
Jul 20 10:37:09 server2 kernel:          res 51/40:00:f4:07:e8/40:00:2a:00:00/00 Emask 0x9 (media error)
Jul 20 10:37:09 server2 kernel: ata2.00: status: { DRDY ERR }
Jul 20 10:37:09 server2 kernel: ata2.00: error: { UNC }
Jul 20 10:37:09 server2 kernel: ata2.00: configured for UDMA/133
Jul 20 10:37:09 server2 kernel: ata2: EH complete
Jul 20 10:37:10 server2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 20 10:37:10 server2 kernel: ata2.00: BMDMA stat 0x24
Jul 20 10:37:10 server2 kernel: ata2.00: cmd 25/00:08:ef:07:e8/00:00:2a:00:00/e0 tag 0 dma 4096 in
Jul 20 10:37:10 server2 kernel:          res 51/40:00:f4:07:e8/40:00:2a:00:00/00 Emask 0x9 (media error)
Jul 20 10:37:10 server2 kernel: ata2.00: status: { DRDY ERR }
Jul 20 10:37:10 server2 kernel: ata2.00: error: { UNC }
Jul 20 10:37:10 server2 kernel: ata2.00: configured for UDMA/133
Jul 20 10:37:10 server2 kernel: ata2: EH complete
Jul 20 10:37:12 server2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 20 10:37:12 server2 kernel: ata2.00: BMDMA stat 0x24
Jul 20 10:37:12 server2 kernel: ata2.00: cmd 25/00:08:ef:07:e8/00:00:2a:00:00/e0 tag 0 dma 4096 in
Jul 20 10:37:12 server2 kernel:          res 51/40:00:f4:07:e8/40:00:2a:00:00/00 Emask 0x9 (media error)
Jul 20 10:37:12 server2 kernel: ata2.00: status: { DRDY ERR }
Jul 20 10:37:12 server2 kernel: ata2.00: error: { UNC }
Jul 20 10:37:12 server2 kernel: ata2.00: configured for UDMA/133
Jul 20 10:37:12 server2 kernel: ata2: EH complete
Jul 20 10:37:14 server2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 20 10:37:14 server2 kernel: ata2.00: BMDMA stat 0x24
Jul 20 10:37:14 server2 kernel: ata2.00: cmd 25/00:08:ef:07:e8/00:00:2a:00:00/e0 tag 0 dma 4096 in
Jul 20 10:37:14 server2 kernel:          res 51/40:00:f4:07:e8/40:00:2a:00:00/00 Emask 0x9 (media error)
Jul 20 10:37:14 server2 kernel: ata2.00: status: { DRDY ERR }
Jul 20 10:37:14 server2 kernel: ata2.00: error: { UNC }
Jul 20 10:37:14 server2 kernel: ata2.00: configured for UDMA/133
Jul 20 10:37:14 server2 kernel: sd 1:0:0:0: SCSI error: return code = 0x08000002
Jul 20 10:37:14 server2 kernel: sdc: Current [descriptor]: sense key: Medium Error
Jul 20 10:37:14 server2 kernel:     Add. Sense: Unrecovered read error - auto reallocate failed
Jul 20 10:37:14 server2 kernel:
Jul 20 10:37:14 server2 kernel: Descriptor sense data with sense descriptors (in hex):
Jul 20 10:37:14 server2 kernel:         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Jul 20 10:37:14 server2 kernel:         2a e8 07 f4
Jul 20 10:37:14 server2 kernel: end_request: I/O error, dev sdc, sector 719849460
Jul 20 10:37:14 server2 kernel: ata2: EH complete
Jul 20 10:37:14 server2 kernel: SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)
Jul 20 10:37:14 server2 kernel: sdc: Write Protect is off
Jul 20 10:37:14 server2 kernel: SCSI device sdc: drive cache: write back
Jul 20 10:37:14 server2 kernel: SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)
Jul 20 10:37:14 server2 kernel: sdc: Write Protect is off
Jul 20 10:37:14 server2 kernel: SCSI device sdc: drive cache: write back
Jul 20 10:37:14 server2 kernel: EXT2-fs error (device sdc1): ext2_get_inode: unable to read inode block - inode=44998281, block=89981174
Jul 20 10:37:16 server2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 20 10:37:16 server2 kernel: ata2.00: BMDMA stat 0x24
Jul 20 10:37:16 server2 kernel: ata2.00: cmd 25/00:08:ef:07:e8/00:00:2a:00:00/e0 tag 0 dma 4096 in
Jul 20 10:37:16 server2 kernel:          res 51/40:00:f4:07:e8/40:00:2a:00:00/00 Emask 0x9 (media error)
Jul 20 10:37:16 server2 kernel: ata2.00: status: { DRDY ERR }
Jul 20 10:37:16 server2 kernel: ata2.00: error: { UNC }
Jul 20 10:37:16 server2 kernel: ata2.00: configured for UDMA/133
Jul 20 10:37:16 server2 kernel: ata2: EH complete
Jul 20 10:37:18 server2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 20 10:37:18 server2 kernel: ata2.00: BMDMA stat 0x24
Jul 20 10:37:18 server2 kernel: ata2.00: cmd 25/00:08:ef:07:e8/00:00:2a:00:00/e0 tag 0 dma 4096 in
Jul 20 10:37:18 server2 kernel:          res 51/40:00:f4:07:e8/40:00:2a:00:00/00 Emask 0x9 (media error)
Jul 20 10:37:18 server2 kernel: ata2.00: status: { DRDY ERR }
Jul 20 10:37:18 server2 kernel: ata2.00: error: { UNC }
Jul 20 10:37:18 server2 kernel: ata2.00: configured for UDMA/133
Anyone tell me what this means?
 
Old 07-21-2011, 01:52 AM   #2
Skillz
Member
 
Registered: Sep 2007
Posts: 252

Original Poster
Rep: Reputation: 32
Here is the output of smartctl -a -d ata /dev/sdc

Reason why I am running the tests on the third hard drive is because I believe something might be wrong with it, some of the files/directories are showing question marks under the attributes that ls -l display and I'm not able to enter them, move them, delete them unless I run a rm -Rf command under root to delete them, but that's all I could do. Only noticed two instances of this, one was a file the other was a directory.

Code:
smartctl version 5.38 [i686-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     ST3500320NS
Serial Number:    9QM0GBVF
Firmware Version: SN04
User Capacity:    500,107,862,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   6
ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 2
Local Time is:    Thu Jul 21 01:48:08 2011 CDT
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: 		 ( 634) 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: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 120) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
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   078   078   006    Pre-fail  Always       -       129084021
  3 Spin_Up_Time            0x0003   094   091   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       37
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       382
  7 Seek_Error_Rate         0x000f   075   060   030    Pre-fail  Always       -       17314205419
  9 Power_On_Hours          0x0032   072   072   000    Old_age   Always       -       25354
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       37
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       9423
188 Unknown_Attribute       0x0032   100   083   000    Old_age   Always       -       2442
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   068   058   045    Old_age   Always       -       32 (Lifetime Min/Max 29/34)
194 Temperature_Celsius     0x0022   032   042   000    Old_age   Always       -       32 (0 21 0 0)
195 Hardware_ECC_Recovered  0x001a   036   020   000    Old_age   Always       -       129084021
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       46
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       46
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 9423 (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 9423 occurred at disk power-on lifetime: 25354 hours (1056 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00   4d+17:39:15.641  READ DMA EXT
  27 00 00 00 00 00 e0 00   4d+17:39:15.641  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   4d+17:39:15.623  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00   4d+17:39:15.618  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00   4d+17:39:15.618  READ NATIVE MAX ADDRESS EXT

Error 9422 occurred at disk power-on lifetime: 25354 hours (1056 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00   4d+17:39:10.775  READ DMA EXT
  27 00 00 00 00 00 e0 00   4d+17:39:10.753  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   4d+17:39:10.736  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00   4d+17:39:10.731  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00   4d+17:39:10.731  READ NATIVE MAX ADDRESS EXT

Error 9421 occurred at disk power-on lifetime: 25354 hours (1056 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00   4d+17:39:05.893  READ DMA EXT
  27 00 00 00 00 00 e0 00   4d+17:39:05.893  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   4d+17:39:05.876  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00   4d+17:39:05.870  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00   4d+17:39:05.870  READ NATIVE MAX ADDRESS EXT

Error 9420 occurred at disk power-on lifetime: 25354 hours (1056 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00   4d+17:39:00.965  READ DMA EXT
  27 00 00 00 00 00 e0 00   4d+17:39:00.964  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   4d+17:39:00.947  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00   4d+17:39:00.943  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00   4d+17:39:00.942  READ NATIVE MAX ADDRESS EXT

Error 9419 occurred at disk power-on lifetime: 25354 hours (1056 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 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 00 08 ff ff ff ef 00   4d+17:38:56.027  READ DMA EXT
  27 00 00 00 00 00 e0 00   4d+17:38:56.026  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00   4d+17:38:56.025  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00   4d+17:38:56.020  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00   4d+17:38:56.019  READ NATIVE MAX ADDRESS EXT

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.
 
Old 07-21-2011, 05:55 AM   #3
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
Blog Entries: 2

Rep: Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886Reputation: 4886
Backup your data from that drive, if you didn't already.
Then download the manufacturers diagnosis tool and test the disk with that.
 
Old 07-21-2011, 10:29 AM   #4
Skillz
Member
 
Registered: Sep 2007
Posts: 252

Original Poster
Rep: Reputation: 32
Quote:
Originally Posted by TobiSGD View Post
Backup your data from that drive, if you didn't already.
Then download the manufacturers diagnosis tool and test the disk with that.
Well I went ahead and had the data center put in a new hard drive in the box, currently in the process of transferring the data to it right now. Once I am done, I'm gonna just have them take the drive out. If I continue to receive errors after that, I'll dig further.

Thanks for the suggestion.
 
  


Reply



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
Oh! Pretty! - and Pretty Demanding of System Resources ;) tallship Linux - General 3 06-04-2010 05:58 PM
problems installing ubuntu live cd hard drive problems! icturubyz2 Linux - Newbie 2 05-26-2009 12:07 AM
Reiser file system / Hard Disk/ Hard Drive Problems Oxyacetylene Linux - Software 4 10-10-2005 02:24 PM
Hard Drive Problems aznboi12321 Linux - Hardware 5 05-03-2005 08:27 AM
Pretty major CDROM drive issue. Nerd2 Linux - Hardware 6 05-23-2003 11:37 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 03:50 AM.

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