Author Topic: What can I do,?? (Read 2892 times)

nikki · « **on:** March 28, 2003, 06:14:00 PM »

Hi, been having trouble with computer, G4, with WD 8meg Cache harddrive. Been Running DiskWarrior at least once a week. Run DiskWarrior and got this today,

DiskWarrior has successfully built a new optimized directory for the disk named "Kev's OSX." The new directory is ready to replace the original directory.

All file and folder data was easily located.

Comparison of the original and replacement directories indicates that there will be changes to the number, the contents and/or the attributes of the files and folders. It is recommended that you preview the replacement directory and examine the items listed below.

? Errors, if any, in the directory structure such as tree depth, header node, map nodes, node size, node counts, node links, indexes and more have been repaired.

? 2 folders had an incorrect item count that was repaired.

? 2 files/folders had to be moved to the "Rescued Items" folder.

? Incorrect values in the Volume Information were repaired.

? The Boot Blocks are damaged and will be repaired after replacing the directory.

? 1 folder will have more items.

? 1 folder will have fewer items.

Disk Information:

Format: Mac OS Extended
Where: (ATA Bus 2 Dev 1, v3.3)
Driver: ".ATADisk"
Block Size: 4 K
Files: 178,537
Folders: 38,850
Free Space: 8.54 GB
Disk Sectors: 64,736,816

Time: 3/28/03 6:00:33 PM
DiskWarrior Version: 2.1

The Bad BootBlocks come back all the time, what can I do to correct this for good.

chuckwagen · « **Reply #1 on:** March 28, 2003, 06:22:00 PM »

Do you have anything out of the ordinary in your startup items folder? Are you starting in OS9 or 10?

nikki · « **Reply #2 on:** March 28, 2003, 06:28:00 PM »

Hi, I'm using OSX and have, DeskTopCalender in the Loggin application.

Thanks for more info

Gary S · « **Reply #3 on:** March 28, 2003, 09:16:00 PM »

Have you run Norton Utilities? I ran it the other day and afterwords ran DFA just to see what it said. I had errors and DFA wouldn't take care of them so I ran DiskWarrior and it repaired them. That was on OS9.1 though.

Norton's isn't working quite right.

kelly · « **Reply #4 on:** March 29, 2003, 10:09:00 AM »

Well. You could backup all your stuff and Reformat the Drive.

How big is the Drive?

How old is it?

nikki · « **Reply #5 on:** March 29, 2003, 10:21:00 AM »

Hi,
The drive is only a few months old, Its a WD 80gig, 8meg cache.

I used carpon copy cloner, to put it on the old drive and erased the WD digital drive, I didn't "0" all data, just erased it.

It comes back every week when I check it with DiskWarrior.
I'll check with Norton and get back to you guys.

Thanks

kelly · « **Reply #6 on:** March 29, 2003, 10:28:00 AM »

Erased what? The new "problem" Drive?

nikki · « **Reply #7 on:** March 29, 2003, 11:44:00 PM »

Erased the WD drive, the one thats giving me the Bad Blocks.

kelly · « **Reply #8 on:** March 29, 2003, 12:58:00 PM »

Ok. What did you Erase it with?

You may want to do the write zero option.

"Reallocation (sparing) of bad blocks that the ATA drive tracks will occur when the block is subsequently written to. Thus the best way to force the drive to reallocate bad blocks is to initialize using the write zeros feature. Use Test Disk to verify surface integrity only. Given this strategy, there on occasion may be a need to initialize using write zeros, verify using Test Disk and if any errors occur, attempt to reinitialize using write zeros again."

"Selecting initialize without selecting either low level format, write zeros or both for an SCSI drive, or without selecting write zeros for an ATA drive will only write zeros to the first 1000 blocks of the drive. It will also write the partition map area including drivers (generally blocks 0 through 700 ), and in cases of Mac OS Standard or Mac OS Extended partitions, call on the operating system to initialize each volume and write the appropriate volume information."

http://docs.info.apple.com/article.html?artnum=24764

If you used Jag's Disk Utility to Erase the Drive this may or may not still apply.

I say better to make sure.

Gary S · « **Reply #9 on:** March 29, 2003, 01:27:00 PM »

Nikki,

What I was getting at about mentioning Norton's is that I have read that it doesn't get along with OSX very well. So I don't know if you want to run it or not.

Bernie · « **Reply #10 on:** March 30, 2003, 09:02:00 PM »

I love Os 9.2.2 Ease of use for the Mac user. Nothing hiding Just simple Os. X ? Hmm Learning commands! WOW sounds just like Windows. like I've said a million times.
APPLE$OFT It's a $$$$ thing

nikki · « **Reply #11 on:** March 31, 2003, 11:32:00 PM »

quote:
Originally posted by chuckwagen:
Do you have anything out of the ordinary in your startup items folder? Are you starting in OS9 or 10?

Why would something in your startup/login item give you bad blocks.???

Thanks kelly, I wrote zero's and it runs good so far.

tacit · « **Reply #12 on:** March 31, 2003, 02:03:00 PM »

"Bad blocks" and "bad boot blocks" are not the same thing,a nd are not even remotely similar or related in any way, even though it sounds like they might be the same thing.

A "bad block" is caused by physical damage to the platter inside of a hard drive. It is a physical flaw in the surface of a disk. You can't write information onto it.

"Bad boot blocks" means that the information written in the outer edge of the disk is not recognized by Disk Warrior. When you turn on your computer, it reads the information written in the very first part of the disk drive, and assumes that this information is a computer program. the computer executes whatever it sees.

This tiny computer program is the "boot code." It instructs the computer how to load and run the operating system. The place on the disk where the boot code is stored is the "boot block."

When your computer starts up, it loads the information into memory, then runs it, and by running it, it loads and runs the operating system. DiskWarrior looks at the information stored in the boot blocks and compares it to the information on a disk when it is shipped from Apple.

Changes to the operating system may change the boot code. Let's say Apple releases an operating system, then Alsoft releases DiskWarrior. then let's say Apple changes the operating system, and changes the boot code. Software update tells you a new version of the operating system is available. You download it and install it. It changes the information in the boot blocks. DiskWarrior doesn't know that Apple has changed the boot code. DiskWarrior thinks the information in the boot blocks is wrong.

It's a harmless "error." Ignore it.

kelly · « **Reply #13 on:** March 31, 2003, 08:35:00 PM »

Thanks for the clarification tacit.

So the moral is to use the most recent version you can.

Do you other people who use Disk Warrior run into this?

Buck · « **Reply #14 on:** April 02, 2003, 11:53:00 PM »

I've never run into this problem. But then I've never known about it. Now that I've read about it here, I most likely will. ;-)

News:

Author Topic: What can I do,?? (Read 2892 times)