#Bad HDD or just the communication via USB3? kernel auto-adding bad blocks to that list in ext3?

1 messages · Page 1 of 1 (latest)

languid tartan
#

Before posting the log: I had resets on USB when using USB3 for a very long time.
I'm currently using a 6.1.97-gentoo built via genkernel IIRC
My main question is: If the kernel recognizes a bad sector during reading on an ext3 filesystem: Would it add that sector to the list of bad blocks? Or is the only way to fill this list via fsck.ext3 -c ?

Oh before I forget: I've been using gentoo for a very long time. Just this discord-server is new to me. So I don't really know what flags to set to this (or any other) post. I hope "Hurt me plenty" specifies a question from somebody like me.
Now the log coming about every 30 seconds while I'm trying to do some sequential IO:

May 1 18:13:51 my-host kernel: sd 6:0:0:0: [sde] tag#0 CDB: Read(10) 28 00 0c 41 90 e0 00 00 20 00
May 1 18:13:51 my-host kernel: I/O error, dev sde, sector 1644988160 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2
May 1 18:14:23 my-host kernel: usb 4-2: reset SuperSpeed USB device number 31 using xhci_hcd
May 1 18:14:23 my-host kernel: sd 6:0:0:0: [sde] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s
May 1 18:14:23 my-host kernel: sd 6:0:0:0: [sde] tag#0 CDB: Read(10) 28 00 0c 42 57 40 00 00 20 00
May 1 18:14:23 my-host kernel: I/O error, dev sde, sector 1645394432 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 2
etc

#

In case my title is too long: The other question was: Is this JUST a communication problem instead of bad sectors? I expect that

amber raptor
#

Could be a few things

#

I'll list some things to check

#
  • bad USB cable
  • enclosure connecter broken
  • not getting enough power
#

The easiest way to rule is to connect it internally and see if it the issues is still there