External drives won't sleep properly

Hi
I have my preferences set to allow drives to sleep when possible.
In Tiger this meant that my external drives slept most of the time. They would awaken only when directly accessed by the Finder or an application.
In Leopard my externals are constantly waking.
I have them excluded from Spotlight. They will start when I access something in the Finder that has nothing to do with the drives. They will also start when I access an app like safari.
Any ideas what is happening?

I have the exact same problem. I have my energy setting to put my drives to sleep when possible. I also have an external Firewire drive. In Tiger the external drive was sleeping unless I was accessing it. Now with Leopard the drive constantly wakes up. Just now I hit the back button on Safari and the drive woke up. Crazy.
Unfortunately I have no idea what is causing this, but do have the same issue. I see you excluded them from Spotlight. I just tried that and will see what happens. Are you using Firewire or USB for the external drive? I'm going to switch to UBS and see if that makes a difference.
-Dan

Similar Messages

External Drives Won't Sleep

Hi
Since upgrading to Leopard none of my external drives go into sleep mode when not being accessed. They do when connected to other Macs... so that points to the iMac.
Tried resetting the SMC and also 'put hard disk(s) to sleep' is checked in energy saver. Any suggestions greatly appreciated. Many thanks
Colin
PS I use Lacie drives... Quadra D2 and Porsche

I have the exact same problem. I have my energy setting to put my drives to sleep when possible. I also have an external Firewire drive. In Tiger the external drive was sleeping unless I was accessing it. Now with Leopard the drive constantly wakes up. Just now I hit the back button on Safari and the drive woke up. Crazy.
Unfortunately I have no idea what is causing this, but do have the same issue. I see you excluded them from Spotlight. I just tried that and will see what happens. Are you using Firewire or USB for the external drive? I'm going to switch to UBS and see if that makes a difference.
-Dan

500GB WD My Book external drive won't sleep!

I recently bought a 500GB WD My Book external drive. I formated it as Mac OS Extended and ran a complete backup of my Mac and other external drive. Now the activity light blinks non stop and the drive stays running even though its not being accessed. I've also checked the security of my network thinking maybe somebody on the outside was getting access. I don't get it. Any information would be greatly appreciated. Thank you in advance!

Open the Spotlight pane of System Preferences and add that drive to the list of locations not to index if it isn't already there.
(26811)

External drive won't mount after plugging in iPhone - MacBook 13'' (2,1)

Hi Support Crew...
I have a 13" MacBook(2,1) running OS X 10.6.2. This is a 2 GHz Intel Core 2 Duo machine w/ 4 GB RAM & 320 GB hard drive.
Today, I had the Iomega drive plugged in via USB, along with my soundcard (MOTU 828mk2) plugged in via FW. This is a very normal setup for me which has been bug free since I bought this computer over 2 years ago. When I plugged in my iPhone 3G via USB I got an error message which comes up when you incorrectly remove a device. This was strange because I didn't unplug anything, I only plugged in the iPhone. The iPhone was playing music when I plugged it in and I had to unplug and plug is back in to get iTunes to recognize it.
Ever since this happened, my Iomega external drive won't mount. I am able to access it via Disk Utility (and ran the Verify Disk/Repair Disk - everything is "ok"), however I can't access the data on the drive. I really really need the data but of course can't access it to backup.
Disk Utility log:
500.11 GB Ext Hard Disk Media (black text)
Iris (grey text) - I ran Verify Disk & Repair Disk
2010-01-22 14:20:51 -0800: Verify and Repair volume “Iris”
2010-01-22 14:20:51 -0800: Starting repair tool:
2010-01-22 14:20:51 -0800: Checking Journaled HFS Plus volume.
2010-01-22 14:20:52 -0800: Checking extents overflow file.
2010-01-22 14:20:52 -0800: Checking catalog file.
2010-01-22 14:20:56 -0800: Checking multi-linked files.
2010-01-22 14:20:56 -0800: Checking catalog hierarchy.
2010-01-22 14:20:58 -0800: Checking extended attributes file.
2010-01-22 14:21:00 -0800: Checking volume bitmap.
2010-01-22 14:21:01 -0800: Checking volume information.
2010-01-22 14:21:01 -0800: The volume Iris appears to be OK.
2010-01-22 14:21:01 -0800: Volume repair complete.
2010-01-22 14:21:01 -0800: Updating boot support partitions for the volume as required.
2010-01-22 14:21:01 -0800: Repair tool completed:
2010-01-22 14:21:01 -0800:
2010-01-22 14:21:01 -0800:
System Profiler shows the drive (on both FW & USB ports when I tried other cords). This drive does not require power and I am not using a USB hub, strictly the laptops ports. And yes, the laptop's power adapter is plugged in.
System Profiler: Device Tree log:
Iomega eGo HDD:
Capacity: 500.11 GB (500,107,862,016 bytes)
Removable Media: Yes
Detachable Drive: Yes
BSD Name: disk1
Product ID: 0x047c
Vendor ID: 0x059b (Iomega Corporation)
Version: 0.01
Serial Number: 000000066273
Speed: Up to 480 Mb/sec
Manufacturer: Iomega
Location ID: 0xfd300000
Current Available (mA): 500
Current Required (mA): 0
Partition Map Type: APM (Apple Partition Map)
S.M.A.R.T. status: Not Supported
Volumes:
Iris:
Capacity: 499.97 GB (499,972,702,208 bytes)
Writable: Yes
File System: Journaled HFS+
BSD Name: disk1s10
When I tried to run Migration Assistant, I just get the spinning search circle and none of the drives come up, just endless searching.
The fact that I got the "Improperly removed device" error when I plugged in the iPhone makes me think something weird is up and it's not actually the external drive. There is clicking/whining/noise, the drives powers up fine and is recognized by the system but the mount point is now "not mounted".
Does anyone have any idea how to fix? If you live in SF, I will buy you a beer.
J

I meant to say; "There are NO clicking/whining/noise sounds made by the external hard drive"

Macbook Pro won't sleep properly.

Hello;
I have a problem with my mid 2009 13'' MacBook Pro that won't sleep properly.
Whenever I close the lid, or chose ->Sleep, it takes a few seconds and the system sleeps (fan off, led fading off) , but INMEDIATELY after just a few miliseconds, the system wakes up again (fan on, led on, hdd spinning).
This sequence happens again and again indefinitely (sleeps / wake / sleeps / wake, and so on...)
Then I open the lid and everything works as expected.
So far I tried all this, with no luck:
- I've installed a clean Mountain Lion from scratch.
- The system is untoched: no new apps installed, no new drivers installed.
- All sharings are disabled.
- Bluetooth is disabled.
- Infrared port is disabled.
- There's nothing attached to the computer except from the magsafe cable.
- There are no background processes preventing the system from sleep (checked using "pmset -g assertions")
- There is no disc loaded in the optical unit.
- "Wake for network access" is disabled in Preferences->Energy Saver.
- SMC y PRAM reseted several times.
As you can see, I don't know what else to try...
I would REALLY appreciate any help or suggerence.
Thanks in advance,
Nicolas.

A SMC will not have any results with this, in my past experince. Surprisingly the loginin items is the usual culprit. Try option, command, delete (don't hold these keys ,just press them)and wait till it goes to sleep, and stays that way. Then if it stays aslep try closing the lid. Disconnect all peropherals. Try system preferences>energy saver, make sure comouter sleep is ot set to never, as well as the display on both power adapter and battery. On the same pane, click schedule and make sure the start up or wake is not clicked. Also try a Ssfe boot: Power off, power back on holding the shift key, coninue to hold the shift key till you see the progress bar.This will disable all 3rd party software (it some times fixes some stufff) try the sleep menu under the Apple, or the option,command,delete. Hope this offers some help. If yourMBP is new, less thsn 1 year old, or you have Applecare, I would let them deal with it. You have a warranty,USE IT! All the best
Close all applications/operations.
You ca try a pram reset for the heck of it, in case there is somrthing strange in there that needs to be flushed.
Pram reset: Power off, power on, hold the following keys before the start chime. option,comman,P,R (no commas) and continue to hold the keys till you hear thestart chime 2 times then relesase.Reboot.
Good luck

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

I installed the latest security update now my Lacie external drive won't show up in finder. Any Help?

I installed the latest security update now my Lacie external drive won't show up in finder. Any Help?

Does it show up in Disk Utility?
See mount section in 1st linked article.
Disk Unmount Using Terminal
Disk Utility – Force Mount Disk

LaCie external drive won't mount on iMAC

Hi,
My external LaCie external drive won't mount on my iMAC running 10.6.8 but will mount and show up on my PC as working fine, however I am not able to read the information on it as it was formatted for my iMAC. Therefore it leads me to believe this is a software issue.
I have reason to believe someone had changed the permissions and prevented the mounting of this external drive (which belongs to me) so that the contents won't be found on my iMAC.
How to resolve this issue?
Thanks in advance,
Cait

Cait,
Please try a SMC reset, it may take 2-3 attempts for it to work. Look over the instructions below carefully.
SMC RESET
Shut down the computer.
Unplug the computer's power cord and all peripherals.
Press and hold the power button for 5 seconds.
Release the power button.
Attach the computers power cable.
Press the power button to turn on the computer.
PRAM RESET
Shut down the computer.
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. You must press this key combination 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.

Now my external firewire drives won't sleep on 2012 iMac

I have WD Mybook Studio and a Lacie2big hard drives. Now they won't sleep when the iMac is put to sleep. I guess I'll have to look for firmware updates. I checked on the WD this morning and didn't see anything new. I'll check on the Lacie tonight.
Has anyone else run into this?

Hey Guys... I was having the same spinning issue with my externals hard drives and this firmware update seemed to fix the problems. The update for the WD drives available on the WD support page.
Pick your drive on: http://support.wdc.com/product/download.asp?level1=4&lang=en
Under "For Mac" select: My Book (your drive trpe) Firmware Update - Mac
I also installed the "Turbo" software... don't know if it helped or not.
I'll try to post this info around for others to fins as well... additionally, if the problem persists I'll let you guys know.

Mavericks and unmounting external drive issues upon sleep

Greetings fellow Mavericks users,
I'm hoping someone here can provide some insight as to how to correct the issue I'm experiencing.
Little background:
I was using 10.6.8 for years on a 2008 Mac Pro. I saw no reason to update the OS until I recently acquired a USB 3.0 PCI card and an external drive. In order to use my new hardware, I had no choice but to upgrade to a new version of OSX. Rather than spend money, I took advantage of the free 10.9.2 upgrade available for my machine. The upgrade went surprisingly well with no major hiccups or problems encountered. Yes, a few apps and programs I had running prior to the upgrade were no longer compatible but in the grand scheme of things, my Mac Pro was still alive and kicking along with my most important programs and data. In fact, the upgrade to 10.9.2 fixed a sleep issue I had with 10.6.8 which required the use of an app called PleaseSleep. I don't need that app anymore as the machine goes to sleep and wakes up fine.
Now, on to my dilemma. Prior to the upgrade, I was using an external USB 2.0 drive to house media that I'd share between multiple network devices around the house via SMB (AFP stinks in this regard, hence my refusal to use it); i.e. BoxeeBox. I had run out of space on the USB2 drive hence the need to move everything to my new external USB3 drive that's connected to an internal USB3 PCI controller. The first problem I ran into was that Mavericks now uses Apple's own iteration of Samba (SMB2). After a bit of head scratching and research, I used an application called SMBUp as a replacement to Apple's SMB implementation. That's one problem solved. The next thing that I kept running into was that whenever the machine would sleep then wake up again, I'd get an annoying "Disk was not properly ejected" error message. After more head scratching and research, I've discovered that this appears to be a bug in OSX and how the OS interfaces with 3rd party USB controllers. Fine. I purchased a small app called Jettison which for all intents and purposes unmounts any external drives automatically before allowing the system to sleep. This is where my long-winded (apologies) description above starts to come into play. Now that I have the SMB issue figured out and am using Jettison to eject this USB3 drive when the machine sleeps, I've discovered that I'll still get the "Disk did not properly eject" error message despite Jettison IF there are users connected to the USB3 media drive. Is there a work around this where I can either get Jettison or Mavericks to kill the network connection to the share drive before it's unmounted prior to the machine sleeping?
TL:DR?
Using Jettison with Mavericks, I'm still getting "Disk did not eject properly" when waking the machine from sleep mode. Any way to fix this?
Thanks in advance for any help/suggestions provided.

I had the same problem with Time Machine and solved it by enabling "Enable Power Nap" in Energy Saver:
System Preferences...
Energy Saver
Restore Defaults
Check "Enable Power Nap: While sleeping, your Mac can back up using Time Machine and periodically check for new email, calendar, and other iCloud updates."
2013 21.5 iMac
OSX Mavericks
Seagate 1 TB slim USB 3.0 (power is drawn from USB port), formatted to Mac Journaling File System

External Drive Won't Mount

My external backup drive wont mount automatically as it used to with my earlier ibook. I have to re-boot computer to get it to mount. After that it functions properly until the next time I turn it on to do a backup.
I am wondering if there is something in the formatting of this drive which is causing this? I have formatted it a few times since this started to happen but obviously without fixing the problem

Further Details:
1) After normal use of computer connect and turn on external drive. Drive does not mount.
2) Re-boot computer and turn on drive. Drive mounts.
3) Eject drive. Turn off drive. Turn on drive again - drive mounts.
4) Run SuperDuper backup. eject drive. turn off drive. turn on drive - drive mounts.
Thus, it seems (see (1) above), something in the normal use of the computer (not an artifact of the superduper backup process) over a period of time affects the system such that the drive won't mount again.

External Drives Won't Mount with Mavericks

My external drives will not mount with Mavericks. They did for a while but I noticed that they stopped doing so a week ago or so. I have a drobo raid, hitiachi drive in an external case and a WD Passport. The drobo goes to sleep, the Hitachi external spins and the WD flashes like its being read.
None of the drives were mounted when I loaded Mavericks and, as far as I know, they've not been erased. They did mount for a few weeks but doesn't look they have since the beginning of November.
I have a brand new 2013 MBP 15" Retina with 750 GB SSHD, 16 GB ram and a 2.7 GHz i7. The drives are all connected via one FW800 through a Thunderbolt dongle.

I eventually gave up. I will probably get another card at some point but it probably won't be a SIIG card. Even though they are recommended by digidesign I just doesn't seem to want to work with my G5. Maybe it's some kind of weird software conflict blocking the functionality of the card? Don't know. Two cards in a row were non functional. Something is gummin up the works and the PCI slots work with the other cards I have. The only thing I did not try is plugging in the optional power connection to the FW800 card, which is supposed to be optional. I called SIIG and they had no idea what the problem was and they also said that the power plug would not make a difference for the problem I was having. Anyway, I'm gonna keep monitoring posts to this cause I'd love to hear the answer.. but I'm throwing in the towel. Good luck to the rest of you still trying to solve the riddle.

IMac repeatedly corrupting external drive directories in sleep mode

When putting my iMac into sleep mode or when it goes into sleep mode after a period of inuse I keep getting the "improper eject" message. After waking the iMac I sometimes get the "disc not initialized" message and discover that the directory has been lost. It's happened to 4 different external drives in the space of a month.
The disks are connected via firewire 800. I have recently added a firewire hub but the problem was happening prior to and post this addition. I can't think of any other changes I've made to my set up that may be causing this behaviour. Previously I've had no problems of this nature in the 2 years since I purchased the iMac.
The drives run without this problem when connected to my MacBookPro.
Does anyone have any ideas or suggextions for running any diagnostic tests I coulod run?
Thanks in advance.

I have the same issue on my 2011 MBP. I have three FW800 drives daisy chained together. The first drive in the series disconnects when my computer goes to sleep and I get the error stating the drive wasn't dismounted properly. The other two drives stay connected fine. I don't have to close the lid, it will do this after the computer goes to sleep based on my power saving settings.
The drive that disconnects is a 500GB G-Drive. The second drive is a 1 TB Hitachi drive mounted in a IcyDock. The third drive is a 500GB G-Mini Drive.
I had the same three drives connected to my previous 2007 MBP and never had the issue. The issue started when I purchased my new MBP in July. My software is up to date and I'm use OS X Lion.

Maxtor External Drive Won't Mount!

Here is my problem.
We got a Maxtor One Touch III 1 TB external drive. I loaded about 850 GB of media onto it, passed it off to my partner to continue to edit our video project. Everything was running fine on my macbook pro 2.2 core duo. He edited for a day on his macbook 1.83 core duo. Said everything was fine.
That night he shut the machine down without unmounting the drive. He said the drive kept blinking so he shut it off. In the morning he tried to connect the drive to a g4 tower running 10.3.9. (I never realized he was so tech-vapid). He said the drive wouldn't mount. Then he moved it back to his macbook. Still wouldn't mount. Now it won't mount on my macbook or any machine. He then wonderfully told me he once had the same problem with a G-Drive 500 GB external. Wouldn't mount after switching it to his g4 and back. G-Tech told him the drive was dead so he sent it back. Maxtor told us this drive is dead, but I just think it sounds fishy.
It is still spinning, but there is no light on. Have tried every different kind of connection and updated drivers, same result. A friend said if it got unintentionally unmounted it might take the OS hours to fix it up because it's a RAID 0, suggested leaving it connected for a few hours and see what happens, but that happened once with my G-RAID and it didn't need time to fix itself. I am stupid for buying a maxtor it seems, but it doesn't change my dilemma.
Someone help.

Check the /Volumes/ folder for a broken alias to the disk. The folder is invisible so you need to use the "Go" menu to open it.

WD External drive won't mount

Hello everyone! I haven't been here in a while because I just haven't had any Mac issues. Now I do.
I have a 1 TB WD external HD that won't mount. I connect it via firewire to an Old G4 Sawtooth running OS 10.5.8. My mac sees the drive, it just won't mount. I've also tried to mount it via USB, but again, my system sees the drive, but won't mount it. I inadvertantly disconnected the firewire cable, which I didn't realize for several hours. I reattached the cable, tried to mount it, and nothing. I ran disc repairs, and Disc Utility actually told me the drive was successfully repaired. Again I tried to remount it, but nothing. I repaired permissions, and this didn't work. I've tried different cables, and this doesn't work.
I don't have another Mac to connect it to, so I don't know if this would work. Here's where things get a little wierd, but interesting. I connected it to my PC laptop, and it mounted. Now, this is a drive that was formatted Mac OS Extended (Journaled) on my G4, so I have to use Mac Drive so my PC will recognize and mount The Drive. So My PC sees The Drive as Mac OS Extended, and mounts it. All files are in tact, and the drive runs normally. This is a music drive and it plays normally on my PC. Meanwhile, if I try connecting it back on My Mac, the name of The Drive randomly changes from 931.5 GB WD to 931.5 GB WD My Media Book. I believe My Media Book is the factory name of The Drive before OS formatting. The Volume name remains the same on my G4 each time I've tried to mount it.
I do have another identical drive that mounts from all the bus ports on my G4. Any ideas here? Can I get my Drive to begin mounting on my G4 again? Any and all answers are appreciated.

Terminal List. disk4 is the malfunctioning drive.
Last login: Mon Feb 25 19:25:12 on ttys000
raymond-medinas-power-mac-g4-agp-graphics:~ raymondmedina$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     Apple_partition_scheme                        *111.8 Gi   disk0
   1:        Apple_partition_map                         31.5 Ki    disk0s1
   2:             Apple_Driver43                         28.0 Ki    disk0s2
   3:             Apple_Driver43                         28.0 Ki    disk0s3
   4:           Apple_Driver_ATA                         28.0 Ki    disk0s4
   5:           Apple_Driver_ATA                         28.0 Ki    disk0s5
   6:             Apple_FWDriver                         256.0 Ki   disk0s6
   7:         Apple_Driver_IOKit                         256.0 Ki   disk0s7
   8:              Apple_Patches                         256.0 Ki   disk0s8
   9:                  Apple_HFS Mac Leopard II          91.8 Gi    disk0s10
10:                  Apple_HFS Mac Tiger               19.7 Gi    disk0s12
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     Apple_partition_scheme                        *186.3 Gi   disk1
   1:        Apple_partition_map                         31.5 Ki    disk1s1
   2:             Apple_Driver43                         28.0 Ki    disk1s2
   3:             Apple_Driver43                         28.0 Ki    disk1s3
   4:           Apple_Driver_ATA                         28.0 Ki    disk1s4
   5:           Apple_Driver_ATA                         28.0 Ki    disk1s5
   6:             Apple_FWDriver                         256.0 Ki   disk1s6
   7:         Apple_Driver_IOKit                         256.0 Ki   disk1s7
   8:              Apple_Patches                         256.0 Ki   disk1s8
   9:                  Apple_HFS Mac Leopard I           186.2 Gi   disk1s10
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     Apple_partition_scheme                        *465.8 Gi   disk2
   1:        Apple_partition_map                         31.5 Ki    disk2s1
   2:             Apple_Driver43                         28.0 Ki    disk2s2
   3:             Apple_Driver43                         28.0 Ki    disk2s3
   4:           Apple_Driver_ATA                         28.0 Ki    disk2s4
   5:           Apple_Driver_ATA                         28.0 Ki    disk2s5
   6:             Apple_FWDriver                         256.0 Ki   disk2s6
   7:         Apple_Driver_IOKit                         256.0 Ki   disk2s7
   8:              Apple_Patches                         256.0 Ki   disk2s8
   9:                  Apple_HFS 500 GB HD               465.6 Gi   disk2s10
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     Apple_partition_scheme                        *931.5 Gi   disk3
   1:        Apple_partition_map                         31.5 Ki    disk3s1
   2:             Apple_Driver43                         28.0 Ki    disk3s2
   3:             Apple_Driver43                         28.0 Ki    disk3s3
   4:           Apple_Driver_ATA                         28.0 Ki    disk3s4
   5:           Apple_Driver_ATA                         28.0 Ki    disk3s5
   6:             Apple_FWDriver                         256.0 Ki   disk3s6
   7:         Apple_Driver_IOKit                         256.0 Ki   disk3s7
   8:              Apple_Patches                         256.0 Ki   disk3s8
   9:                  Apple_HFS 1 TB Music Drive II     931.4 Gi   disk3s10
/dev/disk4
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     Apple_partition_scheme                        *931.5 Gi   disk4
   1:        Apple_partition_map                         31.5 Ki    disk4s1
   2:             Apple_Driver43                         28.0 Ki    disk4s2
   3:             Apple_Driver43                         28.0 Ki    disk4s3
   4:           Apple_Driver_ATA                         28.0 Ki    disk4s4
   5:           Apple_Driver_ATA                         28.0 Ki    disk4s5
   6:             Apple_FWDriver                         256.0 Ki   disk4s6
   7:         Apple_Driver_IOKit                         256.0 Ki   disk4s7
   8:              Apple_Patches                         256.0 Ki   disk4s8
   9:                  Apple_HFS 1TB Music Drive         931.4 Gi   disk4s10
raymond-medinas-power-mac-g4-agp-graphics:~ raymondmedina$
Terminal info on disk4s10.
Last login: Mon Feb 25 22:22:41 on ttys000
raymond-medinas-power-mac-g4-agp-graphics:~ raymondmedina$ diskutil info disk4s10
   Device Identifier:        disk4s10
   Device Node:              /dev/disk4s10
   Part Of Whole:            disk4
   Device / Media Name:      Apple_HFS_Untitled_1
   Volume Name:              1TB Music Drive
   Mount Point:
   File System:              Journaled HFS+
   Owners:                   Disabled
   Partition Type:           Apple_HFS
   Bootable:                 Is bootable
   Media Type:               Generic
   Protocol:                 FireWire
   SMART Status:             Not Supported
   Volume UUID:              61A8EAFF-E1C9-3605-AF92-5A210E3C781A
   Total Size:               931.4 Gi (1000069726208 B) (1953261184 512-byte blocks)
   Free Space:               0.0 B (0 B) (0 512-byte blocks)
   Read Only:                No
   Ejectable:                Yes
   Whole:                    No
   Internal:                 No
Disk Utility Info on 1TB Music Drive.
Name :
1TB Music Drive
Type :
Volume
Disk Identifier :
disk4s10
Mount Point :
Not mounted
File System :
Mac OS Extended (Journaled)
Connection Bus :
FireWire
Device Tree :
IODeviceTree:fwx/node@90a9c5c29aa50b/sbp-2@c000
Writable :
Yes
Universal Unique Identifier :
61A8EAFF-E1C9-3605-AF92-5A210E3C781A
Capacity :
931.4 GB (1,000,069,726,208 Bytes)
Owners Enabled :
No
Can Turn Owners Off :
Yes
Can Be Formatted :
Yes
Bootable :
Yes
Supports Journaling :
Yes
Journaled :
No
Disk Number :
4
Partition Number :
10
I've read that WD uses crappy chipsets in their external drives. I'm wondering if the chipset is suspect here? Just not sure. I did discover that I can clone the drive from my PC as an exact Mac OS Extended (Journaled) drive, and my Mac doesn't even know the difference. I've also read that I can initialize the drive, and reinsert the drivers, and the drive should function normally. Interesting, huh? Well, let me know what you come up with BDAqua. And again, many, many thanks.

External drives won't sleep properly

Similar Messages

Maybe you are looking for