Disk utility errored out when attempting to repair Macintosh HD

My iMac suddenly got really slow this morning, occasionally freezing for a few minutes. I ran disk utility to repair permissions, MacJanitor and then restarted to no avail. Then I started up using the original install CD (10.4.4), ran the hardware test and passed, and attempted to repair the disk with Disk Utility. I got through the first steps, but then when checking the Catalog File, I got the following error:
Invalid Node Structure
Volume Check Failed
Error: Underlying task reported failure on exit.
Before I exited, I repaired disk permissions again, and this time it found a bunch of bad permissions...when I restarted, system was still slow, so I know I still have a problem
Any suggestions on what to do next?
Thanks,
Eric

Try that disk repair a few more times, you never know!
But more then likely it won't be able to repair an Invalid Node Structure. That's a pretty serious error.
If Disk Utility can't fix it, you'll need a more robust utility for the repair. I would recommend DiskWarrior. It is the best at directory repairs. It rebuilds then actually replaces your old directory. I feel every Mac owner should have a copy. Make sure you get the disk so you can boot up on it to run repairs. You can also install it on another drive and run it from there to repair this one. DW works faster that way.
I use DW once a month to try and catch errors in my system from getting too far out of hand.
If you have a good backup, hopefully a clone of your system before you had issues, an Erase and Install will also rid you of this issue. But, beware! You will lose everything on the drive with this procedure. Let us know if you need help with that!
Cheers! DALE

Similar Messages

Disk Utility Error 61 when attempting to create disk image on external driv

I would like to make occasional archive backups of my three macintosh computers. I bought a new Western Digital 2TB drive for this purpose, and formatted it as Mac OS Extended. Trying to do a disk image backup using Disk Utility, I follow the directions:
- Startup from an install DVD.
- Start Disk Utilities and select "Restore"
- Drag "Macintosh HD" into the Source box
- Click on "New Image" and select compressed and 128-bit AES encryption
This leads to the error message: Unable to create "....." (error -61)
I have enocountered this problem both with my iMac G5 and a MacBook, both running Leopard.
Does anyone know what this error means, what I am doing wrong, and/or if there is another way to create disk image backups? Help!

1. For reasons I don't know disc images seem to become more fragile the larger they get. They also can be subject to file corruption that affects the entire disc image, whereas file corruption on a clone would only affect certain files.
2. You cannot put multiple clones on the same volume. Each clone must be on a separate volume, but you can have multiple volumes on a single drive simply by partitioning the drive accordingly. Of course you need a drive large enough to accommodate each clone. Each clone should be to a space equal to the capacity of the cloned drive.
3. I'm not a big fan of TM, although I must confess it has become more reliable since it's release, especially with Snow Leopard. However, there are many backup utilities that can create clones, perform incremental updates, and archive changed files. See the following:
Backup Software Recommendations
Carbon Copy Cloner
Data Backup
Deja Vu
Silver Keeper
MimMac
Retrospect
Super Flexible File Synchronizer
SuperDuper!
Synchronize Pro! X
Synk Pro
Synk Standard
Tri-Backup
Others may be found at VersionTracker or MacUpdate.
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.

Disk repair button in disk utility greyed out and I cant repair my disk

Safari stopped working totally and I downloaded it again but it wont allow me to install it onto the hard drive saying it cant use the software. Disk utility has detected that the disk needs repair but the repair button is blanked out.
Also I have password issues because it wont recognise my master password even though I know what it is. Even though I dont need it now I am sure I will in the future.
Crappy apple 'support' want our money but they only give support for 90 days. If they were so confident about their products working properly they would give us more than 90 day support and if their products really were good then we woudn't need to call would we? MAC *****

I don't know about AppleCare, but they will do an electronic bank draft type vehicle for major purchases as well.
Tiger DVD (now 10.4.6):
Disk Utility - Restore to backup
Reset Password
And "fsck" is your friend to repair the boot drive when you don't have a back up system/clone. Also get a copy of Applejack and use it as well.
Always always backup before applying OS installs and updates.
Might want to start with Apple's Mac 101 Help:
http://www.apple.com/support/mac101/help/
It can help walk you (and us) through what steps...
boot into Open Firmware and Reset NVRAM
boot to your Apple Hardware Test disk using OPTION key and run tests
run Memtest 4 from Single User Mode
MacIntouch: Bad RAM
clone your boot drive system and apps and backup data
Tiger is now out on DVD with 10.4.6 - updated and easier to upgrade
boot into Single User Mode
run
- Best done after ANY freeze or hard restart
install Applejack gets run in Single User Mode
Using Applejack
MacFixit: Repairing Permissions
General Troubleshooting permissions
Repairing Drives
Backup!
G4 MDD 1.25 1.75GB UL3D 15K/10K RAID Mac OS X (10.4.6) SoftRAID 3.5

Disk Utility error msg: Filesystem verify or repair failed!!!

Ok so after erasing my partitioned HD I wanted to use the rest of my HD on my start up HD, So I pulled the expander in the partition window to resize the volume of the HD. Then I clicked apply to resize the HD and ended up with a Partition Failed message that stated
Partition failed with the error:
Filesystem verify or repair failed.
What do I do from here to get my current HD at full capacity?
The current size is 19.9 GB and it should be at 60 GB.

Ok, so I had a partitioned hard drive, and I wanted to expand the start up drive and delete the unnecessary partition. So in disk utility I clicked on partition and deleted the partition I didn't want.
Then I used the expander thing in the bottom corner of the start up hard drive box and clicked apply to enlarge it, but filesystem verify or repair failed message appeared.

Disk Utility error -39 when making image of HD backup

Whenever Apple releases a substantial update I first make a backup of my boot disk to an external Firewire drive before installing it. Before overwriting the existing backup, however, I make a compressed image with Disk Utility on another partition.
With 10.4.4 and 10.4.5 making the image fails with error -39. Somewhere I read that the error had to do with Disk Utility's not being able to cope with large disk images.
Is anybody experiencing this problem? Is there a solution, a workaround, or another program that I could use?

1. For reasons I don't know disc images seem to become more fragile the larger they get. They also can be subject to file corruption that affects the entire disc image, whereas file corruption on a clone would only affect certain files.
2. You cannot put multiple clones on the same volume. Each clone must be on a separate volume, but you can have multiple volumes on a single drive simply by partitioning the drive accordingly. Of course you need a drive large enough to accommodate each clone. Each clone should be to a space equal to the capacity of the cloned drive.
3. I'm not a big fan of TM, although I must confess it has become more reliable since it's release, especially with Snow Leopard. However, there are many backup utilities that can create clones, perform incremental updates, and archive changed files. See the following:
Backup Software Recommendations
Carbon Copy Cloner
Data Backup
Deja Vu
Silver Keeper
MimMac
Retrospect
Super Flexible File Synchronizer
SuperDuper!
Synchronize Pro! X
Synk Pro
Synk Standard
Tri-Backup
Others may be found at VersionTracker or MacUpdate.
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.

Why am I getting a "Disk Full" error message when attempting to export?

I am trying to export my movie at large quality or higher and every time it gives me a "disk full" error. However, I was able to successfully export it at medium quality. I don't understand why I would be getting that error though because both my internal hard drive and external drive, which I am exporting from (but onto the internal), have ample amount of space to accommodate for a large or HD quality video. Any help would be much appreciated!

How much space do you have?

A Disk Utility error message when creating a dmg file

I was trying to create an encrypted dmg file on a USB Drive. It was going smoothly, I had entered the password twice, and then 30 seconds later I got an error message: "unable to create "name-dmg" -illegal seek"
I tried the Help menu, as well as Sherlock to search AppleCare but couldn't find a thing.
Any ideas?

1 The DU info says....
Name.....Kingston
Type.....Volume
Disk Identifier....Disk2s1
Mount Point....../volumes/KINGSTON
File System....Mac OS Extended
Connection bus...USB
Partition type....Apple_HFS
Writable.....Yes
Universal Unique identifier...(too long to write it too)
Capacity....7.5GB
Free Space....&.5GB
Used.......12.5MB
Number of Files....6
Number of Folders....4
Owner enabled.......No
Can turn owners off....Yes (I'll say)
Can be formated....Yes
Bootable....Yes
Supports Journaling....Yes
Journaled.....No
S.M.A.R.T. Status.....Not supported
Disk number....2
Partition number....1
2. The file names I tried were "Financial" then the default on "Disk2s1". By default I mean it's already inserted when the window appears.
3. The size of the image of the image I want to create is 7GB. But like I said this latest attempt a field for selecting a size wasn't in the window. I did set it for 7GB originally.

ITunes crashes / errors out when attempting to get Outlook 2003 contacts

OS: XP Pro SP2
APPS: Office Pro 2003 SP2, iTunes v.6.0.4.2
Hardware: iPod Nano 2GB
Problem: When I sync my ipod nano, iTunes opens, the music syncs and then I get an error:
“iTunes cannot copy contacts to the iPod ‘my name’”
Probable Cause: I installed from MSN Premium something called “Outlook Connector” I was going to use to synch my MSN Hotmail & my Outlook contacts. I believe it was after this install when I began having trouble with synching my contacts between my iPod Nano and Outlook 2003 SP2 for windows.
Solutions I have tried:
- Repaired Outlook using “Detect & Repair” as well as scanpst.exe
- Cleaned the registry
- Restored an older backup PST Outlook file
- Talked with MSN support who referred my to iTunes support
- Purchased Apple Care program (or something)
- Update iPod (wasn’t needed)
- Uninstalled/Reinstalled iTunes
- Scoured google, these forums, newsbin, ms kb, etc…
- The last thing I will do is to restore my whole hard drive to an time when my ipod did synch fine
Please help if you can. I really think this has to do with that MSN Outlook Connector, but I have removed all known traces of it. I wanted to make sure I to get an answer and posted this in both the nano as well as itunes for Windows forums, my apologies if that’s taboo.
Thank you in advance for any assistance, even if someone can point me to more resources.
Paul

I fixed this, YES!
For those who it may help, I went into:
Outlook 2003 > Tools > Address Book
From there I saw theat Outlook Connector (or soemething) created a new address book for my MSN/Hotmail and made that address book the default one.
I simly made my old one the default and ipod now synchs with the Outlook contacts.

Disk Utility error when verifying DIY fusion drive

Hi,
It has been a while since I had to post a problem, but I need others advice on this if you can help. When 10.8.3 came out I installed an M4 512gb ssd in my main drive bay of 2008 unibody aluminium macbook and put a 1tb spinner in the optibay. Created a fusion drive, migrated data and all has been great. Decided to run disk utility today to check for any errors as I had a sleep issue with the 10.8.4 update which I ended up solving by changing the sleep settings in terminal - the issue had caused a few forced shutdowns. I have Disk Utitliy Version 13 (450). The Fusion drive is shown as the logical volume group followed by the volume disk. When I run a verify disk on the volume itself it is all ok:
Verifying volume “Cybernet”
Checking storage systemChecking volume.
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 2170 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 6 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify 309877EC-EA53-443C-A75C-63C159B04EF3
Load and verify 5388E543-6974-4251-BDBD-FA850C121897
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.
Checking file systemPerforming live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Cybernet appears to be OK.
When I run it on the LVG it comes up as:
Verifying partition map for “M4-CT512M4SSD2 Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Checking Core Storage Physical Volume partitions
Checking storage system
Checking volume.
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 2170 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 40 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify 309877EC-EA53-443C-A75C-63C159B04EF3
Load and verify 5388E543-6974-4251-BDBD-FA850C121897
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.
Incorrect size for volume “Cybernet”
Problems were found with the partition map which might prevent booting
Error: Incorrect size for logical volume.
Verifying partition map for “WDC WD10JPVT-00A1YT0 Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Checking Core Storage Physical Volume partitions
Checking storage system
Checking volume.
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 0DAE76E1-A325-4925-902F-1015B270B84C spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 2170 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 43 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify 309877EC-EA53-443C-A75C-63C159B04EF3
Load and verify 5388E543-6974-4251-BDBD-FA850C121897
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0DAE76E1-A325-4925-902F-1015B270B84C appears to be OK.
Incorrect size for volume “Cybernet”
Problems were found with the partition map which might prevent booting
Error: Incorrect size for logical volume.
I got the same when I did a safe boot and when rebooted from the recovery partition.y question is, do I repair or could it damage my setup? eg is Disk Utility being accurate and it can repair the error, or is it a phantom issue that should be ignored bearing in mind it's a DIY fusion drive and it could end up getting mashed?
Thanks!

Hi,
The computer's running fine since I sorted the sleep issue. No issues as far as I can tell, which is why I was surprised to see the error. What does the error actually mean - is it saying that the volume is a different size than the computer thinks it should be and therefore it'll just change a few values? In which case I suppose a repair is harmless? I just don't want to repair and then reboot to find the volume corrupted.

"an error occurred when attempting to change modules" I can not uninstall its grayed out.

I installed lightroom but at opening i have an error "an error occurred when attempting to change modules" I can not uninstall its grayed out.

I fixed the problem myself, no response in chat nor phone (1 hour in hold an no answer) here's the link, step # 5 saved me! Here's the link seems to be a very common problem, hope it works for you! Error changing modules | Lightroom

Os x could not be installed on Mac book pro because storage system verify or repair failed. When i open disk utility HDD does not let me repair.

os x could not be installed on Mac book pro because storage system verify or repair failed.
When i open disk utility HDD does not let me repair.

In order to repair the system disk you must boot from another disk drive. The operating system will not allow the disk drive it is running from to be repaired.
Book the MBP and create a bootable clone on an external disk drive. Then boot from the external disk drive and repair the system disk drive from there.

Disk Utility Error: The underlying task reported failure on exit 1

    #!/bin/bash
      # Author : Bill Hernandez
    # Location : Plano, Texas
    # Updated : Saturday, June 6, 2009 (1:48 PM)
    # script name : setdisk_ownerenabled
    # make sure to set permissions to execute
    <hr>
    # Description :
    <hr>
    # I've noticed that sometimes when using disk utility I cannot repair permissions, or I might get :
    # ERROR: The underlying task reported failure on exit 1
    # This shell script seems to have solved the problem.
    # It worked very well for me,
    # IF YOU USE THIS SCRIPT, IT IS AT YOUR OWN RISK...
    # DO NOT USE IT UNLESS YOU UNDERSTAND WHAT IT DOES
    # After running it, it is best to restart before using Disk Utility again
    <hr>
    # Details :
    <hr>
    # After partitioning a disk using "Disk Utility", and then begin using it, at some point I would get
    # an arror message when trying to save to one of the partitions, yet when I looked at the permissions
    # everything looked fine. I would then try to use Disk Utility to repair permissions and end up with a
    # cryptic error that pretty much told me nothing.
    # I noticed that while in Disk Utility, if I selected a partition the lower LH corner of the dialog
    # showed : Owners Enabled : No
    # I tried selecting the partitions at the Desktop and doing a (CMD-I) and at the very bottom of each
    # info dialog there was a checkbox :
    # [ ] ignore ownership of this volume
    # which I would check, even after logging in as root, and I couldn't seem to get a consistent way
    # to get rid of the permissions dialog failure, so I found the vsdbutil command which can be used
    # as follows to get partition, or disk info :
    # $ vsdbutil -c /Volumes/driveor_partitionname
    # ----> Permissions on '/Volumes/driveor_partitionname' are enabled.
    # if it is not enabled you can enable the disk or partition using :
    # $ vsdbutil -a /Volumes/driveor_partitionname
    # It will set "Owners Enabled : Yes"
    # This below script loops through the mounted disks, partitions, etc. and gives you information.
    # You can leave the three flags below all set to TRUE, or selectively use what you want and change
    # the rest to false...
    <hr>
    # CHOOSE {"TRUE", "FALSE"}
    <hr>
    getvolumestatus="TRUE"         # get "Owners Enabled : (Yes|No)" status
    setvolumestatus="TRUE"         # set "Owners Enabled : Yes"
    list_volumes="TRUE"                   # show volume names
    <hr>
    # DO NOT CHANGE ANYTHING BELOW HERE
    <hr>
    if [ $getvolumestatus == "TRUE" ]; then
     echo '============================='
     echo '$getvolumestatus'
     echo '============================='
     # get "Owners Enabled : (Yes|No)" status
     for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
     vsdbutil -c $i
     done
    fi
    <hr>
    if [ $setvolumestatus == "TRUE" ]; then
     echo '============================='
     echo '$setvolumestatus'
     echo '============================='
     sudo echo -n
     # set "Owners Enabled : Yes"
     for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
     sudo vsdbutil -a "$i"
     echo "setting Owners Enabled : Yes for ---> $i"
     done
    fi
    <hr>
    if [ $list_volumes == "TRUE" ]; then
     echo '============================='
     echo '$list_volumes'
     echo '============================='
     for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
     echo $i
     done
    fi
    <hr>


As it turns out, this didn't completely solve the problem, it solved part of the problem.
Here is a summary to the root cause of the problem.
SUCCESS...
Problem Summary : The system crashed and would hangup during boot, tried many things, until I eventually erased the disk and started over again.
iMacG5 24 GHZ Intel with One internal disk partitioned into 3 logical drives
Cub_1 OS X 10.5.7
Cub_2 OS X 10.5.7 (Carbon Copy Cloner backup of Cub_1)
Cub_3 OS X Server 10.5.7 (standard os x server setup)
At some point after setting up standard preferences, OS X Server crashed.
When I tried to restart, the machine would hang up during boot.
Finally after several attempts, ran Disk Utility from install dvd and repaired Cub_3
When I tried to run "Repair Permissions" on Cub_3 from install dvd, I got an error
Disk Utility Error: The underlying task reported failure on exit 1.
Rebooted, and started in single user mode (CMD-S) during boot until I saw the unix commands on the screen
RAN : root # fsck -fy
Then I began seeing the same command filling the screen :
posix_spawnp("/usr/sbin/mDNSResponder") could not find file or directory
Called Enterprise Support and spoke to Frank Alcorn, he said this was most likely a permissions problem and asked me to try repairing permissions from the install dvd. I told him about the error, but nevertheless I tried it again and got the same Disk Utility Error: The underlying task reported failure on exit 1..
He asked me to try booting into single user mode again, and to try
root # chmod 775 /
root # reboot
During the reboot process the machine got hung up again, and could not get the single user mode to work at all.
Frank said the command needed to be :
root # chmod 1775 /
Frank asked me if I had changed anything in file sharing, and I told him I had. He asked me what I had shared, and I said the entire drive Cub_3. He asked me what I had done for permissions, if I had denied permissions to anyone. I told him that I had set myself up as the only user that could have access to it, and when he said that's where the problem was the lightbulb went off, and it made sense.
Shortly after I set the sharing preferences is when the server crashed. It all makes sense now...
Frank said not to share the entire disk, only portions (share points) of it. I had done this in Panther Server, and Tiger Server and it worked fine, but apparently Leopard Server works a little differently, maybe more secure.
It seems to me that if sharing the entire disk, which is what I needed would cause such a problem there should have been some sort of warning from the operating system, but there wasn't. I had run into this problem several times over the past three weeks since I had started working with Leopard Server, but in each case I ended up re-installing OS X Server and starting over again.
I told him I would try to reboot from the OS X partition (Cub_1) and try it from there.
He asked me to let him know if it worked, and I said I would...
Problem FIX :
I booted back into the partition containing OS X (Cub_1) and did the following via the Terminal.
$ su - root
$ chmod 1775 /
$ reboot
During the reboot process I held down the (OPTION) key, and selected Cub_3 (the os x server partition) and sure enough after a few minutes of holding my breath the login window magically appeared. So I logged in, and did not have to re-install the server. Hallellujah....
This solved the boot hang problem. It is great to finally have an answer. In retrospect it makes sense, but that's why its hindsight...
The reason for sharing the entire disk in my mind was that since I was the only user on the system, it was easier to have one disk mounted on my workstation rather than several folders. It made sense to me, it still does. I don't need a bunch of folders, just one disk is easier...

Error message when attempting to use scanner Canon model MP610

Error message when attempting to use scanner Canon model MP610, any one have any fixes, suggestions?

Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, empty trash, reboot when complete.
For the other problems...
See if the Disk is issuing any S.M.A.R.T errors in Disk Utility...
http://support.apple.com/kb/PH7029
Open Activity Monitor in Applications>Utilities, select All Processes & sort on CPU%, any indications there?
How much RAM & free space do you have also, click on the Memory & Disk Usage Tabs.
Open Console in Utilities & see if there are any clues or repeating messages when this happens.
In the Memory tab of Activity Monitor, are there a lot of Pageouts?

Lightroom 4: An error occurred when attempting to change modules.

I downloaded Lightroom 4 a few days ago and installed it on my MacBook Pro. Everything worked great. I thought it would overwrite Lightroom 3, but it didn't. So Lightroom 3 is still installed, but I haven't opened it since I installed Lightroom 4.
I downloaded Lightroom 4.3 this morning and installed it on the same MacBook Pro. Using my MacBook Pro and a second monitor, I opened Lightroom 4.3 and worked on some photos. Everything worked great.
Then I began watching a slideshow in the Lightroom 4.3 slideshow module on the second monitor with my MacBook Pro in the library module. During the slideshow I clicked on the slideshow module on my MacBook Pro and got this error message:
An error occurred when attempting to change modules.
Now I can’t get into the slideshow module. I just get the error message.
I moved the preferences file to the trash and reopened Lightroom 4 but lost color labels, so I put it back in the preferences folder.
Thanks for your help

I called Adobe and let them fiddle online with Lightroom on my MacBook Pro. The Adobe tech claims I have a corrupt permissions file. He told me to contact Apple and have them rebuild my permissions file.
When I contacted Apple, the tech said to startup my MackBook Pro with the option key held down until the first screen appears. Then click on: Recovery HD, arrow, Language, Disk Utility, Macintosh HD, Repair Disk Permissions.
I did this three times, but some permissions were not repaired. Another Apple tech then suggested I bring my MackBook Pro to a Macintosh authorized repair shop, and have them repair my permissions file. I asked if I can buy Norton Utilities or a similar program and do it myself. The Apple tech said yes, but an authorized repair person will know which permissions to repair and which ones not to touch.
Unless someone on this forum can tell me how to do this repair myself, I’ll get it repaired next week. And, I’ll post the results as soon as I can.

Purchased Light Room 5, installed, registered .. but keep getting this screen "An error occurred when attempting to change modules. ... OK" ?? WTF? ?

Installed Light Room 5.2 from Disc on my mac os x (latest, updated version)
But keep getting this "An error occurred when attempting to change modules.. OK" no other options/selection and of course if I click OK ... it crashed out ...
Can anyone help?
For such a big company .. there isn't any chat option to get to someone to talk to !!!

Just because you are the only user on the computer doesn't mean you are the administrator.
Also, the fact that you are being asked to re-enter your serial number each time you start means that it is not being remembered because something is either preventing it from being written to you disk or (less likely) something is erasing it. This does suggest that you lack certain permissions to make changes to your computer. Not only to save your serial number, but to have access to the Lightroom files needed to change modules (they are just plug-ins within Lightroom).
Try creating a new user account and run Lightroom from there (making sure that it is part of the Administrator group).
To get to chat support, you have to choose the options:

Disk utility errored out when attempting to repair Macintosh HD

Similar Messages

Maybe you are looking for