ntfs_attr_find: Corrupt inode (-1): Input/output error

Using TestDisk to undelete files
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
Message
Author
abiyi
Posts: 19
Joined: 12 Oct 2018, 18:50

ntfs_attr_find: Corrupt inode (-1): Input/output error

#1 Post by abiyi »

TestDisk is unable to undelete files from a faulty NTFS partition on a healthy hard drive (according to CrystalDiskInfo there are no bad sectors in it). But chkdsk has been unable to fix the error. What I need now is to understand what this TestDisk error message means to find the best solution.

Code: Select all

Using locale 'en_US.UTF-8'.


Thu Oct 29 11:42:37 2020
Command line: TestDisk /log /debug /dev/sdb

TestDisk 7.2-WIP, Data Recovery Utility, October 2020
Christophe GRENIER <grenier@cgsecurity.org>
https://www.cgsecurity.org
OS: Linux, kernel 5.6.0-0.bpo.2-amd64 (#1 SMP Debian 5.6.14-2~bpo10+1 (2020-06-09)) x86_64
Compiler: GCC 8.3
Compilation date: 2020-10-19T02:22:42
ext2fs lib: 1.45.5, ntfs lib: libntfs-3g, reiserfs lib: none, ewf lib: 20140804, curses lib: ncurses 6.1
ntfs_mst_post_read_fixup_warn: magic: 0xa42ffb30  size: 1024   usa_ofs: 37503  usa_count: 38646: Invalid argument
ntfs_attr_find: Corrupt inode (-1): Input/output error
ntfs_attr_find: Corrupt inode (-1): Input/output error
ntfs_attr_find: Corrupt inode (-1): Input/output error
ntfs_attr_find: Corrupt inode (-1): Input/output error
ntfs_attr_find: Corrupt inode (-1): Input/output error
ntfs_mst_post_read_fixup_warn: magic: 0xbd8332b4  size: 1024   usa_ofs: 14052  usa_count: 56545: Invalid argument
ntfs_attr_find: Corrupt inode (-1): Input/output error
ntfs_attr_find: Corrupt inode (-1): Input/output error
ntfs_attr_find: Corrupt inode (-1): Input/output error
ntfs_attr_find: Corrupt inode (-1): Input/output error
ntfs_attr_find: Corrupt inode (-1): Input/output error
ntfs_mst_post_read_fixup_warn: magic: 0x545eb0bf  size: 1024   usa_ofs: 30412  usa_count: 22619: Invalid argument
The partition is now empty, so I moved all the files to another partition (EXT4 instead NTFS) in the same hard drive, but in Windows 7 chkdsk finished the process stuck into an error message print loop: "Error in writing the output log". Now the partition is displayed as full (but without any visible files).

I've read about similar cases, but the solution seems to be format the partition, which I don't want to do now.

Can anybody explain me that?

Sponsored links

recuperation
Posts: 953
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: ntfs_attr_find: Corrupt inode (-1): Input/output error

#2 Post by recuperation »

abiyi wrote:
29 Oct 2020, 18:00
TestDisk is unable to undelete files from a faulty NTFS partition on a healthy hard drive (according to CrystalDiskInfo there are no bad sectors in it).
The conclusion is wrong. It is as wrong as thinking that a "no virus found" message from your antivirus program means that there are no viruses. SMART data is only a snapshot based on limited information. Even if you are telling the truth, there could be many broken sectors. But SMART would not know unless those sectors would happen to be read.
As for diagnostic data I only believe in proofs. You did not deliver one. But I would prefer a log file from smartmontools over a picture from CrystaldiskInfo.

But chkdsk has been unable to fix the error. What I need now is to understand what this TestDisk error message means to find the best solution.
The message suggests that there are read errors.
The solution is to duplicate the drive using ddrescue as described in the manual.

abiyi
Posts: 19
Joined: 12 Oct 2018, 18:50

Re: ntfs_attr_find: Corrupt inode (-1): Input/output error

#3 Post by abiyi »

But I would prefer a log file from smartmontools over a picture from CrystaldiskInfo.
I didn't deliver a smartclt report in the post because I hadn't been able to get one from the hard drive through a JMicron SATA bridge (Samsung Story Station). Yesterday I finally found the solution in a forum (the device option did the trick):

Code: Select all

smartctl --xall --device=sat /dev/sdb
So, the full SMART report of the hard drive is this:

Code: Select all

smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.6.0-0.bpo.2-amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST3000DM001-9YN166
Serial Number:    Z1F0QPXA
LU WWN Device Id: 5 000c50 04d9b8f9b
Firmware Version: CC4B
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is:    Thu Oct 29 17:17:49 2020 -04

==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/223651en

SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     128 (minimum power consumption without standby)
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Unavailable

=== 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:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
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: 		(  575) seconds.
Offline data collection
capabilities: 			 (0x73) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No 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: 	 ( 334) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x3085)	SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR--   108   089   006    -    18080888
  3 Spin_Up_Time            PO----   092   090   000    -    0
  4 Start_Stop_Count        -O--CK   097   097   020    -    3734
  5 Reallocated_Sector_Ct   PO--CK   100   100   036    -    0
  7 Seek_Error_Rate         POSR--   084   060   030    -    317151894
  9 Power_On_Hours          -O--CK   082   082   000    -    15814
 10 Spin_Retry_Count        PO--C-   100   100   097    -    0
 12 Power_Cycle_Count       -O--CK   098   098   020    -    2645
183 Runtime_Bad_Block       -O--CK   100   100   000    -    0
184 End-to-End_Error        -O--CK   100   100   099    -    0
187 Reported_Uncorrect      -O--CK   001   001   000    -    2841
188 Command_Timeout         -O--CK   100   099   000    -    2 2 12
189 High_Fly_Writes         -O-RCK   070   070   000    -    30
190 Airflow_Temperature_Cel -O---K   059   039   045    Past 41 (Min/Max 40/41 #1949)
191 G-Sense_Error_Rate      -O--CK   100   100   000    -    0
192 Power-Off_Retract_Count -O--CK   100   100   000    -    906
193 Load_Cycle_Count        -O--CK   068   068   000    -    64364
194 Temperature_Celsius     -O---K   041   061   000    -    41 (0 21 0 0 0)
197 Current_Pending_Sector  -O--C-   100   099   000    -    0
198 Offline_Uncorrectable   ----C-   100   099   000    -    0
199 UDMA_CRC_Error_Count    -OSRCK   200   200   000    -    0
240 Head_Flying_Hours       ------   100   253   000    -    13398h+04m+46.565s
241 Total_LBAs_Written      ------   100   253   000    -    93693822017778
242 Total_LBAs_Read         ------   100   253   000    -    2135216861925
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      5  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x21       GPL     R/O      1  Write stream error log
0x22       GPL     R/O      1  Read stream error log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa1       GPL,SL  VS      20  Device vendor specific log
0xa2       GPL     VS    4496  Device vendor specific log
0xa8       GPL,SL  VS      20  Device vendor specific log
0xa9       GPL,SL  VS       1  Device vendor specific log
0xab       GPL     VS       1  Device vendor specific log
0xb0       GPL     VS    5067  Device vendor specific log
0xbd       GPL     VS     512  Device vendor specific log
0xbe-0xbf  GPL     VS   65535  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 2830 (device log contains only the most recent 20 errors)
	CR     = Command Register
	FEATR  = Features Register
	COUNT  = Count (was: Sector Count) Register
	LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
	LH     = LBA High (was: Cylinder High) Register    ]   LBA
	LM     = LBA Mid (was: Cylinder Low) Register      ] Register
	LL     = LBA Low (was: Sector Number) Register     ]
	DV     = Device (was: Device/Head) Register
	DC     = Device Control Register
	ER     = Error register
	ST     = Status register
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 2830 [9] occurred at disk power-on lifetime: 13704 hours (571 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 36 99 19 f8 00 00  Error: UNC at LBA = 0x369919f8 = 916003320

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 01 00 00 00 36 99 1a c0 40 00     01:00:41.518  READ FPDMA QUEUED
  60 00 00 01 00 00 00 36 99 19 c0 40 00     01:00:41.517  READ FPDMA QUEUED
  60 00 00 01 00 00 00 36 99 18 c0 40 00     01:00:41.517  READ FPDMA QUEUED
  60 00 00 01 00 00 00 36 99 17 c0 40 00     01:00:41.516  READ FPDMA QUEUED
  60 00 00 01 00 00 00 36 99 16 c0 40 00     01:00:41.516  READ FPDMA QUEUED

Error 2829 [8] occurred at disk power-on lifetime: 13702 hours (570 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 1a 37 c6 80 00 00  Error: UNC at LBA = 0x1a37c680 = 439862912

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 1a 38 e1 28 40 00     13:10:05.722  READ FPDMA QUEUED
  60 00 00 01 00 00 00 1a 37 c6 80 40 00     13:10:05.722  READ FPDMA QUEUED
  60 00 00 01 00 00 00 1a 37 c5 80 40 00     13:10:05.721  READ FPDMA QUEUED
  60 00 00 00 f8 00 00 1a 37 c4 88 40 00     13:10:05.704  READ FPDMA QUEUED
  60 00 00 01 00 00 00 11 ba 17 40 40 00     13:10:05.568  READ FPDMA QUEUED

Error 2828 [7] occurred at disk power-on lifetime: 13702 hours (570 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 32 bc 38 88 00 00  Error: UNC at LBA = 0x32bc3888 = 851196040

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 01 00 00 00 32 bc 39 80 40 00     13:09:56.353  READ FPDMA QUEUED
  60 00 00 01 00 00 00 32 bc 38 80 40 00     13:09:56.352  READ FPDMA QUEUED
  60 00 00 01 00 00 00 32 bc 37 80 40 00     13:09:56.351  READ FPDMA QUEUED
  60 00 00 01 00 00 00 32 bc 1e 80 40 00     13:09:56.295  READ FPDMA QUEUED
  60 00 00 01 00 00 00 32 bc 1d 80 40 00     13:09:56.285  READ FPDMA QUEUED

Error 2827 [6] occurred at disk power-on lifetime: 13699 hours (570 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 1a 37 c6 80 00 00  Error: UNC at LBA = 0x1a37c680 = 439862912

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 00 08 00 00 1a 38 e1 28 40 00     10:23:18.860  READ FPDMA QUEUED
  60 00 00 01 00 00 00 1a 37 c6 80 40 00     10:23:18.860  READ FPDMA QUEUED
  60 00 00 01 00 00 00 1a 37 c5 80 40 00     10:23:18.859  READ FPDMA QUEUED
  60 00 00 00 f8 00 00 1a 37 c4 88 40 00     10:23:18.846  READ FPDMA QUEUED
  60 00 00 01 00 00 00 11 ba 17 40 40 00     10:23:18.769  READ FPDMA QUEUED

Error 2826 [5] occurred at disk power-on lifetime: 13699 hours (570 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 32 bc 38 88 00 00  Error: UNC at LBA = 0x32bc3888 = 851196040

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 01 00 00 00 32 bc 39 80 40 00     10:23:14.279  READ FPDMA QUEUED
  60 00 00 01 00 00 00 32 bc 38 80 40 00     10:23:14.278  READ FPDMA QUEUED
  60 00 00 01 00 00 00 32 bc 37 80 40 00     10:23:14.275  READ FPDMA QUEUED
  60 00 00 01 00 00 00 32 bc 36 80 40 00     10:23:14.275  READ FPDMA QUEUED
  60 00 00 01 00 00 00 32 bc 35 80 40 00     10:23:14.273  READ FPDMA QUEUED

Error 2825 [4] occurred at disk power-on lifetime: 13697 hours (570 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 2f 96 e8 c0 00 00  Error: UNC at LBA = 0x2f96e8c0 = 798419136

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 01 00 00 00 2f 96 e8 98 40 00     08:26:21.761  READ FPDMA QUEUED
  60 00 00 01 00 00 00 2f 96 e7 98 40 00     08:26:21.760  READ FPDMA QUEUED
  60 00 00 01 00 00 00 2f 96 e6 98 40 00     08:26:21.759  READ FPDMA QUEUED
  60 00 00 01 00 00 00 2f 96 e5 98 40 00     08:26:21.759  READ FPDMA QUEUED
  60 00 00 01 00 00 00 2f 96 e4 98 40 00     08:26:21.756  READ FPDMA QUEUED

Error 2824 [3] occurred at disk power-on lifetime: 13694 hours (570 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 01 f4 16 80 00 00  Error: UNC at LBA = 0x01f41680 = 32773760

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 01 00 00 00 6e 9d 74 d0 40 00     05:15:44.504  READ FPDMA QUEUED
  60 00 00 01 00 00 00 6e 9d 73 d0 40 00     05:15:44.501  READ FPDMA QUEUED
  60 00 00 01 00 00 00 6e 9d 72 d0 40 00     05:15:44.501  READ FPDMA QUEUED
  60 00 00 01 00 00 00 6e 9d 71 d0 40 00     05:15:44.500  READ FPDMA QUEUED
  60 00 00 01 00 00 00 6e 9d 70 d0 40 00     05:15:44.490  READ FPDMA QUEUED

Error 2823 [2] occurred at disk power-on lifetime: 13691 hours (570 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 00 00 00 1a 37 c6 80 00 00  Error: UNC at LBA = 0x1a37c680 = 439862912

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 00 01 00 00 00 6c e5 84 18 40 00     02:07:45.609  READ FPDMA QUEUED
  60 00 00 01 00 00 00 6c e5 83 18 40 00     02:07:45.609  READ FPDMA QUEUED
  60 00 00 00 08 00 00 1a 38 e1 28 40 00     02:07:45.595  READ FPDMA QUEUED
  60 00 00 01 00 00 00 1a 37 c6 80 40 00     02:07:45.595  READ FPDMA QUEUED
  60 00 00 01 00 00 00 6c e5 82 18 40 00     02:07:45.583  READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     15491         -

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.

SCT Status Version:                  3
SCT Version (vendor specific):       522 (0x020a)
Device State:                        Active (0)
Current Temperature:                    40 Celsius
Power Cycle Min/Max Temperature:     40/40 Celsius
Lifetime    Min/Max Temperature:     21/61 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Data Table command not supported

SCT Error Recovery Control command not supported

Device Statistics (GP/SMART Log 0x04) not supported

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x000a  2            1  Device-to-host register FISes sent due to a COMRESET
0x0001  2            0  Command failed due to ICRC error
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
The solution is to duplicate the drive using ddrescue as described in the manual.
Cloning the partition with ddrescue didn't work: the cloned NTFS partition displays the same errors in chkdsk ("Error in writing the output log") and TestDisk.

Code: Select all

ddrescue \
-vv \
--force \
--no-scrape \
/dev/sdb8 \
/dev/sdb1 \
/root/ddrescue_windows7.log ;
The cloning was done in the same hard drive, I can try with another disk but its integrity is no the best (I replaced it some months ago), the rest are probably in the same estate. If it doesn't work, nothing will.

recuperation
Posts: 953
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: ntfs_attr_find: Corrupt inode (-1): Input/output error

#4 Post by recuperation »

abiyi wrote:
30 Oct 2020, 20:37

Cloning the partition with ddrescue didn't work: the cloned NTFS partition displays the same errors in chkdsk ("Error in writing the output log") and TestDisk.

Code: Select all

ddrescue \
-vv \
--force \
--no-scrape \
/dev/sdb8 \
/dev/sdb1 \
/root/ddrescue_windows7.log ;
The cloning was done in the same hard drive, I can try with another disk but its integrity is no the best (I replaced it some months ago), the rest are probably in the same estate. If it doesn't work, nothing will.
I don't know what the backslash are standing for above.
"The cloning was done in the same hard drive" contradicts the content of your ddrescue command.
It appears strange that you are trying to write the loog on root level where you might not have rights to write.

Raw read error rate and seek error rate suggest that you have a problem.
It appears as if you have already written 47000 TB to the drive - is that correct?

abiyi
Posts: 19
Joined: 12 Oct 2018, 18:50

Re: ntfs_attr_find: Corrupt inode (-1): Input/output error

#5 Post by abiyi »

I don't know what the backslash are standing for above.
I like to put every command option in a separate line for easy reading, that's all.
"The cloning was done in the same hard drive" contradicts the content of your ddrescue command.
why is that?
It appears strange that you are trying to write the loog on root level where you might not have rights to write.
I don't see why. ddrescue was running with root rights, as always does. The logs of testdisk, ddrescue, and smartctl are being written in the root directory. Always.
Raw read error rate and seek error rate suggest that you have a problem.
those are pre-fail errors, still into its respective threshold.
It appears as if you have already written 47000 TB to the drive - is that correct?
I'm looking for that value in the SMART report but I can't find it.

abiyi
Posts: 19
Joined: 12 Oct 2018, 18:50

Re: ntfs_attr_find: Corrupt inode (-1): Input/output error

#6 Post by abiyi »

I did run ntfsresize getting a lot of error message about clusters:

Code: Select all

# ntfsresize --info --force --verbose /dev/sdc8
.
.
.
Cluster accounting failed at 133119996 (0x7ef3ffc): extra cluster in $Bitmap
Cluster accounting failed at 133119997 (0x7ef3ffd): extra cluster in $Bitmap
Cluster accounting failed at 133119998 (0x7ef3ffe): extra cluster in $Bitmap
Filesystem check failed! Totally 132719464 cluster accounting mismatches.
ERROR: NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
The usage of the /f parameter is very IMPORTANT! No modification was
and will be made to NTFS by this software until it gets repaired.
Then, I did run

Code: Select all

chkdsk f: /f
without any other option, on the partition and no bad block was reported. The issue is still not having enough space for log file (the error message is not displayed in the screenshot, it's difficult to capture the screen with those messages rolling on).

I'm not sure why the NTFS partition have those errors, but I'm sure it's not caused by a physical damage. The hard drive is healthy, doesn't have bad sectors, had bad clusters and some metadata corruption.

The only EXT4 partition in the same hard drive is perfectly fine:

Code: Select all

# badblocks -sv -c 512 -o badsectors_sdc2.txt /dev/sdc2
Checking blocks 0 to 492636159
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)
My best guess is those were "heritage" from another damaged hard drive where the data were before, a drive probably dead by now, and then got worst because a laptop hang-up while gigabytes of files were being moved from that NTFS partition to an EXT4 partition.
Attachments
chkdsk4.png
chkdsk4.png (78.09 KiB) Viewed 485 times

recuperation
Posts: 953
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: ntfs_attr_find: Corrupt inode (-1): Input/output error

#7 Post by recuperation »

abiyi wrote:
08 Nov 2020, 21:36
I don't know what the backslash are standing for above.
I like to put every command option in a separate line for easy reading, that's all.
"The cloning was done in the same hard drive" contradicts the content of your ddrescue command.
why is that?
Sorry, that statement of me is wrong. It rather should say:
"The cloning was done in the same hard drive" contradicts the idea of using ddrescue.
It appears as if you have already written 47000 TB to the drive - is that correct?
I'm looking for that value in the SMART report but I can't find it.

Code: Select all

241 Total_LBAs_Written      ------   100   253   000    -    93693822017778
242 Total_LBAs_Read         ------   100   253   000    -    2135216861925
             
       
93693822017778=>

47 Petabyte or 47 000 Terabyte is a lot - if I calculated correctly.

abiyi
Posts: 19
Joined: 12 Oct 2018, 18:50

Re: ntfs_attr_find: Corrupt inode (-1): Input/output error

#8 Post by abiyi »

The cloning was done in the same hard drive" contradicts the idea of using ddrescue.
I get your point, but I'm assuming the hard drive is healthy, just the FAT (that's my guess) of one partition is damaged. The damage is logical, not physical (according to its SMART report).
47 Petabyte or 47 000 Terabyte is a lot - if I calculated correctly.
I used that hard drive to save 2 TB of recovered files from another hard drive... many, many times.

recuperation
Posts: 953
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: ntfs_attr_find: Corrupt inode (-1): Input/output error

#9 Post by recuperation »

abiyi wrote:
09 Nov 2020, 22:41
The cloning was done in the same hard drive" contradicts the idea of using ddrescue.
I get your point, but I'm assuming the hard drive is healthy, just the FAT (that's my guess) of one partition is damaged. The damage is logical, not physical (according to its SMART report).
A NTFS file system has no FAT.
I've read about similar cases, but the solution seems to be format the partition, which I don't want to do now.
As for your questions, I don't know why your drive is misbehaving. It is little surprising that you are refraining from formating or zeroing an empty partition. :roll:

abiyi
Posts: 19
Joined: 12 Oct 2018, 18:50

Re: ntfs_attr_find: Corrupt inode (-1): Input/output error

#10 Post by abiyi »

A NTFS file system has no FAT.
yes, I must have been thinking of another hard drive with FAT32 partition.
As for your questions, I don't know why your drive is misbehaving. It is little surprising that you are refraining from formating or zeroing an empty partition.
Probably I messed up my explanation. I tried to explain that in my first post.

That empty NTFS partition must have a lot of files that were moving to an EXT4 when the laptop hung-up. Many files are safe now, but another lot is missing. I was able to undelete a lot of files from a second NTFS partition, but from this one has been impossible due to the error you already saw.

I want to see a list of deleted files and look for missing files. That's it.

I deleted a couple of partitions in the same hard drive to find bad sectors. Everything's fine.

Post Reply