[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

2447.0. "badblocks and harddrives" by FSCORE::KAYE (He who dies with the most toys is dead) Thu Apr 06 1989 22:24

    Does AmigaDos handle bad blocks on a harddrive? I have 2 10M which
    a friend had already formatted. I am getting read/write errors on
    1 of them. He says that sometimes after he formatted it, it wouldn't
    come back 'initialized', so he would use the 'quick' option. When
    it didn't come back 'initialized' - was this because it detected some
    bad blocks? Should i go thru the whole process again? Is there a
    program out there to exercise a harddrive with different patterns
    and log the bad blocks if format doesn't? These are ST506 drives
    with a 2090A on an Amiga 2000.
    
     mark
T.RTitleUserPersonal
Name
DateLines
2447.1more questionsFSCORE::KAYEHe who dies with the most toys is deadMon Apr 10 1989 16:239
    PREP seems to handle the bad blocks if you answer Y to the bad blocks
    question. It prompts you for Cylinder, Track & Offset. What is Offset?
    Is it the # of bytes from the index mark? If you buy a drive it
    has bad block info as: Cylinder, Track & Bytes. Are Bytes the same
    as Offset? While formatting, can you get it to print out the bad
    block info? Even if it is successful after a few retries i would
    rather flag the block as bad, than trust it.
    
     mark
2447.2Seagate ST225 bad spotCSSE32::SMITHReality, just a visible imagination?Fri Sep 28 1990 18:3318
This is a bit of an old note but the topic applies.

For some time now I have had a bad stop on my ST225 HD.  The last time it reared 
it's ugly head I did a complete backup, PREP and reformat.  This seemed to clear
it up although I do not believe the PREP/reformat added a new bad spot in the 
drive's table.  

Now after several months it's shown up again.  Once it has failed, it fails 
everytime the spot is accessed. I renamed the failing file to BAD.BLOCK and 
and copied a backup file from floppy.

Now this has resolved my problem, however it wastes a rather large chunk of
disk space.

Does anyone know how I could find the head/sector/offset values so I can enter
this into the drive's bad block table during a re-PREP?

...Ed
2447.3Try Quarterback ToolsCGOA01::KASPERMon Jan 07 1991 01:137
    Hi Ed,
    
    A little late but  Quarterback Tools has a Bad Block locator.  From
    what I've hard it works quite well.  Drop a note to Wayne O.
    
    All the best,
    Dave