Results 1 to 8 of 8
  1. #1
    Join Date
    Jul 2009
    Posts
    189

    * Problem - Disk Fail or interface issue?

    I am experiencing a extremely sloooooow speed on my eSATA external drive and always I/O errors.

    So I decided to run a speed test with the tool combined in Ubuntu.

    However I was prompted the following errors:

    Error benchmarking: helper exited with exit code 1: Error reading 104857600 bytes at 104857600 from /dev/sdf when guesstimating buffer size: Input/output error
    Well I am just guessing whether it is a issue with disk or the interface (I mean, the HDD casing) or neither ones (hopefully)

    Your help is appreciated

    Thanks in advance

  2. #2
    Join Date
    May 2006
    Location
    NJ, USA
    Posts
    6,645
    sounds like dead drive
    AS395558

  3. #3
    Join Date
    Dec 2005
    Posts
    3,110
    I would also guess thats the drive.

    Are you able to pull up the smart attributes on it?

    smartctl --all /dev/sdf

    and if you want to do a short test:

    smartctl -t short /dev/sdf

  4. #4
    Join Date
    Jul 2009
    Posts
    189
    Quote Originally Posted by Dougy View Post
    sounds like dead drive
    Yes from my memory drives from dead will have a f**king low speed.


    Quote Originally Posted by PCS-Chris View Post
    I would also guess thats the drive.

    Are you able to pull up the smart attributes on it?

    smartctl --all /dev/sdf

    and if you want to do a short test:

    smartctl -t short /dev/sdf
    Ok, will try to do that now.

  5. #5
    Join Date
    Jul 2009
    Posts
    189
    well the computer cannot detect/mount the disk right now. Will reboot and try again.

  6. #6
    Join Date
    Jul 2009
    Posts
    189
    Quote Originally Posted by PCS-Chris View Post
    I would also guess thats the drive.

    Are you able to pull up the smart attributes on it?

    smartctl --all /dev/sdf

    and if you want to do a short test:

    smartctl -t short /dev/sdf
    Code:
    smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
    Home page is http://smartmontools.sourceforge.net/
    
    === START OF INFORMATION SECTION ===
    Model Family:     Seagate Barracuda 7200.10 family
    Device Model:     ST3320620AS
    Serial Number:    9QF5FAGA
    Firmware Version: 3.AAK
    User Capacity:    320,072,933,376 bytes
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   7
    ATA Standard is:  Exact ATA specification draft version not indicated
    Local Time is:    Sun Aug  1 15:28:20 2010 HKT
    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: 		 ( 430) 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: 	 ( 115) minutes.
    
    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   118   090   006    Pre-fail  Always       -       189998478
      3 Spin_Up_Time            0x0003   095   095   000    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       672
      5 Reallocated_Sector_Ct   0x0033   069   069   036    Pre-fail  Always       -       1250
      7 Seek_Error_Rate         0x000f   072   060   030    Pre-fail  Always       -       18552439
      9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       619
     10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       172
    187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
    189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
    190 Airflow_Temperature_Cel 0x0022   066   047   045    Old_age   Always       -       34 (Lifetime Min/Max 30/35)
    194 Temperature_Celsius     0x0022   034   053   000    Old_age   Always       -       34 (0 23 0 0)
    195 Hardware_ECC_Recovered  0x001a   077   060   000    Old_age   Always       -       111777687
    197 Current_Pending_Sector  0x0012   033   033   000    Old_age   Always       -       1390
    198 Offline_Uncorrectable   0x0010   033   033   000    Old_age   Offline      -       1390
    199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       7
    200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age   Offline      -       0
    202 TA_Increase_Count       0x0032   235   132   000    Old_age   Always       -       121
    
    SMART Error Log Version: 1
    ATA Error Count: 7 (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 7 occurred at disk power-on lifetime: 123 hours (5 days + 3 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
      -- -- -- -- -- -- --
      84 51 00 ee 54 2c e0  Error: ICRC, ABRT at LBA = 0x002c54ee = 2905326
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 00 ef 53 2c e0 00      00:20:37.057  READ DMA
      c8 00 00 ef 52 2c e0 00      00:20:37.140  READ DMA
      c8 00 00 ef 51 2c e0 00      00:20:37.139  READ DMA
      c8 00 00 ef 50 2c e0 00      00:20:37.133  READ DMA
      c8 00 00 ef 4f 2c e0 00      00:20:37.132  READ DMA
    
    Error 6 occurred at disk power-on lifetime: 123 hours (5 days + 3 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
      -- -- -- -- -- -- --
      84 51 af f0 4f 20 e0  Error: ICRC, ABRT 175 sectors at LBA = 0x00204ff0 = 2117616
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 00 9f 4f 20 e0 00      00:20:18.097  READ DMA
      c8 00 00 9f 4e 20 e0 00      00:20:18.096  READ DMA
      c8 00 00 9f 4d 20 e0 00      00:20:18.091  READ DMA
      c8 00 00 9f 4c 20 e0 00      00:20:18.084  READ DMA
      c8 00 00 9f 4b 20 e0 00      00:20:18.083  READ DMA
    
    Error 5 occurred at disk power-on lifetime: 123 hours (5 days + 3 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
      -- -- -- -- -- -- --
      84 51 7f 48 30 38 e0  Error: ICRC, ABRT 127 sectors at LBA = 0x00383048 = 3682376
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 00 c7 2f 38 e0 00      00:09:59.252  READ DMA
      c8 00 00 c7 2e 38 e0 00      00:09:59.348  READ DMA
      c8 00 a0 27 2e 38 e0 00      00:09:59.347  READ DMA
      c8 00 68 bf 2d 38 e0 00      00:09:59.342  READ DMA
      ca 00 08 cf 10 28 e2 00      00:09:59.333  WRITE DMA
    
    Error 4 occurred at disk power-on lifetime: 121 hours (5 days + 1 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
      -- -- -- -- -- -- --
      84 51 00 ce e7 3f e0  Error: ICRC, ABRT at LBA = 0x003fe7ce = 4188110
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 20 af e7 3f e0 00      08:12:45.759  READ DMA
      c8 00 20 8f e7 3f e0 00      08:12:45.758  READ DMA
      ca 00 08 7f e0 01 e0 00      08:12:45.758  WRITE DMA
      ca 00 18 67 e0 01 e0 00      08:12:45.758  WRITE DMA
      ca 00 08 17 98 19 e0 00      08:12:40.604  WRITE DMA
    
    Error 3 occurred at disk power-on lifetime: 32 hours (1 days + 8 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
      -- -- -- -- -- -- --
      84 51 1f e1 9f 0d e0  Error: ICRC, ABRT 31 sectors at LBA = 0x000d9fe1 = 892897
    
      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 03 80 80 9f 0d e0 00      00:19:47.639  READ DMA EXT
      25 03 80 00 9f 0d e0 00      00:19:47.637  READ DMA EXT
      25 03 80 80 9e 0d e0 00      00:19:47.636  READ DMA EXT
      25 03 80 00 9e 0d e0 00      00:19:47.634  READ DMA EXT
      25 03 80 80 9d 0d e0 00      00:19:47.633  READ DMA EXT
    
    SMART Self-test log structure revision number 1
    
    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.
    I got this.

    Seems to be disk fail.

    If I want to have all files got backed up, what is the most safe method to do that?

  7. #7
    Join Date
    Dec 2005
    Posts
    3,110
    Yes that disk is failing and needs replacing ASAP.

    I would rsync the data over, then if the drive fails you can continue if you reset it.

  8. #8
    Join Date
    Jul 2009
    Posts
    189
    Sorry if not mentioned clearly. It is a external drive running on eSATA on my notebook, thus no need to use rsync

    but is it safe to copy files over? When I am trying to copy files yesterday it has a f**king speed (~1KBps) well it may take a looooooong time to copy and are there anyways to safely copy it and prevent it from writing further?

Similar Threads

  1. Problem registering domain - Error: 2 IP authentication fail
    By e[X]treme[Z] in forum Hosting Software and Control Panels
    Replies: 0
    Last Post: 07-20-2009, 01:25 AM
  2. Crash when a single disk fail? - Adaptec 31605
    By misterd in forum Dedicated Server
    Replies: 9
    Last Post: 11-30-2007, 03:02 AM
  3. HELP! Horde & SquirrelMail fail, but NEOmail no problem
    By 0218 in forum Hosting Security and Technology
    Replies: 13
    Last Post: 09-09-2004, 11:34 AM
  4. S.M.A.R.T has detected that my disk will fail
    By DSD in forum Hosting Security and Technology
    Replies: 8
    Last Post: 07-09-2004, 10:27 PM
  5. PIR issue? ORG registrations fail
    By Acroplex in forum Domain Names
    Replies: 19
    Last Post: 01-12-2004, 07:30 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •