The badblocks process becomes stuck until the USB connection is disconnected, and it starts outputting errors.Įventually, all USB ports become unresponsive. However, when attempting to write the block device, the error occurs. Initially, it is detected by lsusb, and the block device is recognized by fdisk. Upon booting into Arch Linux and reaching the desktop, I plug in the USB. This HDD functions properly without the bridge when connected via a SATA interface on another Arch Linux computer. However, when attempting to read the data up to a certain point, the same issue as below occurs. Previously, it could be mounted normally on my Arch Linux, allowing me to view the file list. This HDD functions properly on a Windows system with the same hardware (laptop+bridge+HDD) and has been checked by Windows software to ensure there are no bad blocks. I'm attempting to connect a 2.5" HDD to my laptop using a USB to ATA bridge (152d:a578 JMicron). The USB to ATA bridge fails to work when writing the disk, resulting in all USB ports becoming unresponsive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |