Page 1 of 3 123 LastLast
Results 1 to 10 of 40

Thread: Files with I/O Errors preventing access to full folders?

Hybrid View

  1. #1
    Join Date
    Feb 2013
    Beans
    24

    Question Files with I/O Errors preventing access to full folders?

    So I just recently had my computer's harddrive crap out on me in the process of trying to relocate my files to an external harddrive. Since i cannot boot Win 7 from my HDD, I'm using Xubuntu 12.10 from a CD to boot.

    When trying to move my files to an external hard drive, i receive the error "Error when getting information for file '/media/...xxx.mp3' (or whatever the file happens to be) and it's detailed as an "Input/output error."

    There's no doubt that this is due to bad sectors on the disk. When commanding dmesg, i receive:

    Code:
    end_request: I/O error, dev sda, sector 50748707
    Buffer I/O error on device sda3, logical block 2493348
    ata1: EH complete
    Thing is, these bad sectors are also preventing me from opening folders. If i try to open a folder with a bad document directly in it (not in a subfolder), an error message displays "Failed to open directory "Folder" and it's because of the bad file.

    I need a way to get into these folders to transfer all the files that aren't effected by the bad sectors. My second goal is to repair the damaged files if necessary.

    I've already created and saved a 278GB image.dd using Testdisk onto my 1TB external. I was told i could go back to this if anything were to go wrong when trying to repair the original files. However, after completing the image, i received:

    Code:
    Image created successfully but read errors have occurred.
    What are the next steps i should take? The only thing i can think of is running a chkdsk on the original harddrive, but i'm still hesitant as to how to go about doing this.

    If there's anymore information you need, let me know. My vocabulary with this stuff is pretty limited.

  2. #2
    Join Date
    Feb 2012
    Location
    el_GR
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Files with I/O Errors preventing access to full folders?

    So this is a NTFS filesystem partition, correct ? A Windows partition. Well, would be better to run chkdsk from a Windows machine to correct the NTFS filesystem.

    Also a Linux utility exist to correct NTFS filesystems , but I would be trust more the MS tool for such job. But if you want to try, the utility's name is ntfs-3g.
    Code:
    sudo apt-get install ntfs-3g 
    sudo ntfsfix /dev/sd??
    Where ? , replace it with the drive letter and partition letter. (e.g /dev/sda2)

    You can find drive letter and partition letter with
    Code:
    sudo fdisk -l
    you will see the HPFS/NTFS filesystem.

    Again, better would be to boot from a Windows CD/DVD and try to correct the filesytem with chkdsk .

    Thanks

  3. #3
    Join Date
    Aug 2005
    Beans
    6,024

    Re: Files with I/O Errors preventing access to full folders?

    Quote Originally Posted by NikTh View Post
    So this is a NTFS filesystem partition, correct ? A Windows partition. Well, would be better to run chkdsk from a Windows machine to correct the NTFS filesystem.
    Do NOT run chkdsk on a drive with bad sectors, it will just make things worse.

  4. #4
    Join Date
    Feb 2013
    Beans
    24

    Re: Files with I/O Errors preventing access to full folders?

    Quote Originally Posted by mips View Post
    Do NOT run chkdsk on a drive with bad sectors, it will just make things worse.
    That's what i've heard, which is why i'm trying to be cautious and also made the image.dd in advance.
    What do you recommend i do in order to access and transfer the GOOD files from the folders that refuse to open?

  5. #5
    Join Date
    Mar 2010
    Location
    India
    Beans
    8,149
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Files with I/O Errors preventing access to full folders?

    Quote Originally Posted by SineSpe View Post
    That's what i've heard, which is why i'm trying to be cautious and also made the image.dd in advance.
    What do you recommend i do in order to access and transfer the GOOD files from the folders that refuse to open?
    I would recommend to run photorec on the saved image file to salvage whatever files were accessible (possibly ignoring filesystem errors) at the time you created the image. If the state of the physical drive is not getting worse with every use (that is, the errors are not due to physical wear & tear), you should be good to do it on the drive itself. But in case of doubts, I'd recommend to work on the image.

    Using photorec or testdisk on the image file is a read-only operation, so it will not affect the image. It is as easy as using them on the physical drive. So go with whatever you prefer.

    If using image, I *think the appropriate command will be -
    Code:
    sudo photorec <path to your image.dd>
    Photorec step-by-step : http://www.cgsecurity.org/wiki/PhotoRec_Step_By_Step
    Varun
    Help others by marking threads as [SOLVED], if they are. (See how)
    Wireless Script | Use Code Tags

  6. #6
    Join Date
    Feb 2013
    Beans
    24

    Re: Files with I/O Errors preventing access to full folders?

    I downloaded Testdisk and Photorec to my new computer with Windows 7 and am trying to read it from there. When running, i receive:

    Code:
    Select a media <use Arrow keys, then press Enter>:
    >Disk /dev/sda - 1000GB / 931 GiB <RO> - TOSHIBA
    
    >[Proceed] [Quit]
    I click proceed, and this is where the step-by-step somewhat loses me. I receive:

    Code:
     Partition                  Start        End    Size in sectors
      No partition             0   0  1 121601  80 63 1953525168 [Whole disk]
    * HPFS - NTFS              0  32 33    25 126 37     407552 [SYSTEM]
    P HPFS - NTFS             25 126 38 118858  49 39 1909047296
    P HPFS - NTFS          118858  49 40 121588  24 36   43855872 [Recovery]
    P FAT32 LBA            121588  24 37 121601  25 24     208896 [HP_TOOLS]
    
    >[Search] [Options] [File Opt] [Quit]
    My image.dd file is no longer on my external harddrive, and now in a folder on this new computer's internal. What are the next steps I should take?
    Last edited by SineSpe; June 18th, 2013 at 06:50 PM.

  7. #7
    Join Date
    Aug 2005
    Beans
    6,024

    Re: Files with I/O Errors preventing access to full folders?

    Quote Originally Posted by SineSpe View Post
    That's what i've heard, which is why i'm trying to be cautious and also made the image.dd in advance.
    What do you recommend i do in order to access and transfer the GOOD files from the folders that refuse to open?
    Some things might already not be possible to recover.

    Create an image file of the drive or partition using GNU ddrescue and ensure you enable the log file. Once you have an image you can mount it and try to recover from it. You can also use tools like testdisk/photorec on the image.

    You can also have a look at https://help.ubuntu.com/community/DataRecovery

    Do me a favour and post the S.M.A.R.T. info for the drive here, you can get that info using the smartctl command or you can use a gui called GSmartControl.

  8. #8
    Join Date
    Feb 2013
    Beans
    24

    Re: Files with I/O Errors preventing access to full folders?

    So right now, i believe Photorec is running. I've attached a screenshot of that progress to this post.

    Quote Originally Posted by mips View Post
    Some things might already not be possible to recover.

    Create an image file of the drive or partition using GNU ddrescue and ensure you enable the log file. Once you have an image you can mount it and try to recover from it. You can also use tools like testdisk/photorec on the image.

    You can also have a look at https://help.ubuntu.com/community/DataRecovery

    Do me a favour and post the S.M.A.R.T. info for the drive here, you can get that info using the smartctl command or you can use a gui called GSmartControl.
    This is the SMART information i received by commanding sudo smartctl --all /dev/sda3 :

    Code:
    xubuntu@xubuntu:~/Desktop$ sudo smartctl --all /dev/sda3
    smartctl 5.43 2012-06-30 r3573 [i686-linux-3.5.0-17-generic] (local build)
    Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
    
    === START OF INFORMATION SECTION ===
    Model Family:     Seagate Momentus 5400.6
    Device Model:     ST9320325AS
    Serial Number:    5VD1X5P9
    LU WWN Device Id: 5 000c50 0217228f7
    Firmware Version: 0003DEM1
    User Capacity:    320,072,933,376 bytes [320 GB]
    Sector Size:      512 bytes logical/physical
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   8
    ATA Standard is:  ATA-8-ACS revision 4
    Local Time is:    Tue Jun 18 22:56:16 2013 UTC
    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
    See vendor-specific Attribute list for marginal Attributes.
    
    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:         (    0) 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:      (  99) minutes.
    Conveyance self-test routine
    recommended polling time:      (   3) minutes.
    SCT capabilities:            (0x103f)    SCT Status supported.
                        SCT Error Recovery Control 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   110   074   006    Pre-fail  Always       -       27781091
      3 Spin_Up_Time            0x0003   099   097   085    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   097   097   020    Old_age   Always       -       3277
      5 Reallocated_Sector_Ct   0x0033   089   089   036    Pre-fail  Always       -       243
      7 Seek_Error_Rate         0x000f   081   060   030    Pre-fail  Always       -       4459252319
      9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       6607
     10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   097   097   020    Old_age   Always       -       3175
    184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
    187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       65535
    188 Command_Timeout         0x0032   100   001   000    Old_age   Always       -       17180199630
    189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
    190 Airflow_Temperature_Cel 0x0022   059   037   045    Old_age   Always   In_the_past 41 (0 255 42 25 0)
    191 G-Sense_Error_Rate      0x0032   098   098   000    Old_age   Always       -       4097
    192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       5
    193 Load_Cycle_Count        0x0032   075   075   000    Old_age   Always       -       50757
    194 Temperature_Celsius     0x0022   041   063   000    Old_age   Always       -       41 (0 9 0 0 0)
    195 Hardware_ECC_Recovered  0x001a   050   045   000    Old_age   Always       -       27781091
    197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       423
    198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       423
    199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       3
    240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       224558070110496
    241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       3087503864
    242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       2345006459
    254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       0
    
    SMART Error Log Version: 1
    ATA Error Count: 3280 (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 3280 occurred at disk power-on lifetime: 6591 hours (274 days + 15 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
      -- -- -- -- -- -- -- --  ----------------  --------------------
      60 00 08 ff ff ff 4f 00      05:40:41.201  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:41.193  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:41.179  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:41.169  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:41.158  READ FPDMA QUEUED
    
    Error 3279 occurred at disk power-on lifetime: 6591 hours (274 days + 15 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
      -- -- -- -- -- -- -- --  ----------------  --------------------
      60 00 08 ff ff ff 4f 00      05:40:22.878  READ FPDMA QUEUED
      27 00 00 00 00 00 e0 00      05:40:22.876  READ NATIVE MAX ADDRESS EXT
      ec 00 00 00 00 00 a0 00      05:40:22.875  IDENTIFY DEVICE
      ef 03 46 00 00 00 a0 00      05:40:22.874  SET FEATURES [Set transfer mode]
      27 00 00 00 00 00 e0 00      05:40:22.874  READ NATIVE MAX ADDRESS EXT
    
    Error 3278 occurred at disk power-on lifetime: 6591 hours (274 days + 15 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
      -- -- -- -- -- -- -- --  ----------------  --------------------
      60 00 08 ff ff ff 4f 00      05:40:19.848  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:19.485  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:19.464  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:19.464  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:19.067  READ FPDMA QUEUED
    
    Error 3277 occurred at disk power-on lifetime: 6591 hours (274 days + 15 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
      -- -- -- -- -- -- -- --  ----------------  --------------------
      60 00 08 ff ff ff 4f 00      05:40:00.205  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:00.183  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:00.162  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:00.139  READ FPDMA QUEUED
      60 00 08 ff ff ff 4f 00      05:40:00.117  READ FPDMA QUEUED
    
    Error 3276 occurred at disk power-on lifetime: 6591 hours (274 days + 15 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
      -- -- -- -- -- -- -- --  ----------------  --------------------
      60 00 08 ff ff ff 4f 00      05:39:54.112  READ FPDMA QUEUED
      27 00 00 00 00 00 e0 00      05:39:54.111  READ NATIVE MAX ADDRESS EXT
      ec 00 00 00 00 00 a0 00      05:39:54.110  IDENTIFY DEVICE
      ef 03 46 00 00 00 a0 00      05:39:54.109  SET FEATURES [Set transfer mode]
      27 00 00 00 00 00 e0 00      05:39:54.109  READ NATIVE MAX ADDRESS EXT
    
    SMART Self-test log structure revision number 1
    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Short offline       Completed: read failure       90%      6564         50765010
    # 2  Short offline       Completed without error       00%      5051         -
    # 3  Short offline       Completed without error       00%      4914         -
    # 4  Short offline       Completed without error       00%      4761         -
    # 5  Short offline       Completed without error       00%      4321         -
    # 6  Short offline       Completed without error       00%      4232         -
    # 7  Short offline       Completed without error       00%      4070         -
    # 8  Short offline       Completed without error       00%      3890         -
    # 9  Short offline       Completed without error       00%      3698         -
    #10  Short offline       Completed without error       00%      3454         -
    #11  Short offline       Completed without error       00%      3199         -
    #12  Short offline       Completed without error       00%      3157         -
    #13  Short offline       Completed without error       00%      3125         -
    #14  Short offline       Completed without error       00%      2947         -
    #15  Short offline       Completed without error       00%      2730         -
    #16  Short offline       Aborted by host               60%      2558         -
    #17  Short offline       Completed without error       00%      2164         -
    #18  Short offline       Aborted by host               90%      2164         -
    #19  Short offline       Completed without error       00%      1909         -
    #20  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.
    Attached Images Attached Images
    Last edited by SineSpe; June 19th, 2013 at 12:02 AM.

  9. #9
    Join Date
    Feb 2012
    Location
    el_GR
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Files with I/O Errors preventing access to full folders?

    Quote Originally Posted by mips View Post
    Do NOT run chkdsk on a drive with bad sectors, it will just make things worse.
    LoL..

    and what you suggest?

    I know only chkdsk as a powerful tool and the one (MS official) to correct such errors. I've ran it twice. Well, the truth is that the first time (external HDD) I've lost all of my files. The second time though (internal HDD), everything went well and the problems have been corrected properly.

  10. #10
    Join Date
    Feb 2013
    Beans
    24

    Re: Files with I/O Errors preventing access to full folders?

    Now i do have a Windows 7 reinstallation disc, but when i try to boot from it, it goes to the process of installing Windows. Is there anyway i can simply boot from this disc without reinstalling? It's necessary for me to boot from a disc or something other than my harddrive because the system will run too slowly working from my harddrive.

    I'd much rather use chkdsk, because i've read that ntfs-3g might not be able to get everything that chkdsk would.
    Last edited by SineSpe; June 14th, 2013 at 09:57 PM.

Page 1 of 3 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

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