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

Similar Messages

  • 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

  • Suggestions for formatting external drive with bad block?

    I have a OWC Mercury 300 GB external drive.  I wanted to erase it and use it as a backup for one of my laptops.  The drive had been working fine as a Time Machine back up for an old (intel) iMac. I told Disk Utility to erase and reformat.  It erased, but refused to reformat saying there was a bad block on the drive.  Now Disk Utility recognizes the external drive but won't do anything with it.  No Verify. No Repair.  All grayed out.  Any suggestions?

    I wasn't a hard error, that's why. Repartitioning and reformatting will often fix soft errors in the directory structure. Had there been a real, new, bad block on the drive it would not be repairable. A soft bad block error can be fixed by reformatting. The hard block error may be fixable by using Zero Data one pass that may spare out the bad block. But if none of that works then you need to replace the drive.
    You were fortunate that the error probably was spurious and resolved by repartitioning (may have been in the disk's RDB.)

  • Recovering data from an NTFS drive with bad blocks

    I've got an 80gb NTFS drive that causes an unmountable boot volume BSOD in a PC. Mounted in a 2.5" USB enclosure, Windows 7 sees it only as an empty "RAW" partition and can't actually mount it. Using the Paragon NTFS driver, I can mount it just fine in Snow Leopard on my MBP.
    However, when I attempt to copy files from it, it pretty quickly finds one with a bad block and gives up. I'm looking for the best way to get as much data (really just images) from this as possible without going through and restarting the transfer after each of the many corrupt files.
    I've tried both Minicopier (which still prompted on every error) and Ultracopier (which would freeze every ten or so corrupt files) as far as simple copiers go, and I've tried DiskDrill and now FileSalvage for full-on data recovery applications. I'd rather use something like the former, but am open to free alternatives to the latter as well.
    Any ideas? Thanks!

    I've had problems with NTFS formatted external drives containing unremovable "corrupted files".
    My problem was resolved using windows. Since Mac isn't supposed to handle NTFS I could not find a suitable way to resolve corrupted file issues, though in windows there is a tool to handle this:
    chkdsk X: -F
    where X: is the volume. This resolved my corrupted file issues and the drive worked like a charm with my mac again.

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

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

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

  • What filesystem can recover from bad blocks?

    Hi All,
    I have a hard drive with a few bad blocks on it. I really should toss it in the garbage bin, and not use it anymore. Also, I need to keep backups.
    But if I were to use this harddrive again, what would be the best filesystem to use? Are there any filesystems that can cope with bad blocks? Can those filesystems also cope with new badblocks appearing?
    Best regards,
    Cedric

    WorMzy wrote:
    https://wiki.archlinux.org/index.php/Ba … ad_Sectors
    Any use to you?
    Thank you. I didn't realise one could tell the filesystem about bad blocks. I'll copy all data to another disk, and then create a new filesystem with a list of bad blocks.
    Out of curiosity, when the disk develops more bad blocks, what filesystem will lose the least amout of data?
    Best regards,
    Cedric

  • Hi, my daughter wrote wrong paswords in my ipod touch and it is blocked.  It says it needs to be connected to itunes, but once its there it says the ipod is blocked with a passcode..the ipod is just blocked. what can I do?

    hi, my daughter wrote wrong paswords in my ipod touch and it is blocked.  It says it needs to be connected to itunes, but once its there it says the ipod is blocked with a passcode..the ipod is just blocked. what can I do?

    Place the iOS device in Recovery Mode and then connect to your computer and restore via iTunes. The iPod will be erased.
    iOS: Wrong passcode results in red disabled screen                          
    If recovery mode does not work try DFU mode.                         
    How to put iPod touch / iPhone into DFU mode « Karthik's scribblings         
    For how to restore:
    iTunes: Restoring iOS software
    To restore from backup see:
    iOS: How to back up
    If you restore from iCloud backup the apps will be automatically downloaded. If you restore from iTunes backup the apps and music have to be in the iTunes library since synced media like apps and music are not included in the backup of the iOS device that iTunes makes.
    You can redownload iTunes purchases by:
    Downloading past purchases from the App Store, iBookstore, and iTunes Store

  • 4th Gen Ipod only charges with power block

    I have 3 different 4th gen ipods, 2 of which will charge up when hooked to USB, firewire, and both my aftermarket Imode stereo and wireless car transmitter/charger.
    One of the 4th gen ipods I have will only change when hooked with a firewire cable to the power block. It will not charge in any other manner. Is this a problem with the circuitry inside the ipod or something else? The battery seems to hold its charge just fine otherwise.

    One of the 4th gen ipods I have will only change when hooked with a firewire cable
    Are you sure it is also a 4G iPod? A 3G iPod (does not have click wheel) can only charge using FireWire. If they are all identical looking 4G iPods (with click wheel), the one that does not change over USB probably has a problem with it's USB charging connection. You could try using the Restore button in iTunes, but it seems like a hardware issue.

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

  • Ipod 4G with bad memory

    Hi all,
    First time poster, so please be gentle. I'm having a problem with my 4G Ipod with colour display. When I finish using it I hold the play/pause button until it goes into standby and put the lock on. Normally, it fires straight back up when I turn the lock off, but I'm finding that if I don't use it for a couple of days it stays dead until I press the menu button. Instead of returning to the last played track, it goes to the apple logo and whirrs and clicks for a while before going to the first screen, as if it's been reset.
    There is plenty of battery life, although the battery meter does seem to wander about a bit as it gets lower(goes from green into red and back into green) and I've tried both reset and restore without a change. No problems with syncing and it behaves as normal when I connect it to the computer.
    Hope someone can help.

    That sounds normal to me. If I power off (stand by) the iPod, or just let it do so by itself, and turn it back on soon, it resumes where it left off. If it powers off and I let it sit much longer, then it does the equivalent of a shut down. This is to conserve power. When it is in stand-by mode, it is like computer sleep, and is still using power to maintain that state. But if the user does not re-engage within a set time period (and I don't know what that time is), it powers off more completely so that the batteries are not drained entirely by the time the user tries to use it again a few days later (that would be annoying).
    My 4th gen iPod works that way. Recent iPods like the touch may be different in this respect.

  • Ipod with click wheel Bad Sound

    When i sync the music onto my ipod from my PC all goes good but when i go to listen to the songs on my ipod i hear constant clicking during the songs like im using the click wheel. Any suggestions?

    Checked the cable and newer ipod shuffle works fine.
    You're not trying to connect the iPod with click wheel using the short USB cable for the iPod shuffle, are you?  If so, that won't work.  The shuffle uses its headphone jack for the data connection.  All other iPods use the dock connector, using a standard docking cable.

  • Erasing ipod with disk utility is it worth a shot?

    My 2G ipod is frozen once again can't get it to mount or show up. just asks if I want to ignore or erase the disk or eject. Have tried all the usual tests and self diagnostics. Even tried the tapping on the right side. I'm running the HDD scan now. Just before this happened when it was still mounting I tried to reset and restore it but got a error and failure several times something about the disk . Has anyone had results with erasing the ipod disk with disk utility and then trying to restore and update.? I went to the apple store and they basically said time for a new ipod . It's well out of warranty but I figure its still worth a try erasing if disk utility might help. I already replaced the HD last year and just got a high output Newer battery for it last week so I don't want to give up yet.
    Craig
    15 TiBook 1GHZ, I.25 dual G4 MDD,10G ipod   Mac OS X (10.3.9)  

    Erasing seems to hang from the beginning in Disk utilty. I tried zeroing all data which takes longer but I've gotten disk utilty to get the progress bar to go about three quarters of the way and then it hangs. I also checked it with techtool pro and it was finding a lot of bad blocks in the scan.
    One time I got ipod updater to say it was restored but it wasn't really and I couldn't get the software updated. So I'm back at square one with trying erase with disk utilty but after more than a dozen attempts I'm beginning to think this is a lost cause for resurrecting this ipod HD . This is of course after I received a new extended battery for it last week made by Newer which is only good for 1G and 2G ipods.
    frustrated, Craig

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

Maybe you are looking for