Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Mac OS X > bad block(s) - how to recover?

bad block(s) - how to recover?
Thread Tools
Junior Member
Join Date: Feb 2003
Location: Ann Arbor, Michigan
Status: Offline
Reply With Quote
Jun 26, 2003, 10:32 PM
 
It seems my disk has one or more bad blocks. They seem to be in area where Mail has stored its Inbox (~/Library/Mail/account_name/INBOX.mbox). This has over 1000 messages and is over 80 MB in size. This first showed up when Mail tried to compact the mailbox - it failed with an error message that the disk might be full. It isn't - over 1.5 GB still free. Ran Norton Disk Doctor (ver 6.0.2), which fixed a couple of minor errors but always hangs when doing the media check. The manual says this could be the result of a bad block. Ran Disk Warrior verision 3. It also repaired a couple of minor errors, found no other problems, but the error persists. So how can I recover the data from the INBOX.mbox file? It has been possible to move messages one-by-one to a new mailbox but there are a lot of messages. Moving large blocks of messages causes Mail to crash.

Thanks for any help!
     
Professional Poster
Join Date: Apr 2001
Location: Capital city of the Empire State.
Status: Offline
Reply With Quote
Jun 27, 2003, 12:09 AM
 
I believe that running a defragmenting program will correct the problem by remapping your drive to avoid the bad blocks.
The safest defragger currently available is PlusOptimizer, which is included on the DiskWarrior 2.1 CD (no OS X version is yet available). Although this utility runs in OS 9, it works well on OS X disks. I have used it on my own OS X partition a couple of times.
Norton Speed Disk and Drive 10's defragger both leave you vulnerable to severe disk damage if anything goes wrong during the defragging process. PlusOptimizer does not.
/mal
"I sentence you to be hanged by the neck until you cheer up."
MacBook Pro 15"/2.4 GHz Intel Core 2 Duo/4 GB DDR2 SDRAM/200 GB Hitachi HD/8x SuperDrive/Mac OS X 10.6.1
     
Clinically Insane
Join Date: Apr 2000
Status: Offline
Reply With Quote
Jun 27, 2003, 01:39 AM
 
If your drive is corrupted, don't defrag. Repair first.

Run DiskWarrior over the drive, that'll fix it.
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 08:07 AM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2