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.

Similar Messages

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

  • Fsck on HFS+ File System and bad block counter

    Hi community,
    does the fsck command check also for bad blocks in single user mode? Is in Mac OXS a similar command available like the dumpe2fs command for ext2/3 file systems to print out the actual number of bad blocks?
    Thx & Bye Tom

    +does the fsck command check also for bad blocks in single user mode?+
    No.
    +Is in Mac OXS a similar command available like the dumpe2fs command for ext2/3 file systems to print out the actual number of bad blocks?+
    Not a built-in command. If your device is supported by smartmontools, that's the way to go. It's possible that hfsdebug may do something like what you want, but it doesn't scan for unmapped bad blocks.

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

  • My Arch won't boot anymore something about bad blocks

    It was working fine. I booted it up this morning said it found some bad blocks on some of my Linux partitions. How do I scan the surface of my drives with Archlinux.?. Is that even possible with Linux?. This is my USB drive that has the bad blocks.

    Quicken2k wrote:Boot with ro 1?. I'm new to Arch and need a bit more info. Are you telling me to boot up in read only mode?. How?.
    No worries! Simply, boot your computer and when you get to GRUB, select your Arch install and hit 'e'. Now you can edit the 'kernel' line. Append 1 (one) to the end of the line. Hit enter again, and hit 'b' to boot into single user mode. Now you can login as root, and perform whatever fsck's and debugging. Be sure to report back.

  • How many implimentations can be done for a single BADI definition?

    How many implimentations can be done for a single BADI definition?
    Is there any restriction to impliment a single BADI definition?
    Plz answer with proper explanation....
    Thank you in advance
    REgards,
    Chaitanya

    hi Krishna Chaitanya,
    In a badi if the "Multiple Use" Checkbox is checked then You can have any number of Implementations for the BADI
    Say I have defined a BADI "BADI1"
    and I have 3 implementations
    IMP1
    IMP2
    IMP3
    The order of execution will be IMP1, IMP2 and IMP3
    In a badi if the  "Multiple Use" Checkbox is not checked then You can have ONLY ONE  Implementation for the BADI
    Say I have defined a BADI "BADI1"
    and I have 3 implementations
    IMP1
    IMP2
    IMP3
    Only one Implementation can be active at a time and only that will get executed
    Hope this helps a bit
    Reward if Useful
    Cheers
    Kripa Rangachari.

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

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

  • Ideapad Flex 15 - HDD has bad block

    Hi All,
    Thanks for Any help to address the problem.
    I have already tried running the chkdsk /f /r which just got stuck at 10% and didn't move from there for about 40 minutes.
    I started getting below message in Event viewer :
    Log Name:      System
    Source:        disk
    Date:          1/19/2014 5:25:48 PM
    Event ID:      7
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      PC
    Description:
    The device, \Device\Harddisk0\DR0, has a bad block.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="disk" />
        <EventID Qualifiers="49156">7</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-01-19T23:25:48.278119900Z" />
        <EventRecordID>5403</EventRecordID>
        <Channel>System</Channel>
        <Computer>PC</Computer>
        <Security />
      </System>
      <EventData>
        <Data>\Device\Harddisk0\DR0</Data>
        <Binary>030080000100000000000000070004C0000100009C0000C00000000000000000007007C5090000000C10010000000000FFFFFFFF000000005800008402010000E8200AFF42072000000200003C000000C09AAB030000000080957F0100E0FFFF0000000000000000C0C8250100E0FFFF0000000000000000B883E20400000000280004E283B800000100000000000000700003000000000000000000110000000000000000000000</Binary>
      </EventData>
    </Event>
    Also similar message from Lenovo Solution Center:

    Are you encountering the same startup errors when booting straight from the One Key Recovery button? I assume the startup error is occuring while trying to boot the OS, and not booting the recovery.
    As far as I know, Lenovo utilizes a corporate activation (no printed key) on the Flex 15. You may be able to get Lenovo to send you recovery media, or even have them just re-image if covered by your warranty.
    ←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗
    Tap that kudos button if I helped ^^
    ←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗

  • Correcting a bad block on ext4 and with GTP partition table

    Hello,
    I ran a SMART offline test today which came back as a bad block:
    # 1  Extended offline    Completed: read failure       30%      8363         3212759896
    This is my first run-in with a bad block, and since these drives are big and relatively new, I want to be proactive and fix any problems as they arise. Here is my setup:
    * I have 2x 2TB HDDs of same make and model, with the device link being /dev/sdc and /dev/sdd. /dev/sdc is the one with the error.
    * These two disks are linked via a Linux RAID 1 array under /dev/md0 which is then mounted on /storage.
    * Both drives have only 1 partition under a GUID Partition Table (GPT)
    I've looked around to try to find info on fixing bad blocks, and I came across this: smartmontools.sourceforge.net/badblockhowto.html
    However, it seems to be out-dated and geared for tools like fdisk (which I cannot use for GPT) and filesystems ext2/3 (although, due to the backwards compatibility, I'm sure it works with ext4 as well), and a lot fo the commands gives things like "Couldn't find valid filesystem superblock."
    Can someone point me in the right direction as to how I can fix this issue?
    EDIT:
    My noob is showing. I got the commands above to work, and when I check to see which file is using the bad block it shows this (after all the calculations involved, the block was 401594731):
    debugfs:  icheck 401594731
    Block   Inode number
    401594000       <block not found>
    So i'm assuming that there isn't a file assigned to it (empty space?). But then, when I use dd to read from it, it seems to read just fine:
    sudo dd if=/dev/md0 of=my.block skip=401594731 bs=4096 count=1
    1+0 records in
    1+0 records out
    4096 bytes (4.1 kB) copied, 0.0222587 s, 184 kB/s
    I think it's able to read it since the other disk in the RAID1 array doesn't have the bad block. But I just want to make absolutely sure that there is no file assigned to that block before I nuke it. Given the above information, would it be safe to remove this block from service?
    Last edited by XtrmGmr99 (2012-01-26 01:17:51)

    Yes I think the block is not in use. You can do
    debugfs: testb 401594731
    which will state it clearly ("not in use" vs "marked in use")

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