Well I’m no expert by any means, but I reckon the input/output errors are due to the connection to the drive being lost, no?
Regarding the drive: SMART tells me there are no issues (no critical warnings, no media and data integrity errors)
root@DietPi:~# smartctl -a /dev/sda -d sntjmicron
smartctl 7.1 2019-12-30 r5022 [armv7l-linux-4.19.118-v7l+] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: SAMSUNG MZVLW256HEHP-000L7
Serial Number: S35ENA1K272709
Firmware Version: 5L7QCXB7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 256.060.514.304 [256 GB]
Unallocated NVM Capacity: 0
Controller ID: 2
Number of Namespaces: 1
Namespace 1 Size/Capacity: 256.060.514.304 [256 GB]
Namespace 1 Utilization: 244.637.016.064 [244 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 b28102e969
Local Time is: Thu Jun 11 10:22:42 2020 CEST
Firmware Updates (0x16): 3 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Warning Comp. Temp. Threshold: 69 Celsius
Critical Comp. Temp. Threshold: 72 Celsius
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 7.60W - - 0 0 0 0 0 0
1 + 6.00W - - 1 1 1 1 0 0
2 + 5.10W - - 2 2 2 2 0 0
3 - 0.0400W - - 3 3 3 3 210 1500
4 - 0.0050W - - 4 4 4 4 2200 6000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 32 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 5%
Data Units Read: 38.939.450 [19,9 TB]
Data Units Written: 29.900.926 [15,3 TB]
Host Read Commands: 307.986.706
Host Write Commands: 229.812.741
Controller Busy Time: 1.028
Power Cycles: 3.049
Power On Hours: 886
Unsafe Shutdowns: 141
Media and Data Integrity Errors: 0
Error Information Log Entries: 1.611
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 32 Celsius
Temperature Sensor 2: 36 Celsius
Error Information (NVMe Log 0x01, max 64 entries)
Num ErrCount SQId CmdId Status PELoc LBA NSID VS
0 1611 0 0x010e 0x4202 0x028 0 0 -
1 1610 0 0x000d 0x4202 0x028 0 0 -
2 1609 0 0x0f0c 0x4202 0x028 0 0 -
3 1608 0 0x0e0b 0x4202 0x028 0 0 -
4 1607 0 0x0d0a 0x4202 0x028 0 0 -
5 1606 0 0x0c09 0x4202 0x028 0 0 -
6 1605 0 0x0b08 0x4202 0x028 0 0 -
7 1604 0 0x0a07 0x4202 0x028 0 0 -
8 1603 0 0x0906 0x4202 0x028 0 0 -
9 1602 0 0x0805 0x4202 0x028 0 0 -
10 1601 0 0x0704 0x4202 0x028 0 0 -
11 1600 0 0x0603 0x4202 0x028 0 0 -
12 1599 0 0x0502 0x4202 0x028 0 0 -
13 1598 0 0x0401 0x4202 0x028 0 0 -
14 1597 0 0x030f 0x4202 0x028 0 0 -
15 1596 0 0x020e 0x4202 0x028 0 0 -
... (48 entries not shown)
and I somewhat doubt that the cable is faulty simply because everything is running smoothly except when I remote access the drive and put some stress on it. Of course I can’t be sure, but I think it’s reasonable to assume that a faulty drive/cable would impact everything and not just during certain scenarios.
I’ll try to get a more in-depth log for a crash, maybe that will tell us sómething.
EDIT: By “everything else is running smoothly” I mean that I have not encountered a single issue running downloads with JDownloader or SABNZBD for example.