USB disk won't spin down

I tried asking this in the iMac forum, but as it seems to be a software issue, I hope you don't mind me posting it here:
I have a new iMac and a Lacie Blade Runner external 4TB USB 3.0 drive.  Unfortunately when I power off the Mac, the Lacie keeps spinning and will not power down - very annoying.
Here's the strange thing though.   When connected to my Mac Mini, the drive does power down properly when I shut the Mini down.  (Both Macs are on 10.8.4).  Also, when I power the iMac down in Bootcamp, the drive also spins down properly.  So it does not appear to be a hardware issue.
I have "put the drives to sleep" (or whatever it is called) checked, btw.
Also, the disk will spin down if I put the iMac to sleep.  It's only when I shutdown the iMac fully that the Lacie drive keeps spinning forever.
Any ideas how to get the external drive to power off properly when I shut down?

Is bumping allowed ;-)
Come on chaps - does no-one have any ideas?  My drive is unusable if I have to keep turning it on and off all the time!  How do I get an external USB drive to power off when I switch off my iMac?  Surely there's something I can check?
My Mac Mini shuts it down just fine, but the iMac won't.  Both on 10.8.4.
Any ideas?

Similar Messages

  • In Yosemite: External Hard Drives Won't Spin Down

    Since installing Yosemite, my external (and perhaps internal) drives won't spin down in energy saver mode: 'Put hard drives to sleep when possible.' I'm using Seagate Barracuda 2TB internal drives in external Voyager Q drive bays. They seem to be getting a little too warm, I can also feel them spinning.
    Thanks!
    Steve

    Thanks for those diagnostics & remedies. Those are good to know. Performed all of them but the problem persisted. I tried swapping out different drives and discovered that it was one particular Seagate drive that wasn't spinning down. So that was the culprit. Going to check out the Seagate discussions here or on Seagate and see what can be done, probably nothing.
    Thanks much!
    Steve

  • USB3.0 enclosure won't spin down when ejected or when Mac sleeps

    Hi,
    I just purchased two different USB3.0 2.5'' SATA enclosures to replace USB2.0 enclosures that I currently use.
    In both cases, the drive I have inserted has refused to spin down when the drive was ejected, or when the Mac it was attached to went to sleep.  I have never had this issue with USB2.0, FireWire400, FireWire800 or eSATA drives attached to these Macs.
    I've used the USB3.0 enclosures on two different Macs, one a Mac Pro, the other a MacBook Pro.  One runs Mountain Lion, the other Mavericks.  Both only have USB2.0 ports.*
    Is this a noted bug with USB3.0 drives being used on USB2.0 ports?  I can't find any evidence that it is.
    Comments on this would be welcomed, because otherwise I can see myself trawling through Amazon's range of USB3.0 enclosures until I find one that works properly - probably the most expensive
    * The Mac Pro will shortly have a PCIe USB3.0 card, hence the enclosures, but this won't help matters on my MBP.

    Received the PCIe USB 3.0 card today and was able to test the enclosures with it.  In this case, the drive still fails to spin down when ejected.  So, it's not a USB 2.0/3.0 incompatibility.  The manufacturer advised a firmware update on the enclosure, but this didn't fix the issue.
    The enclosure did spin down when the USB 3.0-equipped Mac slept, but when I woke the Mac it re-mounted a previously unmounted volume on the device, so I suspect this was more a case of the PCIe card simply entirely losing connection with the drive on sleep, and re-recognising if on wake.  This tallies with information I've read regarding the odd and unpredictable performance of USB 3.0 on older Macs.

  • Z77A-GD65 - Secondary HDD won't spin down when set to AHCI mode

    Hi, I have an issue with my secondary WD 1TB Caviar Blue drive which is used for Game installations, movies and music.
    For some reason, when the Intel SATA controller is set to AHCI, no matter what's set in the Power Options under "Turn off hard disk after", it never spins down, it doesn't seem to affect it. I have absolutely made sure that no apps or processes are running from it. It only contains Games, Movies and Music.
    I have even tried leaving the computer on overnight and accessed the disk on the morning and there is no spin up sound.
    My board is an MSI Z77A-GD65, my friend, who has the exact same board and the exact dame drive as me doesn't experience this issue, on his computer, after inactivity, you access the drive and you can hear it spin up.
    I moved the HDD to the external Asmedia SATA controller on the board and set it to IDE and it works perfectly.
    So now there are several questions:
    1. Why won't it spin down when set to AHCI mode?
    2. Is it critical for a mechanical HDD to be set to AHCI if it mostly contains music, movies and game installations? Will I lose out on a lot of sped if I set it IDE?
    Thanks

    Quote from: RemusM on 12-November-13, 22:13:36
    The spinners (mechanical HDDs) don't even reach the SATA II bandwidth.
    Not even close.
    On the other hand, AHCI does not improve the performances on them.
    So if you really need AHCI, use a SATA II port and see how it goes.
    If that doesn't help, remove any overclocking (load the BIOS default settings) and reinstall the Intel RST driver
    (for SATA RAID and AHCI mode):
    http://www.msi.com/product/mb/Z77A-GD65.html#/?div=Driver&os=Win7%2064
    Then... why HDD's SATA 3.0 are manufactured? 
    I'm having a similiar issue. When I try to set ahci on the Asmedia controller (I've got a WD 1TB 3,0 connected to) my system does not boot up. I can only see a black screen.
    Just saying that the WD HDD is only for data, music, etc. There isn't any SO running on it.

  • USB disk won't mount on startup (have tried everything)

    Hi!
    I'm having big problems getting my USB disk to mount on startup.:(
    It used to work perfectly by having 'mount /dev/sdc1 /media/disk' in rc.local (and umount in local.shutdown) but recently it started saying that 'filesystem type must be defined' (or something like that). So I changed the line to 'mount -t ext3 /dev/sdc1 /media/disk' but now I get a message that '/dev/sdc1 does not exist'.
    So I decided to get this fixed in fstab once and for all.
    I checked the designations of the disks with 'fdisk -l' and noticed that the USB disk would alternate between /dev/sdc, /dev/sde and /dev/sdd quite random on every reboot. In other words I couldn't mount it in fstab by using one of those paths cause I'd get the same problem with '/dev/sdc or -e or -d does not exist'. I figured the sollution must be to mount the disk by using UUID. I checked the uuid's and got the following (as you can see the USB disk is on this reboot registered as '/dev/sde'):
    bash-3.2$ ls -l /dev/disk/by-uuid/
    total 0
    lrwxrwxrwx 1 root root 10 2009-02-07 11:56 6cf5e803-429a-44c3-bcf9-0f007df623f3 -> ../../sda1
    lrwxrwxrwx 1 root root 10 2009-02-07 11:56 8ef6be20-ee30-4a00-8946-56a4d94a7245 -> ../../sda3
    lrwxrwxrwx 1 root root 10 2009-02-07 11:56 947b3b86-8501-4011-9da2-4de45eb4ed60 -> ../../sda2
    lrwxrwxrwx 1 root root 10 2009-02-07 11:56 94911fb3-def7-4440-b6a5-5e09f91b19f6 -> ../../sde1
    lrwxrwxrwx 1 root root 10 2009-02-07 11:56 acd197d3-f63e-48f9-88de-41eff1b3b425 -> ../../sda4
    lrwxrwxrwx 1 root root 10 2009-02-07 11:56 b6745703-bde6-44ef-865d-d09501ecc8ab -> ../../sdb1
    I other words the UUID of the disk should be '94911fb3-def7-4440-b6a5-5e09f91b19f6' so I added that to the fstab file, but I still get the same error that the disk doesn't exist. How is this possible? Isn't the UUID supposed to be the same no matter what? When the disk is clearly labeled with this UUID every time I check it why can't it be used in fstab??
    Here's my fstab (I've commented out the lines that I've been trying out):
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs defaults 0 0
    /dev/cdrom /mnt/cdrom iso9660 ro,user,noauto,unhide 0 0
    /dev/dvd /mnt/dvd udf ro,user,noauto,unhide 0 0
    /dev/sda1 /boot ext2 defaults 0 1
    /dev/sda2 / ext3 defaults 0 1
    /dev/sda3 /var reiserfs defaults 0 1
    /dev/sda4 /home ext3 defaults 0 1
    /dev/sdb1 /extra ext3 defaults 0 1
    #/dev/sdc1 /media/disk defaults 0 0
    #UUID=94911fb3-def7-4440-b6a5-5e09f91b19f6 /media/disk defaults 0 0
    What am I doing wrong here? I've also tried to use different options like 'rw,auto,exec' but it won't work.

    It seems I'm able to mount the disk from the terminal by doing '# sudo mount UUID=94911fb3-def7-4440-b6a5-5e09f91b19f6 /media/disk'.
    But this only works when I do it manually. Adding 'mount UUID=94911fb3-def7-4440-b6a5-5e09f91b19f6 /media/disk' to rc.local only gives the error that filesystem must be defined and when it's defined I get the error that device is not found.
    How can it work manually, but not in fstab or rc.local?
    Here's my dmesg:
    BIOS EBDA/lowmem at: 0009f800/0009f400
    Linux version 2.6.28-ARCH (root@T-POWA-LX) (gcc version 4.3.3 (GCC) ) #1 SMP PREEMPT Mon Feb 2 22:22:59 UTC 2009
    KERNEL supported cpus:
    Intel GenuineIntel
    AMD AuthenticAMD
    NSC Geode by NSC
    Cyrix CyrixInstead
    Centaur CentaurHauls
    Transmeta GenuineTMx86
    Transmeta TransmetaCPU
    UMC UMC UMC UMC
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
    BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000007fef0000 (usable)
    BIOS-e820: 000000007fef0000 - 000000007fef3000 (ACPI NVS)
    BIOS-e820: 000000007fef3000 - 000000007ff00000 (ACPI data)
    BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
    BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
    DMI 2.4 present.
    Phoenix BIOS detected: BIOS may corrupt low RAM, working it around.
    last_pfn = 0x7fef0 max_arch_pfn = 0x100000
    x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Scanning 0 areas for low memory corruption
    modified physical RAM map:
    modified: 0000000000000000 - 0000000000010000 (reserved)
    modified: 0000000000010000 - 000000000009f400 (usable)
    modified: 000000000009f400 - 00000000000a0000 (reserved)
    modified: 00000000000f0000 - 0000000000100000 (reserved)
    modified: 0000000000100000 - 000000007fef0000 (usable)
    modified: 000000007fef0000 - 000000007fef3000 (ACPI NVS)
    modified: 000000007fef3000 - 000000007ff00000 (ACPI data)
    modified: 00000000e0000000 - 00000000f0000000 (reserved)
    modified: 00000000fec00000 - 0000000100000000 (reserved)
    kernel direct mapping tables up to 377fe000 @ 10000-16000
    RAMDISK: 7fe0e000 - 7fedf2e4
    Allocated new RAMDISK: 0055f000 - 006302e4
    Move RAMDISK from 000000007fe0e000 - 000000007fedf2e3 to 0055f000 - 006302e3
    ACPI: RSDP 000F8600, 0014 (r0 HP-CPC)
    ACPI: RSDT 7FEF3040, 0038 (r1 HP-CPC AWRDACPI 42302E31 AWRD 0)
    ACPI: FACP 7FEF30C0, 0084 (r2 HP-CPC AWRDACPI 42302E31 AWRD 0)
    ACPI: DSDT 7FEF31C0, 3C55 (r1 HP-CPC AWRDACPI 1000 MSFT 100000E)
    ACPI: FACS 7FEF0000, 0040
    ACPI: SSDT 7FEF6F40, 01CA (r1 HP-CPC POWERNOW 1 LTP 1)
    ACPI: SRAT 7FEF7180, 00A0 (r1 HP-CPC HAMMER 1 AMD 1)
    ACPI: MCFG 7FEF7280, 003C (r1 HP-CPC AWRDACPI 42302E31 AWRD 0)
    ACPI: APIC 7FEF6E80, 0068 (r1 HP-CPC AWRDACPI 42302E31 AWRD 0)
    ACPI: Local APIC address 0xfee00000
    1158MB HIGHMEM available.
    887MB LOWMEM available.
    mapped low ram: 0 - 377fe000
    low ram: 00000000 - 377fe000
    bootmap 00012000 - 00018f00
    (9 early reservations) ==> bootmem [0000000000 - 00377fe000]
    #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
    #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
    #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
    #3 [0000100000 - 000055b520] TEXT DATA BSS ==> [0000100000 - 000055b520]
    #4 [000055c000 - 000055f000] INIT_PG_TABLE ==> [000055c000 - 000055f000]
    #5 [000009f400 - 0000100000] BIOS reserved ==> [000009f400 - 0000100000]
    #6 [0000010000 - 0000012000] PGTABLE ==> [0000010000 - 0000012000]
    #7 [000055f000 - 00006302e4] NEW RAMDISK ==> [000055f000 - 00006302e4]
    #8 [0000012000 - 0000019000] BOOTMAP ==> [0000012000 - 0000019000]
    found SMP MP-table at [c00f46e0] 000f46e0
    Zone PFN ranges:
    DMA 0x00000010 -> 0x00001000
    Normal 0x00001000 -> 0x000377fe
    HighMem 0x000377fe -> 0x0007fef0
    Movable zone start PFN for each node
    early_node_map[2] active PFN ranges
    0: 0x00000010 -> 0x0000009f
    0: 0x00000100 -> 0x0007fef0
    On node 0 totalpages: 523903
    free_area_init_node: node 0, pgdat c0406600, node_mem_map c1000200
    DMA zone: 32 pages used for memmap
    DMA zone: 0 pages reserved
    DMA zone: 3951 pages, LIFO batch:0
    Normal zone: 1744 pages used for memmap
    Normal zone: 221486 pages, LIFO batch:31
    HighMem zone: 2318 pages used for memmap
    HighMem zone: 294372 pages, LIFO batch:31
    Movable zone: 0 pages used for memmap
    SB4X0 revision 0x11
    Ignoring ACPI timer override.
    If you got timer trouble try acpi_use_timer_override
    ACPI: PM-Timer IO Port: 0x4008
    ACPI: Local APIC address 0xfee00000
    ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
    ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23
    ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    ACPI: BIOS IRQ0 pin2 override ignored.
    ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 21 low level)
    Enabling APIC mode: Flat. Using 1 I/O APICs
    Using ACPI (MADT) for SMP configuration information
    SMP: Allowing 2 CPUs, 0 hotplug CPUs
    PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
    PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
    Allocating PCI resources starting at 80000000 (gap: 7ff00000:60100000)
    PERCPU: Allocating 36864 bytes of per cpu data
    NR_CPUS: 16, nr_cpu_ids: 2, nr_node_ids 1
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 519809
    Kernel command line: root=/dev/sda2 ro quiet
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Initializing CPU#0
    PID hash table entries: 4096 (order: 12, 16384 bytes)
    Fast TSC calibration using PIT
    Detected 2188.552 MHz processor.
    Console: colour VGA+ 80x25
    console [tty0] enabled
    Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Scanning for low memory corruption every 60 seconds
    Memory: 2072040k/2096064k available (2227k kernel code, 22632k reserved, 1026k data, 332k init, 1186760k highmem)
    virtual kernel memory layout:
    fixmap : 0xffee8000 - 0xfffff000 (1116 kB)
    pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
    lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
    .init : 0xc0433000 - 0xc0486000 ( 332 kB)
    .data : 0xc032cfd9 - 0xc042db5c (1026 kB)
    .text : 0xc0100000 - 0xc032cfd9 (2227 kB)
    Checking if this processor honours the WP bit even in supervisor mode...Ok.
    SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    Calibrating delay loop (skipped), value calculated using timer frequency.. 4378.48 BogoMIPS (lpj=7295173)
    Security Framework initialized
    Mount-cache hash table entries: 512
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 512K (64 bytes/line)
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 0
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    Checking 'hlt' instruction... OK.
    ACPI: Core revision 20080926
    ACPI: Checking initramfs for custom DSDT
    ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1
    CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping 01
    Booting processor 1 APIC 0x1 ip 0x6000
    Initializing CPU#1
    Calibrating delay using timer specific routine.. 4379.66 BogoMIPS (lpj=7295468)
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 512K (64 bytes/line)
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 1
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#1.
    x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
    CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ stepping 01
    Brought up 2 CPUs
    Total of 2 processors activated (8757.15 BogoMIPS).
    net_namespace: 768 bytes
    Booting paravirtualized kernel on bare hardware
    NET: Registered protocol family 16
    ACPI: bus type pci registered
    PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
    PCI: MCFG area at e0000000 reserved in E820
    PCI: Using MMCONFIG for extended config space
    PCI: Using configuration type 1 for base access
    ACPI: EC: Look up EC in DSDT
    ACPI: Interpreter enabled
    ACPI: (supports S0 S1 S3 S4 S5)
    ACPI: Using IOAPIC for interrupt routing
    ACPI: No dock devices found.
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    pci 0000:00:00.0: reg 18 io port: [0x4100-0x411f]
    pci 0000:00:00.0: reg 1c 64bit mmio: [0xe0000000-0xffffffff]
    pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:02.0: PME# disabled
    pci 0000:00:12.0: reg 10 io port: [0xfe00-0xfe07]
    pci 0000:00:12.0: reg 14 io port: [0xfd00-0xfd03]
    pci 0000:00:12.0: reg 18 io port: [0xfc00-0xfc07]
    pci 0000:00:12.0: reg 1c io port: [0xfb00-0xfb03]
    pci 0000:00:12.0: reg 20 io port: [0xfa00-0xfa0f]
    pci 0000:00:12.0: reg 24 32bit mmio: [0xfe02f000-0xfe02f1ff]
    pci 0000:00:12.0: reg 30 32bit mmio: [0x000000-0x07ffff]
    pci 0000:00:12.0: supports D1 D2
    pci 0000:00:13.0: reg 10 32bit mmio: [0xfe02e000-0xfe02efff]
    pci 0000:00:13.1: reg 10 32bit mmio: [0xfe02d000-0xfe02dfff]
    pci 0000:00:13.2: reg 10 32bit mmio: [0xfe02c000-0xfe02cfff]
    pci 0000:00:13.2: supports D1 D2
    pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
    pci 0000:00:13.2: PME# disabled
    pci 0000:00:14.0: reg 10 io port: [0x500-0x50f]
    pci 0000:00:14.0: reg 14 32bit mmio: [0xfe02b000-0xfe02b3ff]
    HPET not enabled in BIOS. You might try hpet=force boot option
    pci 0000:00:14.1: reg 10 io port: [0x00-0x07]
    pci 0000:00:14.1: reg 14 io port: [0x00-0x03]
    pci 0000:00:14.1: reg 18 io port: [0x00-0x07]
    pci 0000:00:14.1: reg 1c io port: [0x00-0x03]
    pci 0000:00:14.1: reg 20 io port: [0xf800-0xf80f]
    pci 0000:01:00.0: reg 10 32bit mmio: [0xfa000000-0xfaffffff]
    pci 0000:01:00.0: reg 14 64bit mmio: [0xd0000000-0xdfffffff]
    pci 0000:01:00.0: reg 1c 64bit mmio: [0xfb000000-0xfbffffff]
    pci 0000:01:00.0: reg 24 io port: [0xef00-0xef7f]
    pci 0000:01:00.0: reg 30 32bit mmio: [0x000000-0x01ffff]
    pci 0000:00:02.0: bridge io port: [0xe000-0xefff]
    pci 0000:00:02.0: bridge 32bit mmio: [0xfa000000-0xfcffffff]
    pci 0000:00:02.0: bridge 64bit mmio pref: [0xd0000000-0xdfffffff]
    pci 0000:02:01.0: reg 10 io port: [0xdf00-0xdfff]
    pci 0000:02:01.0: supports D1 D2
    pci 0000:02:03.0: reg 10 io port: [0xde00-0xdeff]
    pci 0000:02:03.0: reg 14 32bit mmio: [0xfdeff000-0xfdeff0ff]
    pci 0000:02:03.0: reg 30 32bit mmio: [0x000000-0x00ffff]
    pci 0000:02:03.0: supports D1 D2
    pci 0000:02:03.0: PME# supported from D1 D2 D3hot D3cold
    pci 0000:02:03.0: PME# disabled
    pci 0000:02:04.0: reg 10 32bit mmio: [0xfdefe000-0xfdefe7ff]
    pci 0000:02:04.0: reg 14 io port: [0xdd00-0xdd7f]
    pci 0000:02:04.0: supports D2
    pci 0000:02:04.0: PME# supported from D2 D3hot D3cold
    pci 0000:02:04.0: PME# disabled
    pci 0000:00:14.4: transparent bridge
    pci 0000:00:14.4: bridge io port: [0xd000-0xdfff]
    pci 0000:00:14.4: bridge 32bit mmio: [0xfde00000-0xfdefffff]
    pci 0000:00:14.4: bridge 32bit mmio pref: [0xfdd00000-0xfddfffff]
    bus 00 -> node 0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P_._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled.
    ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled.
    ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled.
    ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled.
    ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 *10 11)
    ACPI: PCI Interrupt Link [LNKF] (IRQs *3 4 5 6 7 10 11)
    ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 *11)
    ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0, disabled.
    PCI: Using ACPI for IRQ routing
    pci 0000:00:00.0: BAR 3: can't allocate resource
    NetLabel: Initializing
    NetLabel: domain hash size = 128
    NetLabel: protocols = UNLABELED CIPSOv4
    NetLabel: unlabeled traffic allowed by default
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp 00:09: mem resource (0xf0000-0xf3fff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp 00:09: mem resource (0xf4000-0xf7fff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp 00:09: mem resource (0xf8000-0xfbfff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp 00:09: mem resource (0xfc000-0xfffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp 00:09: mem resource (0x0-0x9ffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp 00:09: mem resource (0x100000-0x7feeffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling
    pnp: PnP ACPI: found 10 devices
    ACPI: ACPI bus type pnp unregistered
    system 00:01: ioport range 0x228-0x22f has been reserved
    system 00:01: ioport range 0x40b-0x40b has been reserved
    system 00:01: ioport range 0x4d6-0x4d6 has been reserved
    system 00:01: ioport range 0xc00-0xc01 has been reserved
    system 00:01: ioport range 0xc14-0xc14 has been reserved
    system 00:01: ioport range 0xc50-0xc52 has been reserved
    system 00:01: ioport range 0xc6c-0xc6d has been reserved
    system 00:01: ioport range 0xc6f-0xc6f has been reserved
    system 00:01: ioport range 0xcd4-0xcdf has been reserved
    system 00:01: ioport range 0x4000-0x40fe has been reserved
    system 00:01: ioport range 0x4210-0x4217 has been reserved
    system 00:06: ioport range 0x4d0-0x4d1 has been reserved
    system 00:06: ioport range 0x800-0x87f has been reserved
    system 00:08: iomem range 0xe0000000-0xefffffff has been reserved
    system 00:09: iomem range 0x7ff00000-0x7fffffff has been reserved
    system 00:09: iomem range 0x7fef0000-0x7fefffff could not be reserved
    system 00:09: iomem range 0xffff0000-0xffffffff has been reserved
    system 00:09: iomem range 0xfec00000-0xfec00fff has been reserved
    system 00:09: iomem range 0xfee00000-0xfee00fff has been reserved
    system 00:09: iomem range 0xfff80000-0xfffeffff has been reserved
    pci 0000:00:02.0: PCI bridge, secondary bus 0000:01
    pci 0000:00:02.0: IO window: 0xe000-0xefff
    pci 0000:00:02.0: MEM window: 0xfa000000-0xfcffffff
    pci 0000:00:02.0: PREFETCH window: 0x000000d0000000-0x000000dfffffff
    pci 0000:00:14.4: PCI bridge, secondary bus 0000:02
    pci 0000:00:14.4: IO window: 0xd000-0xdfff
    pci 0000:00:14.4: MEM window: 0xfde00000-0xfdefffff
    pci 0000:00:14.4: PREFETCH window: 0x000000fdd00000-0x000000fddfffff
    pci 0000:00:02.0: setting latency timer to 64
    bus: 00 index 0 io port: [0x00-0xffff]
    bus: 00 index 1 mmio: [0x000000-0xffffffff]
    bus: 01 index 0 io port: [0xe000-0xefff]
    bus: 01 index 1 mmio: [0xfa000000-0xfcffffff]
    bus: 01 index 2 mmio: [0xd0000000-0xdfffffff]
    bus: 01 index 3 mmio: [0x0-0x0]
    bus: 02 index 0 io port: [0xd000-0xdfff]
    bus: 02 index 1 mmio: [0xfde00000-0xfdefffff]
    bus: 02 index 2 mmio: [0xfdd00000-0xfddfffff]
    bus: 02 index 3 io port: [0x00-0xffff]
    bus: 02 index 4 mmio: [0x000000-0xffffffff]
    NET: Registered protocol family 2
    Switched to high resolution mode on CPU 0
    Switched to high resolution mode on CPU 1
    IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
    TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    TCP: Hash tables configured (established 131072 bind 65536)
    TCP reno registered
    NET: Registered protocol family 1
    Unpacking initramfs... done
    Freeing initrd memory: 836k freed
    apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
    apm: disabled - APM is not SMP safe.
    highmem bounce pool size: 64 pages
    VFS: Disk quotas dquot_6.5.1
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    msgmni has been set to 1732
    alg: No test for stdrng (krng)
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    pci 0000:00:00.0: MSI quirk detected; MSI disabled
    pci 0000:01:00.0: Boot video device
    pcieport-driver 0000:00:02.0: setting latency timer to 64
    pcieport-driver 0000:00:02.0: found MSI capability
    pci_express 0000:00:02.0:pcie00: allocate port service
    pci_express 0000:00:02.0:pcie01: allocate port service
    pci_express 0000:00:02.0:pcie03: allocate port service
    aer 0000:00:02.0:pcie01: AER service couldn't init device: no _OSC support
    isapnp: Scanning for PnP cards...
    isapnp: No Plug & Play device found
    Serial: 8250/16550 driver4 ports, IRQ sharing disabled
    input: Macintosh mouse button emulation as /class/input/input0
    PNP: No PS/2 controller found. Probing ports directly.
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    cpuidle: using governor ladder
    cpuidle: using governor menu
    TCP cubic registered
    NET: Registered protocol family 17
    Using IPI No-Shortcut mode
    registered taskstats version 1
    Freeing unused kernel memory: 332k freed
    SCSI subsystem initialized
    libata version 3.00 loaded.
    pata_acpi 0000:00:12.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    pata_acpi 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    scsi0 : pata_atiixp
    scsi1 : pata_atiixp
    ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf800 irq 14
    ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf808 irq 15
    ata2.00: ATAPI: HP DVD Writer 740b, ED24, max UDMA/33
    ata2.00: configured for UDMA/33
    scsi 1:0:0:0: CD-ROM HP DVD Writer 740b ED24 PQ: 0 ANSI: 5
    sata_sil 0000:00:12.0: version 2.3
    scsi2 : sata_sil
    scsi3 : sata_sil
    ata3: SATA max UDMA/100 mmio m512@0xfe02f000 tf 0xfe02f080 irq 22
    ata4: SATA max UDMA/100 mmio m512@0xfe02f000 tf 0xfe02f0c0 irq 22
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata3.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
    ata3.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata3.00: configured for UDMA/100
    ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata4.00: ATA-7: WDC WD2500JS-60MHB1, 10.02E01, max UDMA/100
    ata4.00: 488397168 sectors, multi 16: LBA48
    ata4.00: configured for UDMA/100
    scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
    scsi 3:0:0:0: Direct-Access ATA WDC WD2500JS-60M 10.0 PQ: 0 ANSI: 5
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ehci_hcd 0000:00:13.2: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    ehci_hcd 0000:00:13.2: EHCI Host Controller
    ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:13.2: irq 19, io mem 0xfe02c000
    Driver 'sd' needs updating - please use bus_type methods
    sd 2:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
    sd 2:0:0:0: [sda] Write Protect is off
    sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sd 2:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
    sd 2:0:0:0: [sda] Write Protect is off
    sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sda:<6>ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 8 ports detected
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    ohci_hcd 0000:00:13.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    ohci_hcd 0000:00:13.0: OHCI Host Controller
    ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2
    ohci_hcd 0000:00:13.0: irq 19, io mem 0xfe02e000
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 4 ports detected
    ohci_hcd 0000:00:13.1: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    ohci_hcd 0000:00:13.1: OHCI Host Controller
    ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3
    ohci_hcd 0000:00:13.1: irq 19, io mem 0xfe02d000
    sda1 sda2 sda3 sda4
    sd 2:0:0:0: [sda] Attached SCSI disk
    sd 3:0:0:0: [sdb] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
    sd 3:0:0:0: [sdb] Write Protect is off
    sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sd 3:0:0:0: [sdb] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
    sd 3:0:0:0: [sdb] Write Protect is off
    sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sdb: sdb1
    sd 3:0:0:0: [sdb] Attached SCSI disk
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 4 ports detected
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting. Commit interval 5 seconds
    usb 1-7: new high speed USB device using ehci_hcd and address 5
    usb 1-7: configuration #1 chosen from 1 choice
    rtc_cmos 00:03: RTC can wake from S4
    rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one month, 242 bytes nvram
    usb 2-2: new low speed USB device using ohci_hcd and address 2
    usb 2-2: configuration #1 chosen from 1 choice
    8139too Fast Ethernet driver 0.9.28
    8139too 0000:02:03.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    eth0: RealTek RTL8139 at 0xf8182000, 00:13:d3:88:fb:ec, IRQ 20
    eth0: Identified 8139 chip type 'RTL-8100B/8139D'
    lirc_dev: IR Remote Control driver registered, major 61
    lirc_mceusb2: Philips eHome USB IR Transceiver and Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.44 $
    lirc_mceusb2: Daniel Melander <[email protected]>, Martin Blatter <[email protected]>
    usbcore: registered new interface driver lirc_mceusb2
    usb 3-1: new full speed USB device using ohci_hcd and address 2
    C-Media PCI 0000:02:01.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
    usb 3-1: configuration #1 chosen from 1 choice
    input: Power Button (FF) as /class/input/input1
    usb 3-1: reset full speed USB device using ohci_hcd and address 2
    ACPI: Power Button (FF) [PWRF]
    input: Power Button (CM) as /class/input/input2
    ACPI: Power Button (CM) [PWRB]
    processor ACPI_CPU:00: registered as cooling_device0
    ACPI: Processor [CPU0] (supports 8 throttling states)
    processor ACPI_CPU:01: registered as cooling_device1
    ACPI: Processor [CPU1] (supports 8 throttling states)
    lirc_dev: lirc_register_plugin: sample_rate: 0
    lirc_mceusb2[2]: Philips eHome Infrared Transceiver on usb3:2
    usb 3-2: new low speed USB device using ohci_hcd and address 3
    usb 3-2: configuration #1 chosen from 1 choice
    usb 3-4: new full speed USB device using ohci_hcd and address 4
    usb 3-4: configuration #1 chosen from 1 choice
    Linux agpgart interface v0.103
    usbcore: registered new interface driver hiddev
    scsi 1:0:0:0: Attached scsi generic sg0 type 5
    sd 2:0:0:0: Attached scsi generic sg1 type 0
    sd 3:0:0:0: Attached scsi generic sg2 type 0
    input: Logitech HID compliant keyboard as /class/input/input3
    generic-usb 0003:046D:C30E.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech HID compliant keyboard] on usb-0000:00:13.0-2/input0
    parport_pc 00:07: reported by Plug and Play ACPI
    parport0: PC-style at 0x378, irq 7 [PCSPP,EPP]
    input: Logitech HID compliant keyboard as /class/input/input4
    generic-usb 0003:046D:C30E.0002: input,hidraw1: USB HID v1.10 Device [Logitech HID compliant keyboard] on usb-0000:00:13.0-2/input1
    input: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) as /class/input/input5
    generic-usb 0003:045E:0047.0003: input,hidraw2: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb-0000:00:13.1-2/input0
    usbcore: registered new interface driver usbhid
    usbhid: v2.6:USB HID core driver
    nvidia: module license 'NVIDIA' taints kernel.
    piix4_smbus 0000:00:14.0: SMBus Host Controller at 0x500, revision 0
    Driver 'sr' needs updating - please use bus_type methods
    sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 1:0:0:0: Attached scsi CD-ROM sr0
    input: PC Speaker as /class/input/input6
    Initializing USB Mass Storage driver...
    scsi4 : SCSI emulation for USB Mass Storage devices
    usb-storage: device found at 5
    usb-storage: waiting for device to settle before scanning
    scsi5 : SCSI emulation for USB Mass Storage devices
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    usb-storage: device found at 4
    usb-storage: waiting for device to settle before scanning
    ohci1394 0000:02:04.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
    ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[21] MMIO=[fdefe000-fdefe7ff] Max Packet=[2048] IR/IT contexts=[4/8]
    Error: Driver 'pcspkr' is already registered, aborting...
    lp0: using parport0 (interrupt-driven).
    ppdev: user-space parallel port driver
    nvidia 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    nvidia 0000:01:00.0: setting latency timer to 64
    NVRM: loading NVIDIA UNIX x86 Kernel Module 180.22 Tue Jan 6 09:29:08 PST 2009
    EXT3 FS on sda2, internal journal
    ReiserFS: sda3: found reiserfs format "3.6" with standard journal
    ReiserFS: sda3: using ordered data mode
    ReiserFS: sda3: journal params: device sda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
    ReiserFS: sda3: checking transaction log (sda3)
    ReiserFS: sda3: Using r5 hash to sort names
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on sda4, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on sdb1, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    ieee1394: Host added: ID:BUS[0-00:1023] GUID[0010dc0000bc42b8]
    eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
    scsi 5:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0
    sd 5:0:0:0: [sdc] Attached SCSI removable disk
    sd 5:0:0:0: Attached scsi generic sg3 type 0
    scsi 5:0:0:1: Direct-Access Generic USB CF Reader 1.01 PQ: 0 ANSI: 0
    scsi 4:0:0:0: Direct-Access ST316002 3A 8.01 PQ: 0 ANSI: 0
    sd 5:0:0:1: [sdd] Attached SCSI removable disk
    sd 5:0:0:1: Attached scsi generic sg4 type 0
    scsi 5:0:0:2: Direct-Access Generic USB SM Reader 1.02 PQ: 0 ANSI: 0
    sd 4:0:0:0: [sde] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
    sd 4:0:0:0: [sde] Write Protect is off
    sd 4:0:0:0: [sde] Mode Sense: 03 00 00 00
    sd 4:0:0:0: [sde] Assuming drive cache: write through
    sd 4:0:0:0: [sde] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
    sd 4:0:0:0: [sde] Write Protect is off
    sd 4:0:0:0: [sde] Mode Sense: 03 00 00 00
    sd 4:0:0:0: [sde] Assuming drive cache: write through
    sde: sde1
    sd 4:0:0:0: [sde] Attached SCSI disk
    sd 4:0:0:0: Attached scsi generic sg5 type 0
    usb-storage: device scan complete
    sd 5:0:0:2: [sdf] Attached SCSI removable disk
    sd 5:0:0:2: Attached scsi generic sg6 type 0
    scsi 5:0:0:3: Direct-Access Generic USB MS Reader 1.03 PQ: 0 ANSI: 0
    sd 5:0:0:3: [sdg] Attached SCSI removable disk
    sd 5:0:0:3: Attached scsi generic sg7 type 0
    usb-storage: device scan complete
    NET: Registered protocol family 10
    lo: Disabled Privacy Extensions
    eth0: no IPv6 routers present
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on sde1, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    TCP(wget:15427): Application bug, race in MSG_PEEK.
    TCP(wget:18681): Application bug, race in MSG_PEEK.
    TCP(wget:4122): Application bug, race in MSG_PEEK.
    TCP(wget:4275): Application bug, race in MSG_PEEK.
    TCP(wget:19451): Application bug, race in MSG_PEEK.

  • Thunderbolt Drives won't spin down and sleep in Mountain Lion

    In Lion when I put my iMac to sleep, the external Thunderbolt Drives would spin down and sleep as well. In Mountain Lion, when I put my iMac to sleep, the external Thunderbolt drives do NOT spin down and sleep. Can anyone confirm or duplicate this issue?

    I have the same behavior, however I'm using the TB to FW800 adapter. I have 6 FW800 drives in a chain. All would sleep when MBP was put to sleep under 10.8.5 (ironically fixed after 10.8.4, now broken in 10.9).
    Seeing the same issue with native TB drives makes me think it's a problem with TB software in general.

  • Firewire drives won't spin down when I put iMac to sleep

    I have three external hard drives connected to my iMac in a FW800 daisy chain. It used to be, when I put my iMac to sleep, all three of the external drives would spin down and go quiet. I replaced the drive in the middle of the chain with a new one (both LaCie), and now none of the three external drives spin down when my I sleep my iMac.
    Does anyone know how to get them to spin down?

    It's a known issue for many many brands of FW800 drives.  I've been reporting this to apple for a while.  With 10.9.2, my particular drives will spin down if they are mounted and unmounted but if my system wakes from sleep which will spin up all drives, they stay that way until I mount and unmount again.  So....10.9.2 is a little better but FW is still borked.
    This is the primary reason my Mac Pro is still on Mountain LIon.  My MBA is on mavericks.  A note of caution...Mavericks writes to the NVRAM, sometimes when dual booting it is good to clear that memory.

  • HD won't spin down automatically

    IMac DV+ "450" ruby red. Panther 10.39 - no extra software installed. Firmware update done as recommended. Original HD still inside.
    Replaced CD drive with DVD drive >> set HD to slave.
    Problem now: Energy saver will not spin down HD although checkbox is checked. Is this normal (in my configuration since HD is on Slave)?
    Thanks, Martin

    I'm confused now, Martin. Your original post said that this was an "iMac DV+ "450" ruby red"
    All of the 450's (they came in Ruby, Sage and Indigo ) had a DV drive fitted as standard. As you say, the 400's didn't.
    Can you spin the drive down manually, using the sleep command under the Apple menu?
    The slave issue could be involved, but, as I said, this was a very common problem with the Summer 2000's anyway. (I suffered it myself)
    David, I must have dealt with hundreds of queries about exactly this issue with the Summer 2000 iMacs here over the years (though I don't look in here as often as I used to). I promise you, at least with the drives originally fitted, the very common problem of spin down failure of the drives in this model was directly asociated with increased bearing whine and wear over time. The hard drives factually fitted to these machines were generally a "LC" (low cost) model, with a reduced warrantee period.
    Of course, as you say, if a new drive is fitted this may not be as big an issue.
    Cheers
    Rod

  • 7.2.1 - AirDisk won't spin down under Tiger?

    It seems that when the airdisk is mounted under my Tiger machine using AEBSn firmware 7.2.1, it does not spin down. However, when I unmount it, it eventually spins down. On my Leopard machine, even with it still mounted, it eventually spins down.
    Any ideas? Thanks.

    Just confirmed again. My leopard macbook with the airdisk mounted will still allow it to spin down. however, with my tiger machine mounting the airdisk, it NEVER spins down, even when i'm away from the computer, unless i unmount it in tiger.
    is this a known issue in 7.2.1 when drives are mounted under tiger? if so, i'll try 7.1.1 again. thanks.

  • Cool'n'Quiet under Linux: Fan won't spin down

    Hi,
    first off my configuration:
    MSI K8T Neo
    Athlon 64 3000+ (Newcastle) with packaged AMD fan
    Linux 2.6.8-gentoo-r3 (Gentoo)
    The powernow-k8 module works for me and I am able to clock the cpu to 1000 MHz. The problem is that the fan won't slow down, or at least not as far as under Windows. Under Windows I usually have around 3000 or less rpm, under Linux it's *at least* 4000 (and I hear the difference). Are there any BIOS settings I need to change so that the fan slows down? Or is it even possible under Linux? The temperature is 32 C right now which is quite low, so the fan should slow down.
    Thanks in advance.

    guys, how is fan speed regulated? apply a certain voltage depending on the temperature of the CPU. how so? how does it know how hot your cpu can get / how hot it is supposed to get (because it differs alot as far as i know)
       i think the ansewr to this question will help the fan speed problem.
    Quote
    Point 2: Idling at 1000Mhz with C'n'Q enabled in core center the fan speed oscillates between 2860 & 3180 while the CPU temp stays pretty constant at 45C, case temp is 31C.
    the temperature sensor (in my case at least) gets rather large jumps when my proc goes from 990mhz to 2.2k. could it just be that the fan speed is changing accordingly? just the act of right clicking system to check properties moves it to 1.75ghz for a second.
    edit: one more thing, try running prime95 with fan at 2k rpm and 3k rpm. Perhaps the temps dont change because you have enough airflow w/ both settings to take away the heat from 1000mhz, whereas if it was getting hotter the fan speed would affect temps? (like you said) BUT, in response to "So why on earth is core center trying to drive the fan at top revs when obviously minimum revs idoes just as good a job (and is much quieter!)???" the thing is, the computer doesent test a low rpm and realize that its doing the same job, its just programmed to run w/ certain variables =P ie, set variables. it doesent get to reason it out and feel it is obvious that the same rpms are cooling it to 45c =P
    unless its programmed to do that. . .  

  • HD won't spin down in combo SSD + HD 2007 MBP

    I installed an SSD in my optical drive bay in a late 2007 MBP hoping to improve performance, reduce the noise of the HD spinning and increase battery life with virtually no HD activity.
    I set the system to boot from the SSD but the HD is always still annoyingly spinning. Set option to have HD spin no when no activity, of which there should be none (that I am aware of).
    Any ideas on why this might be happening?

    I'm confused now, Martin. Your original post said that this was an "iMac DV+ "450" ruby red"
    All of the 450's (they came in Ruby, Sage and Indigo ) had a DV drive fitted as standard. As you say, the 400's didn't.
    Can you spin the drive down manually, using the sleep command under the Apple menu?
    The slave issue could be involved, but, as I said, this was a very common problem with the Summer 2000's anyway. (I suffered it myself)
    David, I must have dealt with hundreds of queries about exactly this issue with the Summer 2000 iMacs here over the years (though I don't look in here as often as I used to). I promise you, at least with the drives originally fitted, the very common problem of spin down failure of the drives in this model was directly asociated with increased bearing whine and wear over time. The hard drives factually fitted to these machines were generally a "LC" (low cost) model, with a reduced warrantee period.
    Of course, as you say, if a new drive is fitted this may not be as big an issue.
    Cheers
    Rod

  • HDD won't spin down or power off

    Hi,
    I'm working on my new MacBook Pro i7 with a 500GB 7200rpm HDD for a week now and noticed that altough the screen goes to sleep the hdd doesn't.
    I've double checked and reset the energy settings. I've even deleted the plist files for it. I've also repaired disk permissions.
    Still the slight humming is audible and I can even feel the vibration of the drive (which I learned is normal on the unibody MBPs) long after the screen went black.
    Besides being a little noisy it also eats lots of battery power and that's a real problem in combination with the almost constant use of the nvidia gfx chips.
    To me it seems like a faulty firmware or maybe some setting on the hdd for energy saving or performance.
    Firmware Version is: 0008APM2
    Is someone else having these problems?
    Has anyone found a solution for this?
    -thomas

    Sounds like the sleep problem that we're all having with the 2010 MacBook Pro's...
    http://discussions.apple.com/thread.jspa?threadID=2416586&tstart=15

  • AEBS prevents my USB drive from spinning down

    Hi all,
    I thought I would share my concerns about connecting USB external drive with AirPort Extreme. I've seen several post here talking about that issue, but they didn't solve my problem.
    Otherwise great product, AirPort Extreme n prevents my WD MyBook 500GB disk from spinning down when not in use. I bought that particular disc, because of its ability to go to sleep when not accessed for a period of time. It works great when connected to my MacBook via FW400 or USB 2.0, but when I use it via AiPort Disk utility and connect to AEBS the disk will not spin down, keep running and getting hot. I am concerned with that fact, because it consumes more energy and will shorten disc life (yes, it is not a server graded disc, as most of USB ones, and it was not designed to spin continously).
    I read some posts about Spotlight indexing the drive, but that is not true because of three facts:
    - when connected via USB 2.0 or FW400 the disc spins down.
    - when I left it for two hours it was still spinning - Spotlight should have finished indexing by then right?
    - even if I eject network drives from the Desktop, breaking the connection with my MB it is still spinning.
    There seems to be a problem with AE itself. AEBS seem to keep the disc busy all the time or the disc thinks that's the situation.
    From what I've read this is not MyBook only case. People with Lacie, Maxtor and other brands are having the same problem.
    At this point I have no solution to this. I disconnected the drive and access it via FW400 only. That's a shame, because Apple advertises AirPort Extreme using USB drive connectivity as a major selling point. I think that situation is unacceptable. A disc spinning 24/7 is asking for trouble.
    If someone has a solution to that problem, please share it with the forum readers, if not we will have to wait for Apple to fix this. I hope someone from Apple is reading this.
    MacBook C2D   Mac OS X (10.4.9)  

    Otherwise great product, AirPort Extreme n prevents
    my WD MyBook 500GB disk from spinning down when not
    in use. I bought that particular disc, because of its
    ability to go to sleep when not accessed for a period
    of time.
    Other posts indicate you can solve this by privatizing the drive in Spotlight's preferences. I haven't tried this because I like the drive indexed--it is a shared data drive after all.
    I turn the drive off manually when I'm not using it. Unfortunately, the Airport doesn't recognize the drive (or printers that I've turned off, for that matter) when I turn it back on. The only solution I've found is to restart the Airport. Any ideas on this problem?

  • Second disk (HDD) spins down occasionally, ignoring energy setting.

    I've UNCHECKED the setting "Put the hard disk(s) to sleep when possible" because I find no value in this. Yet my second disk (HDD) occasionally spins down when the computer is left idle for a while. (My first disk is an SSD). It's all apple-made, no custom or user changes inside. It's not a big deal, but I know spinning down and up again adds wear to the disk and it's something I'd rather not have the disk doing. It's ignoring the setting, why is this? and can I do something about it?

    I was affraid that would be the case, blah! Well it's an HDD so I can hear it click when it spins down and back up. It's mostly just happening when the computer is idle for a long time but it's still a wasteful act because it usually spins right back up again after a while and it SEEMS this time around it won't wait equally long before it spins down again but does so relatively quickly again as if the drive figured something minor just happened and that it can just go "back to sleep" when it's done, which on it's turn adds to the wear if I'd leave it like this for hours on since SOME activity is always present from time to time on any disk.

  • FCP 5 and Tiger = do I need any utility to not spin-down my LaCie disks?

    Before Tiger, I had a small utility that prevented my FW-disks not to spin down.
    I run FCP 5, DVDSP4, SoundTrack Pro and some other apps on an iBook G4 and an G4 Dual.
    After blowing the iBook disk, I have installed Tiger, and after each app install, I repair the disk permissions. Also after every software upgrade I repair the permission. Should I think of anything else to get a fresh clean system to start working in?
    TIA

    To force your drives to never sleep:
    Launch the Terminal application (Applications>Utilities>Terminal) and type:
    sudo pmset spindown x
    type your password when it asks for it.
    x=the number of minutes that you want till your drive spins down.
    0 = never
    More info on using pmset here:
    http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/pmset.1. html
    And I found this here
    http://www.thexlab.com/faqs/sbbod.html
    I hope that this helps.
    And note that this is a more 'controlled' way of putting the hard disk to sleep than is possible in >system preferences>energy saver>sleep>
    If you go that way, checked means 10 minutes and unchecked means 180 minutes (not never).
    Good luck.
    x

Maybe you are looking for