Stora MS2000 NAND bad blocks: libgssapi_krb5.so.2 disappeared

Today my Netgear Stora MS2000 stoped working. I connected to serial console and found that the problem is in missing library libgssapi_krb5.so.2:
...

Hi guys ,
I've bought a new laptop (Mac Book Pro on OS X Yosemite) and am trying to connect wirelessly to my Stora, where all my files are kept. I...

Similar Messages

A single bad block

Hi,
I am a Graphic Designer from Nepal. I have a single bad block on my 7 month old macbook pro 2011. It hasn't been written over yet with spare as my HD is almost full. Should i wait it to be written over with spare block or should i go on ahead with format. Will it damage more blocks if i wait? i would have returned it but it will cost me more to return it as i will have to sent it abroad as there is no apple stores here (only authorized dealers). It's a single bad block which is not that bad and can happen from the factory. I have even heard many hard disk manufacture dont even exchange it if there is just few bad blocks as it is quite normal. My main question is should i wait for bad block to be written over with spare or should i format it with zeros? thanks in advance.

You ran some driver checking software and it located a bad block, no big deal because all drives have bad blocks.
When your computer attempts to write to the bad block and can't verify it, then it writes the data to a new location and that bad block is mapped off.
This occurs automatically and requires absolutely no assistance from you what so ever.
So don't do anything, it's been all taken care off. If you do, your just wasting your time and could erase your data.
The software your running is for technical use only, just go about using your computer like before and nothing will happen from the bad block.

IMac 27" late 2012 3TB hard drive bad blocks

Hi Guys,
I just received the new iMac 27" late 2012 with 3TB hard drive and as soon as I run Drive Genius version 3.2.2 I saw that the drive has 8 bad blocks.
I tried to deleted the logical volume and reinstall the OS X 10.8.2 and after a scan I got the same 8 bad blocks. I give it another try and erase the entire 3 TB volu except the recovery partition and installed Mountain Lion and after running another Drive Genius SCAN for almost 12 hours I got 8 bad blocks again.
Called Apple Support and they are clueless about what is going on as they are not even aware that the late 2012 iMac 27" is not even in stores yet.
I was told that as long as I do not have errors within the OS X I should not worry about as he HDD is fine. I do not believe it since from my experience when you have a bad block you also have a physical damage on you disk surface.
I called Apple Support again and I was told to go to Genius Bar and have them to replace the HDD to a unit not even a week old. I think that I am going to return the unit, maybe I got a lemon and the unit got dropped during the shipping process or who knows.
I hope that this thread will help other owners to have them to run a check disk or scan disk just to make sure that they do not have a bad hard drive on their new iMac late 2012.
Again I have nothing against to anyone as I just hope that someone from Apple will find this thread and try to prevent this from happening to a large scale.
Thank you.

Colos2012 wrote:
... soon as I run Drive Genius version 3.2.2 I saw that the drive has 8 bad blocks.
Drive Genius will report bad blocks when none are present. It may even be responsible for disk corruption.
See: DriveGenius = Problem
Get rid of Drive Genius. Do not install such junk on a Mac.

How to keeps track of new coming bad blocks on a hdd

I have some 2,5 hdd lying around and wanted to test them for bad blocks and found that I can use Badblocks for this.
But how do I keep the "list" of bad blocks up-to-date if new bad blocks are detected, or is this not posseble?
Solixxx
Last edited by solixxx (2013-09-30 23:48:21)

graysky wrote:You can detect and lock out bad ones... but the danger is not knowing which good blocks will go bad in the future. I have a hdd in an old machine that has bad blocks on it... been running fine for 9+ months now after isolating them.
Exactly :-)
I've been using a drive with isolated bad blocks for over a year now, but I store only data I don't care that much about - I can re-download or recreate it.
I thought you just wanted to list the bad blocks. If you're going to reformat the device, it is the mechanism of isolating the bad blocks I wrote about, so you should be OK.
I think badblocks prevents the bad block from being used by the filesystem, but they still reside on the device, so if you run badblocks again, it should list both the old bad blocks and any new ones too.

Need to copy files from PowerBook G4 with bad blocks

Yesterday my PowerBook G4 which is about 5 years old had problems starting up. When I ran Disk Utility on it I was notified that there was a SMART problem and I should backup my data immediately. I have a lot of important data that still needs to be backed up, but I am having problems with likely bad blocks.
I have tried to backup the data two ways both using a firewire connection to my new MacBook Pro. First, I connected the computers via firewire and used the "T" option when booting my old laptop. I tried to copy the files over by clicking on the directories I need to back up and dragging them over to my new laptop. That would work okay, but when it would hit bad files, everything would freeze. My old laptop wouldn't copy over anymore and I couldn't eject the HD from my new laptop.
Then I tried using Terminal to move files over. I connected the computers in the same way as above and opened Terminal from my new laptop. After going into the directory I wanted to copy from on my old laptop, I typed in the following command,
find . -exec ditto -v {} ~/Data/M33/SE25/ \;
since I was told that might skip over the files with bad blocks and continue on. It did copy some files over, but I had the same problem again with everything freezing up.
I really would like to get as many files transferred as I can without having to do it one-by-one and restarting everything every time my old laptop freezes up. Does anyone have any suggestions how to get around the files with bad blocks or whatever might be happening to freeze up my old laptop?

I did as suggested in that I used the Terminal option and let everything run for 8 hours. Here are some of the notes I got from the system.log file. I will group together the error messages from when they actually occurred. I started the process at midnight. My apologies for some of the mistakes in the posts in the error messages. Some of the characters are messing up the way it is being viewed in the post.
+(Message at 00:46:17)+
disk1s3: I/O error
com.apple.system.fs] [DevNode /dev/disk1s3] [MountPt /Volumes/Macintosh HD 1] [FSLogMsgID 2052406730] [FSLogMsgOrder Last]
disk1s3: media is not present
disk logger: failed to open output file /Volumes/Macintosh HD 1/.fseventsd/0000000000006ca1 (Invalid argument). mount point /Volumes/Macintosh HD 1/.fseventsd
disk1s3: media is not present
0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode /dev/disk1s3] [MountPt /Volumes/Macintosh HD 1] [Path /Volumes/Macintosh HD 1/.Spotlight-V100/Store-V1/Stores/4DE053EA-8C82-4ED5-B5F8-74EDE806556F/live.1.i ndexHead] [FSLogMsgID 1668857477] [FSLogMsgOrder Last]
(/Volumes/Macintosh HD 1/.Spotlight-V100/Store-V1/Stores/4DE053EA-8C82-4ED5-B5F8-74EDE806556F)(Error) IndexCI in openindexfile:open file error: 22, live.2.indexHead
disk1s3: media is not present
(/Volumes/Macintosh HD 1/.Spotlight-V100/Store-V1/Stores/4DE053EA-8C82-4ED5-B5F8-74EDE806556F)(Error) IndexCI in ContentIndexUpdateContent:Caught mach exception. Fun Fun Fun.
(/Volumes/Macintosh HD 1/.Spotlight-V100/Store-V1/Stores/4DE053EA-8C82-4ED5-B5F8-74EDE806556F)(Error) IndexGeneral in bool siwriteBackAndIndex(_SI*, __ContentIndex*, const __CFDictionary*, const __CFDictionary*, db_obj**, const __CFString*, int, bool, bool, bool, __SIUserCtx*, const __CFString*, int32_t, bool):ContentIndexUpdateContent failed
- (/Volumes/Macintosh HD 1/.Spotlight-V100/Store-V1/Stores/4DE053EA-8C82-4ED5-B5F8-74EDE806556F)(Error) IndexGeneral in void setAttributes(siset_attrctx*, Boolean, long unsigned int):Couldn't update index.
disk1s3: media is not present
+(Message at 00:46:19)+
disk1s3: media is not present
+(Message at 00:47:51)+
jnl: disk1s3: replay_journal: from: 364032 to: 624128 (joffset 0x59000)
+(Message at 00:47:52)+
jnl: disk1s3: journal replay done
+(Then from 00:59:30 to 02:45:20 there are occasional messages of the following)+
disk1s3: I/O error
IOSCSIPeripheralDeviceType0E::setPowerState(0x6366d00, 1 -> 4) timed out after 100128 ms
It is now 8:20am and not a lot of data has been copied over and currently I can't tell if anything else is being copied over. The screen on the old laptop is frozen to the way I last saw it before going to sleep.
Sorry if I posted more than I should have. I am just hoping that someone may be able to better see what is going on from the system log. I am going to check again in a couple of hours to see if any more data has been transferred.
Thanks again for everyone's help with this.
Message was edited by: MasterOdin

Interrupted OSX install on drive and now it's full of bad blocks?

So yesterday I was installing OSX Tiger on an external drive in order to run Disk Warrrior and I decided half thru installation that I'd rather partition the drive and only use up a portion instead so I cancelled the installation by hard reset and now the hard drive won't initialize in Disk Utility and so far the surface scan test reports 28000+ bad blocks. What is the likelihood that my actions could have caused this?

According to the tech from MicroMat, this is not necessarily true.
Interesting. I've been told that there is no way the OS can tell the drive to map out some specific physical block, only that it wants to read or write to some logical sector, which the drive translates to the cooresponding physical one. If the drive detects that the physical one is bad, it maps the logical sector to a spare if it can. This map is kept in the drive's firmware & generally cannot be accessed or changed short of factory-type procedures -- for all practical user purposes, it is a permanent change.
The various tech responses in the URL you mentioned seem to imply this is true. At one point he mentions that TTP's surface scan should not turn up the same bad block more than once, since once accessed the drive will not access that (physical) block again. It also appears that TTP & similar utilities can't actually mark blocks bad either, they instead mark ones they judge marginal as used in the file system, which is no more permanent than the file system itself. (The mention of Intech's SpeedTools Media Scanner somehow getting around this was interesting, though.)
I think what the tech meant about zeroing out data permanently remapping a bad block was in reference to this (the file system map vs. the firmware one), but I'm by no means certain. However, what he said about a multipass zero erase being no better than a single pass one makes me believe the only "miss" involved is for (physical) blocks not yet accessed by the drive.
Certainly, that will delete the partion information ...
I guess I wasn't being clear either. There are partitions that don't store regular data but metadata about the drive format itself, for example if uses an Apple or PC partition scheme. I do not believe such partitions are "zeroed out" with any "Erase" tab option of Disk Utility, although they may be written to, for instance to update the fact that only one Mac volume exists after a 'whole disk' erase.
To sum up, what I'm trying to say is that the drive has to access a sector to detect & map a bad one to a spare. If the drive doesn't do that, no utility will either. They are useful to monitor the rate of bad block creation/detection, but that is primarily a check of the drive's health, not a way to avoid problems resulting from bad blocks themselves.

How does the filesystem handle bad blocks?

Let's suppose your hard drive develops a bad sector on it. What happens?
I remember early products where the OS would constantly try to store new files right on top of the bad block, find the file couldn't be written/verified, then would write it elsehere... then the next time it would do the same thing again, expecting the block to "heal" I guess
What happens on MacOS (extended, journaled) if it's writing a file and finds a bad block in freespace? Does the OS know how to "cocoon off" or tag the bad block as bad and not use it?
Now what happens if the bad block develops underneath an active file? What's the recovery pattern? Or is there none - does it just leave the block bad permanently? Is there any way to fix that?

Boot your computer from the DVD that came with it, and use Disk Utility to check the status of the disk. Select the disk and look at the S.M.A.R.T. status at the bottom. If it displays anything other than Verified, then the disk isn't going to last much longer.
Modern hard disks don't develop "bad sectors" that the OS needs to handle. The disk drive itself automatically remaps bad sectors to spare unused sectors in a way that is transparent to the OS. When too many of those bad sectors are remapped, the S.M.A.R.T. status will report an error.
What you're describing is a failing disk. It's more than likely the early stages of a total failure, rather than just a bunch of bad sectors. Same thing happened to my MacBook a few months ago. After about two hours, it failed completely. I picked up a new drive on the way home, and restored it from Time Machine overnight. The only data that I lost was an iTunes purchase that I made that morning (iTunes Support let me download it again). You have a backup, right?
It's also possible that you've either run out of free space on the startup disk, or you have a process running that's consuming too much CPU and/or RAM resources. If that's the case, a reboot will clear it (until whatever caused it happens again).

Mac pro 13'' harddisk makes noises when writing and reading data, but Techtool scanning result shows no bad blocks in the disk, that is normal?

I bought my Mac pro 13 inch, i7 processor and 750G storage 20th November 2012. But I found when copy into or out the Mac, the harddisk makes noises, like bitting something. I thought there are bad blocks in the disk, but the result of Techtool scanning is no bad blocks in disk, and giving a passed conclusion.
I went the apple store for testing, and the repairmen told me there are two choices available for me:1) replace the harddisk 2) back to the store i bought machine from for a new one. i think that the machine only bought few days, it had better not be disassembled, so i went back for a new one. unfortunately, the new one makes more noises than my old one. i don't know why like apple named brands notebooks have such problems. did you undergo this experience ?

All of the HDDs, be they in my MBPs or enclosures are barely audible. I would say the you deserve no less. I suggest that you do not leave until you are satisfied with a near silent HDD.
Why you got two in a row is a puzzle, but then some people beat the odds and win the lottery. In your case the results are not exactly positive. All HDDs eventually fail, and some fail sooner than others. At least you should start with a quiet one.
Good luck.
Ciao.

Mac Pro & Powerbook data transfer / what about bad blocks

Hello,
Well i have Mac Pro and a old Powerbook G4. Both are running OSX (one intel version and the other PPC). the powerbook is booting from an external firewire drive which i have installed OSX (PPC) on. ( mainly because the internal drive of the laptop died).
So I want to transfer some data from the external drive to my Mac Pro. Is it okay just to shutdown the Powerbook, and connect it & mount it on the Mac Pro as an external drive? (not the actual Powerbook, just the external drive itself...) Will there be complications since it has OSX (PPC) installed? I want to transfer some files of the external to my Mac Pro.
(...I know another option would be to network them together too.....)
I am not trying to boot from it...
another quick question....
The external drive with OSX (PPC) installed, has had a shady history, it has crashed a few times on me, bad blocks, sometimes a click here and there...it been partioned a few times....etc..
When I transfer data or files from the bad drive to my good one, could it possibly transfer those bad data blocks to the other hard drive on my Mac Pro, and possibly "infect" it?

The following may help you:
A Basic Guide for Migrating to Intel-Macs
If you are migrating a PowerPC system (G3, G4, or G5) to an Intel-Mac be careful what you migrate. Keep in mind that some items that may get transferred will not work on Intel machines and may end up causing your computer's operating system to malfunction.
Rosetta supports "software that runs on the PowerPC G3 or G4 processor that are built for Mac OS X". This excludes the items that are not universal binaries or simply will not work in Rosetta:
Classic Environment, and subsequently any Mac OS 9 or earlier applications
Screensavers written for the PowerPC
System Preference add-ons
All Unsanity Haxies
Browser and other plug-ins
Contextual Menu Items
Applications which specifically require the PowerPC G5
Kernel extensions
Java applications with JNI (PowerPC) libraries
See also What Can Be Translated by Rosetta.
In addition to the above you could also have problems with migrated cache files and/or cache files containing code that is incompatible.
If you migrate a user folder that contains any of these items, you may find that your Intel-Mac is malfunctioning. It would be wise to take care when migrating your systems from a PowerPC platform to an Intel-Mac platform to assure that you do not migrate these incompatible items.
If you have problems with applications not working, then completely uninstall said application and reinstall it from scratch. Take great care with Java applications and Java-based Peer-to-Peer applications. Many Java apps will not work on Intel-Macs as they are currently compiled. As of this time Limewire, Cabos, and Acquisition are available as universal binaries. Do not install browser plug-ins such as Flash or Shockwave from downloaded installers unless they are universal binaries. The version of OS X installed on your Intel-Mac comes with special compatible versions of Flash and Shockwave plug-ins for use with your browser.
The same problem will exist for any hardware drivers such as mouse software unless the drivers have been compiled as universal binaries. For third-party mice the current choices are USB Overdrive or SteerMouse. Contact the developer or manufacturer of your third-party mouse software to find out when a universal binary version will be available.
Also be careful with some backup utilities and third-party disk repair utilities. Disk Warrior (does not work), TechTool Pro (pre-4.5.1 versions do not work), SuperDuper (newest release works), and Drive Genius (untested) may not work properly on Intel-Macs. The same caution may apply to the many "maintenance" utilities that have not yet been converted to universal binaries.
Before migrating or installing software on your Intel-Mac check MacFixit's Rosetta Compatibility Index.
Additional links that will be helpful to new Intel-Mac users:
Intel In Macs
Apple Guide to Universal Applications
MacInTouch List of Compatible Universal Binaries
MacInTouch List of Rosetta Compatible Applications
MacUpdate List of Intel-Compatible Software
Transferring data with Setup Assistant - Migration Assistant FAQ
Because Migration Assistant isn't the ideal way to migrate from PowerPC to Intel Macs, using Target Disk Mode or copying the critical contents to CD and DVD or an external hard drive will work better when moving from PowerPC to Intel Macs.
Basically the instructions you should follow are:
1. Backup your data first. This is vitally important in case you make a mistake or there's some other problem.
2. Connect a Firewire cable between your old Mac and your new Intel Mac.
3. Startup your old Mac in Target Disk Mode.
4. Startup your new Mac for the first time, go through the setup and registration screens, but do NOT migrate data over. Get to your desktop on the new Mac without migrating any new data over.
4. Copy the following items from your old Mac to the new Mac:
In your /Home/ folder: Documents, Movies, Music, Pictures, and Sites folders.
In your /Home/Library/ folder:
/Home/Library/Application Support/AddressBook (copy the whole folder)
/Home/Library/Application Support/iCal (copy the whole folder)
Also in /Home/Library/Application Support (copy whatever else you need including folders for any third-party applications)
/Home/Library/Keychains (copy the whole folder)
/Home/Library/Mail (copy the whole folder)
/Home/Library/Preferences/com.apple.mail.plist (* This is a very important file which contains all email account settings and general mail preferences.)
/Home/Library/Preferences/ copy any preferences needed for third-party applications
/Home /Library/iTunes (copy the whole folder)
/Home /Library/Safari (copy the whole folder)
If you want cookies:
/Home/Library/Cookies/Cookies.plist
/Home/Library/Application Support/WebFoundation/HTTPCookies.plist
For Entourage users:
Entourage is in /Home/Documents/Microsoft User Data
Also in /Home/Library/Preferences/Microsoft
Credit goes to another forum user for this information.
If you need to transfer data for other applications please ask the vendor or ask in the Discussions where specific applications store their data.
5. Once you have transferred what you need restart the new Mac and test to make sure the contents are there for each of the applications.
Written by Kappy with additional contributions from a brody.

Disk Utility: for bad blocks on hard disks, are seven overwrites any more effective than a single pass of zeros?

In this topic I'm not interested in security or data remanence (for such things we can turn to e.g. Wilders Security Forums).
I'm interested solely in best practice approaches to dealing with bad blocks on hard disks.
I read potentially conflicting information. Examples:
… 7-way write (not just zero all, it does NOT do a reliable safe job mapping out bad blocks) …
— https://discussions.apple.com/message/8191915#8191915 (2008-09-29)
… In theory zero all might find weak or bad blocks but there are better tools …
— https://discussions.apple.com/message/11199777#11199777 (2010-03-09)
… substitution will happen on the first re-write with Zeroes. More passes just takes longer.
— https://discussions.apple.com/message/12414270#12414270 (2010-10-12)
For bad block purposes alone I can't imagine seven overwrites being any more effective than a single pass of zeros.
Please, can anyone elaborate?
Anecdotally, I did find that a Disk Utility single pass of zeros seemed to make good (good enough for a particular purpose) a disk that was previously unreliable (a disk drive that had been dropped).

@MrHoffman
As well pointed your answers are, you are not answering the original question, and regarding consumer device hard drives your answers are missleading.
Consumer device hard drives ONLY remap a bad sector on write. That means regardless how many spare capacity the drive has, it will NEVER remap the sector. That means you ALWAYS have a bad file containing a bad sector.
In other words YOU would throw away an otherwise fully functional drive. That might be reasonable in a big enterprise where it is cheaper to replace the drive and let the RAID system take care of it.
However on an iMac or MacBook (Pro) an ordinary user can not replace the drive himself, so on top of the drive costs he has to pay the repair bill (for a drive that likely STILL is in perfect shape, except for the one 'not yet' remaped bad block)
You simply miss the point that the drive can have still one million good reserve blocks, but will never remap the affected block in a particular email or particular song or particular calendar. So as soon as the file affected is READ the machine hangs, all other processes more or less hang at the same moment they try to perform I/O because the process trying to read the bad block is blocking in the kernal. This happens regardless how many free reserve blocks you have, as the bad block never gets reallocated, unless it is written to it. And your email program wont rewrite an email that is 4 years old for you ... because it is not programmed to realize a certain file needs to be rewritten to get rid of a bad block.
@Graham Perrin
You are similar stubborn in not realizing that your original question is awnsered.
A bad block gets remapped on write.
So obviously it happens at the first write.
How do you come to the strange idea that writing several times makes a difference? How do you come to the strange idea that the bytes you write make a difference? Suppose block 1234 is bad. And the blocks 100,000,000 to 100,000,999 are reserve blocks. When you write '********' to block 1234 the hard drive (firmware) will remap it to e.g. 100,000,101. All subsequent writes will go to the same NEW block. So why do you ask if doing it several times will 'improve' this? After all the awnsers here you should have realized: your question makes no sense as soon as you have understood how remapping works (is supposed to work). And no: it does not matter if you write a sequence od zeros, of '0's or of '1's or of 1s or of your social security number or just 'help me I'm hold prisoner in a software forum'.
I would try to find a software that finds which file is affected, then try to read the bad block until you in fact have read it (that works surprisngly often but may take any time from a few mins to hours) ... in other words you need a software that tries to read the file and copies it completely, so even the bad block is read (hopefully) successful. Then write the whole data to a new file and delete the old one (deleting will free the bad block and ar some later time something will be written there and cause a remap).
Writing zeros into the bad block basically only helps if you don't care that the affected file is corrupted afterwards. E.g. in case of a movie the player might crash after trying to display the affected area. E.g. if you know the affected file is a text file, it would make more sense to write a bunch of '-' signs, as they are readable while zero bytes are not (a text file is not supposed to contain zero bytes)
Hope that helped ;)

Do the bad blocks preventing me mount my system HD mean I need to replace it?

I have asked this question elsewhere in a different way but didn't get much help - since then I've ran a few more tests and can hopefully zero in on the issue.
I have a 3TB fusion drive late 2012 model 27" iMac that started behaving sluggishly - transferring things from folder to folder in Finder would bring up the spinning beachball (luckily I managed to transfer my important files). When I ran Disk Utility it said that 't stopped verifying "MacintoshHD" and this disk needs to be repaired using the Recovery HD'. I did the restart and attempted the repair and got the message that DU couldn't repair the HD, backup files and reformat the disk. When I attempted to do this I then got the window "Disk Erase failed with the error: The given file system is not supported on Core Storage". The image of the HD also disappeared from view so I can't do anything... not reformat, reinstall Yosemite etc
I ran Tech Tools ProToGo from a USB drive and it showed I had 90 bad blocks on my HD (not the SSD part) but the repair button was greyed out.
I like to think I'm relatively competant with self repair/diagnosis but I've hit a brick wall here. The jury seems to be out whether bad blocks are an indication that the HDD has to be replaced - I've read conflicting reports in these very forums.
FTR I installed Yosemite on an external HD and am using my iMac that way so I guess a lot of stuff under the hood continues to work perfectly.
I would really appreciate any advice.
I've included a couple of relevant pics below; here's the link from my previous question that has a lot more pics and info if anyone wants to have a look Total HD crash - how to get the files

I've tried reading through both threads but am not quite able to follow along....one thought though, have you tried using OS X Internet Recovery?
OS X: About OS X Recovery - Apple Support maybe the Utilities there will allow you to repair the hard drive.

How to repair a bad block on internal hard drive?

I've just performed a surface test on my internal HD
It reports back one bad block, at # 1, 118, 671, 700.Filename = N/A.
1. Should I be concerned about this? I have not noticed any performance issues.
2. If I wanted to get rid of it anyway, how do I repair that bad block?
Please advise.
Many thanks.
/gh

Good to know this happens automatically.
Is that something OS X automatically does on startup, or on shut down, or in background?
But in this case, that automatic feature seems to have missed this block. Else the bad block would not show up in the utility, with a file in it.
Or ,,,,perhaps it still shows up as a bad block in the utility, even though it's been mapped out.
If that's the case, then I guess I need another kind of utility that would report the block has been mapped out....
Any suggestions?

Bad blocks on an external drive, and disk tools for a MacIntel...

I'm having a problem with my external drive which was pulled from my 12" PBook G4 and put into a USB 2.0 enclosure. When I try to transfer data from my internal HDD it runs for a bit, then, it just stops... no spinning ball and it won't allow me cancel the copy. If I fuss with it long enough (clicking on as many finder features as possible), the Finder will eventually stop responding.
I ran Drive Genius as it was the only software I could find that would work as on my computer. Using the "Scan" function, it came back and told me that I had several bad blocks (I had to stop the scan at 115 because I needed to restart my computer). In the program's help guide, it said that it cannot do anything about the bad blocks, and I may need to reformat.
So, I reformatted using Disk Utility on my system start-up disk (not the disk that came with the compuer), then I tried to zero-out all data. Spinning beach ball and the application stopped responding.
Is it possible to quarantine bad blocks if they can't be reformatted or zeroed out on a MacIntel?
Thank you kindly for any help.

Sorry for the additional posts, I don't know how to edit my last post...
Disk Utility is still at 49 minutes remaining, and it's been almost an hour. Still letting it run, and hoping for the best.

How to recover data from a hard drive with bad blocks?

An external hard drive, 4TB Iomega...connected via eSATA cable...had a power outage and the drive won't be read by OSX now. (Yes, it was on a surge protector and no I did not have a backup. I was actually preparing for the process of creating a backup when the power went out!) Anyway, I have tried using Data Rescue 3 and DiskDrill to try and recover data from the drive. I can recover the first 1/3 of the drive, but it ejects when either app tries to access the bad block. Can anyone tell me how/what software to use to recover the data? I know there are programs that will avoid the bad block but I've only found them for Windows. Are there any that will do such a thing in Lion? Any help will be appreciated...and no, I can not afford a data recovery service. Trying to do this on my own.

Basics of File Recovery
If you stop using the drive it's possible to recover deleted files that have not been overwritten by using recovery software such as Data Rescue II, File Salvage or TechTool Pro. Each of the preceding come on bootable CDs to enable usage without risk of writing more data to the hard drive. Two free alternatives are Disk Drill and TestDisk. Look for them and demos at MacUpdate or CNET Downloads.
The longer the hard drive remains in use and data are written to it, the greater the risk your deleted files will be overwritten.
Also visit The XLab FAQs and read the FAQ on Data Recovery.

More than 1200 bad blocks do I need to change my Hard Disk

Hi
my hard disk on a Macbook pro has more than 1200 bad blocks do I need to change my Hard Disk
Thanks for your help

yousseffromlimoges wrote:
my hard disk on a Macbook pro has more than 1200 bad blocks do I need to change my Hard Disk
What software and version did you use to determine you had 1200+ bad blocks?
Was it compatible with Lion?
Run the scan again and take a screen shot of the results and make sure to save it to a external media and disconnect it, you will need this to perform a warranty call and have the drive replaced.
After you have backed up your files to a external storage drive and disconnected it.
Hold Command r upon rebooting and enter the Lion Recovery Partition and run Disk Utility, see if the drive needs repair. I suspect it does. Check the smart status too.
Follow the
Restoring OS X 10.7 (new drive, total reformat method)
https://discussions.apple.com/message/16276201#16276201
Also make a clone of your OS X Lion Partition on a external drive, this way your prepared if the drive dies, you can option boot off the clone. If you get a new drive you have a copy of Lion Recovery on the USB.
It's highly unusual for a drive to have 1200+ bad blocks, the Zero Erase Free Space will confirm it as it's going to use up all your spare blocks.
The drive will likely brick, which you then can option boot off the clone.
Schedule a Apple warranty/AppleCare call if your under it, or order a new drive online from OtherWorld Computing "kits", iFixit for videos or other Mac places online.
http://eshop.macsales.com/installvideos/
You can read my link provided how to format the drive.
However if your Zero Erase Free Space turns out fine, then I suspect the software you used or perhaps something else is wrong with your OS X not correctly reporting your drives data characteristics correctly.
You could be spared a costly repair if that's the case.
Good Luck.

Stora MS2000 NAND bad blocks: libgssapi_krb5.so.2 disappeared

Similar Messages

Maybe you are looking for