You are not logged in.
Pages: 1
I have a 4TB Toshiba drive (N300) in my Computer mounted via NTFS-3g. The drive isn't that old and never gave me Issues. Smart is looking alright too. Though i now saw that whenever i suspend the system i'd get the error "softreset failed (device not ready)" within my journal. I googled and most i have read is about failing hardware so i'm now somewhat concerned. I didn't actually notice any issues and the Error only shows up in the Journal after system woke up after it was suspended. I'll post a small log below..
However what i found when googling the drive is some Firmware Update that states:
"Optimized the timing of SATA negotiation at power-on to allow some specific systems to recognize the HDD after resuming the system from sleep."
Could that be the solution for this or is this about something else? I never was updating firmware on a HDD before so if that is unlikely to fix the error i'd rather skip this step.
Feb 18 16:37:26 Linux kernel: ata3.00: Entering standby power mode
Feb 18 16:37:26 Linux kernel: ata3: SATA link down (SStatus 0 SControl 300)
Feb 18 16:37:29 Linux kernel: ata3: link is slow to respond, please be patient (ready=0)
Feb 18 16:37:34 Linux kernel: ata3: found unknown device (class 0)
Feb 18 16:37:34 Linux kernel: ata3: softreset failed (device not ready)
Feb 18 16:37:36 Linux kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 18 16:37:36 Linux kernel: ata3.00: configured for UDMA/133
Feb 18 17:49:38 Linux kernel: ata3: SATA max UDMA/133 abar m131072@0xfce80000 port 0xfce80200 irq 40 lpm-pol 0
Feb 18 17:49:38 Linux kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 18 17:49:38 Linux kernel: ata3.00: ATA-10: TOSHIBA HDWG440, 0601, max UDMA/133
Feb 18 17:49:38 Linux kernel: ata3.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
Feb 18 17:49:38 Linux kernel: ata3.00: Features: NCQ-prio
Feb 18 17:49:38 Linux kernel: ata3.00: configured for UDMA/133Last edited by Oddwierdo (2024-02-18 16:24:35)
Offline
Do you note any actual issues apart from the message? I'd ignore it
Offline
No, nothing i noticed it by accident though since i was afraid of data-loss i checked what it might be. It's not super important data on that drive.. though of course i wouldn't like losing it. But just getting a new HDD because a random Error also seem a bit overkill. That is why i wonder if the firmware update i mentioned could be the exact issue. Though i have no clue about that hardware stuff and if the fix they mention could be related. It just sounds "similar" to me lol. That is why i'm asking maybe someone can make more out of it.
Offline
Run a smart test[1] on the disk and after the needed self test time has elapsed post/investigate the output of "smartctl -a" s we might be able to asses how it's looking. GEnerally speaking some SATA errors can be somewhat normal depending on connector/board or so, but if it can safely recover I'd not worry too much.
Offline
Pages: 1