? bad block utility

? bad block utility

Post by Bob Danie » Wed, 27 Sep 1995 04:00:00

Sorry to reply to my own post, but its right in the SCO manual. The
utility is badtrk.

>We have an SCO UNIX box that's developed a bad block on its IDE disk.  As
>soon as the system hits multi-user mode, it generates the message

>Warning: wd: on fixed disk ctlr=0 dev=1/40 block=70815 cmd=00000020
>status=00005910, sector=213966, cylinder/hd=212/4

>over and over ,,,,

>Anybody know of a utility that will let me mark the block bad and prevent
>the system from checking it?

bob daniel                      | Network Commmunications Group, Inc.

http://www.ncgi.com             | fax:   719.634.6110

1. Finding out if there are bad blocks in the bad blocks list


I'm trying to find out whether there are any bad blocks in the ext2fs
bad block list. I think there might be, because I had a whole lot of
ext2fs error messages popping up during a compile, and when I removed
the directory I was working with and ran e2fsck -cf /dev/hdc6, it told
me the filesystem was modified, even though none of the regular checks
had failed (I'd previously run e2fsck -f /dev/hdc6, so all the duplicate
blocks and unattached inodes and stuff had been sorted out). I think the
drive might still be under warranty, so if there are bad blocks I'll
take it back.

Please remove the ".nospam" from my address before replying
| Bruce Merry (Entropy)            | bmerry at iafrica dot com       |
| Proud user of Linux!             | http://www.cs.uct.ac.za/~bmerry |
|               When you make your mark on the world,                |
|                 watch out for people with erasers.                 |

2. Can't get DHCP to work!

3. How do you add a bad block to e2fs bad block list?

4. getty and modem

5. My bad blocks aren't getting marked bad ...

6. Hardware Recommendations PLEASE.

7. Bad magic number in super-block / Group descriptors look bad


9. Non blocking socket blocks; says 'read would block' ?

10. 014 Bad Bad Bad !!! for Linux

11. Bad, bad, bad VM behaviour in 2.4.10

12. Bad driver...Bad bad driver

13. Bad, bad, bad error...