Lacie 1TB External HDD just went ghost

I was using my computer this afternoon and ejected my harddrives to take the MBP to another room. When I mounted everything back, my Lacie 1TB USB 3.0 HDD just didn't mount. I have 2x of the same HDD and a WD 2TB. All of them are Mac Journaled, one Lacie is configured as Time Capsule and the other is just backup for music, FCP files, etc.
I've switched USB ports, USB Cables, everything. It doesnt show up on Disk Utility either.
It always asked to Force Eject as Spotlight was forever indexing this HD.
Any thoughts?

purduegrad_macguy wrote:
I've been using my Lacie 1TB external HDD for my Time Machine backups for quite sometime. Its never given me any problems until now.
Mine Failed after 3 years and 4 months of using it as a Dedicated TM Backup drive...
When I used Disk Utility for repairs... it went from 7 minutes to 4 hours and after about 10 minutes it was saying 40 hours...
So I just replace it with a New EHD...

Similar Messages

Lacie 1TB external HDD recently stopped doing Time Machine backups. Disk Utility recommends that the disk needs to be repaired.

I've been using my Lacie 1TB external HDD for my Time Machine backups for quite sometime. Its never given me any problems until now.
It recently stopped doing the backups, so I checked Disk Utility and it recommended that I repair the disk. How long does it take for Disk Utility to repair a 1TB external HDD?
Other things to consider:
- Cant find the disk in the Finder, I used to be able to do that before.
- When I tried to go a Time Machine backup, it said the disk was not available.
Upon using disk utiliy, I successfully verified the disk. Then I initiated the disk repair process.
The current status:
- checking file system
- Volume repair complete
- Updating boot support partitions for the volume as required.
The progress bar says "Verify and Repair volume "LaCie"" - the progress bar does not indicate how much has been done or how long it will take.
Capacity: 1 TB (1,000,204,476,416 Bytes)
Mount Point: Not Mounted
Format: Mac OS Extended (Journaled)
All other status fields blank.
Any one know how long it will take for Disk Utility to repair the external HDD? Any other ideas as to how I can get the Lacie HDD to reconnect with the Macbook and resume normal operations? i.e. Time Machine backups, accessing contents through the Finder.

purduegrad_macguy wrote:
I've been using my Lacie 1TB external HDD for my Time Machine backups for quite sometime. Its never given me any problems until now.
Mine Failed after 3 years and 4 months of using it as a Dedicated TM Backup drive...
When I used Disk Utility for repairs... it went from 7 minutes to 4 hours and after about 10 minutes it was saying 40 hours...
So I just replace it with a New EHD...

Lacie 1Tb USB HDD not recognized, even in Disc Utility

Hi to all,
I have just bought a Lacie 1Tb external USB disk. It did not work correctly under Mac OS X but it works when I use it under Parallels. It is formatted as NTFS and I manage to use correctly under OS X my old Lacie 250 Gb (also NTFS). When I connect the drive to my MacBook Pro nothing happens or sometimes a folder appears on my desktop (with the content of the HDD, read only) and in Finder the HDD is mounted with an icon with a W on it (not the usual orange icon with usb symbol). I cannot use the HDD. If I open Disc Utility the HDD is not shown at all but it appears correctly under System Profile. If I boot with the installation DVD and the USB attached, Disc Utility (launched from the DVD) sees correctly the drive. My conclusion is that there is some software that conflict with Mac OS X in mounting the device. Someone of you has any clue to provide? Is there a way to "reset" the way MAC OS X handles NTFS partitions (if it is a problem with NTFS)? The USB disk works correctly on another Mac with OS X (I tried it at the shop).
Thank you in advance for your help and I wish you all a Happy New Year.

Thank you for your reply.
At the moment also the other HDD has the same behaviour. It looks like I screwed up the usual NTFS OS X handling What I did was to uninstall Mac Fuse completely (by disabling it and then by removing the icon from System Preferences, as described in the Mac Fuse help page). I had no need to install drivers to make the "old" HDD to work (when it worked . Also when I tested the 1TB HDD on a Mac at the shop, the Mac came with a clean standard install. The worst thing is that Disc Utility completely ignores the HDD presence so I cannot even initialize it. As I said I could initialize it booting with installation DVD but I would like to fix the issue. I removed Mac Fuse I had installed to try to reset the things... with no success I think that, even without any external software to read/write NTFS partitions, I should be able to mount the drive or at least work with it under Disk Utility, shouldn't I?

Problem with using Seagate 1tb external hdd with my macbook!

Hi... I just bought online Seagate 1tb external HDD without knowing that it's not MacOSx compatible...
I heard that I can format it to fat32 to make it mac compatible...
Would it work? Or what else can I do except returning it back?
Thank you in advance for any help...

Hi laundry beach... Thanks...
here is the seagate's page about the 1tb EHD:
http://www.seagate.com/www/en-us/products/external/freeagent/freeagent_go/#tTabC ontentSpecifications
And this is the link by seagate for how to format the drive for mac:
http://www.seagate.com/ww/v/index.jsp?locale=en-US&name=how-to-reformat-your-dri ve-dn&vgnextoid=da3bd85104b51210VgnVCM1000001a48090aRCRD
it says PC compatible but not mac compatible... that's why I think that it's not mac compatible...
So does that make sense to use it by formating it to some mac compatible state?
Or would it work without seams?

LaCie 1TB external hard drive can not connect to E4200

I have my LaCie 1TB external hard drive plugged into the USB-port of the Linksys E4200 so I can access that drive wireless.
However, in my disk management (via Cisco Connect), it does not show under Storage > Disk.
How can I solve this so I can access this hard drive from any computer in the network?
The drive is formatted in NTFS.
Thanks

Connect the hard drive directly to the computer and make sure that your computer can detect the hard drive.
If it is detected and working properly on your computer then connect the hard drive the USB port on the router.
Follow this link to setup storage device connected to E3000 router.

Trouble with Lacie 1TB external hard disk

Recently got a Lacie 1TB external hard disk. Need to get as close to 1TB actual capacity as I can.
Used cfdisk to create a single Linux partition, and thought I tried to "maximize" the size.
Used mkfs -t ext3 /dev/sdb1 to create the file system.
Tried to mount the disk. The first go around apparently failed (dmesg said there was no journal).
I repeated all of the above and the second time it mounted, but "df -h" reports:
/dev/sdb1 925G 200M 878G 1% /mnt/external_1
What the hell happened?
Can someone please advise on how to fix this, and actually maximize the real available space? Please include the exact utilities and flags you would recommend.
thanks much.

lucke,
i know disks always have less capacity than the nominal size. but a 1TB disk should have more than 900 MB available. possibly as much as 980 MB. that would be commensurate with my past experience using other external drives. over 200 GB used off the bat is ridiculous, and i've never seen anything like that before.
as a revised question to people out there, which fs would you recommend to get the most out of this disk. it's going to have 900+ GB of files, each almost exactly 170 MB, and will be processed via the USB2 interface.

Finder Crashes When Plugging in Iomega 1TB External HDD

I know I have seen this question asked many times, and while I can find answers specific to a certain HDD's internal software causing the issue, I cannot find the resolutions involving the capacity of the disk space used...
Anyway, whenever I plug-in my Iomega drive (USB 2.0), everything mounts properly in Finder and I am able to access the drive itself. I can browse through the folders without issue. However, if I transfer a file from the drive, or on occassion even open a file, Finder becomes unresponsive. There are times where nothing will rectify this and over a course of 10-min the entire computer becomes unresponsive, forcing a "manual" restart. Other times if I pull the USB cord from the port Finder will begin functioning normally.
The drive opens in Disk Utility, where I have ran the "Verify Disk" fx, which says the drive is OK.
The drive details all seem normal, although under S.M.A.R.T. Status it says it is not supported, and I cannot remember if this is normal for an External HDD or not.
As mentioned above, I have read that nearing or reaching the drive's capacity can cause these symptoms. Without realizing it I have let it become quite full, with ~7.7gb of available space remaining of the 1TB, so I am wondering if this is the cause of my issue. I have tried deleting files from the drive in order to free-up space, but Finder inevitably crashes in the process.
Any help or suggestions would be greatly appreciated.
Thanks

The next time you have the problem, note the exact time: hour, minute, second.
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Scroll back in the log to the time you noted above. Select any messages timestamped from then until the end of the episode. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

Can't mount 1tb External HDD - error message

Hello,
First of all, I wasn't sure exactly where to post this, so please let me know if it should be moved.
Als, I have done pretty extensive searches on this problem ad error message but all the results were about 2 years old - i'm posting now in the hope that someone has some new answers!
I have a Macbook August 2007 model, and I have been using a Iomega 1TB external hardrive with no problems for the last year, until yesterday..
I can only think that I might have been too quick to take out the usb cable after ejecting it or the mac was too slow responding after I clicked to eject - I was running iMovie HD at the same time, which seems to slow things down. Now it will not mount, though I can see it in Disk Utility. I'm gutted if this is what caused it because I am so meticulous about ejecting it properly!!
When I tried to verify and repair, I got the following error code:
Verify and Repair disk “ABBY'S 1TB”
** /dev/disk2s1
** Phase 1 - Read FAT
Unable to read FAT (Input/output error)
Error: The underlying task reported failure on exit
1 non HFS volume checked
1 volume could not be repaired because of an error
I'm not technical enough to know which way it has been formatted, sorry.. but I just looked on Disk Utility and it says 'MS-DOS File System (FAT32)' .. I don't know what FAT and HFS mean...
I heard that if i try to mount it on a PC, it might work and then I could copy everything to dvds and try to reformat it.. is this a good option? I don't actually have a pc, I have used Macs for years, but I could wait til next week and find one to use..
But if anyone has any tips on how I can try to repair it or recover the lost data, I'd be really happy to hear from you.
Thanks,
Abby
Message was edited by: Abigail Lawson

Hey there Shaun7036,
It sounds like you are unable to mount your external USB drive when you connect it to your Mac and you have already reformatted, and repaired it. I would next reset your SMC and then your PRAM.
Shut down the computer.
Plug in the MagSafe power adapter to a power source, connecting it to the Mac if its not already connected.
On the built-in keyboard, press the (left side) Shift-Control-Option keys and the power button at the same time.
Release all the keys and the power button at the same time.
Press the power button to turn on the computer.
Note: The LED on the MagSafe power adapter may change states or temporarily turn off when you reset the SMC.
Intel-based Macs: Resetting the System Management Controller (SMC)
http://support.apple.com/kb/ht3964
Then:
Shut down your Mac.
Locate the following keys on the keyboard: Command (⌘), Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.
After resetting NVRAM or PRAM, you may need to reconfigure your settings for speaker volume, screen resolution, startup disk selection, and time zone information.
About NVRAM and PRAM
http://support.apple.com/kb/ht1379
Thank you for using Apple Support Communities.
Take care,
Sterling

Problems with 1TB external HDD

I have two external HDD, one a LaCie 2TB and one a Maxtor Basics 1.5TB. Both devices come formatted as FAT32. I have tried reformatting using Disk Utility to Mac OS Extended but the process fails on both devices, whichever of my iMac I use. The only thing I can then do is re-partition them as FAT32 again.
Equally frustrating, the devices are not visible when I try to access them from other machines on the network whereas other drives connected to the same machine are fully visible.
Is there a size limit for formatting using Mac OS Extended or something?
Any suggestions of how I might at least get them visible for sharing across the network - even if they have to stay as FAT32 drives?

Hi Brian
Connect the External HD directly up to one of the iMac's and follow the Formatting and Partitioning instructions in Ken's article: (but note that doing so will erase the data on the drive)
Ken Stone's article: http://www.kenstone.net/fcphomepage/partitioningtiger.html
It's sounding more like your trouble is with network sharing than format, if so have a look
at: http://support.apple.com/kb/HT1549
and: http://db.tidbits.com/article/9261
Dennis

Toshiba 1TB external HDD

I purchesed one of these about amonth ago, to day when I plugged the machine into the mains an turned it on nothing happend. i have left it for about an hour and tried again, still nothing happens, what could be the problem and how would i go about fixing this.
Cheers in advance.

I had a similar problem with my Toshiba 320GB external HDD. It would work when connected to by Dynadock, but not when connected to any of the USB ports on my Qosmio G50. I tried removing all the USB drivers and restarting without luck.
It turned out to be the fact I wasn't using the original USB cable that came with the HDD, but a stock stadard USB cable. The original cable that came with the carries 5volts whereas a std USB may not. And the reason the Dynadock worked is that it has a mains power source.

LaCie 1TB External Un-RAID?

I have a on 1tb LaCie Big Disk external hard drive that I mirror raided when I got it a few months back. However, I recently purchased another 1tb HD that I was planning on using as a back up to the other for a full 1tb back up.
I've stared at Disk Utility for an hour and can't figure how to restore the disk from 500 back to 1TB. Basically turning off the mirror. Please help me with this if you have any knowledge of this subject. Thanks

I assume it's a hardware-based. In that case, you'll need to pull all the data off the drive, then switch modes (which I believe is adjusted from the back of the enclosure in this particular model).
http://www.lacie.com/download/manual/2bigQuadraen.pdf
You'll then need to initialize the resultant drive and put the data back on. And you should know, with striped RAID 0 you'll lose everything, if one of the drives fails. You must be 100% sure you're backing up everything in that box somewhere else, because RAID 0 is a ticking time-bomb.

External HDD just won't fly on USB... (and other random rants)

Hi there Apple lovers and problem solvers!
I have an external drive that can connect via firewire AND usb 2.0. The drive runs fine on the firewire but whenever I plug it into the USB I immediately get the alert message "USB Over Current Notice, A USB device is currently drawing too much power. The hub it is attached to will be deactivated".
I am trying all sorts of things. I purchased an i-rocks USB hub that is self powered and still, no cigar.
If I were using the storage device just for backup, I would be happy going via firewire, but since I am using this device for faster realtime audio recording and movie making, I would like to run via USB 2.0. My understanding is that USB 2.0 generates faster test results than the Firewire 1394 and I would like to know for myself and not be limited to the Firewire.
I'm a bit dissapointed because I upgraded from my 17" powerbook to the 24" iMac as I was having USB issues thinking these same USB issues wouldn't haunt me in a desktop machine and yet here I am again, dealing with these same problems. Whats the problem? Why can a PC user plug in my drive into a USB and it fires up no problem? Why is my USB always inferior or lacking the guts to do the core stuff I need to do. I love apple, the interface is great... but I spend way too much time fiddling with the odd issue like USB circuits that can't handle the juice or commit to doing what they just can't achieve. Whats the solution here?
I'm on Leopard and I upgraded over the top of Tiger (which ppl tell me was a no no). Is there going to be a fix that will correct the apparent problems that are caused by upgrading to leopard from tiger instead of a clean install? Ever since the upgrade my USB shorts out... for example, when the CPU is a bit intensive, like flying between expose, widgets and an animating finder window, its like the USB shorts out and my mouse will flick around the screen... it makes me want to downgrade back to tiger. What do I do?????? Is there an update to fix this coming anytime soon?
Kind regards,
Robert Norris, Apple convert and previous apple preacher who has converted an army of pc users to apple. Please help me stay a happy customer.

Hi cosmicbdog
Humm..(just checking) I hope you don't have it connect FireWire AND USB at the same time? Have you tried a different USB cord perhaps that one has a short, or some other device is also drawing on the bus.
Have a look at "USB compared with FireWire" in the following article:
http://en.wikipedia.org/wiki/Usb#USBcompared_withFireWire
Also have a look at this "USB Device Troubleshooting" article:
http://docs.info.apple.com/article.html?artnum=58033
I installed 10.5 over 10.4.11 with no issues what so ever, only lost a couple of small unsupported third party App's.
Have you run Disk Utility / Repair Disk Permissions sense upgrading? note: 10.5.. repair disk permissions hangs on less than a min. for a short time so be patient and let it finish.
http://kb.wisc.edu/helpdesk/page.php?id=3810
Dennis

Format External Drive Error can't unmount disk LaCie 1TB External Drive

Need Help Can't Format This disk. I have tried Formating with Disk Utility and It says it can't be unmounted.
Help!!

Drive Partition and Format
1. Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
If you are preparing an external or a non-startup drive, then open Disk Utility in your Utilities folder.
2. After Disk Utility loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Apply button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Security button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Steps 4-6 are optional but should be used on a drive that has never been formatted before, if the format type is not Mac OS Extended, if the partition scheme has been changed, or if a different operating system (not OS X) has been installed on the drive.

Problems formatting new seagate 1tb external hdd

hi,
new here as... well... I've not had problems with my mac prior to this.
I did have a buffalo 1tb drive, but earlier in the week I got a warning that this was unstable and I should copy data from it. saved my itunes library, and attempted to re-format the drive, but disk utility was unable to do so. I was getting errors stating it was unable to verify the drive, or re-format it.
I've just got a new seagate 1tb drive and I'm having similar/identical problems: I can't verify the drive and I'm unable to format it either.
I have been able to format the drive as an ms-dos (fat) drive, but if memory serves itunes/mac ran into problems when there was more than 200gb on the disc (and my itunes library's already past that!)
any and all help gratefully received.
cheers!
Leo.

Try erasing the drive and reformatting it as Mac OS Extended (Journaled) using disk Utility from your install disk. First mount the drive on your desktop then
1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. select the drive you want to format, and see if that works.

My macbook retina (15" mid 2012) crash when plug Lacie Thunderbolt external HDD

Hello,
I got this problem several times, and now I decided to post here to find some help. I got a macbook retina 15" mid 2012 and a Lacie 1T Rugged Thunderbolt. They works together perfectly at the first few months. And the crash started to happen about 4-5 months ago. It sometime crash my mac when I plug the Lacie in, sometime not. I tried to run the Lacie Firmware Updater but it said "No Lacie devices found".
Anyone please help.
Below is the log from the Console-> System Diagnostic Reports on Jan 7th 2014:
The log file name is : "wpa_supplicant_2014-01-07-000045_cuongs-MacBook-Pro.crash"
Process:         wpa_supplicant [132]
Path:            /Library/StartupItems/wpa_supplicant_srv/wpa_supplicant
Identifier:      wpa_supplicant
Version:         ???
Code Type:       X86 (Native)
Parent Process: launchd [1]
Responsible:     SystemStarter [115]
User ID:         0
Date/Time:       2014-01-07 00:00:45.420 -0500
OS Version:      Mac OS X 10.9 (13A603)
Report Version: 11
Anonymous UUID: E0CBEC6A-A197-B3B1-60B3-D048528D270B
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000078
VM Regions Near 0x78:
--> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL /Library/StartupItems/wpa_supplicant_srv/wpa_supplicant
    __TEXT                 0000000000001000-000000000005b000 [ 360K] r-x/rwx SM=COW /Library/StartupItems/wpa_supplicant_srv/wpa_supplicant
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   wpa_supplicant                          0x00045d6c l2_packet_receive + 63
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x00008ba0 ecx: 0x00000001 edx: 0x020fee00
edi: 0x020fee00 esi: 0x00045d2d ebp: 0xbffffc88 esp: 0xbffffc40
   ss: 0x00000023 efl: 0x00010212 eip: 0x00045d6c   cs: 0x0000001b
   ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
cr2: 0x00000078
Logical CPU:     3
Error Code:      0x00000004
Trap Number:     14
Binary Images:
    0x1000 -    0x5afff +wpa_supplicant (???) <4CC4D923-8EC1-4402-F06C-1C2C4747E543> /Library/StartupItems/wpa_supplicant_srv/wpa_supplicant
0x8feb6000 - 0x8fee8417 dyld (239.3) <4B280BB1-55F8-313F-86A6-8ADD644ED69E> /usr/lib/dyld
0x900c6000 - 0x900cbff3 libsystem_platform.dylib (24.1.4) <875321B9-34EF-3FCC-880C-633FA05223F5> /usr/lib/system/libsystem_platform.dylib
0x90205000 - 0x9020ffff com.apple.bsd.ServiceManagement (2.0 - 2.0) <B84F3916-236A-347B-9C1F-3DE571496737> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManage ment
0x90210000 - 0x902fcff7 libxml2.2.dylib (26) <32040145-6FD6-3AD2-B98B-39F73BF9AC47> /usr/lib/libxml2.2.dylib
0x90346000 - 0x903affff com.apple.datadetectorscore (5.0 - 354.0) <0C6C812D-3E7A-31A4-BFDE-CD3316AA35B6> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
0x903b0000 - 0x903b4ffc libpam.2.dylib (20) <50623D44-795F-3E28-AA85-23E0E7E2AE0E> /usr/lib/libpam.2.dylib
0x903b5000 - 0x904c7ffc libsqlite3.dylib (158) <B3DB0FED-FE4C-314D-8329-CF7708C8AAF4> /usr/lib/libsqlite3.dylib
0x904c9000 - 0x90532fff com.apple.SystemConfiguration (1.13 - 1.13) <542075CD-9085-3F30-B84B-DD0277D6A40E> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x90533000 - 0x9059dff7 com.apple.framework.CoreWiFi (2.0 - 200.21.1) <13EE6C12-B981-3132-864A-D493B91AE37E> /System/Library/Frameworks/CoreWiFi.framework/Versions/A/CoreWiFi
0x905a3000 - 0x905a6ff9 com.apple.TCC (1.0 - 1) <A5FCF7AA-3F56-3A19-9DF1-661F1F02F79D> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
0x9096a000 - 0x9096bfff libsystem_blocks.dylib (63) <2AC67D5E-ECD4-3644-A53C-9684F9B7AA33> /usr/lib/system/libsystem_blocks.dylib
0x90afd000 - 0x90b25fff libsystem_info.dylib (449.1.3) <BB68E8CC-422F-3121-8C86-D0F766FB696D> /usr/lib/system/libsystem_info.dylib
0x90c5b000 - 0x90d06fff libcrypto.0.9.7.dylib (106) <DA3D5F8E-5822-3D41-BC1C-FFE1CC9BB42B> /usr/lib/libcrypto.0.9.7.dylib
0x90dfc000 - 0x910fdff7 com.apple.CoreServices.CarbonCore (1077.13 - 1077.13) <C514A490-8689-3665-AD82-863B5FF8D6AE> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x922e7000 - 0x922effff libcopyfile.dylib (103) <1B1484BD-08B6-3BA9-94CA-A7C24B610EB3> /usr/lib/system/libcopyfile.dylib
0x931a8000 - 0x931b6fff libxar.1.dylib (202) <B73748D4-F830-3C71-98B3-7A3ABF5136FD> /usr/lib/libxar.1.dylib
0x931c2000 - 0x931d0ff7 libz.1.dylib (53) <858B4D9F-D87E-3D81-B07A-DF9632BD185F> /usr/lib/libz.1.dylib
0x9335e000 - 0x93370fff libsystem_asl.dylib (217.1.4) <51EB17C9-9F5B-39F3-B6CD-8EF238B05B89> /usr/lib/system/libsystem_asl.dylib
0x93377000 - 0x93382ffb libcommonCrypto.dylib (60049) <F8E60C43-22EE-3E0B-9546-3365056901F1> /usr/lib/system/libcommonCrypto.dylib
0x934d0000 - 0x934d8fff liblaunch.dylib (842.1.4) <3798500D-4436-3AEB-B273-7F2428C33A4A> /usr/lib/system/liblaunch.dylib
0x936d3000 - 0x936ebff7 libsystem_malloc.dylib (23.1.10) <69F485C9-B3E7-3E36-A06C-D7DFD29D22E1> /usr/lib/system/libsystem_malloc.dylib
0x93fb2000 - 0x94028ff3 com.apple.securityfoundation (6.0 - 55122) <25149798-A37E-316F-84AB-93029EAF33D8> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
0x94051000 - 0x940afffd com.apple.AE (665.5 - 665.5) <54F2F247-160C-3A22-A6E3-5D49655A67AB> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x9447e000 - 0x94485ffb libsystem_pthread.dylib (53.1.4) <8B1B7B84-1B5D-32A8-AC0D-1E689E5C8A4C> /usr/lib/system/libsystem_pthread.dylib
0x94486000 - 0x944b7ffa libsystem_m.dylib (3047.16) <28E614E8-7802-3E84-960A-AD4721EF10F7> /usr/lib/system/libsystem_m.dylib
0x94854000 - 0x94871ff4 libsystem_kernel.dylib (2422.1.72) <C5641F6C-E271-380A-A656-AE4C04345602> /usr/lib/system/libsystem_kernel.dylib
0x948cf000 - 0x948e7ffd libdispatch.dylib (339.1.9) <6249BAE5-044F-3A7A-9CCC-03FF7E6B405B> /usr/lib/system/libdispatch.dylib
0x94a96000 - 0x94ad3ff7 libauto.dylib (185.5) <CD008E66-4A0C-35F5-8D72-80D76A716A03> /usr/lib/libauto.dylib
0x94b71000 - 0x94b7dffe libkxld.dylib (2422.1.72) <F9B35FA5-C936-3286-A055-2B0780A674AC> /usr/lib/system/libkxld.dylib
0x9553e000 - 0x9553fffd libunc.dylib (28) <22A126A1-DCFB-3BE5-A66B-C973F0A5D839> /usr/lib/system/libunc.dylib
0x965fd000 - 0x9667dff7 com.apple.CoreServices.OSServices (600.4 - 600.4) <1227DF22-E2DA-3764-A1CA-10CC0CEBE377> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x966c2000 - 0x966cdff6 com.apple.NetAuth (5.0 - 5.0) <3B2E9615-EE12-38FC-BDCF-09529FF9464B> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x96c47000 - 0x96cd9ffe libsystem_c.dylib (997.1.1) <D06FD754-8CE3-3EB7-BE05-2EF939BBE05F> /usr/lib/system/libsystem_c.dylib
0x96cda000 - 0x96cdcfff libsystem_configuration.dylib (596.12) <1C31C3F6-568D-3854-AE03-A5DA2F39297E> /usr/lib/system/libsystem_configuration.dylib
0x97284000 - 0x973e6ff3 com.apple.CFNetwork (673.0.3 - 673.0.3) <5E0E9AE8-073B-3F2B-B0C7-A0129DE787F6> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x97899000 - 0x978bdfff libxpc.dylib (300.1.17) <252BC88F-A5CA-3E67-AEDB-3D7B9F4537E2> /usr/lib/system/libxpc.dylib
0x978c1000 - 0x978ecff7 libpcap.A.dylib (42) <66FBEAD3-FE91-3A89-8706-FB95229068AC> /usr/lib/libpcap.A.dylib
0x978ed000 - 0x978edffd libOpenScriptingUtil.dylib (157) <4D06E8ED-D312-34EA-A448-DFF45ADC3CE5> /usr/lib/libOpenScriptingUtil.dylib
0x978ee000 - 0x978effff libDiagnosticMessagesClient.dylib (100) <B936B1D4-90BB-395D-8EA9-E1237608E7D0> /usr/lib/libDiagnosticMessagesClient.dylib
0x97929000 - 0x9792cfff libdyld.dylib (239.3) <729B32AC-EEE2-3739-8CE3-F90838D51906> /usr/lib/system/libdyld.dylib
0x9795e000 - 0x97b064af libobjc.A.dylib (551.1) <31CBE178-E972-30D1-ADC6-4B8345CAE326> /usr/lib/libobjc.A.dylib
0x97b07000 - 0x97b2aff7 libc++abi.dylib (48) <5367BE5A-D475-3FB4-972D-E1DC999A709A> /usr/lib/libc++abi.dylib
0x97f24000 - 0x97f50ff7 com.apple.DictionaryServices (1.2 - 208) <33873336-BECD-3F62-A315-C45F24C1818C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x98133000 - 0x9820eff7 com.apple.LaunchServices (572.23 - 572.23) <7E52FB5C-9ECF-3CB9-BF18-6652B8D8CDE0> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x982b7000 - 0x982e2ff7 libsystem_network.dylib (241.3) <71EBA489-386D-3608-ADE6-CB50EBD1AB1B> /usr/lib/system/libsystem_network.dylib
0x983dd000 - 0x98407fff libxslt.1.dylib (13) <249D54AB-1D82-38FE-ABEC-0D575450C73B> /usr/lib/libxslt.1.dylib
0x98734000 - 0x98735ffa libsystem_sandbox.dylib (278.10) <F3C9C427-AF9F-3CE0-95FF-DC9ACA0B5760> /usr/lib/system/libsystem_sandbox.dylib
0x98737000 - 0x9873cff6 libcompiler_rt.dylib (35) <9924DF2E-D80B-3A21-920D-544A4597203F> /usr/lib/system/libcompiler_rt.dylib
0x98fb9000 - 0x98fb9fff libkeymgr.dylib (28) <1B097DEA-011E-3B1C-86D5-6C7FAD5C765A> /usr/lib/system/libkeymgr.dylib
0x98fba000 - 0x99021ffc com.apple.framework.CoreWLAN (4.0 - 400.45.1) <8DADD7D2-AB98-34ED-8D6F-335338502CBE> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
0x99022000 - 0x99072ff7 libcorecrypto.dylib (161.1) <135FD99E-2211-3DF4-825C-C9F816107F0C> /usr/lib/system/libcorecrypto.dylib
0x99073000 - 0x9907cfff com.apple.DiskArbitration (2.6 - 2.6) <6379523D-3196-370C-AE4A-8EA586E36909> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x9907d000 - 0x9907efff libSystem.B.dylib (1197.1.1) <C58F0CC9-C1FD-3024-9358-D3359A6BBCAD> /usr/lib/libSystem.B.dylib
0x990d9000 - 0x990dbfff libquarantine.dylib (71) <EE3B510E-1AEC-3171-8A1A-D6A5A42CF35C> /usr/lib/system/libquarantine.dylib
0x990f8000 - 0x99101fff libsystem_notify.dylib (121) <623269F5-1518-3035-A916-8AF83C972154> /usr/lib/system/libsystem_notify.dylib
0x994a7000 - 0x99714ff6 com.apple.security (7.0 - 55471) <5FCF76B2-92C6-3404-87D3-91B3F6E203AA> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x99715000 - 0x99716fff liblangid.dylib (117) <F18F76C6-7E4B-34AD-AE81-C1C031BF2F7D> /usr/lib/liblangid.dylib
0x99a2e000 - 0x99a35ff2 com.apple.NetFS (6.0 - 4.0) <915AA303-C02B-3B0C-8208-D8AAA4350DB4> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x99b1f000 - 0x99b3eff9 com.apple.framework.Apple80211 (9.0 - 900.47) <68E399FF-AB98-378D-94AC-D0869A72344F> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211
0x99b3f000 - 0x99b57fff com.apple.CFOpenDirectory (10.9 - 173.1.1) <630A5CCF-8FC3-379D-B0BD-41DCE1F0B624> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
0x99c70000 - 0x99c76ffb libunwind.dylib (35.3) <099D1A6F-A1F0-3D05-BF1C-0A7BB32D39C2> /usr/lib/system/libunwind.dylib
0x99d80000 - 0x99e18ff7 com.apple.Metadata (10.7.0 - 800.12) <0AE4CD6B-FDFC-31ED-9F2C-FE870155CAF9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x9a165000 - 0x9a181fff libCRFSuite.dylib (34) <FFF76EBA-DF35-3A5F-857F-3F4B1C9F4C77> /usr/lib/libCRFSuite.dylib
0x9a28b000 - 0x9a451ffb libicucore.A.dylib (511.25) <44DDE9A4-578E-3D23-A41A-D8795D000A18> /usr/lib/libicucore.A.dylib
0x9a4ee000 - 0x9a6f0ff7 com.apple.CoreFoundation (6.9 - 855.11) <50F70E07-043A-3A2F-87EF-A36BA6C5C9D9> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x9a6f1000 - 0x9a766ffb com.apple.framework.IOKit (2.0.1 - 907.1.13) <86D72735-9DFB-35C8-83F7-CE0DCF17D354> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x9a767000 - 0x9a7bcfff libc++.1.dylib (120) <10C0A136-64F9-3CC2-9420-013247032120> /usr/lib/libc++.1.dylib
0x9a7c7000 - 0x9a83afff com.apple.SearchKit (1.4.0 - 1.4.0) <6F607AB6-7553-37BA-BEC5-98FD7C27FAD7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x9a83b000 - 0x9a83bfff com.apple.CoreServices (59 - 59) <06747539-5035-3307-8645-9BC4E7F89023> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x9a83c000 - 0x9ab67ff6 com.apple.Foundation (6.9 - 1056) <C8AE9C03-3460-354A-A8B6-EF4955BE600D> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x9ab68000 - 0x9ab6cffa libcache.dylib (62) <9730D7F2-D226-3F30-8D26-BF598CB781F6> /usr/lib/system/libcache.dylib
0x9b009000 - 0x9b00afff libremovefile.dylib (33) <ED35EA79-EB06-3B84-A6D4-B1A9D6B8648D> /usr/lib/system/libremovefile.dylib
0x9b00b000 - 0x9b017ffc libbz2.1.0.dylib (29) <3CEF1E92-BA42-3F8A-8E8D-9E1F7658E5C7> /usr/lib/libbz2.1.0.dylib
0x9b05f000 - 0x9b067fff libsystem_dnssd.dylib (522.1.11) <1C015806-B971-34F9-B162-3DF7897351D0> /usr/lib/system/libsystem_dnssd.dylib
0x9c141000 - 0x9c145ff7 libmacho.dylib (845) <D8E93E59-1F80-3413-B9CF-78B848F6E873> /usr/lib/system/libmacho.dylib
0x9c16b000 - 0x9c17dfff libbsm.0.dylib (33) <1BE92DB5-0D2F-3BB5-BCC6-8A71EF2A3450> /usr/lib/libbsm.0.dylib
External Modification Summary:
Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
Calls made by all processes on this machine:
    task_for_pid: 105
    thread_create: 0
    thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=71.6M resident=14.6M(20%) swapped_out_or_unallocated=57.0M(80%)
Writable regions: Total=55.8M written=456K(1%) resident=500K(1%) swapped_out=0K(0%) unallocated=55.3M(99%)
REGION TYPE                      VIRTUAL
===========                      =======
Kernel Alloc Once                     4K
MALLOC                             47.6M
MALLOC (admin)                       16K
Stack                              64.0M
VM_ALLOCATE                           8K
__DATA                             1640K
__IMPORT                              4K
__LINKEDIT                         43.1M
__OBJC                              460K
__PAGEZERO                            4K
__TEXT                             28.5M
__UNICODE                           544K
mapped file                       188.5M
shared memory                         4K
===========                      =======
TOTAL                             374.3M

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you boot, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to boot and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal boot may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, reboot as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Lacie 1TB External HDD just went ghost

Similar Messages

Maybe you are looking for