Disk unmounted

Hi guys
When I verify the HD disk in Disk utility, red writing The disk "MACINTOSH" could not be unmounted
Incorrect number of file hard links...
The volume Macintosh HD was found corrupt and needs to be repaired.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.
Okay so when I hold the buttons down no apple appears but little lock with password window
What can i do? Anyone? And easy on me I'm just a begginer
Miro

That's a firmware password, if you don't know it, then it's a real pain to remove it.
If you didn't put it there, then someone else did and you should go to them or Apple with it as they can disable it.
In fact if someone else is managing your machine, you should just take your problem to them as they have the firmware password.

Similar Messages

Disk unmounting at logoff, how do I disable this feature?

I noticed one of my 120GB single-partition disks, used solely for backing up another 120GB single-partition boot disc, usually appears on my desktop after a short delay when logging in.
It appears that the disk unmounts every time I log out, and then remounts when any user logs in. I have a nightly backup utility that writes to that disc. When I am logged in, it works fine, but when I am logged off, the backup fails because that destination disk is not available.
Every login reveals this message in /var/log/system.log
Jul 8 07:59:38 gossamer diskarbitrationd[43]: disk1s10 hfs 571D9205-D45D-34A3-8E62-FF642016B325 Seagate /Volumes/Seagate
which seems to be the mounting of the disk, as similar messages appear for the other /Volumes only at startup.
So, does anyone have any ideas how to keep this particular disk mounted when a user logs off? It is connected on the same ribbon cable as my bootable 10.4.7 disk on a Sonnet PCI ATA66 card. I don't remember which is Master or Slave, but that's probably not a factor.

sudo defaults write
/Library/Preferences/SystemConfiguration/autodiskmount
AutomountDisksWithoutUserLogin -bool true
I tried looking at existing defaults with >defaults read
and didn't see any thing to give me an idea of any current setting that I could revert to in case of a problem.
Also, man autodiskmount says:
AUTODISKMOUNT(8) BSD System Manager's Manual AUTODISKMOUNT(8)
NAME
autodiskmount -- disk support tool
SYNOPSIS
autodiskmount
DESCRIPTION
This command is deprecated and exists only for backwards compatibility.
SEE ALSO
fstab(5)
Darwin July 18, 2004 Darwin
So, I am a little uncomfortable messing with these defaults that I don't fully understand, and not sure how to revert to the existing state.
I found the executeable in /sbin/autodiskmount, not in the /System/Library/SystemConfiguration/autodiskmount path. So that suggestion doesn't fully make sense to me. I agree that it should be possible, as I have other Volumes that remain mounted when any user logs off, they are on the on-board ATA interface. Maybe this is a unique issue with my PCI ATA66 card?
G3 Desktop, SonnetEncoreZIF G4 1GHz, 768MB, WingsAV-6MB, DVR-106D, 60GB Maxtor Mac OS X (10.4.7) PCI: TempoUltraATA66-120GB Maxtor, 120GB Seagate; TangoUSB/FW; ATIRadeon-17" LCD

Disk unmount protocols

Don't know whether someone has any ideas on this but the question has been posted on Apple AS & UNIX discussions without a reply (except for others reinforcing the question).
Here's the issue:
If, in Terminal, one does the command
diskutil mount diskXXX
or
diskutil unmount diskXXX
the response is very quick, ~1 second.
However, if this is done in AS editor as "do shell script", the unmount (while reliable) takes upwards of 20 seconds on my fast machine, whereas the mount time is very quick.
According to an AS Discussions respondent, the same sort of delay can be expected when using a Cocoa obj-C application.
Still another AS Discussions respondent had queried Mac Fix It on the reason for this and was told that it probably had to do with preparation of the disk for unmounting -- but then, why wouldn't the same thing happen directly in Terminal?
In fact, using both approaches (Terminal & AS), I tried to unmount a disk with an open application and in both cases got a "disk failed to unmount" response (meaning that the direct UNIX command results in some checking, at least).
A workaround would be great, but an understanding of what's going on might also be useful. Any ideas?

the response is very quick, ~1 second.
However, if this is done in AS editor as "do shell
script", the unmount (while reliable) takes upwards
of 20 seconds on my fast machine, whereas the mount
time is very quick.
According to an AS Discussions respondent, the same
sort of delay can be expected when using a Cocoa
obj-C application.
I don't buy that at all.
It has got to be AppleScript getting itself confused. The problem here is that you are issuing a shell command via AppleScript. So, that command runs the same speed however you run it. For some reason, in the unmount only, AppleScript is taking its time returning from the "do shell script" command. Most likely it is confused about the result of the command that was run and/or confused about the status of the process that was spawned. It probably has some hard-coded 15 second sleep to make sure the child process finishes.
I wrote a quick and dirty C++ program to test my theory. I created a disk image named "test.dmg" that mounts a volume named "test". It runs really fast. Here is the source:<pre>#include <iostream>
int main(void)
std::cout << "Mounting image..." << std::endl;
system("hdiutil mount test.dmg");
std::cout << "Image mounted..." << std::endl;
std::cout << "Waiting 10 seconds..." << std::endl;
sleep(10);
std::cout << "Unmounting image..." << std::endl;
system("hdiutil unmount /Volumes/test");
std::cout << "Image unmounted..." << std::endl;
return 0;
</pre>Now, this is a C++ program. I could have just as easily written it in C or Objective-C - it doesn't matter. The one one thing it doesn't use is any AppleEvents of any kind. A Carbon or Cocoa app could probably do the same thing using AppleEvents and it would probably be 2-3 times as slow and at least 2000 lines of code.
I'm no fan of AppleScript. Hypercard running on a MacPlus was faster than AppleScript. I really don't understand why so many people use it. If you are an AppleScript fan, I'm not going to change your mind, nor will I attempt to. But there is nothing inherent about Objective-C that would make it as slow as AppleScript. There are some "six of one, half a dozen of the other" performance issues between Objective-C's message dispatch and C++'s virtual functions. But AppleScript is something altogether different.

Startup Disk unmounted

I couldn't find a problem that matched mine exactly. I'm helping someone out at the office - she as an earlier Mac Pro running Tiger. The computer was having a kernel panic just about every morning at start-up. Today we tried running disk utility from the factory boot disc, but the process crapped out half-way through (trying to rebuild the catalog b-tree, it fails before it finishes).
Afterwards, I tried to re-boot the machine, but it doesn't see the startup disk. If you look in Disk Utility (again after booting from the boot disc), you see the hardware, but the volume 'Macintosh HD' is unmounted and greyed out now. It doesn't show up in the Startup Disk utility, and the installer doesn't even see it as a place to reinstall the OS.
What are my options? Is the HD just gone? I'm going to run out for DiskWarrior now, and any help would be most appreciated.

I believe the disk is dead.
You could alternately boot her Mac from another Mac in Target Disk Mode with firewire cable to verify that her machine is functioning ok.
But most likely the drive is gone.
Have you tried resetting PRAM and then SMC?
SMC:
http://support.apple.com/kb/HT1806
PRAM:
http://support.apple.com/kb/HT1379
Probably will not help but may be worth a shot!

Macbook Pro 13 (late 2013) - external disks unmount after sleep

I've seen many other similar posts - just adding mine to the pile - wondering if anyone has seen a fix or has a recommendation
Macbook Pro 13 inch (late 2013) the Thunderbolt and firewire drives unmount when Macbook pro sleeps. (NOTE firewire drive connected via Thunderbolt display - but same happens with TB drives when connected direct to MBP)
Not a showstopper - but frustrating - fix would be nice.
Thanks
PS I had a Macbook Air 2011, with no "unmount" problem when i upgraded to Mavericks.
PPS - Really enjoyed moving from MBA to MBP 13 - superior build quality, keyboard much better and display.... amazing. Weight difference neglible.

Short update: After reading a while I tried several keyboard shortcuts during start up ... and I solved the issue:
Hold Command + Option + 'p' + 'r' during startup. This zaps the PRAM (Parameter RAM), an option that long-time Mac users will remember. Press and hold the key combination until you hear the second set of chimes. Zapping the PRAM returns it to its default configuration for display and video settings, time and date settings, speaker volume, and DVD region settings.
Thanks to all people who document such issues and its solution.

Airport Disk Unmounts Frequently

I have a 3TB WD Elements drive attached to my Airport Extreme. My MacBook Pro (late 2008 model) is connected over wifi. Every ten minutes or so, I get an alert telling me that there was a server interruption. I just click Ignore and everything seems to keep on working.
This only seems to happen when the disk is idle. I don't have this problem if I'm copying files to or from it; for example, yesterday I copied a large number of photographs to it over a three hour period with no problems.
Is there some kind of time-out I can adjust to cut down on the frequency of these annoying messages?
Thanks,
Dave

New input: I spoke to the salesman at the store where I bought the AirPort. He said that another customer of his had a very similar problem and it turned out that it had to do with the electrical power and not the WAN. Out in the country our power supply is not very clean. I am using a UPS in my office to clean up the power and handle fluctuations (as was his other customer). Could it be that minor power fluctuations (even filtered through a UPS) could cause this issue? The satellite goes down in thunder storms - and we have really dirty power during thunder storms as well.

HT3275 I continue to get the following error message: Unable to complete back up.an error occurred while creating backup folder. It's a brand new drive. When I attempt to repair it using disk utility I get:unable to repair disk cannot unmounted

I have been trying to use time machine on a new lacie 2tb usb 2 drive for back up. I continue to get: "unable to complete backup.An error occured while creating backup folder". When I use disk utility to repair I get another error message: unable to repair disk unmountable.
Help me Obie One Canobie you are my last hope

I have confused myself with the facts! Started out keeping track of every step and every variable but have sort of lost it as we progress here. First I quit all applications then swapped connections between mouse port and backup disk port to influence possible bad connections question. Changed power outlet receptacle for the backup disk. Disabled the put-the-HD-to-sleep option. Then powered down the computerator.
Next started up computerator. Turned Time Machine ON and experienced multiple successful backups! Then I started up a few applications, Mail and Text Edit (but not Safari so far). Had a few more successes. After each backup, I used Disk Utility to verify the backup disk is still OK. This because the error about unable to unmount the backup disk seems to go hand in hand with Disk Utility finding the backup disk to be bad.
Put computer to sleep for the night. Upon starting up in the morning, and before doing anything else, I did a backup disk verification... BAD! Did a restart and verified the backup disk... OK.
Did a few Sleep-bad, Restart -OK repetitions.
It seems consistent: Sleeping the computer apparently messes up the backup disk but doing a Restart "repairs" it.
=============================
Now then, I don't understand everything I know here. Methinks that maybe keeping the HD from sleeping during lulls in activity has allowed successful backups through the day but manually putting everything to sleep for the night causes a return to the problem of spinning-back-up-too-slowly (which was explained earlier). Is there any truth in this?
I may abandon this Seagate thing for something more compatible. What's out there that we know works reliably for us?

Usb disk is unmounted automatically

Hi,
I have attached a 2TB USB disk and set up rsync to make a 'backup' (I know, it is not a backup, merely a copy) to this backup-disk.
But: without any mention in the logs, the disk gets unmounted. I have rebooted the server yesterday evening at 23:00 and I made sure that disk was mounted. This morning at 9:00, the drive is not mounted anymore... Of course this can cause problems, because rsync is scheduled to run every day, and if I make a copy to a directory on the same disk, I'll be out of space very soon.
I have also noticed that when the drive has not been used for a while, that it takes some time for tab completion in bash to work when working on that drive - but I guess that is caused by te disk spinning down in between uses...
Is there something I'm overlooking in my setup or should I script away (in udev I suppose) and check if the drive is mounted before running the rsync?
Drive details: Samsung Story Station 2TB USB / 1 partition (ext4) / mounted by UUID in fstab:
UUID=e3434573-ad6f-4c44-8168-391292ba5ec5 /media/backup ext4 defaults 0 0
The server is a brand spanking new install with up-to-date archlinux x86_64.
Thx!

I've never had problems with usb disks unmounting spontaneously, so I'm just guessing, but could it be usb powermanagement? laptop-mode-tools does all kinds of powermanagement tuning, so if you have this installed disable it to see if that is the case. The spindown is caused harddisk powermanagement that you can set with hdparm, but this shouldn't cause unmounting. To determine if the problem is specific to that particular usb harddisk, all usb harddisks, or all usb storage see if it happens with a usb pendrive as well, or a different usb harddisk.
Last edited by rwd (2011-03-05 17:32:29)

PhotoShop CC 2014 - Blowing Directories on Hard Drives - Should Ship with a free Version of Disk Warrior ;-)

Since installing PS CC 2014 I have had serious problems.
Problems one could expect from a 'new' software.
However, having my drives' directories damaged due to Scratch Disks is something I have never seen before.
I had PS use an SSD as Scratch Disk. As this became full, I assigned another scratch disk (This time a RAID0).
As it ran full (200GB of PS Scratch) All the other files on that drive vanished. And photoshop was no longer able to even save the current document
(event though the destination had enough space avail.) See screenshot:(Watch the finder status in the back, the doc to be saved was 200MB and my disk had 3.38 GB avail.
But PS would not let me save due to scratch disks full)
Anyway, back to the serious problem. The RAID0 scratch disk, after I quit PS, was not longer mountable.
Trying to repair it with DU reported:
And trying with terminal This:
** /dev/rdisk13
Executing fsck_hfs (version hfs-226.1.1).
** Checking Journaled HFS Plus volume.
** Checking extents overflow file.
** Checking catalog file.
** Rebuilding catalog B-tree.
CreateNewBTree returned -34
Disk full error
So I went ahead and did some research and found Disk Warrior.
It was able to rebuild my catalog and I am up an running again.
But having to spend $99 on a PS bug is not so nice. I have been able to recreate this problem 3 times the past hours.
The problem occurs only when PS is using the RAID as Scratch disk. If I try to fill the drive by writing to it via terminal or Finder,
i just get a Disk is Full. PS on the other hand will blow the catalog and make the disk unmountable...
Any Ideas ?

Thanks for your reply, Chris Cox. I've checked the Windows System Event Log and here are the details:
Details (Tab) of same error (Photoshop)
I noticed since Jan 5, 2015, Photoshop has crashed a lot. I run Adobe Illustrator with it but it doesn't give the same errors. Other applications run fine too, so I'm not sure if it as you mentioned that it is the "system" that is crashing so often.
(You seem to have suggested a video card upgrade. I will work on that next. Thanks)
I hope you or anyone who can, help me with this problem with Photoshop and the issue with my account in Creative Cloud.
Looking forward to your help. Thank you.

Permissions are badly messed up on any disk Time Machine has used to backup

*The Short Version:*
After using an external disk as a Time Machine target, disk permissions are forever and always utterly ignored which causes huge problems when said disk is supposed to share publicly and privately accessible files/folders over the local network.
Said disk is no longer used for Time Machine, but permissions still refuse to work after the "Ignore ownership..." option is disabled, ACL's are cleared, and more.
*The Long Version:*
So, I'm trying to share some folders off of an external disk I temporarily used for a week as a Time Machine backup disk.
Because I have both "public", and private documents on the disk, I need to use disk permissions, to disallow access to some folders. Enabling file sharing works great, except any and every user get full read/write access to everything.
I have another external aswell, which is identical, just it's never been used as a Time Machine target volume, and permissions are obeyed perfectly.
Originally I think the Ignore ownership option was enabled, but the checkbox wasn't showing up on the Get Info panel. After some messing around, I realized it's not displayed if there's a folder called "Backups.backupdb" on the root of the disk.
Now, a few hours later, after renaming "Backups.backupdb" to "Backups.backupdb_OLD", clearing ACL permissions from the disk, unmounting, mounting, restarting file sharing, and lots more, IT STILL IGNORES ANY AND ALL PERMISSIONS?!
Is there some kinda super secret disk flag option or something I'm missing which causes OSX to still ignore permissions no matter what?
I hope someone here knows what's going on, 2 hours of Googling hasn't helped at all.

UPDATE
I seem to have gotten file sharing to obey the permissions, to some degree. It included removing the share from system preferences, using TinkerTool System to change the permissions to anything (didn't seem to work via normal Finder, as I'd already tried that), and then adding the volume back in sharing preferences.
This doesn't really seem very reliable tho, so I'm hoping someone can come with a technical reason/solution for this.

Yosemite: problem with external disk

Hello,
After installing Yosemite I cannot use Time Machine anymore because the external disk (WD My Passport Edge) cannot be mounted. Does someone know what to do? Thanks in advance for your help.
The Disk Utility Program shows the external disk however none of the action button is active.

See mount section at the end.
Disk Unmount Using Terminal
Disk Utility – Force Mount Disk

Best approach for Time Machine / Entourage / FileVault / sparse bundle disk

I am looking to set up Time Machine belatedly on my G5 to provide hassle-free backup for me and my family. I use Entourage. I also want to provide a small amount of encrypted storage. I’ve scoured the obvious places which have plenty of ideas, but nothing which pulls it all together.
My thoughts so far have been:
1. Time Machine doesn’t work well with Entourage as Entourage uses a monolithic single file (which in my case is several GB big) – backing this up every hour will bring my machine to its knees, fill up the backup disk and will possibly give a corrupt backup as the file could be accessed by Entourage or the MS daemon process during the backup.
2. I thought of turning FileVault on which would automatically contain the Entourage file. This would mean:
a) the sparse bundle format (8 MB bands) of FileVault would limit the volume of changed Entourage data which would be backed up each time by Time Machine and
b) the backup would only occur during logout (which is fine with me) when Entourage and the MS daemon are not running so that the backup won’t be corrupt.
3. However I am not hearing good things about the reliability of FileVault (comments?) and don’t want all the data in my Home folders lost – I don’t need that much encryption anyway.
4. So I thought about setting up a couple of encrypted disk images made of sparse bundles – one for the Entourage data (symbolically linked to the right place for Entourage to pick the folder up) and the other for the other small number of files I need encrypted. This could be auto-mounted at login.
5. However I think that using disk images rather than FileVault loses the automatic backup by Time Machine at logout. Maybe there is a way to get Time Machine to automatically backup these disk images during logout.
6. Perhaps there is another way to get the disk images backed up at logout other than using Time Machine.
So my questions are:
A. What is the best overall approach to providing a low-maintenance reliable backup which deals appropriately with Entourage and provides a small amount of encrypted space?
B. Can Time Machine be made to backup disk images other than FileVault disk images at logout? (for example is there a particular location / filename format for FileVault images which I could emulate with the other disk images to fool Time Machine into backing them up?)
C. When Time Machine runs at logout, have MS Entourage and the daemon process already been shut down and the disks unmounted, to prevent corruption?
D. Is there another way of backing up the sparse image disks at logout?
C. Is this all going to get magically fixed in Snow Leopard?
D. Will MS come up with a sensible storage format for Entourage?
Any thoughts greatly appreciated.

I don't know if there is a complete solution, but here are some things you could consider.
1. TM does not run automatically at logout unless FileVault is enabled.
2. You can change the backup period using third-party utilities like TimeMachineEditor - VersionTracker or MacUpdate.
3. You can exclude the Microsoft User Data folder from the TM backup and back it up separately using third-party backup software.
4. You can use third-party backup software instead of TM, such as:
1. Retrospect Desktop (Commercial - not yet universal binary)
2. Synchronize! Pro X (Commercial)
3. Synk (Backup, Standard, or Pro)
4. Deja Vu (Shareware)
5. Carbon Copy Cloner (Donationware)
6. SuperDuper! (Commercial)
7. Intego Personal Backup (Commercial)
8. Data Backup (Commercial)
9. SilverKeeper 2.0 (Freeware)
10. Tri-Backup (Commercial)
11. Apple Backup (requires a .Mac account with Apple both to get the software and to use it.)
Apple's Backup is a full backup tool capable of backing up across multiple media such as CD/DVD. However, it cannot create bootable backups. It is primarily an "archiving" utility.
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.
Third-party backup utilities can run backups on schedules you set up. Thus, you can schedule your backups to occur at a time when you do not use the machine such as early in the AM for example.

Trouble with LaCie disk and time machine

HI everyone,
I've been having trouble with using time machine to back-up to my 1 TB LaCie drive (purchased 5/12, unfornuately I was dumb and didn't register the drive and no longer have the box with the serial number and there is no serial number on my drive. The only problem I had up until the end of August was that every so often the LaCie drive (using my FW 800 port) would unmount after waking up from sleep.
The end of August the drive unmounted for no reason while I was on the computer doing a task. Could not get the LaCie drive remounted (rebooting, etc. etc.) To make a long story short, ended up calling apple care who took me through resetting my SMC and PRAM to no avail. Was booted to higher level of support who walked me through trying to repair my drive using the disk utiltiy. When that didn't work, she walked me through erasing and reformatting the LaCie drive and starting a new time machine back-up. Every thing ok until about ten days ago.
Last week, when I woke my iMac up from sleep, I got an error saying that the disk was not ejected properly and I could not mount the drive. Restarting did nothing, the disk did not mount. Shutting down and rebooting seemed to solve the problem and the disk was mounted. Every so often I've had the problem with the disk unmounting after waking up from sleep before. So, I changed my energy sleep preferences. At the end of the day when I am done, I'd unmount the LaCie drive before putting the Mac to sleep using the apple menu.
Today I came in to start my day, plugged the drive in and it would not mount. Tried rebooting nothing. Went into the disk utility, at first the LaCie drive passed the disk verify (6:26:25 and 6:26:38). Then I went into repair disk on the indented drive at 6:27:13, I wasn't sure what it is was doing, thinking that it had hung, I stopped the repair at 6:27:24. Exited disk utility, and the LaCie drive mounted. But I was getting a read only error when I tried to back-up using time machine. So, I went back into disk utility at 6:27:35, when I verified the disk (indented disk), I got an error saying the disk need to be repaired. After several minutes the disk could not be repaired. So, I erased and reformatted the drive. Ran a time machine back-up and it seemed to back-up everything on my hard drive. Just ran another verify disk and it passed.
Is the drive failing? Have some other back-ups of my documents, my address book, iCal and am going to make a backup of some of my pref files and important e-mail files and am going to do some more back-ups after I am done.
Have reached out to the women at apple care whom I talked to last August, but don't expect to hear back from her for at least 24 hours.
Here is my disk utility log
2013-11-07 06:26:25 -0500: Verifying partition map for “LaCie”
2013-11-07 06:26:25 -0500: Starting verification tool:
2013-11-07 06:26:25 -0500: Checking prerequisites
2013-11-07 06:26:25 -0500: Checking the partition list
2013-11-07 06:26:25 -0500: Checking for an EFI system partition
2013-11-07 06:26:25 -0500: Checking the EFI system partition’s size
2013-11-07 06:26:25 -0500: Checking the EFI system partition’s file system
2013-11-07 06:26:25 -0500: Checking all HFS data partition loader spaces
2013-11-07 06:26:25 -0500: Checking Core Storage Physical Volume partitions
2013-11-07 06:26:25 -0500: The partition map appears to be OK
2013-11-07 06:26:25 -0500:
2013-11-07 06:26:25 -0500:
2013-11-07 06:26:38 -0500: Verifying partition map for “LaCie”
2013-11-07 06:26:38 -0500: Starting verification tool:
2013-11-07 06:26:38 -0500: Checking prerequisites
2013-11-07 06:26:38 -0500: Checking the partition list
2013-11-07 06:26:38 -0500: Checking for an EFI system partition
2013-11-07 06:26:38 -0500: Checking the EFI system partition’s size
2013-11-07 06:26:38 -0500: Checking the EFI system partition’s file system
2013-11-07 06:26:38 -0500: Checking all HFS data partition loader spaces
2013-11-07 06:26:38 -0500: Checking Core Storage Physical Volume partitions
2013-11-07 06:26:38 -0500: The partition map appears to be OK
2013-11-07 06:26:38 -0500:
2013-11-07 06:26:38 -0500:
2013-11-07 06:27:13 -0500: Disk Utility started.
2013-11-07 06:27:21 -0500: Verifying and repairing partition map for “LaCie”
2013-11-07 06:27:21 -0500: Starting repair tool:
2013-11-07 06:27:21 -0500: Checking prerequisites
2013-11-07 06:27:21 -0500: Checking the partition list
2013-11-07 06:27:21 -0500: Checking for an EFI system partition
2013-11-07 06:27:21 -0500: Checking the EFI system partition’s size
2013-11-07 06:27:21 -0500: Checking the EFI system partition’s file system
2013-11-07 06:27:23 -0500: Checking all HFS data partition loader spaces
2013-11-07 06:27:24 -0500: Reviewing boot support loaders
2013-11-07 06:27:24 -0500: Checking Core Storage Physical Volume partitions
2013-11-07 06:27:24 -0500: Updating Windows boot.ini files as required
2013-11-07 06:27:24 -0500: The partition map appears to be OK
2013-11-07 06:27:24 -0500:
2013-11-07 06:27:24 -0500:
2013-11-07 06:27:35 -0500: Verifying volume “LaCie”
2013-11-07 06:27:35 -0500: Starting verification tool:
2013-11-07 06:27:35 -0500: Checking file system2013-11-07 06:27:35 -0500: Error: This disk needs to be repaired. Click Repair Disk.2013-11-07 06:27:35 -0500:
2013-11-07 06:27:35 -0500: Disk Utility stopped verifying “LaCie”: This disk needs to be repaired. Click Repair Disk.
2013-11-07 06:28:05 -0500:
2013-11-07 06:28:13 -0500: Verify and Repair volume “LaCie”
2013-11-07 06:28:13 -0500: Starting repair tool:
2013-11-07 06:28:13 -0500: Checking file system2013-11-07 06:28:13 -0500: Volume repair complete.2013-11-07 06:28:13 -0500: Updating boot support partitions for the volume as required.2013-11-07 06:35:05 -0500: Stopped by user
2013-11-07 06:44:56 -0500: Disk Utility started.
2013-11-07 06:45:20 -0500: Verifying volume “LaCie”
2013-11-07 06:45:20 -0500: Starting verification tool:
2013-11-07 06:45:20 -0500: Checking file system2013-11-07 06:45:20 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:45:20 -0500: Checking extents overflow file.
2013-11-07 06:45:20 -0500: Checking catalog file.
2013-11-07 06:45:59 -0500: Missing thread record (id = 5057741)
2013-11-07 06:46:06 -0500: Checking multi-linked files.
2013-11-07 06:46:19 -0500: Checking catalog hierarchy.
2013-11-07 06:46:38 -0500: Invalid directory item count
2013-11-07 06:46:38 -0500: (It should be 0 instead of 4)
2013-11-07 06:46:38 -0500: Invalid volume directory count
2013-11-07 06:46:38 -0500: (It should be 166840 instead of 166841)
2013-11-07 06:46:38 -0500: Checking extended attributes file.
2013-11-07 06:47:05 -0500: Checking multi-linked directories.
2013-11-07 06:48:10 -0500: Checking volume bitmap.
2013-11-07 06:48:12 -0500: Checking volume information.
2013-11-07 06:48:12 -0500: The volume LaCie was found corrupt and needs to be repaired.
2013-11-07 06:48:12 -0500: Error: This disk needs to be repaired. Click Repair Disk.2013-11-07 06:48:12 -0500:
2013-11-07 06:48:12 -0500: Disk Utility stopped verifying “LaCie”: This disk needs to be repaired. Click Repair Disk.
2013-11-07 06:48:12 -0500:
2013-11-07 06:50:02 -0500: Verify and Repair volume “LaCie”
2013-11-07 06:50:02 -0500: Starting repair tool:
2013-11-07 06:50:02 -0500: Checking file system2013-11-07 06:50:02 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:50:02 -0500: Checking extents overflow file.
2013-11-07 06:50:02 -0500: Checking catalog file.
2013-11-07 06:50:41 -0500: Missing thread record (id = 5057741)
2013-11-07 06:50:48 -0500: Checking multi-linked files.
2013-11-07 06:51:02 -0500: Checking catalog hierarchy.
2013-11-07 06:51:20 -0500: Invalid directory item count
2013-11-07 06:51:20 -0500: (It should be 0 instead of 4)
2013-11-07 06:51:20 -0500: Invalid volume directory count
2013-11-07 06:51:20 -0500: (It should be 166840 instead of 166841)
2013-11-07 06:51:20 -0500: Checking extended attributes file.
2013-11-07 06:51:47 -0500: Checking multi-linked directories.
2013-11-07 06:52:55 -0500: Checking volume bitmap.
2013-11-07 06:52:56 -0500: Checking volume information.
2013-11-07 06:52:56 -0500: Repairing volume.
2013-11-07 06:52:56 -0500: Missing directory record (id = 5057741)
2013-11-07 06:52:56 -0500: Look for missing items in lost+found directory.
2013-11-07 06:53:10 -0500: Rechecking volume.
2013-11-07 06:53:10 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:53:10 -0500: Checking extents overflow file.
2013-11-07 06:53:10 -0500: Checking catalog file.
2013-11-07 06:53:16 -0500: Incorrect number of thread records
2013-11-07 06:53:22 -0500: Checking multi-linked files.
2013-11-07 06:53:35 -0500: Checking catalog hierarchy.
2013-11-07 06:53:53 -0500: Invalid directory item count
2013-11-07 06:53:54 -0500: (It should be 5 instead of 6)
2013-11-07 06:53:54 -0500: Invalid volume directory count
2013-11-07 06:53:54 -0500: (It should be 166844 instead of 166842)
2013-11-07 06:53:54 -0500: Invalid volume file count
2013-11-07 06:53:54 -0500: (It should be 1056326 instead of 1056321)
2013-11-07 06:53:54 -0500: Checking extended attributes file.
2013-11-07 06:54:20 -0500: Checking multi-linked directories.
2013-11-07 06:55:25 -0500: Checking volume bitmap.
2013-11-07 06:55:26 -0500: Checking volume information.
2013-11-07 06:55:26 -0500: Repairing volume.
2013-11-07 06:58:06 -0500: Rechecking volume.
2013-11-07 06:58:06 -0500: Checking Journaled HFS Plus volume.
2013-11-07 06:58:06 -0500: Checking extents overflow file.
2013-11-07 06:58:07 -0500: Checking catalog file.
2013-11-07 06:58:12 -0500: Incorrect number of thread records
2013-11-07 06:58:18 -0500: Checking multi-linked files.
2013-11-07 06:58:31 -0500: Checking catalog hierarchy.
2013-11-07 06:58:50 -0500: Invalid volume directory count
2013-11-07 06:58:50 -0500: (It should be 166844 instead of 166842)
2013-11-07 06:58:50 -0500: Invalid volume file count
2013-11-07 06:58:50 -0500: (It should be 1056326 instead of 1056321)
2013-11-07 06:58:50 -0500: Checking extended attributes file.
2013-11-07 06:59:17 -0500: Checking multi-linked directories.
2013-11-07 07:00:22 -0500: Checking volume bitmap.
2013-11-07 07:00:24 -0500: Checking volume information.
2013-11-07 07:00:24 -0500: Repairing volume.
2013-11-07 07:03:03 -0500: Rechecking volume.
2013-11-07 07:03:03 -0500: Checking Journaled HFS Plus volume.
2013-11-07 07:03:03 -0500: Checking extents overflow file.
2013-11-07 07:03:04 -0500: Checking catalog file.
2013-11-07 07:03:09 -0500: Incorrect number of thread records
2013-11-07 07:03:15 -0500: Checking multi-linked files.
2013-11-07 07:03:29 -0500: Checking catalog hierarchy.
2013-11-07 07:03:47 -0500: Invalid volume directory count
2013-11-07 07:03:47 -0500: (It should be 166844 instead of 166842)
2013-11-07 07:03:47 -0500: Invalid volume file count
2013-11-07 07:03:47 -0500: (It should be 1056326 instead of 1056321)
2013-11-07 07:03:47 -0500: Checking extended attributes file.
2013-11-07 07:04:14 -0500: Checking multi-linked directories.
2013-11-07 07:05:19 -0500: Checking volume bitmap.
2013-11-07 07:05:20 -0500: Checking volume information.
2013-11-07 07:05:20 -0500: The volume LaCie could not be repaired after 3 attempts.
2013-11-07 07:05:21 -0500: Volume repair complete.2013-11-07 07:05:21 -0500: Updating boot support partitions for the volume as required.2013-11-07 07:05:21 -0500: Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.2013-11-07 07:05:21 -0500:
2013-11-07 07:05:21 -0500: Disk Utility stopped repairing “LaCie”: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
2013-11-07 07:05:21 -0500:
2013-11-07 07:09:45 -0500: Disk Utility started.
2013-11-07 07:11:45 -0500: Preparing to erase : “LaCie”
2013-11-07 07:11:45 -0500:     Partition Scheme: GUID Partition Table
2013-11-07 07:11:45 -0500:     1 volume will be erased
2013-11-07 07:11:45 -0500:         Name        : “LaCie”
2013-11-07 07:11:45 -0500:         Size        : 999.86 GB
2013-11-07 07:11:45 -0500:         File system    : Mac OS Extended (Journaled)
2013-11-07 07:11:45 -0500: Unmounting disk
2013-11-07 07:11:45 -0500: Erasing
2013-11-07 07:11:54 -0500: Initialized /dev/rdisk1s2 as a 931 GB HFS Plus volume with a 81920k journal
2013-11-07 07:11:54 -0500: Mounting disk
2013-11-07 07:11:54 -0500: Erase complete.
2013-11-07 07:11:54 -0500:
2013-11-07 10:38:00 -0500: Disk Utility started.
2013-11-07 10:38:12 -0500: Verifying volume “LaCie”
2013-11-07 10:38:12 -0500: Starting verification tool:
2013-11-07 10:38:14 -0500: Checking file system2013-11-07 10:38:14 -0500: Checking Journaled HFS Plus volume.
2013-11-07 10:38:14 -0500: Checking extents overflow file.
2013-11-07 10:38:14 -0500: Checking catalog file.
2013-11-07 10:38:29 -0500: Checking multi-linked files.
2013-11-07 10:38:29 -0500: Checking catalog hierarchy.
2013-11-07 10:38:41 -0500: Checking extended attributes file.
2013-11-07 10:39:04 -0500: Checking multi-linked directories.
2013-11-07 10:39:31 -0500: Checking volume bitmap.
2013-11-07 10:39:32 -0500: Checking volume information.
2013-11-07 10:39:32 -0500: The volume LaCie appears to be OK.
2013-11-07 10:39:32 -0500: Repair tool completed:
2013-11-07 10:39:32 -0500:
2013-11-07 10:39:32 -0500:

I just got a call back from the upper level support person at apple care who had been advising me on my trouble with time machine and my LaCie 1 TB FWD. I had sent her much of the same verbiage as I posted here. As some of you have probably figured out, the verdict is that the drive is probably failing. She says this because I have had to do two erase and reformats. She thought that the intermitant problem that I have had with the drive unmounting when my iMac wakes from sleep could be related to the drive failing.
In the meantime I have a secondary back-up (not using time machine) and the LaCie 1 TB FWD is working for the moment.
Thanks to all who read all my verbiage.
And in the meantime, I've learned something. I marked this question as solved. But I'm open to other things to try.
Message was edited by: njtreehugger minor edits and update

My external drive won't mount. Disk Utility says it can't repair disk and to backup the disk and reformat, but how can I do that if it won't mount?

My external drive won't mount. Disk Utility says it can't repair disk and to backup the disk and reformat, but how can I do that if it won't mount?

See mount section in 1st linked article.
Disk Unmount Using Terminal
Disk Utility – Force Mount Disk

Suspend to RAM fails to Remount Hard Disk on Resume

I can resume just fine with pm-suspend and s2ram -f, but on resume my hard disk fails to remount. If I try to run any command bash can't find it. I can still use any programs I had open before suspending normally, provided they don't have to access the disk. There are no errors or logs to check, because they can't be written to with the hard disk unmounted.
This machine can be identified by:
sys_vendor = "Hewlett-Packard"
sys_product = "HP Pavilion dv7 Notebook PC"
sys_version = "F.13"
bios_version = "F.13"

Hello Plutonian!
Did it become for readonly system ?
Must be a relevant line in the related log file, or in last case in syslog i think.

Disk unmounted

Similar Messages

Maybe you are looking for