Input/output error from the log, do I need to continue to run the tool?

Using TestDisk to repair the filesystem
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
Locked
Message
Author
bdonglobal
Posts: 4
Joined: 05 Sep 2023, 01:16

Input/output error from the log, do I need to continue to run the tool?

#1 Post by bdonglobal »

when I use testdisk to do deep search, I got a very slow speed, meantime, I got many Input/Output error from testdisk.log. What does this mean? should I continue?

Code: Select all

file_pread(17,1,buffer,5063394616(632924327/0/1)) read err: Input/output error
file_pread(17,16,buffer,5063394665(632924333/0/2)) read err: Partial read
file_pread(17,16,buffer,5063394681(632924335/0/2)) read err: Input/output error
file_pread(17,1,buffer,5063394681(632924335/0/2)) read err: Input/output error
file_pread(17,1,buffer,5063394682(632924335/0/3)) read err: Input/output error
file_pread(17,1,buffer,5063394683(632924335/0/4)) read err: Input/output error
file_pread(17,16,buffer,5063394684(632924335/1/1)) read err: Input/output error
file_pread(17,1,buffer,5063394684(632924335/1/1)) read err: Input/output error
file_pread(17,16,buffer,5063394685(632924335/1/2)) read err: Input/output error
file_pread(17,1,buffer,5063394685(632924335/1/2)) read err: Input/output error
file_pread(17,16,buffer,5063394686(632924335/1/3)) read err: Input/output error
file_pread(17,1,buffer,5063394686(632924335/1/3)) read err: Input/output error
file_pread(17,16,buffer,5063394687(632924335/1/4)) read err: Input/output error
file_pread(17,1,buffer,5063394687(632924335/1/4)) read err: Input/output error
file_pread(17,16,buffer,5063393077(632924134/1/2)) read err: Partial read
file_pread(17,16,buffer,5063393093(632924136/1/2)) read err: Input/output error
file_pread(17,1,buffer,5063393093(632924136/1/2)) read err: Input/output error
file_pread(17,16,buffer,5063393094(632924136/1/3)) read err: Input/output error
file_pread(17,1,buffer,5063393094(632924136/1/3)) read err: Input/output error
file_pread(17,16,buffer,5063393095(632924136/1/4)) read err: Input/output error
file_pread(17,1,buffer,5063393095(632924136/1/4)) read err: Input/output error
file_pread(17,16,buffer,5063393088(632924136/0/1)) read err: Input/output error
file_pread(17,1,buffer,5063393088(632924136/0/1)) read err: Input/output error
file_pread(17,16,buffer,5063393089(632924136/0/2)) read err: Input/output error
my hard disk is RAID0, 12 hard disks, and 43T in total.
the reason to use testdisk is: yesterday I got Input/Output error when using 'ls' command in Ubuntu. and then I reboot the machine as usual by "reboot" command. after the machine booted, the 43T hard disk cannot be mount successfully. Then I use xfs_repair to repair it, but get "bad primary superblock...........cannot find second superblock........". Then I search the network and found testdisk.

Now the tool is still running and very slow, the result is ,

Code: Select all

Disk /dev/md126 - 48 TB / 43 TiB - CHS 11719409664 2 4                                                                                                                 
Analyse cylinder 623833295/3129475071: 05%                                                                                                                             
Read error at 620899776/0/1 (lba=4967198208)                                                                                                                           
                                                                                                                                                                       
  Unknown               2613203127 3492644378  879441252                                                                                                               
  Unknown               3121927844 15222054413719203 15222051291791360                                                                                                 
  Unknown               3343244132 28534529107286883 28534525764042752                                                                                                 
  Unknown               3410550780 5376907624 1966356845                                                                                                               
  Mac HFS               3579075702 3579122346      46645 [974b5d539560c243cac88b3d9e5]                                                                                 
  Mac HFS               3579029061 3579075705      46645 [974b5d539560c243cac88b3d9e5]                                                                                 
  Unknown               3861923846 5712350327 1850426482                                                                                                               
  Unknown               4062940396 6083106648 2020166253                                                                                                               
  Unknown               4224842528 18649920455179039 18649916230336512                                                                                                 
  Mac HFS               4250822314 4250858717      36404 [9ad11e66ae73d37353c7776c83d]                                                                                 
  Mac HFS               4250785914 4250822317      36404 [9ad11e66ae73d37353c7776c83d]                                                                                 
  Unknown               4261743291 5929192957 1667449667                                                                                                               
  MS Data               4317399024 98050242543 93732843520                                                                                                             
  Unknown               4471742885 5047503611  575760727                                                                                                               
  Mac HFS               4616942927 4616989826      46900 [1e27a05ae15c9eefc1a61545ef0]                                                                                 
  Mac HFS               4616896031 4616942930      46900 [1e27a05ae15c9eefc1a61545ef0]                                                                                 
  Unknown               4629259432 32766090818675879 32766086189416448                                                                                                 
  Unknown               4696328634 1936921060793 1932224732160                                                                                                         
  Mac HFS               4830745547 4856759057   26013511 [7d13C4780A44E320ff910d5EB8B]                                                                                 
  Mac HFS               4804732040 4830745550   26013511 [7d13C4780A44E320ff910d5EB8B]                                                                                 
  Mac HFS               4839979916 4865996479   26016564 [B86d8dBC4a37D87bAAAf6aABEA8]                                                                                 
  Mac HFS               4813963356 4839979919   26016564 [B86d8dBC4a37D87bAAAf6aABEA8]                                                                                 
  Unknown               4942801358 5515335151  572533794
Top
recuperation
Posts: 2737
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Input/output error from the log, do I need to continue to run the tool?

#2 Post by recuperation »

Please post your complete logfile and a smartmontools logfile for each of your drives.
viewtopic.php?f=5&t=10910
Top
bdonglobal
Posts: 4
Joined: 05 Sep 2023, 01:16

Re: Input/output error from the log, do I need to continue to run the tool?

#3 Post by bdonglobal »

this is the smartmontools output for /dev/sda, others are similar.

Code: Select all

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-197-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     Samsung SSD 870 EVO 4TB
Serial Number:    S6BANG0R102393T
LU WWN Device Id: 5 002538 f71110c49
Firmware Version: SVT01B6Q
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   Unknown(0x09fc), ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA >3.2 (0x1ff), 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Sep  5 13:56:08 2023 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

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:                (    0) seconds.
Offline data collection
capabilities:                    (0x53) 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.
                                        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:        (   2) minutes.
Extended self-test routine
recommended polling time:        ( 320) minutes.
SCT capabilities:              (0x003d) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   078   078   010    Pre-fail  Always       -       985
  9 Power_On_Hours          0x0032   095   095   000    Old_age   Always       -       21784
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       19
177 Wear_Leveling_Count     0x0013   098   098   000    Pre-fail  Always       -       39
179 Used_Rsvd_Blk_Cnt_Tot   0x0013   078   078   010    Pre-fail  Always       -       985
181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
183 Runtime_Bad_Block       0x0013   078   078   010    Pre-fail  Always       -       985
187 Reported_Uncorrect      0x0032   089   089   000    Old_age   Always       -       103653
190 Airflow_Temperature_Cel 0x0032   070   060   000    Old_age   Always       -       30
195 Hardware_ECC_Recovered  0x001a   199   199   000    Old_age   Always       -       103653
199 UDMA_CRC_Error_Count    0x003e   100   100   000    Old_age   Always       -       0
235 Unknown_Attribute       0x0012   099   099   000    Old_age   Always       -       15
241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       167634790546

SMART Error Log Version: 1
Warning: ATA error count 65535 inconsistent with error log pointer 3

ATA Error Count: 65535 (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 65535 occurred at disk power-on lifetime: 21769 hours (907 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
  -- -- -- -- -- -- --
  00 51 01 10 00 00 00  Error:  at LBA = 0x00000010 = 16

  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 08 00 60 03 78 00 00   6d+10:32:18.228  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   6d+10:32:18.228  READ LOG EXT
  60 08 00 60 03 78 00 00   6d+10:32:18.228  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   6d+10:32:18.228  READ LOG EXT
  60 08 00 60 03 78 00 00   6d+10:32:18.228  READ FPDMA QUEUED

Error 65534 occurred at disk power-on lifetime: 21769 hours (907 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
  -- -- -- -- -- -- --
  40 51 01 10 00 00 00  Error: UNC at LBA = 0x00000010 = 16

  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 08 00 60 03 78 00 00   6d+10:32:18.075  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   6d+10:32:18.075  READ LOG EXT
  60 08 00 60 03 78 00 00   6d+10:32:18.075  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   6d+10:32:18.075  READ LOG EXT
  60 08 00 60 03 78 00 00   6d+10:32:18.075  READ FPDMA QUEUED

Error 65533 occurred at disk power-on lifetime: 21769 hours (907 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
  -- -- -- -- -- -- --
  00 51 01 10 00 00 00  Error:  at LBA = 0x00000010 = 16

  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 08 00 60 03 78 00 00   6d+10:32:17.921  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   6d+10:32:17.921  READ LOG EXT
  60 08 00 60 03 78 00 00   6d+10:32:17.921  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   6d+10:32:17.921  READ LOG EXT
  60 08 00 60 03 78 00 00   6d+10:32:17.921  READ FPDMA QUEUED

Error 65532 occurred at disk power-on lifetime: 21769 hours (907 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
  -- -- -- -- -- -- --
  00 51 01 10 00 00 00  Error:  at LBA = 0x00000010 = 16

  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 08 00 60 03 78 00 00   6d+10:32:17.767  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   6d+10:32:17.767  READ LOG EXT
  60 08 00 60 03 78 00 00   6d+10:32:17.767  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   6d+10:32:17.767  READ LOG EXT
  60 08 00 60 03 78 00 00   6d+10:32:17.767  READ FPDMA QUEUED

Error 65531 occurred at disk power-on lifetime: 21769 hours (907 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
  -- -- -- -- -- -- --
  00 51 01 10 00 00 00  Error:  at LBA = 0x00000010 = 16

  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 08 00 60 03 78 00 00   6d+10:32:17.613  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   6d+10:32:17.613  READ LOG EXT
  60 08 00 60 03 78 00 00   6d+10:32:17.613  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   6d+10:32:17.613  READ LOG EXT
  60 08 00 60 03 78 00 00   6d+10:32:17.613  READ FPDMA QUEUED

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
  256        0    65535  Read_scanning was never started
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.
Top
bdonglobal
Posts: 4
Joined: 05 Sep 2023, 01:16

Re: Input/output error from the log, do I need to continue to run the tool?

#4 Post by bdonglobal »

and this is the tops lines of testdisk.log, after these, all output is

Code: Select all

file_pread(17,1,buffer,6423607(802950/1/4)) read err: Input/output error

Code: Select all


Mon Sep  4 08:44:01 2023
Command line: TestDisk

TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Linux, kernel 4.15.0-197-generic (#208-Ubuntu SMP Tue Nov 1 17:23:37 UTC 2022) x86_64
Compiler: GCC 7.2
ext2fs lib: 1.44.1, ntfs lib: libntfs-3g, reiserfs lib: none, ewf lib: none, curses lib: ncurses 6.0
Warning: can't get size for Disk /dev/mapper/control - 0 B - 0 sectors, sector size=512
Warning: can't get size for Disk /dev/md - 0 B - 0 sectors (RO), sector size=512
Warning: can't get size for Disk /dev/md127 - 0 B - CHS 1 2 4, sector size=512
Hard disk list
Disk /dev/sda - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - ATA Samsung SSD 870, FW:1B6Q
Disk /dev/sdb - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - ATA Samsung SSD 870, FW:1B6Q
Disk /dev/sdc - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - ATA Samsung SSD 870, FW:1B6Q
Disk /dev/sdd - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - ATA Samsung SSD 870, FW:1B6Q
Disk /dev/sde - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - ATA Samsung SSD 870, FW:1B6Q
Disk /dev/sdf - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - ATA Samsung SSD 870, FW:1B6Q
Disk /dev/sdg - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - ATA Samsung SSD 870, FW:1B6Q
Disk /dev/sdh - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - ATA Samsung SSD 870, FW:1B6Q
Disk /dev/sdi - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - ATA Samsung SSD 870, FW:1B6Q
Disk /dev/sdj - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - ATA Samsung SSD 870, FW:1B6Q
Disk /dev/sdk - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - ATA Samsung SSD 870, FW:1B6Q
Disk /dev/sdl - 4000 GB / 3726 GiB - CHS 486401 255 63, sector size=512 - ATA Samsung SSD 870, FW:1B6Q
Disk /dev/sdm - 500 GB / 465 GiB - CHS 60801 255 63, sector size=512 - ATA Samsung SSD 870, FW:1B6Q
Disk /dev/md126 - 48 TB / 43 TiB - CHS 11719409664 2 4, sector size=512
Disk /dev/md126p1 - 536 MB / 512 MiB - CHS 131072 2 4, sector size=512
Disk /dev/md126p2 - 209 MB / 200 MiB - CHS 51200 2 4, sector size=512
Disk /dev/md126p3 - 10 GB / 10 GiB - CHS 2621440 2 4, sector size=512
Disk /dev/md126p4 - 47 TB / 43 TiB - CHS 11716605440 2 4, sector size=512

Partition table type (auto): EFI GPT
Disk /dev/md126 - 48 TB / 43 TiB
Partition table type: EFI GPT

Analyse Disk /dev/md126 - 48 TB / 43 TiB - CHS 11719409664 2 4
hdr_size=92
hdr_lba_self=1
hdr_lba_alt=93755277311 (expected 93755277311)
hdr_lba_start=34
hdr_lba_end=93755277278
hdr_lba_table=2
hdr_entries=128
hdr_entsz=128
Current partition structure:
 1 P EFI System                  2048    1050623    1048576
 2 P Unknown                  1050624    1460223     409600
 3 P Unknown                  1460224   22431743   20971520
 4 P Unknown                 22431744 93755275263 93732843520

search_part()
Disk /dev/md126 - 48 TB / 43 TiB - CHS 11719409664 2 4
FAT32 at 256/0/1
FAT1 : 32-1055
FAT2 : 1056-2079
start_rootdir : 2080 root cluster : 2
Data : 2080-1048575
sectors : 1048576
cluster_size : 8
no_of_cluster : 130812 (2 - 130813)
fat_length 1024 calculated 1022
heads/cylinder 255 (FAT) != 2 (HD)
sect/track 63 (FAT) != 4 (HD)
set_FAT_info: name from BS used

FAT32 at 256/0/1
     MS Data                     2048    1050623    1048576 [NO NAME]
     FAT32, blocksize=4096, 536 MB / 512 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=8/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1050624    1460223     409600
     ext4 blocksize=1024 Large_file Sparse_SB, 209 MB / 200 MiB
Unknown XFS version 5

XFS Marker at 182528/0/1

recover_xfs
     MS Data                  1460224   22431743   20971520
     XFS 6.2+ - bitmap version blocksize=4096, 10 GB / 10 GiB
Unknown XFS version 5

XFS Marker at 2803968/0/1

recover_xfs
     MS Data                 22431744 93755275263 93732843520
     XFS 6.2+ - bitmap version blocksize=4096, 47 TB / 43 TiB

Results
   P MS Data                     2048    1050623    1048576 [NO NAME]
     FAT32, blocksize=4096, 536 MB / 512 MiB
   P MS Data                  1050624    1460223     409600
     ext4 blocksize=1024 Large_file Sparse_SB, 209 MB / 200 MiB
   P MS Data                  1460224   22431743   20971520
     XFS 6.2+ - bitmap version blocksize=4096, 10 GB / 10 GiB
   P MS Data                 22431744 93755275263 93732843520
     XFS 6.2+ - bitmap version blocksize=4096, 47 TB / 43 TiB

Hint for advanced users. dmsetup may be used if you prefer to avoid to rewrite the partition table for the moment:
echo "0 1048576 linear /dev/md126 2048" | dmsetup create test0
echo "0 409600 linear /dev/md126 1050624" | dmsetup create test1
echo "0 20971520 linear /dev/md126 1460224" | dmsetup create test2
echo "0 93732843520 linear /dev/md126 22431744" | dmsetup create test3

interface_write()
 1 P MS Data                     2048    1050623    1048576 [NO NAME]
 2 P MS Data                  1050624    1460223     409600
 3 P MS Data                  1460224   22431743   20971520
 4 P MS Data                 22431744 93755275263 93732843520

search_part()
Disk /dev/md126 - 48 TB / 43 TiB - CHS 11719409664 2 4
FAT32 at 256/0/1
FAT1 : 32-1055
FAT2 : 1056-2079
start_rootdir : 2080 root cluster : 2
Data : 2080-1048575
sectors : 1048576
cluster_size : 8
no_of_cluster : 130812 (2 - 130813)
fat_length 1024 calculated 1022
heads/cylinder 255 (FAT) != 2 (HD)
sect/track 63 (FAT) != 4 (HD)
set_FAT_info: name from BS used

FAT32 at 256/0/1
     MS Data                     2048    1050623    1048576 [NO NAME]
     FAT32, blocksize=4096, 536 MB / 512 MiB
FAT32 at 256/1/3
FAT1 : 32-1055
FAT2 : 1056-2079
start_rootdir : 2080 root cluster : 2
Data : 2080-1048575
sectors : 1048576
cluster_size : 8
no_of_cluster : 130812 (2 - 130813)
fat_length 1024 calculated 1022
heads/cylinder 255 (FAT) != 2 (HD)
sect/track 63 (FAT) != 4 (HD)
set_FAT_info: name from BS used

FAT32 at 256/1/3
     MS Data                     2048    1050623    1048576 [NO NAME]
     FAT32, blocksize=4096, 536 MB / 512 MiB
FAT32 at 256/1/3
FAT1 : 32-1055
FAT2 : 1056-2079
start_rootdir : 2080 root cluster : 2
Data : 2080-1048575
sectors : 1048576
cluster_size : 8
no_of_cluster : 130812 (2 - 130813)
fat_length 1024 calculated 1022
heads/cylinder 255 (FAT) != 2 (HD)
sect/track 63 (FAT) != 4 (HD)
set_FAT_info: name from BS used

FAT32 at 256/1/3
     MS Data                     2054    1050629    1048576 [NO NAME]
     FAT32, blocksize=4096, 536 MB / 512 MiB

block_group_nr 1

recover_EXT2: "e2fsck -b 32768 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=1/357647, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=2048
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 11719408896
recover_EXT2: part_size 93755271168
     MS Data                     4094 93755275261 93755271168
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 48 TB / 43 TiB

block_group_nr 1

recover_EXT2: "e2fsck -b 32768 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=1/357647, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=2048
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 11719408896
recover_EXT2: part_size 93755271168
     MS Data                     4096 93755275263 93755271168
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 48 TB / 43 TiB
     Linux Swap                315384     315399         16
     SWAP2 version 0, pagesize=8192, 8192 B
     Linux Swap                315392    4509679    4194288
     SWAP2 version 1, pagesize=4096, 2147 MB / 2047 MiB

block_group_nr 3

recover_EXT2: "e2fsck -b 98304 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=3/357647, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=2048
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 11719408896
recover_EXT2: part_size 93755271168
     MS Data                     4094 93755275261 93755271168
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 48 TB / 43 TiB

block_group_nr 3

recover_EXT2: "e2fsck -b 98304 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=3/357647, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=2048
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 11719408896
recover_EXT2: part_size 93755271168
     MS Data                     4096 93755275263 93755271168
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 48 TB / 43 TiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=8/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1050624    1460223     409600
     ext4 blocksize=1024 Large_file Sparse_SB, 209 MB / 200 MiB

block_group_nr 1

recover_EXT2: "e2fsck -b 8193 -B 1024 device" may be needed
recover_EXT2: s_block_group_nr=1/25, s_mnt_count=0/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1050622    1460221     409600
     ext4 blocksize=1024 Large_file Sparse_SB Backup_SB, 209 MB / 200 MiB

block_group_nr 1

recover_EXT2: "e2fsck -b 8193 -B 1024 device" may be needed
recover_EXT2: s_block_group_nr=1/25, s_mnt_count=0/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1050624    1460223     409600
     ext4 blocksize=1024 Large_file Sparse_SB Backup_SB, 209 MB / 200 MiB

block_group_nr 3

recover_EXT2: "e2fsck -b 24577 -B 1024 device" may be needed
recover_EXT2: s_block_group_nr=3/25, s_mnt_count=0/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1050622    1460221     409600
     ext4 blocksize=1024 Large_file Sparse_SB Backup_SB, 209 MB / 200 MiB

block_group_nr 3

recover_EXT2: "e2fsck -b 24577 -B 1024 device" may be needed
recover_EXT2: s_block_group_nr=3/25, s_mnt_count=0/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1050624    1460223     409600
     ext4 blocksize=1024 Large_file Sparse_SB Backup_SB, 209 MB / 200 MiB

block_group_nr 5

recover_EXT2: "e2fsck -b 40961 -B 1024 device" may be needed
recover_EXT2: s_block_group_nr=5/25, s_mnt_count=0/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1050622    1460221     409600
     ext4 blocksize=1024 Large_file Sparse_SB Backup_SB, 209 MB / 200 MiB

block_group_nr 5

recover_EXT2: "e2fsck -b 40961 -B 1024 device" may be needed
recover_EXT2: s_block_group_nr=5/25, s_mnt_count=0/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1050624    1460223     409600
     ext4 blocksize=1024 Large_file Sparse_SB Backup_SB, 209 MB / 200 MiB

block_group_nr 7

recover_EXT2: "e2fsck -b 57345 -B 1024 device" may be needed
recover_EXT2: s_block_group_nr=7/25, s_mnt_count=0/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1050622    1460221     409600
     ext4 blocksize=1024 Large_file Sparse_SB Backup_SB, 209 MB / 200 MiB

block_group_nr 7

recover_EXT2: "e2fsck -b 57345 -B 1024 device" may be needed
recover_EXT2: s_block_group_nr=7/25, s_mnt_count=0/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1050624    1460223     409600
     ext4 blocksize=1024 Large_file Sparse_SB Backup_SB, 209 MB / 200 MiB

block_group_nr 9

recover_EXT2: "e2fsck -b 73729 -B 1024 device" may be needed
recover_EXT2: s_block_group_nr=9/25, s_mnt_count=0/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1050622    1460221     409600
     ext4 blocksize=1024 Large_file Sparse_SB Backup_SB, 209 MB / 200 MiB

block_group_nr 9

recover_EXT2: "e2fsck -b 73729 -B 1024 device" may be needed
recover_EXT2: s_block_group_nr=9/25, s_mnt_count=0/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1050624    1460223     409600
     ext4 blocksize=1024 Large_file Sparse_SB Backup_SB, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=7/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1230858    1640457     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=3/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1233208    1642807     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=3/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1233226    1642825     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=3/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1233244    1642843     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=3/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1233262    1642861     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=3/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1233506    1643105     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=3/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1238068    1647667     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=3/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1238088    1647687     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=3/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1238106    1647705     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=3/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1238124    1647723     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=3/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1238280    1647879     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=3/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1238336    1647935     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=3/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1238384    1647983     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB

recover_EXT2: s_block_group_nr=0/25, s_mnt_count=3/4294967295, s_blocks_per_group=8192, s_inodes_per_group=2048
recover_EXT2: s_blocksize=1024
recover_EXT2: s_blocks_count 204800
recover_EXT2: part_size 409600
     MS Data                  1238438    1648037     409600
     ext4 blocksize=1024 Large_file Sparse_SB Recover, 209 MB / 200 MiB
Unknown XFS version 5

XFS Marker at 182528/0/1

recover_xfs
     MS Data                  1460224   22431743   20971520
     XFS 6.2+ - bitmap version blocksize=4096, 10 GB / 10 GiB

block_group_nr 3

recover_EXT2: "e2fsck -b 98304 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=3/357643, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=2048
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 11719277568
recover_EXT2: part_size 93754220544
     MS Data                  1054718 93755275261 93754220544
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 48 TB / 43 TiB

block_group_nr 3

recover_EXT2: "e2fsck -b 98304 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=3/357643, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=2048
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 11719277568
recover_EXT2: part_size 93754220544
     MS Data                  1054720 93755275263 93754220544
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 48 TB / 43 TiB

block_group_nr 5

recover_EXT2: "e2fsck -b 163840 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=5/357643, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=2048
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 11719277568
recover_EXT2: part_size 93754220544
     MS Data                  1054718 93755275261 93754220544
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 48 TB / 43 TiB

block_group_nr 5

recover_EXT2: "e2fsck -b 163840 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=5/357643, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=2048
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 11719277568
recover_EXT2: part_size 93754220544
     MS Data                  1054720 93755275263 93754220544
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 48 TB / 43 TiB

block_group_nr 7

recover_EXT2: "e2fsck -b 229376 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=7/357643, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=2048
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 11719277568
recover_EXT2: part_size 93754220544
     MS Data                  1054718 93755275261 93754220544
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 48 TB / 43 TiB

block_group_nr 7

recover_EXT2: "e2fsck -b 229376 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=7/357643, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=2048
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 11719277568
recover_EXT2: part_size 93754220544
     MS Data                  1054720 93755275263 93754220544
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 48 TB / 43 TiB

block_group_nr 9

recover_EXT2: "e2fsck -b 294912 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=9/357643, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=2048
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 11719277568
recover_EXT2: part_size 93754220544
     MS Data                  1054718 93755275261 93754220544
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 48 TB / 43 TiB

block_group_nr 9

recover_EXT2: "e2fsck -b 294912 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=9/357643, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=2048
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 11719277568
recover_EXT2: part_size 93754220544
     MS Data                  1054720 93755275263 93754220544
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 48 TB / 43 TiB

block_group_nr 9

recover_EXT2: "e2fsck -b 294912 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=9/357643, s_mnt_count=0/4294967295, s_blocks_per_group=32768, s_inodes_per_group=2048
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 11719277568
recover_EXT2: part_size 93754220544
     MS Data                  1054720 93755275263 93754220544
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 48 TB / 43 TiB
Unknown XFS version 5

XFS Marker at 786688/0/1

recover_xfs
     MS Data                  6293504   27265023   20971520
     XFS 6.2+ - bitmap version blocksize=4096, 10 GB / 10 GiB
file_pread(17,16,buffer,6423590(802948/1/3)) read err: Partial read
file_pread(17,16,buffer,6423606(802950/1/3)) read err: Input/output error
file_pread(17,1,buffer,6423606(802950/1/3)) read err: Input/output error
file_pread(17,1,buffer,6423607(802950/1/4)) read err: Input/output error
file_pread(17,16,buffer,6423588(802948/1/1)) read err: Partial read
file_pread(17,16,buffer,6423604(802950/1/1)) read err: Input/output error
file_pread(17,1,buffer,6423604(802950/1/1)) read err: Input/output error
file_pread(17,16,buffer,6423605(802950/1/2)) read err: Input/output error
file_pread(17,1,buffer,6423605(802950/1/2)) read err: Input/output error
file_pread(17,16,buffer,6423606(802950/1/3)) read err: Input/output error
file_pread(17,1,buffer,6423606(802950/1/3)) read err: Input/output error
file_pread(17,16,buffer,6423607(802950/1/4)) read err: Input/output error
file_pread(17,1,buffer,6423607(802950/1/4)) read err: Input/output error
file_pread(17,16,buffer,6423598(802949/1/3)) read err: Input/output error
file_pread(17,1,buffer,6423598(802949/1/3)) read err: Input/output error
file_pread(17,16,buffer,6423599(802949/1/4)) read err: Input/output error
file_pread(17,1,buffer,6423599(802949/1/4)) read err: Input/output error
file_pread(17,16,buffer,6423600(802950/0/1)) read err: Input/output error
file_pread(17,1,buffer,6423600(802950/0/1)) read err: Input/output error
file_pread(17,16,buffer,6423601(802950/0/2)) read err: Input/output error
file_pread(17,1,buffer,6423601(802950/0/2)) read err: Input/output error
file_pread(17,16,buffer,6423602(802950/0/3)) read err: Input/output error
Top
recuperation
Posts: 2737
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Input/output error from the log, do I need to continue to run the tool?

#5 Post by recuperation »

The disk whose data you showed, seems to be broken. You can either consult a professional recovery lab or try to read out the array using ddrescue as described in the manual.

When looking at the amount of data written compared to the specified total amount of terabytes written I have no idea why your disk failed so early.

12 disks in a RAID0 configuration is an entity which is 12 times more unreliable than a single disk.
I wonder why one could set up a computer this way.
Top
bdonglobal
Posts: 4
Joined: 05 Sep 2023, 01:16

Re: Input/output error from the log, do I need to continue to run the tool?

#6 Post by bdonglobal »

the computer has been running for 2 years when we get the hardward, not sure how long it has run previously.

when you say "failed so early", do you mean "(907 days + 1 hours)"?

and the reason to use RAID0 may be something I don't know, but it is running this way. I will report to my admin and check if we could change to other RAID mode.

I cancelled the testdisk tool, and running xfs_repair -L /dev/md126, then I still get "bad primary superblock", but don't know why, the hard disk is mounted successfully now. miracle. the disk currently is mounted. then I run some services, and observed the following log at /var/log/syslog. it seems like the hard disk is damaged, cannot read block.

Code: Select all

Sep  6 02:11:07 c-server13 kernel: [164379.772827] sd 0:0:9:0: [sdj] tag#0 Add. Sense: Unrecovered read error
Sep  6 02:11:07 c-server13 kernel: [164379.772832] sd 0:0:9:0: [sdj] tag#0 CDB: Read(16) 88 00 00 00 00 01 a0 71 f1 b0 00 00 00 08 00 00
Sep  6 02:11:07 c-server13 kernel: [164379.772836] print_req_error: critical medium error, dev sdj, sector 6986789296
Sep  6 02:11:07 c-server13 kernel: [164379.774154] XFS (md126p4): metadata I/O error: block 0x1384010eb0 ("xfs_trans_read_buf_map") error 61 numblks 8
Sep  6 02:11:07 c-server13 kernel: [164379.774216] [UFW BLOCK] IN=eno1 OUT= MAC=ec:f4:bb:e8:71:00:3c:e8:24:1a:b1:02:08:00 SRC=139.144.68.8 DST=43.227.255.119 LEN=40 TOS=0x00 PREC=0x00 TTL=240 ID=52308 PROTO=TCP SPT=60000 DPT=5135 WINDOW=1024 RES=0x00 SYN URGP=0 
Sep  6 02:11:08 c-server13 kernel: [164379.935498] sd 0:0:9:0: [sdj] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep  6 02:11:08 c-server13 kernel: [164379.935525] sd 0:0:9:0: [sdj] tag#0 Sense Key : Medium Error [current] [descriptor] 
Sep  6 02:11:08 c-server13 kernel: [164379.935532] sd 0:0:9:0: [sdj] tag#0 Add. Sense: Unrecovered read error
Sep  6 02:11:08 c-server13 kernel: [164379.935537] sd 0:0:9:0: [sdj] tag#0 CDB: Read(16) 88 00 00 00 00 01 a0 71 f1 b0 00 00 00 08 00 00
Sep  6 02:11:08 c-server13 kernel: [164379.935541] print_req_error: critical medium error, dev sdj, sector 6986789296
Sep  6 02:11:08 c-server13 kernel: [164379.936900] XFS (md126p4): metadata I/O error: block 0x1384010eb0 ("xfs_trans_read_buf_map") error 61 numblks 8
Sep  6 02:11:08 c-server13 kernel: [164380.097996] sd 0:0:9:0: [sdj] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep  6 02:11:08 c-server13 kernel: [164380.098000] sd 0:0:9:0: [sdj] tag#0 Sense Key : Medium Error [current] [descriptor] 
Sep  6 02:11:08 c-server13 kernel: [164380.098003] sd 0:0:9:0: [sdj] tag#0 Add. Sense: Unrecovered read error
Sep  6 02:11:08 c-server13 kernel: [164380.098007] sd 0:0:9:0: [sdj] tag#0 CDB: Read(16) 88 00 00 00 00 01 a0 71 f1 b0 00 00 00 08 00 00
Sep  6 02:11:08 c-server13 kernel: [164380.098009] print_req_error: critical medium error, dev sdj, sector 6986789296
Sep  6 02:11:08 c-server13 kernel: [164380.099358] XFS (md126p4): metadata I/O error: block 0x1384010eb0 ("xfs_trans_read_buf_map") error 61 numblks 8
Sep  6 02:11:08 c-server13 kernel: [164380.260742] sd 0:0:9:0: [sdj] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep  6 02:11:08 c-server13 kernel: [164380.260769] sd 0:0:9:0: [sdj] tag#0 Sense Key : Medium Error [current] [descriptor] 
Sep  6 02:11:08 c-server13 kernel: [164380.260772] sd 0:0:9:0: [sdj] tag#0 Add. Sense: Unrecovered read error
Sep  6 02:11:08 c-server13 kernel: [164380.260786] sd 0:0:9:0: [sdj] tag#0 CDB: Read(16) 88 00 00 00 00 01 a0 71 f1 b0 00 00 00 08 00 00
Sep  6 02:11:08 c-server13 kernel: [164380.260792] print_req_error: critical medium error, dev sdj, sector 6986789296
Sep  6 02:11:08 c-server13 kernel: [164380.260861] XFS (md126p4): metadata I/O error: block 0x1384010eb0 ("xfs_trans_read_buf_map") error 61 numblks 8
Sep  6 02:11:08 c-server13 kernel: [164380.430720] sd 0:0:9:0: [sdj] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep  6 02:11:08 c-server13 kernel: [164380.430745] sd 0:0:9:0: [sdj] tag#0 Sense Key : Medium Error [current] [descriptor] 
Sep  6 02:11:08 c-server13 kernel: [164380.430750] sd 0:0:9:0: [sdj] tag#0 Add. Sense: Unrecovered read error
Sep  6 02:11:08 c-server13 kernel: [164380.430755] sd 0:0:9:0: [sdj] tag#0 CDB: Read(16) 88 00 00 00 00 01 a0 71 f1 b0 00 00 00 08 00 00
Sep  6 02:11:08 c-server13 kernel: [164380.430759] print_req_error: critical medium error, dev sdj, sector 6986789296
Sep  6 02:11:08 c-server13 kernel: [164380.432184] XFS (md126p4): metadata I/O error: block 0x1384010eb0 ("xfs_trans_read_buf_map") error 61 numblks 8
Sep  6 02:11:08 c-server13 kernel: [164380.601622] mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Sep  6 02:11:08 c-server13 kernel: [164380.601628] mpt3sas_cm0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
Top
recuperation
Posts: 2737
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Input/output error from the log, do I need to continue to run the tool?

#7 Post by recuperation »

I am referring to the amount of data written.
Top
Locked

Return to “Filesystem repair”