You are not logged in.
Pages: 1
Whether I'm tranferring files or not, my hard drive randomly disconnects.
I do this to mount to my drive, and use Thunar to tranfer files to my home drive:
sudo mount /dev/sdb2 "/run/media/yoru/Fat Fck"
However in the middle of tranferring I get this error:
Oct 21 12:05:44 arch kernel: ata5.00: exception Emask 0x50 SAct 0x1 SErr 0x4070802 action 0xe frozen
Oct 21 12:05:44 arch kernel: ata5.00: irq_stat 0x00000040, connection status changed
Oct 21 12:05:44 arch kernel: ata5: SError: { RecovComm HostInt PHYRdyChg PHYInt CommWake DevExch }
Oct 21 12:05:44 arch kernel: ata5.00: failed command: READ FPDMA QUEUED
Oct 21 12:05:44 arch kernel: ata5.00: cmd 60/20:00:a0:49:2e/00:00:00:00:00/40 tag 0 ncq dma 16384 in
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x50 (ATA bus error)
Oct 21 12:05:44 arch kernel: ata5.00: status: { DRDY }
Oct 21 12:05:44 arch kernel: ata5: hard resetting link
Oct 21 12:05:47 arch warp-svc[618]: 2024-10-21T09:05:47.347Z DEBUG tunnel_loop{protocol="wireguard"}: boringtun::noise::timers: KEEPALIVE(PERSISTENT_KEEPALIVE)
Oct 21 12:05:47 arch kernel: ata5: found unknown device (class 0)
Oct 21 12:05:47 arch kernel: ata5: SATA link down (SStatus 0 SControl 310)
Oct 21 12:05:47 arch kernel: ata5: hard resetting link
Oct 21 12:05:51 arch kernel: ata5: found unknown device (class 0)
Oct 21 12:05:51 arch kernel: ata5: SATA link down (SStatus 0 SControl 310)
Oct 21 12:05:52 arch kernel: ata5: hard resetting link
Oct 21 12:05:55 arch kernel: ata5: found unknown device (class 0)
Oct 21 12:05:55 arch kernel: ata5: SATA link down (SStatus 0 SControl 310)
Oct 21 12:05:55 arch kernel: ata5.00: disable device
After the "disable device" error, my hard drive disconnects.
After a while, it starts to soft reset itself, and comes back:
Oct 21 12:06:09 arch kernel: ata5: softreset failed (1st FIS failed)
Oct 21 12:06:11 arch kernel: ata5: found unknown device (class 0)
Oct 21 12:06:12 arch kernel: ata5: SATA link down (SStatus 0 SControl 310)
Oct 21 12:06:12 arch kernel: sd 4:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Oct 21 12:06:12 arch kernel: ata5: limiting SATA link speed to 1.5 Gbps
Oct 21 12:06:12 arch kernel: ata5: found unknown device (class 0)
Oct 21 12:06:12 arch warp-svc[618]: 2024-10-21T09:06:11.347Z DEBUG tunnel_loop{protocol="wireguard"}: boringtun::noise::timers: KEEPALIVE(PERSISTENT_KEEPALIVE)
Oct 21 12:06:14 arch rtkit-daemon[1078]: Supervising 9 threads of 6 processes of 1 users.
Oct 21 12:06:14 arch rtkit-daemon[1078]: Supervising 9 threads of 6 processes of 1 users.
Oct 21 12:06:19 arch rtkit-daemon[1078]: Supervising 9 threads of 6 processes of 1 users.
Oct 21 12:06:19 arch rtkit-daemon[1078]: Supervising 9 threads of 6 processes of 1 users.
Oct 21 12:06:21 arch kernel: ata5: softreset failed (1st FIS failed)
Oct 21 12:06:21 arch rtkit-daemon[1078]: Supervising 9 threads of 6 processes of 1 users.
Oct 21 12:06:21 arch rtkit-daemon[1078]: Supervising 9 threads of 6 processes of 1 users.
Oct 21 12:06:22 arch warp-svc[618]: 2024-10-21T09:06:22.059Z DEBUG actor_connectivity::connectivity: Routes changed:
Oct 21 12:06:22 arch warp-svc[618]: NewNeighbour; Destination: 192.168.1.1;
Oct 21 12:06:22 arch kernel: ata5: found unknown device (class 0)
Oct 21 12:06:22 arch kernel: ata5: SATA link down (SStatus 0 SControl 310)
Oct 21 12:06:23 arch kernel: ata5: limiting SATA link speed to 1.5 Gbps
Oct 21 12:06:23 arch rtkit-daemon[1078]: Supervising 9 threads of 6 processes of 1 users.
Oct 21 12:06:23 arch rtkit-daemon[1078]: Supervising 9 threads of 6 processes of 1 users.
Oct 21 12:06:23 arch kernel: ata5: found unknown device (class 0)
any solution?
Offline
looks like a dying/dead drive - maybe thermal related
Offline
looks like a dying/dead drive - maybe thermal related
aw man, any way it could be faulty cable?
Offline
Did you already look at the devices SMART data? https://wiki.archlinux.org/title/S.M.A.R.T.
Offline
Did you already look at the devices SMART data? https://wiki.archlinux.org/title/S.M.A.R.T.
yes, I did a long test it didn't give any errors.
sudo smartctl -t long /dev/sdb
@yoru in ~
$ sudo smartctl -H /dev/sdd <--- name changed to sdd because it changes the name after it got disconnected and reset, restarting the computer renames it to sdb again
[sudo] password for yoru:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.11.4-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Offline
Could you please post the output of "hdparm -I /dev/sdX" against the relevant drive? This might be another case of https://lore.kernel.org/all/ZlY8SbGVMHho-dLz@ryzen.lan/
Offline
Could you please post the output of "hdparm -I /dev/sdX" against the relevant drive? This might be another case of https://lore.kernel.org/all/ZlY8SbGVMHho-dLz@ryzen.lan/
sure thing:
$ sudo hdparm -I /dev/sdd
/dev/sdd:
ATA device, with non-removable media
Model Number: ST1000VX000-1ES162
Serial Number: W4Y1QZXS
Firmware Revision: CV26
Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0x001f)
Supported: 9 8 7 6 5
Likely used: 9
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 1953525168
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 1024*1024: 953869 MBytes
device size with M = 1000*1000: 1000204 MBytes (1000 GB)
cache/buffer size = unknown
Form Factor: 3.5 inch
Nominal Media Rotation Rate: 7200
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = ?
Advanced power management level: 192
Recommended acoustic management value: 128, current value: 128
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
SET_MAX security extension
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* Media Card Pass-Through
* General Purpose Logging feature set
* 64-bit World wide name
Write-Read-Verify feature set
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* unknown 119[6]
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Gen3 signaling speed (6.0Gb/s)
* Native Command Queueing (NCQ)
* Phy event counters
* READ_LOG_DMA_EXT equivalent to READ_LOG_EXT
* DMA Setup Auto-Activate optimization
* Device-initiated interface power management
* Software settings preservation
unknown 78[7]
* SMART Command Transport (SCT) feature set
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
unknown 206[7]
unknown 206[12] (vendor specific)
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
supported: enhanced erase
100min for SECURITY ERASE UNIT. 100min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5000c5007d774edb
NAA : 5
IEEE OUI : 000c50
Unique ID : 07d774edb
Checksum: correct
Offline
btw it's not mounted rn, if that matters
Offline
aw man, any way it could be faulty cable?
well, although bad cables are always a possibility it rarely happens "from yesterday to tomorrow" without physical interaction - it's more likely a drive, the psu or the controller dies than a dumb cable
from several tests it turned out: a sata data cable either works or it does not at all
Offline
Is this issue also present for when you boot the linux-lts kernel (you can verify via "uname -r")?
Offline
Is this issue also present for when you boot the linux-lts kernel (you can verify via "uname -r")?
$sudo mount /dev/sdb2 "/run/media/yoru/Fat Fuck"
[sudo] password for yoru:
Error reading bootsector: Input/output error
Failed to sync device /dev/sdb2: No such device
Failed to mount '/dev/sdb2': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.
doesn't sound good at all..
Last edited by yorunoken (2024-10-21 11:30:35)
Offline
yorunoken wrote:aw man, any way it could be faulty cable?
well, although bad cables are always a possibility it rarely happens "from yesterday to tomorrow" without physical interaction - it's more likely a drive, the psu or the controller dies than a dumb cable
from several tests it turned out: a sata data cable either works or it does not at all
good thing I don't have a lot of important stuff in it
Last edited by yorunoken (2024-10-21 11:31:14)
Offline
And this mount error is not present when you use the linux kernel again?
But yeah, after all it might be bad hardware ..
Offline
And this mount error is not present when you use the linux kernel again?
But yeah, after all it might be bad hardware ..
it's weird, now it didn't gave a different bad block error and promptly disappeared. It looks like it's trying to do the soft reset thing again, will try with the stock kernel again.
I have another computer, so I'll try plug it in the other one soon and see what happens
Offline
okay, I managed to mount it after it reappeared, but the same thing happens. I copy some stuff to my main drive, and after a while it gets disconnected
Oct 21 14:43:44 arch kernel: ata5.00: exception Emask 0x50 SAct 0x8 SErr 0xb0802 action 0xe frozen
Oct 21 14:43:44 arch kernel: ata5.00: irq_stat 0x00400000, PHY RDY changed
Oct 21 14:43:44 arch kernel: ata5: SError: { RecovComm HostInt PHYRdyChg PHYInt 10B8B }
Oct 21 14:43:44 arch kernel: ata5.00: failed command: READ FPDMA QUEUED
Oct 21 14:43:44 arch kernel: ata5.00: cmd 60/08:18:c8:2a:e4/00:00:0d:00:00/40 tag 3 ncq dma 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error)
Oct 21 14:43:44 arch kernel: ata5.00: status: { DRDY }
Oct 21 14:43:44 arch kernel: ata5: hard resetting link
Oct 21 14:43:47 arch warp-svc[639]: 2024-10-21T11:43:47.203Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 14:43:48 arch kernel: ata5: found unknown device (class 0)
Oct 21 14:43:48 arch kernel: ata5: SATA link down (SStatus 0 SControl 300)
Oct 21 14:43:48 arch warp-svc[639]: 2024-10-21T11:43:48.534Z DEBUG actor_connectivity::connectivity: Routes changed:
Oct 21 14:43:48 arch warp-svc[639]: NewNeighbour; Destination: 192.168.1.1;
Oct 21 14:43:48 arch warp-svc[639]: 2024-10-21T11:43:48.534Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 14:43:48 arch warp-svc[639]: 2024-10-21T11:43:48.536Z DEBUG actor_connectivity::connectivity: Routes changed:
Oct 21 14:43:48 arch warp-svc[639]: NewNeighbour; Destination: 192.168.1.1;
Oct 21 14:43:48 arch warp-svc[639]: 2024-10-21T11:43:48.536Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 14:43:48 arch kernel: ata5: hard resetting link
Oct 21 14:43:52 arch kernel: ata5: found unknown device (class 0)
Oct 21 14:43:52 arch kernel: ata5: SATA link down (SStatus 0 SControl 300)
Oct 21 14:43:52 arch kernel: ata5: limiting SATA link speed to <unknown>
Oct 21 14:43:52 arch kernel: ata5: hard resetting link
Oct 21 14:43:52 arch warp-svc[639]: 2024-10-21T11:43:52.539Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 14:43:56 arch kernel: ata5: found unknown device (class 0)
Oct 21 14:43:56 arch kernel: ata5: SATA link down (SStatus 0 SControl 3F0)
Oct 21 14:43:56 arch kernel: ata5.00: disable device
Oct 21 14:43:56 arch warp-svc[639]: 2024-10-21T11:43:56.542Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 14:43:59 arch kernel: ata5: found unknown device (class 0)
Oct 21 14:43:59 arch kernel: ata5: SATA link down (SStatus 0 SControl 300)
Oct 21 14:43:59 arch kernel: ata5: limiting SATA link speed to 1.5 Gbps
Oct 21 14:44:00 arch warp-svc[639]: 2024-10-21T11:44:00.544Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 14:44:03 arch kernel: ata5: found unknown device (class 0)
Oct 21 14:44:03 arch kernel: ata5: SATA link down (SStatus 0 SControl 310)
Oct 21 14:44:03 arch kernel: ata5: limiting SATA link speed to 1.5 Gbps
Oct 21 14:44:04 arch warp-svc[639]: 2024-10-21T11:44:04.547Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read index block: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read index block: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read index block: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read index block: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read index block: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read index block: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read index block: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read index block: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read index block: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read index block: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read index block: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read index block: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read index block: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=5881 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=5899 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=5921 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=5931 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=5949 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=5974 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=5996 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=6023 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=6035 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=6058 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=6072 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=6085 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=6104 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=6125 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=6141 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=6159 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=6178 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=6196 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: Failed to read of MFT, mft=6211 count=1 br=-1: Input/output error
Oct 21 14:44:07 arch ntfs-3g[38544]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Offline
https://wiki.archlinux.org/title/Power_ … Management
Bogus DIPM "support"?
Offline
https://wiki.archlinux.org/title/Power_ … Management
Bogus DIPM "support"?
Hello, I assume you wanted me to set it to "max_performance"? Nothing has changed, except I'm misunderstanding something.
Also, an update: I transferred all my fails to my main drive, and formatted this one to an ex4 drive. Now it basically won't mount at all:
Oct 21 23:49:00 arch udisksd[36640]: Mounted /dev/sdb1 at /run/media/yoru/owo on behalf of uid 1000
Oct 21 23:49:00 arch kernel: EXT4-fs (sdb1): recovery complete
Oct 21 23:49:00 arch kernel: EXT4-fs (sdb1): mounted filesystem 3ffc189b-3661-4235-8a75-2d3adad2ad42 r/w with ordered data mode. Quota mode: none.
Oct 21 23:49:01 arch warp-svc[627]: 2024-10-21T20:49:01.865Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 23:49:03 arch warp-svc[627]: 2024-10-21T20:49:03.446Z DEBUG actor_connectivity::connectivity: Routes changed:
Oct 21 23:49:03 arch warp-svc[627]: NewNeighbour; Destination: 192.168.1.1;
Oct 21 23:49:03 arch warp-svc[627]: 2024-10-21T20:49:03.446Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 23:49:04 arch kernel: ata5.00: exception Emask 0x50 SAct 0x80300004 SErr 0x4070802 action 0xe frozen
Oct 21 23:49:04 arch kernel: ata5.00: irq_stat 0x00000040, connection status changed
Oct 21 23:49:04 arch kernel: ata5: SError: { RecovComm HostInt PHYRdyChg PHYInt CommWake DevExch }
Oct 21 23:49:04 arch kernel: ata5.00: failed command: READ FPDMA QUEUED
Oct 21 23:49:04 arch kernel: ata5.00: cmd 60/08:10:00:08:c0/00:00:07:00:00/40 tag 2 ncq dma 4096 in
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x50 (ATA bus error)
Oct 21 23:49:04 arch kernel: ata5.00: status: { DRDY }
Oct 21 23:49:04 arch kernel: ata5.00: failed command: READ FPDMA QUEUED
Oct 21 23:49:04 arch kernel: ata5.00: cmd 60/08:a0:00:08:80/00:00:06:00:00/40 tag 20 ncq dma 4096 in
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error)
Oct 21 23:49:04 arch kernel: ata5.00: status: { DRDY }
Oct 21 23:49:04 arch kernel: ata5.00: failed command: READ FPDMA QUEUED
Oct 21 23:49:04 arch kernel: ata5.00: cmd 60/08:a8:00:08:c0/00:00:06:00:00/40 tag 21 ncq dma 4096 in
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error)
Oct 21 23:49:04 arch kernel: ata5.00: status: { DRDY }
Oct 21 23:49:04 arch kernel: ata5.00: failed command: READ FPDMA QUEUED
Oct 21 23:49:04 arch kernel: ata5.00: cmd 60/08:f8:00:08:80/00:00:07:00:00/40 tag 31 ncq dma 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error)
Oct 21 23:49:04 arch kernel: ata5.00: status: { DRDY }
Oct 21 23:49:04 arch kernel: ata5: hard resetting link
Oct 21 23:49:07 arch warp-svc[627]: 2024-10-21T20:49:07.448Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 23:49:08 arch kernel: ata5: found unknown device (class 0)
Oct 21 23:49:08 arch kernel: ata5: SATA link down (SStatus 0 SControl 300)
Oct 21 23:49:08 arch warp-svc[627]: 2024-10-21T20:49:08.996Z DEBUG actor_connectivity::connectivity: Routes changed:
Oct 21 23:49:08 arch warp-svc[627]: NewNeighbour; Destination: 192.168.1.1;
Oct 21 23:49:08 arch warp-svc[627]: 2024-10-21T20:49:08.996Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 23:49:08 arch warp-svc[627]: 2024-10-21T20:49:08.997Z DEBUG actor_connectivity::connectivity: Routes changed:
Oct 21 23:49:08 arch warp-svc[627]: NewNeighbour; Destination: 192.168.1.1;
Oct 21 23:49:08 arch warp-svc[627]: 2024-10-21T20:49:08.997Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 23:49:09 arch kernel: ata5: hard resetting link
Oct 21 23:49:09 arch systemd[754]: Started kitty child process: 37338 launched by: 37319.
Oct 21 23:49:12 arch kernel: ata5: found unknown device (class 0)
Oct 21 23:49:12 arch kernel: ata5: SATA link down (SStatus 0 SControl 300)
Oct 21 23:49:12 arch kernel: ata5: limiting SATA link speed to <unknown>
Oct 21 23:49:12 arch kernel: ata5: hard resetting link
Oct 21 23:49:13 arch warp-svc[627]: 2024-10-21T20:49:13.000Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 23:49:16 arch kernel: ata5: found unknown device (class 0)
Oct 21 23:49:16 arch kernel: ata5: SATA link down (SStatus 0 SControl 3F0)
Oct 21 23:49:16 arch kernel: ata5.00: disable device
Oct 21 23:49:16 arch kernel: sd 4:0:0:0: rejecting I/O to offline device
Oct 21 23:49:16 arch kernel: I/O error, dev sdb, sector 973342720 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2
Oct 21 23:49:16 arch kernel: Buffer I/O error on dev sdb1, logical block 121667584, lost sync page write
Oct 21 23:49:16 arch kernel: JBD2: I/O error when updating journal superblock for sdb1-8.
Oct 21 23:49:16 arch kernel: Aborting journal on device sdb1-8.
Oct 21 23:49:16 arch kernel: I/O error, dev sdb, sector 973342720 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2
Oct 21 23:49:16 arch kernel: I/O error, dev sdb, sector 973342720 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2
Oct 21 23:49:16 arch kernel: Buffer I/O error on dev sdb1, logical block 121667584, lost sync page write
Oct 21 23:49:16 arch kernel: JBD2: I/O error when updating journal superblock for sdb1-8.
Oct 21 23:49:17 arch warp-svc[627]: 2024-10-21T20:49:17.003Z WARN network_info::linux::dns_manager::dns_owner: Could not determine resolv.conf file owner: No comment line contained an owner slug
Oct 21 23:49:20 arch kernel: ata5: found unknown device (class 0)
Oct 21 23:49:20 arch kernel: ata5: SATA link down (SStatus 0 SControl 300)
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=15s
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#2 Sense Key : Illegal Request [current]
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#2 Add. Sense: Unaligned write command
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#2 CDB: Read(10) 28 00 07 c0 08 00 00 00 08 00
Oct 21 23:49:20 arch kernel: I/O error, dev sdb, sector 130025472 op 0x0:(READ) flags 0x83700 phys_seg 1 prio class 0
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#20 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=15s
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#20 Sense Key : Illegal Request [current]
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#20 Add. Sense: Unaligned write command
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#20 CDB: Read(10) 28 00 06 80 08 00 00 00 08 00
Oct 21 23:49:20 arch kernel: I/O error, dev sdb, sector 109053952 op 0x0:(READ) flags 0x83700 phys_seg 1 prio class 0
Oct 21 23:49:20 arch kernel: I/O error, dev sdb, sector 130025472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#21 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=15s
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#21 Sense Key : Illegal Request [current]
Oct 21 23:49:20 arch kernel: EXT4-fs error (device sdb1): ext4_wait_block_bitmap:582: comm ext4lazyinit: Cannot read block bitmap - block_group = 496, block_bitmap = 16252928
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#21 Add. Sense: Unaligned write command
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#21 CDB: Read(10) 28 00 06 c0 08 00 00 00 08 00
Oct 21 23:49:20 arch kernel: I/O error, dev sdb, sector 113248256 op 0x0:(READ) flags 0x83700 phys_seg 1 prio class 0
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#31 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=15s
Oct 21 23:49:20 arch kernel: I/O error, dev sdb, sector 2048 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#31 Sense Key : Illegal Request [current]
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#31 Add. Sense: Unaligned write command
Oct 21 23:49:20 arch kernel: I/O error, dev sdb, sector 2048 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] tag#31 CDB: Read(10) 28 00 07 80 08 00 00 00 08 00
Oct 21 23:49:20 arch kernel: Buffer I/O error on dev sdb1, logical block 0, lost sync page write
Oct 21 23:49:20 arch kernel: I/O error, dev sdb, sector 125831168 op 0x0:(READ) flags 0x83700 phys_seg 1 prio class 0
Oct 21 23:49:20 arch kernel: EXT4-fs (sdb1): I/O error while writing superblock
Oct 21 23:49:20 arch kernel: EXT4-fs (sdb1): Remounting filesystem read-only
Oct 21 23:49:20 arch kernel: ata5: EH complete
Oct 21 23:49:20 arch kernel: ata5.00: detaching (SCSI 4:0:0:0)
Oct 21 23:49:20 arch kernel: ata5: limiting SATA link speed to 1.5 Gbps
Oct 21 23:49:20 arch kernel: sd 4:0:0:0: [sdb] Synchronizing SCSI cache
Oct 21 23:49:20 arch kernel: EXT4-fs (sdb1): unmounting filesystem 3ffc189b-3661-4235-8a75-2d3adad2ad42.
Oct 21 23:49:20 arch kernel: Buffer I/O error on dev sdb1, logical block 0, lost sync page write
Oct 21 23:49:20 arch kernel: EXT4-fs (sdb1): I/O error while writing superblock
Last edited by yorunoken (2024-10-21 21:04:21)
Offline
Primarily to check whether it was set to med_with_dipm
Oct 21 23:49:20 arch kernel: Buffer I/O error on dev sdb1, logical block 0, lost sync page write
Oct 21 23:49:20 arch kernel: EXT4-fs (sdb1): I/O error while writing superblock
it failed to write the FS which is now somehow corrupted, but the main issue remain the
Oct 21 23:49:04 arch kernel: ata5: SError: { RecovComm HostInt PHYRdyChg PHYInt CommWake DevExch }
Oct 21 23:49:04 arch kernel: ata5.00: failed command: READ FPDMA QUEUED
Oct 21 23:49:04 arch kernel: ata5.00: cmd 60/08:10:00:08:c0/00:00:07:00:00/40 tag 2 ncq dma 4096 in
res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x50 (ATA bus error)
Oct 21 23:49:04 arch kernel: ata5.00: status: { DRDY }
If it's not ALPM (nb. that writing into /sys/class/scsi_host/… is transient and won't survive reboots, also check the LTS kernel behavior) check the cable (notably if you've moved or tampered w/ the hardware) either the ATA bus or the drive controller are going down.
You basically want to check whether the drive is ok on a different ATA port resp. in a different system.
Also, for good measure
SMART overall-health self-assessment test result: PASSED
That's borderline meaninless, post the output of "smartctl -a" on the device.
Offline
Primarily to check whether it was set to med_with_dipm
Oct 21 23:49:20 arch kernel: Buffer I/O error on dev sdb1, logical block 0, lost sync page write Oct 21 23:49:20 arch kernel: EXT4-fs (sdb1): I/O error while writing superblock
it failed to write the FS which is now somehow corrupted, but the main issue remain the
Oct 21 23:49:04 arch kernel: ata5: SError: { RecovComm HostInt PHYRdyChg PHYInt CommWake DevExch } Oct 21 23:49:04 arch kernel: ata5.00: failed command: READ FPDMA QUEUED Oct 21 23:49:04 arch kernel: ata5.00: cmd 60/08:10:00:08:c0/00:00:07:00:00/40 tag 2 ncq dma 4096 in res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x50 (ATA bus error) Oct 21 23:49:04 arch kernel: ata5.00: status: { DRDY }
If it's not ALPM (nb. that writing into /sys/class/scsi_host/… is transient and won't survive reboots, also check the LTS kernel behavior) check the cable (notably if you've moved or tampered w/ the hardware) either the ATA bus or the drive controller are going down.
You basically want to check whether the drive is ok on a different ATA port resp. in a different system.Also, for good measure
SMART overall-health self-assessment test result: PASSED
That's borderline meaninless, post the output of "smartctl -a" on the device.
Alright, I'll check for the cables and other things you've mentioned tomorrow (thank you!)
Here's the output of smartctl -a
@yoru in ~
? sudo smartctl -a /dev/sdb
[sudo] password for yoru:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.11.4-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Surveillance
Device Model: ST1000VX000-1ES162
Serial Number: W4Y1QZXS
LU WWN Device Id: 5 000c50 07d774edb
Firmware Version: CV26
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database 7.3/5528
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Tue Oct 22 03:06:10 2024 +03
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: ( 80) 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: ( 105) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x10b9) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control 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 110 099 006 Pre-fail Always - 28883384
3 Spin_Up_Time 0x0003 099 097 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 081 081 020 Old_age Always - 19995
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 080 060 030 Pre-fail Always - 103821848
9 Power_On_Hours 0x0032 083 083 000 Old_age Always - 15690
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 097 097 020 Old_age Always - 3216
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 - 17180590091
189 High_Fly_Writes 0x003a 021 021 000 Old_age Always - 79
190 Airflow_Temperature_Cel 0x0022 072 052 045 Old_age Always - 28 (Min/Max 28/30)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 094 094 000 Old_age Always - 13959
193 Load_Cycle_Count 0x0032 090 090 000 Old_age Always - 20028
194 Temperature_Celsius 0x0022 028 048 000 Old_age Always - 28 (0 15 0 0 0)
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 - 3
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 Extended offline Interrupted (host reset) 00% 15641 -
# 2 Short offline Completed without error 00% 15640 -
# 3 Conveyance offline Completed without error 00% 14542 -
# 4 Short offline Completed without error 00% 14542 -
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.
The above only provides legacy SMART information - try 'smartctl -x' for more
Offline
Drive looks ok, it's very likely a bus problem.
Offline
Drive looks ok, it's very likely a bus problem.
That's great to hear! I still need to check for the other stuff you've mentioned, correct?
Last edited by yorunoken (2024-10-22 13:36:58)
Offline
Correct.
It's the cable or the port or the power cable or your motherboard.
You can rule out software/kernel related issues (bus configuration) by eg. running some live distro.
Offline
as it was the issue on several topics: it can be an issue of the power supply
if possible try to test a connection on another supply rail
Offline
Pages: 1