ZFS one of the pools gets suspended even under activity

I have 4TB usb hdd ( spinning disk ) and starting to have issues. Sometimes it gets suspended from inactivity and sometimes it gets suspended when its active ( copy paste from one pool to my 4TB pool )
Is this a sign that my 4TB is almost "kaput"?
Every time it gets suspended i have to hard-reset my pc as "shutdown -r now" wont work.
When i run zpool status i get this:
scan: scrub repaired 0B in 00:00:01 with 0 errors on Mon Aug 19 10:06:12 2024
sometimes its 1B sometimes its 0.
 
Explain in more detail what "suspended" means. Is this a file system software concept: Is it unmounted, or the pool exported? Or is it it a hardware/communication concept, like the OS loses communication (the device vanishes), or the disk itself goes to sleep? Please give us more details, and perhaps include relevant lines from dmesg, or /var/log/messages, or commands.

The zpool scrub indicates that there are no data or metadata problems. The disk drive might have an internal problem, which smartctl can tell us more about.
 
Dont recall its state or status whre it shows SUSPENDED when i check zpool status.
I have exported my pool for now as i have some work to do.
The disk drive might have an internal problem, which smartctl can tell us more about.
Thanks for it, going to do some check up.
 
By the way, "don't recall its state or status" is really hard to help debug. Anyway, the "suspended" is referring to its zpool status. And that typically means that ZFS is unable to communicate with the disk. If instead ZFS was getting IO errors or corrupted data, it would show a status of "degraded"; but with IO errors, it can be quite hard for a file system to distinguish between errors that originate within the disk drive, and communication errors that make reaching the drive impossible.

Given that it is likely communication errors, doing smartctl is not a high priority. I would first look at dmesg and other logs for device connection and disconnection.
 
By the way, "don't recall its state or status" is really hard to help debug. Anyway, the "suspended" is referring to its zpool status. And that typically means that ZFS is unable to communicate with the disk. If instead ZFS was getting IO errors or corrupted data, it would show a status of "degraded"; but with IO errors, it can be quite hard for a file system to distinguish between errors that originate within the disk drive, and communication errors that make reaching the drive impossible.

Given that it is likely communication errors, doing smartctl is not a high priority. I would first look at dmesg and other logs for device connection and disconnection.
Im actually doing smartctl long test .. will be over in 6h. ( 500 minutes for 4TB disk )
 
Back
Top