Notice - Aperture and Lacie. Disk Corruption.

Noticed an issue with Aperture Libraries on Lacie Biggest Quadra RAID drive.
Apertures get stuck in an endless loop when trying to quit. The progress dialoguebox displayed in Aperture "Updating Sharing Previews"
In Console, we have looping instances of this:
0-07-23 8:15:50 AM com.lacie.desktopmanager.service[7508] SCSIStackDevice: Remote Comms command failed [c0:s0]
10-07-23 8:15:50 AM com.lacie.desktopmanager.service[7508] Device (LaCie Biggest Quadra Media) not comms-capable

Hello Marco,
You might like to read this online artice about Referenced Masters which may help explain your problem:
http://homepage.mac.com/bagelturf/aparticles/ref/ref.html
USB2 will slow your experience of Aperture. I have a 160GB USB2 drive that takes 160 seconds to mount on my desktop. In comparison, my 1TB Firewire 800 drive takes just 9 seconds.

Similar Messages

Bit locker drive encryption failed due to power failer and hard disk corrupted

I ran Bitlocker drive ecryption drive D. My pc is windows 7 ultimate, while it was in progress of 1% due to power failer the encryption failed, when power resume the drive didn't showed the file format nor the size but it shows the size in disk management.
It showed like this in My computer
I do Have the recovery code password and back of recovery password so I ran the "manage-bde-_unlock D:-rp[my code ]
and my pc got hang no other option rather than to press the restart button.
then I used commang "repair-bde -force D:I:-rp[my rp] and following info showed but it stucked in 1% about 8 hours, and there was no increase in the pecentage
I also connected the hardisk to mac but all othe partation showed but didn't showed the encrypted one.
I had lots of memorable picture and other backups so any one kindly help me to get out of this problem. Thanks for help

Hi,
The BitLocker encryption and decryption processes can be interrupted by turning the computer off, and it will resume where it left off the next time Windows starts. This is true even if the power is suddenly unavailable.
Bitlocker-repair (repair-bde) tool
can't repair a drive that failed during the encryption or decryption process.
In addition, could you please explain a bit for what drive you are trying to deal with? external one?
When you first restart your PC, have you seen any signs that indicate that the encryption is in process?
Regarding your scenario, please take a look to see if the following articles could help here:
Scenario 11: Recovering Data Protected by BitLocker Drive Encryption (Windows 7)
Besides, when running manage-bde command, did we followed the steps mentioned in the below article?
Scenario 14: Using a Data Recovery Agent to Recover BitLocker-Protected Drives (Windows 7)
Best regards
Michael Shao
TechNet Community Support

My emac won't boot past grey loading screen with apple and spinning disk

I tried starting it up and it does the usual except when it gets to the grey screen with the loading disc and apple, it does nothing else. I dont have access to an install disc and even if I did, the tray doesn't even open. Please help!!!

Do you have the Install Discs for this Mac?
Might be time for a relatively painless Archive & Install, which gives you a new/old OS, but can preserve all your files, pics, music, settings, etc., as long as you have plenty of free disk space and no Disk corruption, and is relatively quick & painless...
http://docs.info.apple.com/article.html?artnum=107120
Just be sure to select Preserve Users & Settings.
But with that loginwindow crash, we may need to trick it...
Reset OS X Password Without an OS X CD...
http://theappleblog.com/2008/06/22/reset-os-x-password-without-an-os-x-cd/
Admin Hack...
http://www.hackmac.org/?q=node/4
Starts up like the first time you buy a new Mac, but after filling in all that info again, you should have access to the computer and the other Users & files will still be there... give the new User a different name than an existing one.

Time Machine, Disk Utility, and clearing out corrupted snapshots

Hi, all. I've been having some troubling issues with Time Machine and could use your collective insight.
I have a 500GiB external USB2 disk that I've been using for Time Machine since December (the oldest snapshot in Backups.backupdb is named 2007-12-13-222250). Everything worked fine until sometime in late January, when Time Machine decided to ax 2/3 of my Applications directory. Time Machine's logging is terse, so I wasn't able to determine what caused the corruption. The fact that this error wasn't caught and flagged by Time Machine bothers me.
Especially because I discovered this in the process of needing to recover from a crash on my laptop's hard drive -- I had to roll back to a previous, complete snapshot to get all my applications back.
After that I had to engage in some jiggery-pokery to get Time Machine to re-snapshot everything, but things proceeded normally until I received my new copy of DiskWarrior 4.1 last night (although DiskWarrior is an innocent bystander here). I tried to use DiskWarrior to rebuild the directory on the Time Machine disk, but it failed before trying to write anything.
(For those who care: after some back and forth with Alsoft tech support, we determined this was likely because my Time Machine volume has 6.2GB of catalog data, and DiskWarrior works by rebuilding the directory in memory, so it has to be able to fit the whole catalog into virtual memory.)
I was a little paranoid that something might be wrong with the disk after that, so I fired up Disk Utility and told it to repair the disk. It churned for about 6 hours and repaired an extraordinarily large number of hardlink reference count errors, but completed by claiming that the disk had been repaired.
When I next told Time Machine to run, instead of copying over a couple GB of data like it usually does, it started copying 38GB! ***? I took a look at the previous Time Machine snapshots, and discovered that Disk Utility had totally corrupted every snapshot I'd made since last month's fandango. Most of the root-level directories in the snapshots now look like this:
$ ls -al /Volumes/Time\ Machine\ Backups/Backups.backupdb/xxx.net/2008-03-13-025640/Euphrosyne/
total 128
drwxrwxr-t@ 16 root admin 1020 Feb 15 00:17 ./
drwxr-xr-x@ 3 root ogd 204 Mar 13 02:56 ../
-r--r--r--@ 9151 root 20051003 0 Feb 11 23:13 .DRM_Data
-r--r--r--@ 50574 root 20051004 0 Feb 11 23:13 .DS_Store
-r--r--r--@ 9154 root 20051006 0 Feb 11 23:13 .SymAVQSFile
-r--r--r--@ 9155 root 20051007 0 Feb 11 23:13 .VolumeIcon.icns.candybarbackup
drwxr-xr-x@ 2 ogd admin 68 Feb 29 2004 .buildinstaller1.tmp/
-r--r--r--@ 9149 root 20051001 0 Feb 11 23:13 .com.apple.timemachine.supported
-r--r--r--@ 9150 root 20051002 0 Feb 11 23:13 .com.apple.timemachine.supported (from old Mac)
-r--r--r--@ 9153 root 20051005 0 Feb 11 23:13 .redethist
-r--r--r--@ 58730 root 20051009 0 Feb 11 23:13 Applications
-r--r--r--@ 37526 root 20051012 0 Feb 11 23:13 Desktop Folder
-r--r--r--@ 13328 root 20051013 0 Feb 11 23:13 Developer
-r--r--r--@ 64211 root wheel 0 Feb 11 23:13 Library
-r--r--r--@ 49886 root 20051080 0 Feb 11 23:13 Network
-r--r--r--@ 5643 root 20051120 0 Feb 11 23:13 System
lrwxr-xr-x 1 root ogd 60 Mar 13 02:56 User Guides And Information@ -> /Library/Documentation/User Guides and Information.localized
drwxr-xr-x@ 5 root admin 204 Dec 6 02:07 Users/
-r--r--r--@ 2554 root wheel 0 Feb 11 23:13 Volumes
-r--r--r--@ 37448 root 20051010 0 Feb 11 23:13 bin
-r--r--r--@ 37525 root 20051011 0 Feb 11 23:13 cores
lrwxr-xr-x@ 1 root ogd 11 Mar 13 02:56 etc@ -> private/etc
-r--r--r--@ 26309 root 20051078 0 Feb 11 23:13 mach_kernel
-r--r--r--@ 26310 root 20051079 0 Feb 11 23:13 mach_kernel.ctfsys
lrwxr-xr-x 1 root ogd 12 Mar 13 02:56 opt@ -> /private/opt
drwxr-xr-x@ 8 root wheel 272 Dec 6 02:31 private/
-r--r--r--@ 52664 root 20051119 0 Feb 11 23:13 sbin
lrwxr-xr-x@ 1 root ogd 11 Mar 13 02:56 tmp@ -> private/tmp
-r--r--r--@ 41668 root 20052660 0 Feb 11 23:13 usr
lrwxr-xr-x@ 1 root ogd 11 Mar 13 02:56 var@ -> private/var
That is clearly, completely wrong, and it alarms me that Disk Utility could cause so much damage to a Time Machine volume.
Since I also use SuperDuper! to regularly clone this disk, it's not as big a nightmare as it could be, but this means that I'm going to have to clear out every snapshot for the last month by hand, both because I obviously can't trust them anymore, and because I keep getting messages like this in the logs:
2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.com.apple.timemachine.supported to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.com.apple.timemachine.supported (from old Mac) to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.DRM_Data to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.DS_Store to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.redethist to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.SymAVQSFile to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.VolumeIcon.icns.candybarbackup to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
I'd like to keep the old snapshots if I can. What's likely to happen if I just go and clear out the b0rked backup sessions by hand?
(Hmm... it appears yes, because I just deleted them all and the disk didn't recover the freed space.)
Here's the important question: has anyone else had issues using Disk Utility on a Time Machine volume, and does anyone at Apple have any plans to add integrity checking to Time Machine? As it stands, I don't really feel like I can trust it in its present form, as convenient as it is...

I have trouble with disk utility on my new (1 TB Lacie) as well as on my old (500 GB WD) drive. After doing a backup, du tells me a never ending list of errors like
HasFolderCount flag needs to be set (id = 599567)
(it should be 0x10 instead of 0)
Everything was O.K. before doing the backup; so is the disk to be backupped, according to du.
Up to now, no other problem occurred, but I´d like to clear this issue before my trust in time machine is restored.

Aperture Kernel Panics & Fusion Disk Corruptions

We have a new iMac with the Fusion drive bought not to long ago. It has 16gb memory. Since it's back to school, we are busier than this past summer
We are editing about 200 - 400 images a day. While in Aperture we have had kernel panics and a major spinning ball freezes with a total reboot freeze that ended up with corruption on the Fusion drive.
We have ask some tech people, and all have said, when working with large raw images, which we do, the drive cannot keep up with editing, esp when using the brush tool. Also missing files sometimes, like magic their gone.
Anyone else have this.
PS we have swaped out the memory 3 times and still had issues. I don't think the drive can handle the work.

While I am runing a DIY Fusion Drive on a Mac Pro, I am a heavy user of Aperture and have noticed no problems what so ever with my current setup.
It might be helpful if you canpost a crash dump from one of your kernel panics.
Allan

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

Warning - itunes 7 and lacie Big Disk

At poresent I am attempting to re build my Lacie 500Gb hard drive because itunes 7 has crashed it, please be careful if you have wav files on a lacie big disk
Disk utility does not work to repair the drive, tech tools has recommended using file recovery, what a wonderful way to spend a Friday evening, not listening to music but finding it
Oh and if anyone from the itunes team is reading this and I certainly hope there is, please be aware that if I lose my 500+ strong CD collection from my Big Disk, I will be asking them to send the person responsible for saying this product was safe for public consumption to come to Australia and sit in front of my mini and re rip every single CD one after another. Then they can rebuild the playiists that I so anally created, then they should be made to go and apologise to every single person in the world that their shoddy decision has effected
What a fantastic start to the weekend, thanks itunes, next time wait until it's ready
DjDs
Mac Mini 1.25Ghz PowerPC G4 Mac OS X (10.4.7) 1GB DDR SD DRAM, Migli Mini TV, Lacie Big Disk

I have recently "upgraded" to iTunes 7 myself. I use my old PB 17" as a music server (since work bought me a new 15" MacBook Pro), and . . . uh oh . . . I have my iTunes library on a LaCie Bigger Disk Extreme.
Perusing through the forums, it would seem that a lot of folks have trouble with the new iTunes and external drives, not just LaCie.
iTunes 7 corrupted the directory of the LaCie disk to the point at which I couldn't even mount the disk, and Disk Utility couldn't help me. It was really strange. The first time I ran iTunes 7, it did that whole gapless-playback scan (whatever the heck that is) and then could find none of the songs (it asked me on each song if I'd like to locate the original?). Then, I quit iTunes and couldn't open the LaCie drive icon on the desktop. So, I rebooted, and the LaCie drive wouldn't even mount.
The latest version of DiskWarrior (3.0.3), however, recognized the drive and rebuilt the directory and, I am happy to report, with the rebuilt directory ALL my music works and iTunes 7 seems to work like a charm.
It's a little frustrating that Apple released such a problematic product, BUT, I guess they can't try every possible hardware combination. iTunes and an external hard drive, though, would seem to be pretty common.
Talltexan, have you got the latest DiskWarrior?
Stuart

Problem fixing Lacie disk as storage directory for Itunes and other program

Hello,
I have a Lacie disk 250 GB, it works well but i don´t know why it creates different volumes, like "Lacie Disk 1", "Lacie Disk 2", etc. Like that untill 5! The problem is that once the system creates a new volume version, i can´t find the files in the older volume version. I have a lot of information in my "Lacie Disk 4" but can´t reach it. How can I do to enter to the Volumes folder from the finder? Thank u very much for assistance

Hi eww,
Sorry, i didn´t explained it very well, but the problem is that I don´t understand this problem too. So, to answer you. 1) I did not partitioned my disk ; 2) When I connect it, i have just "Lacie Disk" on my finder ; 3) When I mention "volumes" the thing is that when I want to choose a directory for my downloads or Itunes, it appears on Powerbook G4/Volumes/LacieDisk. But then, I try to find it on the Finder but I can´t see that folder "volumes".
I opened Disk utility, and just to show how it appears
"Mount Point : /Volumes/LaCie Disk 5". My problem is that i don´t know why, it changed from LaCieDisk 4 to 5, and that i have information on that one which I can´t see but know it is there.
Hope to be clearer now, but i´m not sure :)) If you want i can send u by email a photo of my problem

Recover OCR and VOTE disk after complete corruption of ASM disk groups.

Hi Gurus,
I am simulating a recovery situation to perform recover of OCR and Vote files after complete corruption of ASM related disks and diskgroups. I have setup my environment as follows:\
Environment: RAC
OS: OEL 5.5 32-bit
GI Version: 11.2.0.2.0
ASM Disk groups: +OCR, +DATA
OCR, Vote Files location: +OCR
ASM Redundancy: External
ASM Disks: /dev/asm-disk1, /dev/asm-disk2
/dev/asm-disk1 - mapped on +OCR
/dev/asm-disk2 - mapped on +DATA
With the above configuration in place I have manually corrupted +OCR, +DATA diskgroups with dd command. I used this command to completely corrupt +OCR disk group.
dd if=/dev/zero of=/dev/asm-disk1. I have manual backups as well as automatic backups of OCR and Vote disk. I am not using ASMLib.
I followed this link:
http://docs.oracle.com/cd/E11882_01/rac.112/e17264/adminoc.htm#TDPRC237
When I tried to recover OCR file, I could not do so as there is no such diskgroup which ASM can restore the OCR, Voting disk to. I could not Re-create OCR and DATA diskgroups as I cannot connect to ASM instance. If you have a solution or workaround for my situation please describe it. That will be greatly appreciated.
Thanks and Regards,
Suresh.

Please go through the following document which have the detailed steps to restore the OCR
How to restore ASM based OCR after complete loss of the CRS diskgroup on Linux/Unix systems [ID 1062983.1]

Corrupt files in Aperture and RAM upgrade

I have been having trouble with some corrupted Files in Aperture and after reading some discussion groups I was led to beIieve it might be a hardware problem and not just a software bug-some people experiencing similar problems traced it back to bad RAM. I performed a Hardware test w/ the Mac OS start-up disc. The results indicated this error code:
**Error*code***Error*code**2MEM/104/4:DIMM2/J13
Can anyone help me here? Does this indicate there's a problem w/ the RAM in my DIMM2?
I'm running a Dual 2 GHz PowerPC G5, OS 10.4.9. Quite a while ago I added 2 1GB RAM modules tro complement the original 512.
Thanks-
Bob
G5 Mac OS X (10.4.9)

Yeah, sounds like it's a bad chip. Remove the chip from the DIMM2/J13 slot (you'll have to remove it's pair too) and run the test again to make sure the others work. Too bad with the original 512 it probably won't let you open aperture (though you can hack it to work.)
Depending on the ram it could be under warrenty. I had a crucial chip that tested bad and the replaced it no questions asked.

I just purchased Aperture and have 20,000 photos in my iPhoto Library. Can I import only certain events from iPhoto into Aperture or do I have to merge the whole iPhoto library?

I just purchased Aperture and have 20,000 + photos in my iPhoto Library. I see that I can create a unified library between the two. I am wondering if I can import only certain events from iPhoto (like only 2014 events) into Aperture or do I have to merge the whole iPhoto library? Are there any benefits to bringing the whole iPhoto library over to Aperture (iPhoto is SO SLOW for me, I wonder if it is because I have so many photos). Or, any detriment to only bring a few events over?
And, if I don't merge the two libraries, I assume that means I cannot do it at a later date?
Help. My local Apple store has had very few Aperture workshops, and the next one is like 2 months away.

Thank you so much for this information. Here are some responses/comments:
Disk space - it says 114.43 GB out of 499.25 GB free. I have no idea if that is enough.
iPhoto version is 9.5.1
Again, I am not sure how to know if I have 3rd party software...but I don't think I do. Is 3rd party software anything non-apple?
I will try rebuilding the library. if that doesn't help, maybe I need more memory...? That is what Apple suggested, but that, of course, means buying something else. I've already bought APERTURE, on their recommendation...
It wasn't, and they told me it was slow because I had too many photos for iPhoto to handle and that I should buy Aperture. Which I did.
What is your iPhoto version? Are you using the most recent version 9.5.1?
iPhoto can handle 20000 photos, no problem. Your computer can be slow for several reasons:
The most common problem for slowness - insufficient disk space. Don't let your free disk space drop below 20 GB of free space, better more. If the operating system does not have enough working space and the applications you are using, you will notice a very lagging behaviour.
Older or incompatible softweare can cripple your mac. Do you have any older third-party software installed, that might have installed incompatible kernel extensions?
Aperture might be slow or keep crashing, if you imported a corrupted image or incompatible video, that cannot be processed. Then Aperture will try over and over again to create previews and never succeed. You could test for this situation, by launching Aperture with the Shift-key held down. This will defer the generation of previews. If Aperture will launch and work better this way, you probably have some bad media in your photo library.
Another problem to check for is a corruption of your Aperture/iPhoto library. You have run the First Aid Tools to repair the iPhoto Library, but have you ever tried to rebuild the library? See this post by Old Toad: Rebuild iPhoto Version 11

Aperture and Snow Leopard problems

I have multiple issues with Aperture after upgrading to SL (currently on 10.6.2). The major issues are:
(1) Whenever I import new images or make modification to existing images Aperture does not quit anymore. Command quit doesn't do anything and I have to force quit in order to exit program.
(2) After importing new files, often not all images are shown in the project or album (although all images have been imported and the tooltip shows the correct number of images in the project/album). Furthermore, keywords searches do not work. A force quit and reopening solves this problem.
(2) When saving or opening images the dialog box does not work properly and some folders are overlayed with black/grey boxes and things look corrupted.
Obviously, I have installed 2.1.4 and I do not have Aperture in any subfolder (it is directly in the app folder). Furthermore, I have deleted the preferences file (com.apple.Aperture.plist) but this did not help.
What to do next? Re-install Aperture? If I have to do this what docs do I have to delete and how can I avoid loosing any important information? I have a very large image library with many adjustments, keywords, rankings etc and I definitely do not want to loose any of that information. Thanks much for your help and advise.

I decided to backup up everything. I then erased the HD and reinstalled Leopard Disk 1 and 2. Did all the system updates and added all the optional software on the disks. Then installed Snow Leopard. Then installed Aperture and all updates including 2.1.4 and my printer drivers. Then followed with all my other apps like MS Office and Quicken.
Took about 2 hours.
Everything works perfectly and is quite snappy including Aperture. No problems with any of the Aperture functions.
It's a lot of work but its easy to do if you have other things to do while the software is installing.
If you are up to all that and dont mind the time, you'll be happy plus you now have a clean, fresh disk.

Aperture and computer unresponsive with photostream

Hello every one, this will be my last ditch attempt with aperture before binning it.
Its been very unstable for me for sometime now many months on both an imac and macbook, updates from apple seem to be making matters worse.
To cap it all photostream seems to kill it entirely. Most of the time it seems to either be processing images or doing something with photostream. Whilst this is happening aperture is either dog slow or totally unresponsive and infact half the time my entire mac seems like its about to melt down.
Aperture as a programme seems to be falling over pretty rapidly for me, I don't know if anyone else feels that way. In an attempt to mitigate the issues I expereince all the time I have given up using raw, because these knock it over, on an imac quad core i7 with 8 gig of ram. Lion certainly has not helped and with photostream compounding it, I am finding productivity with aperture sliding.
IS anyone else having issues with this 'professional' software now?
Yes I have rebuilt the database and library many many times, fixed permissions, done all those things that make no difference what so ever. I repprossed all masters and thumbs before going to be one night and this helped for a while.
Aperture on my macbook is game over really, its just too slow and unresponsive to be considered viable.

Would referenceing be a mistake or might this eleviate some of the issues.
That depends; referencing will help, if you do not have enough free space on your system drive and you can free your disk this way. But you should connect your external drive to a fast port - fire wire, thunderbolt ...
If you on the other hand allready have all the disk space you need, this might may things worse, if your external disk is slow.
You really need to find out, what Aperture is doing; that is why I suggested to show the Activity window and watch the Console Window (Utilities -> Console). The performance you see is very untypical for a moderate sized Library.
I suspect your Aperture LIbrary may be corrupted in some way or your Preferences are faulty.
How to solve such problems is described in this support article.
Aperture 3: Troubleshooting Basics
Try to repair the permissions in your Library, and if that dos not help, repair the library as described in the article.
Post back, if that does not solve the problem.
Regards
Léonie
P.S. I would not change the type of the library to referenced, while there may be a problem with the library that need repairing.

Time Capsule with 250Gb LaCie disk

I've just purchased a 1Tb Time Capsule. I want to connect my existing 250Gb LaCie disk to the USB port in the time capsule. However, when I do this it doesn't appear in "Disks" under Airport utility or as as a disk in Finder - the only disk I see is the one in the time capsule itself. The disk works fine when connected directly to my MacBook Pro via the firewire port.
Looking at the LaCie disk in Disk Utility it is formatted Mac OS Extended (Journaled) and the Partition Map Scheme is Apple Partition Map.
Any ideas what the problem could be?
Thanks
Mike

Just noticed that the disk does not mount if connected directly to my MacBook Pro via a USB 2.0 port so the problems seems to be a more general one to do with the USB connection. I have no idea why this disk won't connect via USB 2.0 but is fine using Firewire 800!
Mike

How to get Aperture and iPhoto to use Pentax *ist DL RAW images natively

Using some techniques that I found in various places in these forums, I am going to give step-by-step instructions to get Aperture and iPhoto to recognize Pentax *ist DL RAW images natively.
Note: This worked for me using 10.4.6 with the latest iPhoto 06 and Aperture updates. I do NOT know if this will work on older versions of OS X, iPhoto, or Aperture.
Note: If you also use a Pentax *ist DS camera, these instructions will probably disable support for that particular device due to the modifications made to a system file. Only complete these instructions if you want to use a *ist DL camera.
** These instructions involve modifying system level files using a HEX editor. If you are not comfortable with this, do NOT attempt to do this or you could kill your system. Remember, BACKUP BACKUP BACKUP. These steps worked great for me but follow at your own risk!! **
Ok, lets begin...
1) Download this great patch by macintosh_tech
http://idisk.mac.com/macintosh_tech-Public
This patch contains an updated raw.plist file which includes the RAW information for the *ist DL. This patch also contains an updated libRaw.dylib file and an updated Raw Presets file for Aperture.
** Do NOT copy the libRaw.dylib file from this patch to the folder listed in the patch Read_Me. This file did not work on my Intel-based Mac and crashed my system!!
I was able to modify my original libRaw.dylib file using a HEX editor to get it to work on my system. Instructions for this modification will follow.
2) Open the .dmg of the patch in a Finder window
3) Open a new finder window and browse to /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ImageIO.fra mework/Resources
*4) Backup the libRaw.dylib and Raw.plist files. Copy them to a safe location. For extra safety, you can just copy the whole Resources folder to a safe location (Make sure that you COPY it and dont MOVE it)*
5) Right-click the libRaw.dylib file and select "Get Info". Look at the bottom of the info window and expand the "Ownership & Permissions" tab. In this section, expand the "Details" tab. If the lock icon is in the locked position, click it to unlock it. Change "Owner" to your user name. If requested, enter your system password at this point. Close the info window. This step lets you modify the libRaw.dylib file.
6) Complete step 5 for the Raw.plist file.
7) Copy the Raw.plist file from the "Place In System Folder" folder from the patch to the Resources folder. It will ask you if you wnt to overwrite the existing file. Click "Replace".
8) Open a new finder window and browse to the /Users/YOURUSERNAME/Library/Application Support/Aperture/ folder.
* 9) Backup the "Raw Decode Presets.plist" file *
10) Copy the "Raw Decode Presets.plist" file from the "Place In Home Directory" folder from the patch to the /Users/YOURUSERNAME/Library/Application Support/Aperture/ folder. Click "replace" if it asks you.
11) Here's the tricky part. Download a HEX editor if you don't have one. I used 0xED. It is free and can be downloaded from
http://www.versiontracker.com/dyn/moreinfo/macosx/29521
12) Open the libRaw.dylib file from the Resources folder in your HEX editor.
Note: This is your original libRaw.dylib file from your /System/Library/...../Resources/ folder, NOT the file from the patch.
Use the Find function and search for the string "Pentax *ist DS". Make sure you are using "Search Type: Text" (or equivilent in your editor) and that you use proper case. When you find this string, change the "S" in the "DS" to an "L". The string should now look like "Pentax *ist DL". Use the "Find Next" function to find the next instance of "Pentax *ist DS". Again, change the "S" to an "L". There should be two total instances that you need to change. Save the file and exit the editor.
13) Open Disk Utility and repair permissions. This will set the raw.plist and libRaw.dylib files back to their original permissions.
14) Reboot the system.
15) You should now be able to view .PEF files natively in Aperture and iPhoto. I appologize in advance for any typos. Let me know how this works, as this is my first tutorial of this nature.
Macbook 2.0 Mac OS X (10.4.6)

It would appear that my last post was a moot point as the 10.4.7 update adds support for the *ist DL. It's nice to have it biult into the operating system now.

*Notice* - Aperture and Lacie. Disk Corruption.

Similar Messages

Maybe you are looking for

Notice - Aperture and Lacie. Disk Corruption.