-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"ERROR - runtime: error when scanning drive [Input/output error]" instead deetcting bad block #29
Comments
Curious. bbf is issuing bog standard ATA commands as far as I know. I'll have to investigate more. |
I'm getting the same error message but my dmesg looks a bit different. Disk is also having Offline_Uncorrectable and Current_Pending_Sector values >0. It's plugged in straight to a mainboard sata port (intel z370 chipset).
|
That's a very different error. As it says:
How many logical blocks is the device? It's saying that 207726777 is bad. The kernel always lists errors it gets when the device reports it. |
I'm sorry with the same error message I meant that bbf aborts the scan with "ERROR - runtime: error when scanning drive [Input/output error]" as well when it reaches the faulty sector. |
What settings are you using? |
I wanted to scan for all bad blocks (SMART reports multiple) with |
OK. There is a big difference between |
Hello!
I'd like to ask you how to deal with situation like below.
I run bbf against HDD, hdd is connected to motherboard using controller H310 flashed to IT firmware (
)
Hdd has non zero values in Offline_Uncorrectable, Current_Pending_Sector and Reallocated_Sector_Ct fields.
In dmesg I have:
kernel 5.9.0
Is t something you can improve in bbf, maybe I should native SATA controller to connect hdd to motherboard? Maybe something else?
The text was updated successfully, but these errors were encountered: