Fix command only trying to fix one block

Question

Fix command only trying to fix one block

lamarios opened this issue 6 years ago · 13 comments

I have a not very healthy disk with a lot of bad blocks (22616) but when i run the fix command it only seems to be fixing the first block of my bad block file:

sudo bbf -i 3t.WMC4N0J3YP10 -c my-captcha  fix  /dev/sdc
Reading block 5694484064 succeeded (1 attempts)
Writing block 5694484064 succeeded (1 attempts)

and then it mounts the drive. Is it expected behavior ?

Answer 1 · 2018-12-12T04:10:19.000Z

Sounds like something is automatically mounting the device. bbf is definitely not doing that. Try removing it from fstab and trying again.

Answer 2 · 2018-12-12T04:25:21.000Z

Weird, I removed the drive from fstab and also the fstab entry for the mergerfs pool it belongs to but it's still mounting on its own.

Answer 3 · 2018-12-12T11:52:44.000Z

What distro? Is it mounting to /media/${USER}/ ? If so then it could be the desktop's filemanager trying to mount it. Might reset when bbf is trying to write to it and it sees it again. Would need to turn that off (or wipe the beginning of the drive so it can't mount it.

Answer 4 · 2018-12-12T12:18:11.000Z

Using Arch as a server without much installed on it so there are no desktop environment. It is mounted in the /mnt folder. The interesting part is that it mounts it back at the proper mount point even if the fstab entre is commented.

…

On Wed, 12 Dec 2018 at 7:52 PM, trapexit ***@***.***> wrote: What distro? Is it mounting to /media/${USER}/ ? If so then it could be the desktop's filemanager trying to mount it. Might reset when bbf is trying to write to it and it sees it again. Would need to turn that off (or wipe the beginning of the drive so — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABIycw8ZRYG6oDnl35DBTd5WbLNrVsDJks5u4O4MgaJpZM4ZOq1v> .

Answer 5 · 2018-12-12T12:52:36.000Z

https://dominicm.com/mount-filesystem-partitions-in-arch-linux/

via systemd maybe?

Answer 6 · 2018-12-12T13:48:53.000Z

I’ll check that out on my side as it seems that it’s not related to bbf. Thanks !

…

On Wed, 12 Dec 2018 at 8:52 PM, trapexit ***@***.***> wrote: https://dominicm.com/mount-filesystem-partitions-in-arch-linux/ via systemd maybe? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABIyc3N-jNLt5jLyBERTSK524im_ctbsks5u4PwUgaJpZM4ZOq1v> .

Answer 7 · 2018-12-13T02:02:19.000Z

Well, I edited the fstab and rebooted to make sure and when i run the bbf command it will stop at the same state as before but the disk won't be automatically mounted this time.

Could it be because my drive is in a really bad shape ? I actually noticed bad sectors on this drive before so what i did is try to read every blocks using dd if=/dev/sdc of=/dev/null to see what is the first failing block and create a partition from beginning to before that particular block so that there are no actual partition on the bad blocks.

Does BBF needs to have a partition on the blocks to be working ? If yes then that might be why.

Answer 8 · 2018-12-13T04:06:21.000Z

No, bbf works with the block device. It doesn't care at all.

What do you mean it stops? It exits? How did you create the block list? Does scanning work?

Answer 9 · 2018-12-13T04:18:12.000Z

The only output I get from the fix command is what I posted originally it runs on the first block of my bad block file then stops, no error whatsoever. The scan command works, that’s how I got the bad block file.

…

On Thu, 13 Dec 2018 at 12:06 PM, trapexit ***@***.***> wrote: No, bbf works with the block device. It doesn't care at all. What do you mean it stops? It exits? How did you create the block list? Does scanning work? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABIyc3M_tYjKftvU0HgZaYmh9hhvw_Iqks5u4dI9gaJpZM4ZOq1v> .

Answer 10 · 2018-12-13T04:39:37.000Z

It's a bug. Fix incoming.

Answer 11 · 2018-12-13T04:48:15.000Z

Grab the latest. Should work. Sorry about that. Clearly didn't test it after changing things last time.

Answer 12 · 2018-12-13T05:43:29.000Z

Works great, thanks !

Answer 13 · 2018-12-13T23:29:05.000Z

Cool. Let me know if you have any more issues, questions, or suggestions.