TechTool Pro 6 Identified Bad Blocks on HD

I ran TechTool Pro 6 (Surface Scan) on my iMac and it found 63 bad blocks for 1,953,525,168 blocks scanned. If I reformat my HD and zeroed it can I get rid off these bad blocks?  Or the best option is to get a new HD and restore my data on it? I mean how many bad blocks is the limit to either reformat or get a new drive?
I would apprreciate any comments/feedback.
Thanks,
Rudy

That seems a bit much, but Zeroing one pass may eliminate them, how old is this dive & what Brand/Model?
LOL, kind of insulting about his home aren't you?

Similar Messages

  • 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.

  • 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.

  • Bad Blocks on iMac (9,1) - Should I replace the drive?

    My wife's early 2009 iMac (9,1) started hangs and crashes. DiskWarrior reported hardware problems, TechTool Pro 7.0.4 found thousands of bad blocks on the factory 1TB hard drive.
    After reformatting, there were still hundreds of bad blocks, so I zeroed the drive (one pass only). Now I am left with 98 bad blocks in a range in mid-drive. I can partition the drive and install OS 10.9.3.
    Should this drive be replaced?

    Yes.

  • Powerbook hard drive has 384 bad blocks -- replace?

    I just ran techtool pro on my powerbook and it found a bunch of bad blocks. I read that if you have more than 5 bad blocks you should repair or replace the drive. But when I ran disk utility to repair it I got a message that the drive appears to be fine. The question is this; do I really need to buy a new drive?

    When you go into disk utility, does the SMART status say failing? If so, replace the drive now. If you don't have it, you might want to install SMARTReporter which puts in icon on the menu bar which indicates the SMART status. It's available at http://www.corecode.at/smartreporter/
    You should be making frequent backups and use TechTool to examine the drive on a regular basis. If the count increases, get a new drive.
    One thing you can do is to erase your hard drive, using the security erase feature which writes zero's on the hard drive. This also maps out the bad sectors so the system won't try and use them.

  • Does RAID Rebuild Fix Bad Blocks on RAID Slice?

    I have RAID 1 enabled (the mirroring option) between two drives on my XServe G4. Yesterday, Server Monitor reported that the RAID was degraded. I booted off the install CD. I launched Disk Utility. Disk Utility immediately rebuilt the RAID. By immediately I mean that it didn't ask if I wanted to, but it took over two hours.
    Today, I ran TechTool Pro. It says that one of the disks in the RAID has 3 bad blocks. It says that the only way to fix that is to erase the disk and zero all data.
    When TechTool scanned the RAID itself as a disk, however, it did not report any bad blocks. This makes me wonder if rebuilding the RAID somehow took care of the bad blocks already.
    Please let me know if my theory is correct!

    Oh...if you have data you are trying to save then its best to try cloning the drive to another one, which should save its data as-is to another drive. Hopefully you can do so without there being hangups around the bad blocks and keep at least most of your data intact. I'd recommend you try using Carbon Copy Cloner to do this, but you will need a secondary drive that is at least the size of the data on the problematic drive.

  • 4G iPod with bad blocks

    Hi there,
    I hope someone can give me a light on what's going on with my 4G iPod. I started noticing it siped some musics that work fine on iTunes. And sometimes it would block. I restored it (through iTunes) a couple of times without solving the problem. Then I used Micromat's techtool pro and scanned the disk founding it had bad blocks. I erased the disk with disk utility (writing zeros) and tried to complete the Techtool's scan. It failed so I believe the bad blocks weren't all mapped.
    The scan went for three days in a row and I wondered if there is a quick way to simply map the bad blocks and use my iPod again without expecting the song to skip.
    Thanks in advance,
    JP

    I have come across this with many Ipods.
    A droppage or even just old fashioned wear and tear can cause deterioration of the Hard disk, It would be nice if the iPod Firmware had a "Smart Mode Engineering" that could be used to access the Hard disk directly (Via USB I/O)
    the iPods would need to have powered support for various revisions, and a max operation time limit. (Running a disk check tends to wear the drive out further)
    In this way, a diagnostic map could be made for the disk that the Smart mode could use, and work around the disk errors.
    Whatever songs end up going bad, with bad sectors, could be flagged, considered unusable and the song re-loaded to a different point on the disk.
    Yes, you lose space, but it's cheaper than replacing the unit, or having it repaired.
    Just my two cents.
    -sean

  • Bad block--what must I do?

    TechTool Pro's Surface Scan test informs me that there is one (1) bad block on my hard drive. Must I really reformat the whole drive and then reinstall the OS and then use my backup to put the rest of the files back? Or is there some other way? Any help will be appreciated.

    Depends on the nature of your back-up, sers.
    This is the sort of situation where a bootable SuperDuper or Carbon Copy Cloner backup comes into its own.
    Simply wipe the drive using Disk Utility, with basic zeroing selected in the security options, boot from the back-up, and clone back to the internal.
    Then run TTPs "surface scan" again. If it finds more bad blocks on the new scan after the old ones have in theory been "mapped out" it suggests that the drive itself is probably deteriorating to the point where there are more "bad blocks" on it than the "mapping out" process can handle, and you should very seriously think about replacing the drive. A few bad blocks, that can be dealt with by zeroing to "remap" the drive, are pretty common, but if new ones keep on appearing things aren't looking so good.
    For a more thorough examination you might also want to run "Smart Utility" over the drive , to see what it has to say about it. http://www.volitans-software.com/smart_utility.php
    Cheers
    Rod

  • Would TechTool Pro help?

    Hi
    I have an older 120gb LaCie d2 which Disk Utility sometimes reported a "minor volume header error" which it couldn't fix.
    Think trouble started after an incorrect power off.
    While transferring files to or from it the drive would spin down then spin back up again, and stay spinning but I could no longer access it or unmount it without a forced restart as the Finder would just hang if I tried to shutdown.
    Upon restart the drive couldn't be seen or mounted.
    Even with the computer shutdown it would keep spinning until the power was manually turned off.
    I erased it, ran Disk Utility which said it appeared ok.
    But the problem was still there.
    Ran Disk Warrior, though I'm not sure it has done anything.
    I partitioned it but still get the same problem, though now ejecting one of the partitions will eject the other without the need for a restart.
    But the "copying to..." window won't disappear even if I press "stop"
    Relaunching the Finder clears it though.
    When running a system from one partition the same problem occurs when copying files to the other, though everything else Finder, other apps still run.
    So I was wondering would TechTool or Drive 10 or something similar be of any help?
    Or should I just replace the drive?
    Any suggestions are much appreciated
    Thanks
    Anthony
    Ti G4   Mac OS X (10.3.9)   867 1GB ram

    Anthony:
    TechTool Pro might be worth a try, if you have a copy, although if Disk Warrior found no problems TTP may not, either. So, if you have a copy on hand, try it, but don't rush out and buy one.
    What would be worth a try is, if you can back up your data from the HDD in question, to completely wipe the HDD, zeroing all data. That should take care of any bad blocks and directory problems. Worth a try before deciding to replace the drive, I think.
    Good luck.
    cornelius
    PB G3 Pismo400, 100 GB 5400 Toshiba internal, 1 GB RAM   Mac OS X (10.3.9)   Beige G3 OS 8.6

  • Acmcneill1ug 14, 2014 7:16 AM I have IMac OSX 10.9.4, 4GB,Processor 3.06 with Intell2Duo. I would like to check for Malware. I run a TechTool Pro 6 every month and that comes up great. When check how much memory I am using, with only Safar

    Acmcneill1ug 14, 2014 7:16 AM
    I have IMac OSX 10.9.4, 4GB,Processor 3.06 with Intell2Duo. I would like to check for Malware. I run a TechTool Pro 6 every month and that comes up great.
    When check how much memory I am using, with only Safari open I am using 3.9 and more of her 4.0 memory. She is very. very slow in processing. I had 4000
    trash to clean out and it took her over an hour to expel. Also for some reason Safari will not allow me to click on a link, in my G-mail, and let it go to the page.
    It has a sign saying a pop-up blocker is on and will not let me do it. I must open the stamp to look at my e-mails and if I have redirected link now I can do it.
    I have not changed my preferences so where is this pop-up blocker?
    I have looked at preferences on Safari and Google, which I do not understand Google, and do not see where this blocker could be.
    Malware is something I want to make sure is not on my computer. Tech Tool Pro 6 is all I know of and it does not detect Malware.
    Help.
    Ceil

    Try Thomas Reed's Adware removal tool. He posts extensively in the communities.
    Malware Guide - Adware
    Malware Discussion

  • 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.

  • 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 ;)

  • 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.

  • [Repaired] Bad blocks cause kernel blocking to the device

    I got
    May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] Unhandled sense code
    May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
    May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] Sense Key : 0x3 [current]
    May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] ASC=0x14 ASCQ=0x0
    May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 25 42 ea af 00 00 01 00
    May 10 10:08:13 qslap kernel: end_request: I/O error, dev sdb, sector 625142447
    May 10 10:08:13 qslap kernel: Buffer I/O error on device sdb, logical block 78142805
    in system log when I try to access /dev/sdb in some way (for example, plug in, fdisk, gparted, but not palimpsest).
    This kind of log repeats several times and blocks any access to that device for tens of seconds (Seems kernel keep retrying, not give up the first time), which is annoying.
    From palimpsest, I can see:
    Current Pending Sector Count: Value: 1 sector
    Uncorrectable Sector Count: Value: 1 sector
    It says when write fails, "Current Pending Sector" will be remapped automatically by hardware.
    I got the sector size = 512 bytes:
    # fdisk -lu /dev/sdb
    Disk /dev/sdb: 320.1 GB, 320072933376 bytes
    255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0xaaaaaaaa
    Disk /dev/sdb doesn't contain a valid partition table
    badblocks detects the bad sector well:
    # badblocks -svw -b 512 /dev/sdb 625142447 625142447
    Checking for bad blocks in read-write mode
    From block 625142447 to 625142447
    Testing with pattern 0xaa: 625142447one, 0:20 elapsed
    done
    Reading and comparing: done
    Testing with pattern 0x55: done
    Reading and comparing: done
    Testing with pattern 0xff: done
    Reading and comparing: done
    Testing with pattern 0x00: done
    Reading and comparing: done
    Pass completed, 1 bad blocks found.
    From above, you can see that write a block one time takes 20 seconds due to kernel blocking.
    badblocks writes 4 times,  ~80 seconds.
    Note: badblocks doesn't find any bad blocks when performing a full disk read-only test.
    However, the sector wasn't automatically remapped (badblocks has already written that sector)
    the kernel is still generating logs and blocking, which is very annoying.
    I also tried to write at that sector directly, no luck:
    # dd if=/dev/zero of=/dev/sdb bs=512 count=1 seek=625142447
    dd: writing `/dev/sdb': Input/output error
    1+0 records in
    0+0 records out
    0 bytes (0 B) copied, 7.26951 s, 0.0 kB/s
    What should I do to let the hardware remap that sector?
    If no way due to hardware limitation, then how can I mute the annoying log and let the kernel not blocking ?
    Additional: I am looking for a way to let kernel not blocking, give up at the begining asap, or let the hardware SMART mark that sector not to be 'Pending', not for a way to create fs with bad blocks marked.
    I know if I provide a list of badblocks to mkfs.*** to create a fs, these blocks will not be used.
    However, when I plug in the removable harddisk, BEFORE performing ANY r/w instructions, the kernel starts to generate logs and /dev/sdb is not visible in tens of seconds. Same situation occurs when I run / fdisk / gparted (these programs are not responsible for tens of seconds due to kernel blocking) ...
    I guess that SMART does these checks automatically and cause kernel blocking, while SMART can't handle these things well.
    This is the output of smartctl -a /dev/sdb -d sat, which may be helpful:
    smartctl 5.39.1 2010-01-28 r3054 [i686-pc-linux-gnu] (local build)
    Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
    === START OF INFORMATION SECTION ===
    Model Family: Seagate Momentus 5400.5 series
    Device Model: ST9320320AS
    Serial Number: 5SX3YFQ8
    Firmware Version: SD03
    User Capacity: 320,072,933,376 bytes
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: 8
    ATA Standard is: ATA-8-ACS revision 4
    Local Time is: Mon May 10 11:25:42 2010 CST
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    See vendor-specific Attribute list for marginal Attributes.
    General SMART Values:
    Offline data collection status: (0x00) Offline data collection activity
    was never started.
    Auto Offline Data Collection: Disabled.
    Self-test execution status: ( 121) The previous self-test completed having
    the read element of the test failed.
    Total time to complete Offline
    data collection: ( 700) seconds.
    Offline data collection
    capabilities: (0x73) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    No Offline surface scan supported.
    Self-test supported.
    Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 1) minutes.
    Extended self-test routine
    recommended polling time: ( 114) minutes.
    Conveyance self-test routine
    recommended polling time: ( 2) minutes.
    SCT capabilities: (0x103f) SCT Status supported.
    SCT Feature Control supported.
    SCT Data Table supported.
    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000f 094 088 006 Pre-fail Always - 182650280
    3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0
    4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 595
    5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
    7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 30942693
    9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 4482
    10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 1
    12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 579
    184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
    187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 1812
    188 Command_Timeout 0x0032 100 099 000 Old_age Always - 2
    189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
    190 Airflow_Temperature_Cel 0x0022 067 039 045 Old_age Always In_the_past 33 (0 166 39 23)
    191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 98
    192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 48
    193 Load_Cycle_Count 0x0032 011 011 000 Old_age Always - 178621
    194 Temperature_Celsius 0x0022 033 061 000 Old_age Always - 33 (0 12 0 0)
    195 Hardware_ECC_Recovered 0x001a 060 039 000 Old_age Always - 182650280
    197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1
    198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1
    199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
    SMART Error Log Version: 1
    ATA Error Count: 1979 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    Error 1979 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 da 01 ff ff ff 4f 00 13:43:15.498 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:13.155 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
    Error 1978 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 da 01 ff ff ff 4f 00 13:43:13.155 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
    Error 1977 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.885 READ DMA EXT
    Error 1976 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 da 01 ff ff ff 4f 00 13:43:08.457 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:06.082 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.814 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
    Error 1975 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 da 01 ff ff ff 4f 00 13:43:06.082 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.814 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Extended offline Completed: read failure 90% 4480 625142447
    # 2 Short offline Completed: read failure 90% 4474 625142447
    # 3 Extended offline Completed: read failure 90% 4474 625142447
    # 4 Short offline Completed: read failure 90% 4474 625142447
    # 5 Conveyance offline Completed: read failure 90% 4473 625142447
    # 6 Short offline Completed: read failure 90% 4473 625142447
    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    Last edited by b6fan (2010-05-10 07:18:46)

    Bad block repaired by SeaTools for DOS.
    Seems only SeaTools for DOS can repair this issue.

Maybe you are looking for