On 2/24/23 22:24, Albretch Mueller wrote:
I have been "heavily" downloading data from archive.org which I actually need for my own corpora research from two different places. One offering me 1.5MiB/s and the other 0.5MiB/s download speed.Is my hard drive actually failing? (smartctl tells me it doesn't seem to be the case) or are they or my ISP somehow hacking into my computer to "motivate" such apparent errors? How could I check either case? I have read about XFS needing special care, but I would like to have a better idea of the source of such errors first. this is what I see on the screen when the drive is disconnected somehow, but I always reconnected by clicking on its sign using the GUI just fine. It doesn't sound like a failing drive either. What could possibly going on? $ kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.UnknownMethod" "No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/UDisks2/drives/..." ... $ sudo systemctl --user --failed Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user) $ sudo dmesg ... [22565.451321] usb-storage 1-1:1.0: USB Mass Storage device detected [22565.451467] scsi host3: usb-storage 1-1:1.0 [22566.457236] scsi 3:0:0:0: Direct-Access ST16000N M001G-2KK103 PQ: 0 ANSI: 5 [22566.457527] sd 3:0:0:0: Attached scsi generic sg2 type 0 [22566.457823] sd 3:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16). [22566.457997] sd 3:0:0:0: [sdb] 31251759104 512-byte logical blocks: (16.0 TB/14.6 TiB) [22566.458365] sd 3:0:0:0: [sdb] Write Protect is off [22566.458369] sd 3:0:0:0: [sdb] Mode Sense: 28 00 00 00 [22566.458640] sd 3:0:0:0: [sdb] No Caching mode page found [22566.458644] sd 3:0:0:0: [sdb] Assuming drive cache: write through [22566.538074] sdb: sdb1 sdb2 [22566.583373] sd 3:0:0:0: [sdb] Attached SCSI disk [22575.515358] XFS (sdb1): Mounting V5 Filesystem [22575.742880] XFS (sdb1): Starting recovery (logdev: internal) [22575.919197] XFS (sdb1): Ending recovery (logdev: internal) [22575.932002] xfs filesystem being mounted at /media/user/77d8da74-a690-481a-86d5-9beab5a8e842 supports timestamps until 2038 (0x7fffffff) [22582.368977] usb 1-1: USB disconnect, device number 21 [22582.380548] XFS (sdb1): Unmounting Filesystem [22582.380594] XFS (sdb1): log I/O error -5 [22582.380603] XFS (sdb1): xfs_do_force_shutdown(0x2) called from line 1211 of file fs/xfs/xfs_log.c. Return address = 000000009651f22d [22582.380604] XFS (sdb1): Log I/O Error Detected. Shutting down filesystem [22582.380605] XFS (sdb1): Please unmount the filesystem and rectify the problem(s) [22582.380608] XFS (sdb1): Unable to update superblock counters. Freespace may not be correct on next mount. ... $ sudo blkid ... /dev/sdb1: UUID="77d8da74-a690-481a-86d5-9beab5a8e842" BLOCK_SIZE="512" TYPE="xfs" PARTLABEL="primary" PARTUUID="f646c65f-bc46-4185-ba1e-583f157d6cb3" ... $ sudo smartctl -l selftest /dev/sdb smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-18-amd64] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Interrupted (host reset) 00% 601 - # 2 Extended offline Completed without error 00% 96 - # 3 Conveyance offline Completed without error 00% 74 - # 4 Short offline Completed without error 00% 74 - # 5 Extended offline Aborted by host 90% 73 - # 6 Short offline Completed without error 00% 0 - $
It looks like your USB connection is unreliable. I suggest removing the drive from its USB enclosure, installing the drive internally, connecting the drive to the system power supply, and connecting the drive to a or HBA SATA 6 Gbps port using a 6 Gbps cable. Unless you have suitable test equipment, you may need to try multiple computers, SATA ports, HBA's, and/or SATA cables as you search for the right combination.
Once the drive has a reliable hardware connection, I would run a SMART long test 'smartctl -t long ...', generate a complete SMART report 'smartctl --xall ...', check the filesystem fsck.xfs(8), and validate the integrity of the data.
David
