crazy situation

English Hardware
1

Hello,

I’ve been using Open Suse Tumbleweed for several years and I recently encountered some difficulties: when I copy a file from my SD card to my hard drive, I end up with two different files (the md5sums are not the same).

So I initially thought of a defective hard drive but I have the same problem if I copy a file from my SD card to an external hard drive!!

These files are large files (HD video file), but I don’t understand what is happening. I have the impression that this is reproduced in all the writings of my files: I have to pass fsck regularly, it finds me errors…

The funny thing is that if I reinstall the system from scratch, the problem does not arise for a while, then it comes back without me knowing why…

Where to start to see what’s wrong? Do you think a rootkit could be causing this problem?

PS: I also put the result of SMART because I think that I will be asked:

# smartctl -a /dev/sda
smartctl 7.2 2021-09-14 r5237 [x86_64-linux-5.17.1-1-default] (SUSE RPM)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, [www.smartmontools.org](http://www.smartmontools.org/)

=== START OF INFORMATION SECTION ===
Model Family:     Seagate BarraCuda 3.5 (SMR)
Device Model:     ST2000DM008-2FR102
Serial Number:    WFL3HA8W
LU WWN Device Id: 5 000c50 0cd2f8e0b
Firmware Version: 0001
User Capacity:    2 000 398 934 016 bytes [2,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
TRIM Command:     Available
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Apr 10 02:56:38 2022 CEST
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:                    (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:        ( 200) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x30a5) SCT Status 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   059   048   006    Pre-fail  Always       -       31112923
  3 Spin_Up_Time            0x0003   098   098   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   098   098   020    Old_age   Always       -       2368
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   091   060   045    Pre-fail  Always       -       1142310008
  9 Power_On_Hours          0x0032   091   091   000    Old_age   Always       -       7941h+31m+09.973s
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   098   098   020    Old_age   Always       -       2367
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       1 1 1
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   066   058   040    Old_age   Always       -       34 (Min/Max 20/35)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       35
193 Load_Cycle_Count        0x0032   098   098   000    Old_age   Always       -       4227
194 Temperature_Celsius     0x0022   034   042   000    Old_age   Always       -       34 (0 19 0 0 0)
195 Hardware_ECC_Recovered  0x001a   075   064   000    Old_age   Always       -       31112923
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       7878h+07m+12.549s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       65939235862
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       57291789010

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      7931         -
# 2  Short offline       Completed without error       00%      7910         -
# 3  Short offline       Completed without error       00%      7893         -
# 4  Short offline       Completed without error       00%      7879         -
# 5  Short offline       Completed without error       00%      7866         -
# 6  Short offline       Completed without error       00%      7856         -
# 7  Short offline       Completed without error       00%      7850         -
# 8  Extended offline    Interrupted (host reset)      70%      7849         -
# 9  Short offline       Completed without error       00%      7834         -
#10  Short offline       Completed without error       00%      7822         -
#11  Short offline       Completed without error       00%      7806         -
#12  Short offline       Completed without error       00%      7791         -
#13  Short offline       Completed without error       00%      7775         -
#14  Short offline       Completed without error       00%      7774         -
#15  Short offline       Completed without error       00%      7764         -
#16  Short offline       Completed without error       00%      7757         -
#17  Short offline       Completed without error       00%      7742         -
#18  Short offline       Completed without error       00%      7733         -
#19  Short offline       Completed without error       00%      7723         -
#20  Short offline       Completed without error       00%      7708         -
#21  Short offline       Completed without error       00%      7696         -

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.
2

There are numerous ways to “copy” a file. Have you tried several different ways? Do all copy methods produce this problem? What filesystems are on the sources and targets?

3

Hello,
I have tried Dolphin, cp and scp.

Same problem.

More info about the disks:

fdisk -l /dev/sda
**Disque /dev/sda : 1,82 TiB, 2000398934016 octets, 3907029168 secteurs**
Modèle de disque : ST2000DM008-2FR1
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 4096 octets
taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets

Formated in Ext 4

fdisk -l /dev/sdd
**Disque /dev/sdd : 28,91 GiB, 31046238208 octets, 60637184 secteurs**
Modèle de disque : Storage Device   
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0x00000000

**Périphérique****Amorçage****Début****     Fin****Secteurs****Taille****Id****Type**
/dev/sdd1              8192 60637183 60628992  28,9G  c W95 FAT32 (LBA)

I also noticed something: when I use the md5sum command sometimes it’s very long and sometimes it’s very fast for the same file. I feel that in case of newly copied file; md5sum takes a cached version (maybe in ram memory) rather than actually checking on disk… But that’s just a guess!

I also tried to test my disk with seagate’s Seatools software and everything seems ok:

https://i.imgur.com/7eSV4X6.png

https://i.imgur.com/4iJmBYd.png

4

You mention one of the file systems involved as Ext4, but not the other one.

Another question. When you copy it back again to the original file system, but with another name, how about the checksum then?

5

Another thought. You did not tell anything about the file that is copied. Could it be a sparse file?

6

Hello,

I come back to you because I still have a file copy problem: I first reformatted my /home partition in btrfs and I could see errors in my files. I also installed another hard disk (ssd, in btrfs) and I still have the same problems. The hard drives don’t seem to be the source of the bad copy.

In addition to the sums of controls which are not the same, I actually have this kind of visual bugs in the videos that I copy:

https://i.imgur.com/um0gkhQ.png

How to understand what is wrong? (I’m personally leaning towards an I/O problem at the kernel level, but that’s a little too specific for me)

Thank you.

7

The files I’m trying to copy are from an SD card that was used in my camera. Fortunately linux does not modify these files. These files created by my camera are therefore the originals that I cannot copy.

8

So, most probably, not a Linux file system.

9

And? linux can read an sd card…

10

I asked you more things you did not answer.

One way people can be able to help in computer technical problems is that they might look at a problem from another perspective. And thus they might ask things that, in your first opinion, look off-topic When you then ignore them (not even saying why you do not want to answer), or ridicule them, you will miss a lot of the expertise that those people can use in solving problems. Simply because they will leave a thread and go for one that is more rewarding.

11

Have you read the first message of this thread?

12

I do not know why you ask. Of course I have. In fact my attention (as mod) was drawn to this thread because of it’s title that did not reveal anything about the subject.

I can not read anything about the file system type. You only talk about the hardware (SD card and hard drive, external or not).

Then in post #3 you have an incomplete fdisk listing of sda, with a non proven remark that the whole disk has an Ext4 file system on it.

And you show there a probably (but the prompts that would confirm the completeness aren’t there) fdisk listing of sdd. It seems to have 1 partition with a partition type of x’0C’ which can point to W95 or FAT32, but no remark on what file system type is on it, if there is one).

So I asked, were it only to get the information on both with the same completeness. Still no answer.

Maybe you do not know how to get the information, that is no problem, but you did not ask, you simply ignored.

lsblk -f