Corrupt Disk

I've noticed my 2012 McBook Pro running slower, slower app launch & response time.
I run disk utility verify disk and get a waring of a corrupt disk and to run disk utility in the recover hd to repair (I will copy the log at the end).
So I booted in the recovery hd and run verify disk, and it says the disk appears to be ok.
Booted up normally, run disk utility again, and get the same error.
What I have tried was, running repair disk anyways in the recovery HD and that didn't work. I've also ran Cocktail scripts to try cleaning up my drive. I've also tried reinstalling the OS (10.8.5) and still no luck.
LOG:
2013-11-20 09:57:37 -0600: Disk Utility started.
2013-11-20 09:57:50 -0600: Verifying volume “Labeling_02”
2013-11-20 09:57:50 -0600: Starting verification tool:
2013-11-20 09:57:50 -0600: Checking file system2013-11-20 09:57:51 -0600: Performing live verification.
2013-11-20 09:57:51 -0600: Checking Journaled HFS Plus volume.
2013-11-20 09:59:12 -0600: Checking extents overflow file.
2013-11-20 09:59:12 -0600: Checking catalog file.
2013-11-20 09:59:12 -0600: Checking multi-linked files.
2013-11-20 09:59:12 -0600: Checking catalog hierarchy.
2013-11-20 09:59:12 -0600: Checking extended attributes file.
2013-11-20 09:59:12 -0600: Incorrect number of extended attributes
2013-11-20 09:59:12 -0600: (It should be 467651 instead of 467650)
2013-11-20 09:59:12 -0600: Checking volume bitmap.
2013-11-20 09:59:12 -0600: Checking volume information.
2013-11-20 09:59:12 -0600: The volume Labeling_02 was found corrupt and needs to be repaired.
2013-11-20 09:59:12 -0600: Error: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.2013-11-20 09:59:12 -0600:
2013-11-20 09:59:12 -0600: Disk Utility stopped verifying “Labeling_02”: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
2013-11-20 09:59:12 -0600:

So the next step is to back up, erase, reformat an reinstall. Restoring from a back up shouldn't be a problem, since the problem looks to be in the low levels of the file system (not backed up when using time machine, which is the backup method I would recommend for this). it'll be time consuming, but it's a good idea to nip that in the bud before it gets out of control and renders the OS unusable. In rare cases, this can be a sign of hardware failure, so if you have troubles reinstalling the OS, we may be looking at a failing HDD.

Similar Messages

  • Disk utility intermittently reports corrupt disk

    As a matter of routine maintenance I like to "Verify Disk" in disk utility from time to time.
    The issue I am having is that disc utility intermittently identifies that the Server drive is corrupt and needs to be repaired. Here is a typical sequence:
    1) Run verify disk and it reports a corrupt disk.
    2) Boot up off a different disk and re-run verify / repair disk on the problematic disk and it reports that the disk is fine.
    3) Boot up on the original (problematic) disk and re-run verify disk and it reports the disk as fine.
    4) Checking again the next day the original problem resurfaces - disk is corrupt.
    The server appears to be running fine, but I am loathe to have an issue like this potentially simmering in the background. I am also averse to upgrades until this issue is resolved. Any pointers on getting this resolved would be much appreciated.
    Coincidentally, I have run disk warrior and it reports no issues.

    Here is the typical disk utility log when reporting the error:
    Verifying volume “Server”
    Verifying volume when it is mounted with write access.
    Checking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Incorrect block count for file kdc.log
    (It should be 91 instead of 92)
    Incorrect number of thread records
    Invalid leaf record count
    (It should be 1567637 instead of 1567636)
    Checking multi-linked files.
    Checking catalog hierarchy.
    Checking extended attributes file.
    Checking volume bitmap.
    Volume bitmap needs minor repair for under-allocation
    Checking volume information.
    Invalid volume file count
    (It should be 684309 instead of 684308)
    Invalid volume free block count
    (It should be 47746895 instead of 47747031)
    Volume header needs minor repair
    The volume Server was found corrupt and needs to be repaired.
    Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.

  • "DDE server window: itunes.exe - corrupt disk " please help!!!

    i keep trying to oppen my itunes on my laptop (a dell inspiron with windows 7) and it keeps saying:  "DDE server window: itunes.exe - corrupt disk "
    also says  "the folder "iTunes" is on a locked disk or you do not have write permissions for this folder"
    i dont know anything about this kind of stuff i need detailled help please

    hi Hung Tang!
    hmmm. just to be on the safe side, please try searching for that file again, after having done this:
    Open "My computer". go to the Tools menu. Select "folder options ..." click the "view" tab. Make sure "Show hidden files and folders" is checked and "Hide extensions for known file types" is unchecked, like so:
    http://www.pixentral.com/show.php?pic=1yUGzJM0gRKQ8LtcizzwMSgXNb2u
    If the QT file still isn't showing up then, and the fix from that QTfW thread is still impossible to apply, then I think that a
    b clean
    uninstall then reinstall (with freshly downloaded itunes and ipod software) would be prudent. we want to try to try to get rid of any corrupted files (in either your itunes or quicktime set-ups).
    Da Gopha, "iTfW: stepwise clean uninstallation of iTunes", 09:51am Apr 5, 2005 CDT
    It would also be prudent to back up your music prior to doing this. we aren't going to be doing anything that would normally affect them, but it's best not to tempt fate.
    love, b

  • How to trash a corrupted disk image ? ?

    I have what I know is a corrupted disk image which I can't seem to delete by just putting it in the trash, then emptying it. When I attempt this, I just get a progress bar saying the trash is emptying, yet there is no blue on the progress bar, none at all, no matter how long I leave it up. To get rid of this bar, I even began trying some terminal commands to empty the trash, which was nerve wracking, as although I was using a trusted website to guide me, I haven't used the terminal before. In the end, I could only get rid of this progess bar by relaunching the finder.
    So, how should I get rid of this disk image? I know it is definatley a corrupted image, as I began making it using disk utility, and stupidly quit disk utility whilst it was in the middle of making it.
    Here is my info on the image:
    - It is encryped.
    - It's 60 GB in size.
    - I originally created it on an external hard drive, then moved it to my trash to try to delete it.
    Any help on how to delete it from an experienced user? I'd be most grateful. I think for now I'll try putting it inside another larger disk image on my external drive and erasing that image using disk utility. I can't erase the whole external hard drive, so that's the only option I can think of.
    I've just realised the problem maybe that I was trying to put a large 60 GB disk image in my iBook's trash, and as I only have 30 GB avaliable on my iBook's hard drive, surely that caused a problem? I can't believe I only just realised that... what an idiot I am!

    I would suggest you reboot your Powerbook G4 and then download a copy of TrashIt <http://www.macupdate.com/info.php/id/8214>. That app should allow you to remove the large disk image in your Trash.
    Also, the free space that you have on your internal hard drive shouldn't effect your Mac's ability to delete a file on a separate drive that is larger than that free space. If the disk image is corrupted, that's probably the real issue. After you get rid of the file, I would suggest running DiskWarrior on both of your drives to verify that everything is okay.
    PowerMac G5   Mac OS X (10.4.6)   1GB RAM, nvidia 6800 ultra, Apple 30" Cinema Display

  • Corrupted Disk Image

    I have a sparse disc image that was corrupted during a hard reset. Now, when I try to open it, it says that it cannot because "disk image is corrupted". I have very important files on the disc image and really need to get it recovered. So far I have only tried repairing it in disc utility-to no avail.
    Is there any other way I can recover it?
    Thank you in advanced.

    I hate to be the bearer of bad news, but I don't know of anyway to mount a corrupted disk image. That said, you could investigate the Unix command, which may have way to verify and mount it:
    hdiutil
    Launch the Terminal app in /Apps/Utilities/, type this in, and hit the return key;
    man hdiutil
    Hit the space bar to page through the document, when you get an alert sound, type in a q, and quit the Terminal program.
    G4 450 MP Gigabit   Mac OS X (10.4.7)  

  • How to restore a time machine backup from a corrupted disk

    Hi.
    I have quite a problem. I recently downgraded to os x 10.5.4 due to the requirements of Digidesign's Pro Tools. I did so with a clean install in order to have the most optimized computer possible without loads of unused data. I had backed up my data using Time Machine on an external hard-drive (LaCie, 1 TB) so I wasn't worried about losing important data.
    However, when I inserted my external hard-drive after the clean installation it turns out to be corrupted in some way. It is only recognized in Disk Utility, it doesn't mount on my desktop.
    Disk Utility is unable to repair the disk. The errors are:
    +Verify and Repair volume “Kristoffer's back-up disk”+
    +Checking Journaled HFS Plus volume.+
    +Invalid node structure+
    +Volume check failed.+
    +Error: Filesystem verify or repair failed.+
    I went out and bought "Data Rescue II" at once to try to recover my data. It works fine with the stuff I've manually dragged to the disc but the Time Machine backup folders seem compressed in some way (It's only about 86 MB). And when I click a file restored from one of the Time Machine folders it seems like it's just a shortcut to an "original file". I get this error when double-clicking such a file:
    +The alias "filename" could not be opened, because the original item cannot be found.+
    Is there some way for me to get Time Machine to understand the back up disk even though it's corrupted? Or some other way to retrieve my data?
    I have TONS of extremely important data on the disk so it would cost me a huge amount of work to format the disk and start from scratch.
    ANY help is greatly appreciated

    ohnoono wrote:
    Hi.
    I have quite a problem. I recently downgraded to os x 10.5.4 due to the requirements of Digidesign's Pro Tools. I did so with a clean install in order to have the most optimized computer possible without loads of unused data. I had backed up my data using Time Machine on an external hard-drive (LaCie, 1 TB) so I wasn't worried about losing important data.
    However, when I inserted my external hard-drive after the clean installation it turns out to be corrupted in some way. It is only recognized in Disk Utility, it doesn't mount on my desktop.
    Disk Utility is unable to repair the disk. The errors are:
    +Verify and Repair volume “Kristoffer's back-up disk”+
    +Checking Journaled HFS Plus volume.+
    +Invalid node structure+
    +Volume check failed.+
    +Error: Filesystem verify or repair failed.+
    I went out and bought "Data Rescue II" at once to try to recover my data. It works fine with the stuff I've manually dragged to the disc but the Time Machine backup folders seem compressed in some way (It's only about 86 MB). And when I click a file restored from one of the Time Machine folders it seems like it's just a shortcut to an "original file". I get this error when double-clicking such a file:
    +The alias "filename" could not be opened, because the original item cannot be found.+
    Is there some way for me to get Time Machine to understand the back up disk even though it's corrupted?
    no, that's quite impossible. you may try using Disk warrior on that drive. it's known to be able to fix the kind of error that DU is reporting. if that doesn't work your only hope is data recovery. If Data Rescue II doesn't work you can try other data recovery software like Filesalvage or try professional data recovery services (those can can a fortune).
    Or some other way to retrieve my data?
    I have TONS of extremely important data on the disk so it would cost me a huge amount of work to format the disk and start from scratch.
    ANY help is greatly appreciated

  • Corrupt disk label error when running explorer

    I am getting corrupt label error in one of the disks when running explorer on T5120 server. I observed this behaviour in /var/adm/messages.

    Well we don't have any database on this server. This server is a mail server & they don't require raw devices. I checked iostat on the disk & there is no activity on the disk.
    I ran format command & got the info below. I checked the partition table of the disk & i guess there is something wrong with the partition table.
    *#format*
    Searching for disks...done
    c6t60060E80056F9B0000006F9B0000049Cd0: configured with capacity of 66.40GB
    partition> p
    Current partition table (default):
    Total disk cylinders available: 18131 + 2 (reserved cylinders)
    Part Tag Flag Cylinders Size Blocks
    0 root wm 0 - 34 131.25MB (35/0/0) 268800
    1 swap wu 35 - 69 131.25MB (35/0/0) 268800
    2 backup wu 0 - 18130 66.40GB (18131/0/0) 139246080
    3 unassigned wm 0 0 (0/0/0) 0
    4 unassigned wm 0 0 (0/0/0) 0
    5 unassigned wm 0 0 (0/0/0) 0
    6 usr wm 70 - 18130 66.14GB (18061/0/0) 138708480
    7 unassigned wm 0 0 (0/0/0) 0
    Can i try labeling the disk?

  • Keeps corrupting disk partition, even new disk

    After 6.5 reliable years, my Macbook Pro (mid-2007 model 3,1) failed to boot, just freezing at the white screen (in Mtn. Lion) even when the shift is held down for "safe boot". Although Disk Utility and Apple Hardware Test found nothing wrong with the hard drive, I replaced it along with the battery with brand new ones. Since then, no matter what OS X version I load (10.6.8, 10.8, Mavericks), the same problem occurs without warning after 2 or 3 weeks of normal use.
    Disk Warrior finds one or two damaged, seemingly non-crucial files each time, but their removal does not correct things. I partitioned the disk last time, and loaded Snow Leopard onto both so I would have a spare. Also fixed permissions. But sure enough, after a couple of weeks the partition most used is not openable while the other one still operates beautifully, no twirling beach balls or anything. But I know it's living on borrowed time.
    Can a logic board crap out after years pass and permanently corrupt a disk partition while leaving the rest intact? Could a failing PRAM battery do something like this?

    Could be that your new disk is also borked, but I would try getting a new SATA cable in the meantime.
    Good luck!

  • Time Machine IS killing or corrupting disks

    To all those " This is just coincidence" guys.
    I have heard about several people being unable to mount their harddrives,
    I had a email traffic with a couple of them and told them to to a manual fsck
    everyone of these guys has a corrupted super block...
    I work with harddrives for about 10 years now, as i do with unix.
    Time Machine IS corrupting, at least, some hard drives.
    I have seen TM corrupting the volume headers and super blocks on 3 brand new external hard drives and one internal harddrive
    Extended read/write tests on this HD's don't show any errors
    Reformating to HFS+, fire up TM and boom, corrupted hard disk
    They had the same issues with TM over Airport, and now they turned it off
    but... it happens to wired hard drives too.
    Apple, fix this!
    Message was edited by: ruebezahl
    Message was edited by: ruebezahl

    The volume structure on an HFS+ volume that is comparable to the superblock of a UFS volume is the volume header, or volume information block (VIB).
    Apple has a detailed description of the HFS+ Volume format:
    http://developer.apple.com/technotes/tn/tn1150.html
    Micromat posted in the MacFixIt Forums some instructions for viewing the text representation of the volume header, using the free utility hfsdebug:
    Use hfsdebug to view volume header:
    syntax given on page 1494 of “Mac OS X Internals” by Amit Singh.
    Using your browser, go to http://www.osxbook.com/software/hfsdebug/ . Download hfsdebug from the link at the bottom of the page. After the download is complete, double-click the .dmg file you downloaded. When this disk image mounts, you see a free utility named hfsdebug. Copy the hfsdebug file to your desktop.
    Open Terminal, located in /Applications/Utilities. Type the following three commands, each on its own line, and press the Return key at the end of each line:
    cd ~/Desktop
    chmod u+x hfsdebug
    sudo ./hfsdebug -d /dev/rdisk1s10 -v
    Enter your administrative password at the prompt.
    Here is a sample of the output:
    MMT3s-Computer:~ MMT3$ cd ~/Desktop
    MMT3s-Computer:~/Desktop MMT3$ chmod u+x hfsdebug
    MMT3s-Computer:~/Desktop MMT3$ sudo ./hfsdebug -d /dev/rdisk1s10 -v
    Password:
    # HFS Plus Volume
    Volume size = 9699188 KB/9471.86 MB/9.25 GB
    # HFS Plus Volume Header
    signature = 0x482b (H+)
    version = 0x4
    lastMountedVersion = 0x4846534a (HFSJ)
    attributes = 00000000000000000010000100000000
    . kHFSVolumeUnmounted (volume was successfully unmounted)
    . kHFSVolumeJournaled (volume has a journal)
    journalInfoBlock = 0x1993a3
    createDate = Tue Oct 11 20:35:24 2005
    modifyDate = Wed Oct 11 21:23:41 2006
    backupDate = Fri Jan 1 00:00:00 1904
    checkedDate = Tue Oct 11 20:35:24 2005
    fileCount = 178583
    folderCount = 47879 /* not including the root folder */
    blockSize = 4096
    totalBlocks = 2424797
    freeBlocks = 693970
    nextAllocation = 2343707
    rsrcClumpSize = 65536
    dataClumpSize = 65536
    nextCatalogID = 265932
    writeCount = 8163599
    encodingsBitmap = 00000000000000000000000000000000
    00000010000000000000000000001111
    # Finder Info
    # Bootable system blessed folder ID
    finderInfo[0] = 0x1f7ca (LaCie_Boot:/System/Library/CoreServices)
    # Parent folder ID of the startup application
    finderInfo[1] = 0
    # Open folder ID
    finderInfo[2] = 0
    # Mac OS 9 blessed folder ID
    finderInfo[3] = 0
    # Reserved
    finderInfo[4] = 0
    # Mac OS X blessed folder ID
    finderInfo[5] = 0x1f7ca (LaCie_Boot:/System/Library/CoreServices)
    # VSDB volume identifier (64-bit)
    finderInfo[6] = 0xcd566ff7
    finderInfo[7] = 0x351c415f
    # File System Boot UUID
    UUID = 38178E0C-3CC2-37E3-8E87-B5C2662DCF95
    # Allocation Bitmap File
    logicalSize = 659456 bytes
    totalBlocks = 161
    fork temperature = /* Metadata Zone */
    clumpSize = 356352 bytes
    extents = startBlock blockCount % of file
    0x74b86 0xa1 100.00 %
    161 allocation blocks in 1 extents total.
    161.00 allocation blocks per extent on an average.
    # Extents Overflow File
    logicalSize = 5242880 bytes
    totalBlocks = 1280
    fork temperature = /* Metadata Zone */
    clumpSize = 5242880 bytes
    extents = startBlock blockCount % of file
    0xa98c9 0x500 100.00 %
    1280 allocation blocks in 1 extents total.
    1280.00 allocation blocks per extent on an average.
    # Catalog File
    logicalSize = 92274688 bytes
    totalBlocks = 22528
    fork temperature = /* Metadata Zone */
    clumpSize = 11534336 bytes
    extents = startBlock blockCount % of file
    0x148dde 0x5800 100.00 %
    22528 allocation blocks in 1 extents total.
    22528.00 allocation blocks per extent on an average.
    # Attributes File
    logicalSize = 0 bytes
    # Startup File
    logicalSize = 0 bytes

  • Corrupted disk issues between iMacs and Mac OSX Lion

    My iMac can't boot up, because it started to fill a black bar at the bottom of the screen and it suddenly disappears. Tried to repair my disk but Disk Utility said "the disk cannot be repaired". So I formatted twice and made a brand new installation, and the same problem returned. I went to the apple support and they said that a bunch of iMacs were having the same issue, and told me to stay at snow leopard until a fix was realeased. Is this normal to iMac self-corruption? Or is just a real Lion problem?

    My iMac can't boot up, because it started to fill a black bar at the bottom of the screen and it suddenly disappears. Tried to repair my disk but Disk Utility said "the disk cannot be repaired". So I formatted twice and made a brand new installation, and the same problem returned. I went to the apple support and they said that a bunch of iMacs were having the same issue, and told me to stay at snow leopard until a fix was realeased. Is this normal to iMac self-corruption? Or is just a real Lion problem?

  • Any way to fix a corrupt disk without a SL disc?

    Ran Disc Utility today and got this:
    The volume X452 was found corrupt and needs to be repaired.
    Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.
    My SL disc is a 15 hr drive away, anyway to fix this?

    Sorry, but unless you can boot from another volume you cannot repair the drive. You do not require the SL installer disc, but you do need to boot from another SL system. Or, if your computer has a Firewire port then you could connect it to another Intel Mac running SL and use Disk Utility from the other computer to repair your drive.
    Now, that said you can attempt a local fix depending on what the problem is. Here's how:
    Boot into single-user mode. After startup is completed you will be in command line mode and should see a prompt with a cursor positioned after it. At the prompt enter the following then press RETURN:
    /sbin/fsck -fy
    If you receive a message that says "*** FILE SYSTEM WAS MODIFIED ***" then re-run the command until you receive a message that says "** The volume (nameofvolume) appears to be OK." If you re-run the command more than seven times and do not get the OK message, then the drive cannot be repaired this way.
    If you were successful then enter:
    reboot
    and press RETURN to restart the computer.
    Now the above cannot effect the repairs that Disk Utility can when booted from another drive or computer. But it can fix some problems. And, you should consider installing AppleJack - CNet Downloads or MacUpdate.

  • Time Machine Freezes and Corrupts Disk

    Hello,
    I have been attempting to set up one of my external hard drives for use in Time Machine, but every time I click "Erase" when Time Machine asks me to, Time Machine freezes, and my Hard Drive gets corrupt. After force quitting Time Machine and mounting my drive again, it says "The disk you inserted was not readable by this computer." I have had to go back to a PC on numerous occasions and format the disk as FAT32, and then come back and try it again. I have attempted to erase the disk through Disk Utility, but the same error occurs.
    I am attempting to do this with a 100GB Store-It drive by Hitatchi. Please let me know if anyone has any suggestions as to how I can solve this issue.
    Thanks,
    Thomas

    I had the same problem with a new 120GB WD external 2.5" HDD. It seems to perform the initial backup then gets frozen at the very end of the first actualization, CPU running at 100%. Doesn't mount any more, DU shows it but declares it as non-repairable because of different issues: index faulty, B-tree header faulty etc. The same on another Mac. Re-formatting leads to the same results.
    What to do?
    Berndt

  • Installation LS failed. Corrupted Disk??

    I tried to install Snow Leopard last week (upgrading), but with still 46 minutes to go.I got message to clean the disk and try again. Which I did several times. Same error.
    I tried via start holding "c" and starting up from installation disk, but after a while I got message that files could not be copied etc...
    I used disk utilities to verify disk and permissions, but disk seems to be Ok according Disk Utility.
    When I looked into the log files it shows 5 warnings about SUID files that has been modified and were not repaired.
    Maybe somebody can explain (regarding permissions differ etc........ and the 5 warnings regarding SUID files) and if I have to worry or have to take action.
    Is it just a problem of corrupted installation disk? or of my system somehow?
    I have inserted a part of the disk utility log to illustrate.
    r-- .
    2009-09-07 01:29:46 +0700: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTPlugIn. prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    2009-09-07 01:29:46 +0700: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTRegiste r.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    2009-09-07 01:29:46 +0700: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTRegiste r.prefPane/Contents/Resources/QTAbout.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    2009-09-07 01:29:46 +0700: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTStreami ng.prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    2009-09-07 01:29:46 +0700: Permissions differ on "System/Library/PreferencePanes/QuickTime.prefPane/Contents/Resources/QTUpdate. prefPane/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    2009-09-07 01:29:53 +0700: Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
    2009-09-07 01:29:53 +0700: Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/ CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
    2009-09-07 01:29:55 +0700: Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResou rces", should be -rw-rw-r-- , they are lrw-rw-r-- .
    2009-09-07 01:30:45 +0700: Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
    2009-09-07 01:30:46 +0700: Warning: SUID file "System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Reso urces/Locum" has been modified and will not be repaired.
    2009-09-07 01:30:46 +0700: Warning: SUID file "System/Library/Extensions/webdavfs.kext/Contents/Resources/loadwebdav" has been modified and will not be repaired.
    2009-09-07 01:30:47 +0700: Permissions differ on "System/Library/CoreServices/Menu Extras/RemoteDesktop.menu/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    2009-09-07 01:30:49 +0700: Warning: SUID file "usr/sbin/pppd" has been modified and will not be repaired.
    2009-09-07 01:30:49 +0700: Warning: SUID file "usr/sbin/vpnd" has been modified and will not be repaired.
    2009-09-07 01:30:54 +0700:
    2009-09-07 01:30:54 +0700: Permissions repair complete
    2009-09-07 01:30:54 +0700:
    2009-09-07 01:30:54 +0700:
    Thanks in advance
    Hans

    I think you are using good judgment. But, in case you decide to install given a safe way to do so, then here is a safe way.
    In your place, I would move to SL if, and only if, I had an external drive with a bootable clone of my internal on it and had my files backed up in some other secure place. I think that there is enough risk in going to SL that such conservatism is warranted. I would not use time machine alone for backup/restoring. This app can be problematic and, consequently, its solo use is too risky for me. You will be able to extract your settings, files, and programs from your clone if you do an erase and install.
    To erase and install (see upgrade option below), start up to your DVD and stop after selecting your language. Use the menus to start Disk Utility and erase your drive. Quit Disk Utility and proceed with your installation. At the end, you will be able to choose to reclaim your settings, files, and apps from the clone (plug in the external at the point of the last install restart).
    If you do not like SL, then you can restore your internal using the clone. I would do all cloning and related restoration with SuperDuper or some other up-to-date cloning app. Your clone also will serve as an independent backup for your data.
    Upgrading is a very sound process on a Mac. Still, I also would insist on having a bootable clone on an external before upgrading. An upgrade is performed by installing over your existing installation from the desktop or having started from your SL DVD. All your programs, data, and settings will be present after an upgrade, but incompatible programs will be archived.

  • T42 File recovery with corrupted disk

    I have an error on my T42 that is not allowing it to boot in Safe mode or any other. I have used the IBM Rescue & Recovery tool to store all files that show up on my c and d drives to another network drive. However, it looks like it did not copy anything but original OS files to my network drive. Not the My Documents directory which is really what i need.
    Is there a utility that can help me search the disk and recover my My Documents folder? I am entering this message through the Opera browser in the Rescue & Recovery application.
    Thanks

    R-Studio
    It must be run from another computer with the corrupted connected via USB or as a second hard drive..
    \\ I do not respond to PM regarding individual tech support. Keep discussions in the forum for the benefit of others //

  • Can Floppy Drives corrupt disks?

    Is it possible that a floppy drive can be corrupting every disk that gets placed in it?
    I have been trying to copy off all the data I have on floppies from the mid-late 1990's to my 7100 now that I upgraded the orginial 250 MB HD with a 4 GB disc (which I'll probably never fill up, but hey, it was free). The drive was working without flaw until last week when I attempted to install ClarisWorks 4.0 from floppies. I think Disc 1 got corrupted somehow (my guess is dirt got inside the casing, as there seem to be circular scratches on the disc surface and it made a strange noise in the drive), and the drive wouldn't read it. But now, it seems like 2 out of every 3 discs I put into the drive are unreadable because "A disc error occurred."
    I know they're about 10+ years old, but I find it strangely coincidental that all of a sudden all the discs I'm putting in happen to have disc errors. Could all of them have gone bad all at once? Or did that dirty CW 4 disc screw up my drive somehow, which is managing to spread to all other discs inserted into it. I have an external USB drive that I've attached to my G5, and the discs are unreadable when I put it in there as well. However, if I put in a disc that I haven't yet put into the 7100, they seem to read fine.
    Any thoughts? I really want to get all this data off these discs.

    Michael,
    The most common problem is read errors. Demagnetizing requires a power circuit that is in record mode. The holes in the disk offer a 'do not erase' position to prevent that possibility. Accidental over-writing is always possible. When we have floppy disk errors, we take the disk to five or ten other computers and sometimes one will read the disk. It is totally trial and error.
    Salvaging the data by any other means requires a level of sophistication and diagnostic equipment of a known quality that most owners charge dearly for their services.
    When we need to transfer files using floppy disks with older computers, we follow a little ritual. If a disk fails to be recognized from one particular machine to another, we then format another disk in the destination machine, add test files, then test it in the machine of data origination.
    There is a lot of variation in older disk drives manifest over time and hundreds of computers. Expensive equipment or lots of trial and error may be your only hope. Just be sure and make your trials with unimportant disks to test the quality of the drive you are about to use.
    Ji˜m

Maybe you are looking for