Usb3 errors on new mac mini (late 2014)

Hello to Everyone,
i have the following problem:
USB3 Devices does not work on my new MacMini (Late 2014).
I tried different USB3 Devices/Adapters with SSD/SATA Drives Connected and they are recognized by the system,
but when trying to access them, they just hang, or the MacMini reboots randomly when accessing usb3 devices !
This happens with Yosemita and Win8.1 either.
Connecting the SSD/SATA Drives with USB2 Adapters, works fine.
Connecting the same USB3 Adapters to another Computer with USB3 (like MacMini 2013) everything works fine, too.
Anyone has an idea or the same problem ?
Hopefully Apple releases an Bios update soon.
regards,
Stefan

Reset the SMC and PRAM
Intel-based Macs: Resetting the System Management Controller (SMC)
About NVRAM and PRAM
Does it happen in Safe Mode?
OS X: What is Safe Boot, Safe Mode?
\Next after it happens, start up the Mini and then open Console in the Utilities foler and look for USB related log entries and post them here.
You can also call Apple. You get 90 days of free telephone support
Complimentary Support (USA)

Similar Messages

Can I use my old mac mini (G4) as an optical drive with new mac mini late 2014?

Can I use my old mac mini (G4 Tiger) as an optical drive with new mac mini, late 2014?

I think so
DVD or CD sharing: Using Remote Disc - Apple Support
You should also be able to connect the two via FireWire using a FW 400 cable plugged into the old Mini, thne a FR 400 femial to FW 880 adopter plugging into a FW to Thunderbolt adopter
How to use and troubleshoot FireWire target disk mode - Apple Support

Mountain Lion Won't Install on Mac Mini (Late 2014)

My relatively new Mac Mini (Late 2014) is running Yosemite.
I have purchased Mountain Lion in order to run a favoured version of sound editing software which is not compatible with either Yosemite or Mavericks.
Attempts to download my purchased Mountain Lion from the App Store result in the following message "We could not complete your purchase. OSX Mountain Lion is not compatible with this computer".
The 'Learn More' button takes me to the support article which states that Mountain Lion requires hardware of Mac Mini (Early 2009 or newer).
In terms of software, it requires that Lion is already installed.
My query is do I need to purchase Lion and install it before I can install Mountain Lion?
My concern with this is that Lion itself requires Snow Leopard itself installed on the machine!
Cheers,
Lou.

That is correct. Versions of OSX prior to Yosemite do not have the divers to support the 2104 Mac Mini.
You may be able to run ML as a virtual machine (VM) using a VT app like the free VirualBox and paid parallels.
However,you may not be able to get a copy of ML to install unless yo have another Mac that allows you to download the installer.

Mac Mini(Late 2014) - Tick Sound

Hello Apple User's. I just purchased a new Mac Mini late 2014 a month back. I had no problems initially after setting up my mac for the first time. I'm Currently working with Apple as a Technical Support Advisor in level 1. I was doing R&D on my mac and happened to corrupt the OS. Hence did IR and Re-installed the OS.I hear these tick noises only after re-installing OS. Hence I'm pretty sure the OS build which I got by default with mac was the best compatible OS. Now after doing IR I have 10.10.1 with a different build. I'm 100% sure it has to do with the build of my OS. Anyways I'm trying to find a solution for the same. Hence I would suggest all the Apple fans to keep an eye on this section.
Message was edited by: KARTHIK_SPARTA

Well I'm sorry for the late reply. But I'm back with a Solution for the "Tick Sounds" on the Mac's. After researching carefully, I happened to learn that , the Tick noise in SSD HD is because of the Head Parking of the pointer on the HD. Hence in order to get rid of the Tick sound, I would suggest all , to turn off/Disable the option "Put hard disk to sleep whenever possible" in Energy Saver section of System Preferences. Thus when the system is idling or in use (awake), you don't get to hear the Tick Sound's. Well after careful observation for almost a month now, I hardly get to hear the Tick Sound once in a day or so.
In Energy Saver "Put HD to sleep whenever possible" is more useful to portables like, MacBook Pro or MacBook Air , since it will consume less battery, and thus enhance the battery life but not for machines like iMac/Mac Mini.
Also some people have installed some 3rd party utilities like Hard Disk Advanced Power Management (HDAPM) to minimise the head parking or reduce the Tick Sound. I would personally not suggest to go for it, since it will change the default behaviour of the HD set by the manufacturer and may corrupt the HD and it may eventually fail. But if you would really like to give it a try, go for HD SPY utility in Mac Appstore , since Apple would have released the utility after taking due consideration in the Appstore.
And for tbirdvet, thank's for the response. I will have to read more about the mechanism on how the Fusion Drive work's and then take a call on it.
Nevertheless I would appreciate if anyone comes out with a different solution for the Tick Sounds from the HD.

Mac Mini (Late 2014) not recognizing SSD OCZ Vertex 2

Hello community,
After days of tests and readings, I turn to you to seek for advice.
Here is my problem:
I am trying to upgrade a new Mac Mini (Late 2014 model) from it's original mechanical HDD to a Vertex 2 SSD I have been using for a few years with no problems to report, great product.
First 1 cloned my HDD onto the Vertex 2 SSD using SuperDuper, all went well.
I then switched disks and set the SSD in the SATA III slot inside the Mac Mini and reboot... the disk would boot, the recovery system and the disk utility would not see the disk (or it would see it just long enough to try to make a disk verification and then would disappear).
Here is what I have already tried:
- Boot from Linux LiveCD, I can see the Vertex SSD, I can see all it's file and browse them
- Reformat the disk, in HFS+ with GUID partition table
- Clean PRAM
- Perform a Hardware Check - all good
- Boot from the original HDD connected through a SATA-to-USB adapter - all good, i can boot the system, but i don't see the SSD drive (or only for a moment then as soon as i try some action on it (like a disk verification) it stalls and then disappears)
- Try to OCZ toolbox to make a security erase and start fresh. I had here a major issue, the OCZ toolbox would not start, it froze after a lot of complaints a "Scanning for hard disk partitions and creating /etc/fstab" and wouldn't move.
- Dissassembled the Mac Mini, removed the SSD, put it in a Macbook Pro, use OCZ Toolbox on it, this time, it loaded perfectly, identified the disk, i did a firmware update to the latest (1.37) and performed a security erase. All went perfectly. For verificiation I rebooted in recovery mode from the Macbook with the SSD and formatted properly the disk using the Apple Disk Utility (GUIP partition table+ HFS+ partition) and the system neatly identified it as a good host for system install. Then i removed the Vertex 2 SSD from the Macbook pro, put it back in the Mac Mini (reassembled it - god, that's a big pain !) and boot it again in recovery, only to see... nothing, the disk is still not recognized by the system.
Voilà... now I'm out of idea, It could be some low level hardware incompatibility, or anything else, i read about TRIM and Yosemite sometime not behaving well, about SATA II and SATA III compatibility problems, but so far, nothing clear.
I therefore welcome in anticipation your knowledge and hope we can figure this out. For the sake of extending the reach, I will also post this on Anandtech and Apple support forums.

Well, thank you tbirdvet, but the problem was actually an incompatibility at the controller level.
To quote the OCZ support :
The issue is incompatibility between the older SandForce 1222 controller used in the Vertex 2 and the newer Intel Haswell platform used in the Late 2014 Mac Mini. The incompatibility started with the Intel 8 and now 9 series chipsets and spans across all products that used the controller regardless of manufacturer. It is expected behavior to be able to connect the Vertex 2 then clone to it, but if you try and cold boot to it the detection will fail. Unfortunately, the Vertex 2 and the controller it utilized are long EOL and never received a firmware update (if that was even possible) to adjust for the release of these new chipsets.
So I can stop looking around it simply wont boot, ever. Product being End Of Support, no new firmware will ever fix this.
So I guess, i'll have to look another SSD.

Mac Mini Late 2014 crashing nightly

Several nights now my new mac mini (Late 2014), 10.10 has crashed and shutdown. It cold boots with power button press. Logs show it might be trouble with sleep, but posting this since long thread on these troubles with Yosemite is for Mac Mini 2012.
Just got the machine on Friday. Used migration assistant to load settings and maps from Mavericks lap top. Crashed on both tries, but did set up an account. None of my user files transferred, did that manually. Hoping not to do a fresh install, but need to know if settings from Mavericks could cause a problem.
Here is the log leading up to the crash. There are a few wake ups preceding this one (over an hour before) that didn't shutdown.
10/27/14 12:28:21.000 AM kernel[0]: Wake reason: EC.SleepTimer (SleepTimer)
10/27/14 12:28:21.000 AM kernel[0]: Previous sleep cause: 5
10/27/14 12:28:21.000 AM kernel[0]: AppleThunderboltNHIType2::prePCIWake - power up complete - took 315 us
10/27/14 12:28:21.000 AM kernel[0]: IOThunderboltSwitch<0xffffff8034179600>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0
10/27/14 12:28:21.000 AM kernel[0]: TBT W (2): 0x0040 [x]
10/27/14 12:28:21.000 AM kernel[0]: AppleThunderboltGenericHAL::earlyWake - complete - took 188 milliseconds
10/27/14 12:28:21.260 AM sharingd[220]: 00:28:21.259 : SDStatusMonitor::kStatusWirelessPowerChanged
10/27/14 12:28:21.000 AM kernel[0]: en1: BSSID changed to 20:e5:2a:01:6d:d4
10/27/14 12:28:22.000 AM kernel[0]: AirPort: Link Up on awdl0
10/27/14 12:28:22.916 AM hidd[68]: MultitouchHID: device bootloaded
10/27/14 12:28:24.000 AM kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,0301,0de1,0300,c5e1,3c00]
10/27/14 12:28:25.000 AM kernel[0]: Sound assertion in AppleHDAController at line 5480
10/27/14 12:28:25.000 AM kernel[0]: Sound assertion in IOHDACodecDevice at line 145
10/27/14 12:28:25.000 AM kernel[0]: Sound assertion in AppleHDANode at line 291
10/27/14 12:28:25.000 AM kernel[0]: Sound assertion in AppleHDANode at line 320
10/27/14 12:28:25.000 AM kernel[0]: Sound assertion in AppleHDAFunctionGroup at line 919
10/27/14 12:28:26.213 AM discoveryd[48]: AwdlD2d AwdlD2dStartAdvertisingPair: 'chicago' Advertising service started
10/27/14 12:28:26.214 AM discoveryd[48]: AwdlD2d AwdlD2dStartAdvertisingPair: 'chicago' Advertising service started
10/27/14 12:28:26.215 AM discoveryd[48]: AwdlD2d AwdlD2dStartAdvertisingPair: '6928e7efff8bc50a00000000000008efip6arpa' Advertising service started
10/27/14 12:28:26.000 AM kernel[0]: Sound assertion in AppleHDAController at line 5480
10/27/14 12:28:26.000 AM kernel[0]: Sound assertion in IOHDACodecDevice at line 145
10/27/14 12:28:26.000 AM kernel[0]: Sound assertion in AppleHDANode at line 291
10/27/14 12:28:26.000 AM kernel[0]: Sound assertion in AppleHDAFunctionGroup at line 932
10/27/14 12:28:26.000 AM kernel[0]: Sound assertion in AppleHDAWidget at line 3425
10/27/14 12:28:26.000 AM kernel[0]: Sound assertion in AppleHDAPath at line 1154
10/27/14 12:28:26.000 AM kernel[0]: Sound assertion in AppleHDAPathSet at line 1125
10/27/14 12:28:26.000 AM kernel[0]: Sound assertion in AppleHDAEngine at line 15146
10/27/14 12:28:27.000 AM kernel[0]: Sound assertion in AppleHDAController at line 5480
10/27/14 12:28:27.000 AM kernel[0]: Sound assertion in IOHDACodecDevice at line 145
10/27/14 12:28:27.000 AM kernel[0]: Sound assertion in AppleHDANode at line 291
10/27/14 12:28:27.000 AM kernel[0]: Sound assertion in AppleHDAPathSet at line 147
10/27/14 12:28:27.000 AM kernel[0]: Sound assertion in AppleHDAEngine at line 15151
10/27/14 12:28:28.000 AM kernel[0]: Sound assertion in AppleHDAController at line 5480
10/27/14 12:28:28.000 AM kernel[0]: Sound assertion in IOHDACodecDevice at line 145
10/27/14 12:28:28.000 AM kernel[0]: Sound assertion in AppleHDANode at line 291
10/27/14 12:28:28.000 AM kernel[0]: Sound assertion in AppleHDAEngine at line 2092
10/27/14 12:28:28.000 AM kernel[0]: Sound assertion in AppleHDAEngine at line 15034
10/27/14 12:28:28.000 AM kernel[0]: ARPT: 52793.981728: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
10/27/14 12:28:28.000 AM kernel[0]: en1: BSSID changed to 20:e5:2a:01:6d:d4
10/27/14 12:28:28.276 AM sharingd[220]: 00:28:28.276 : SDStatusMonitor::kStatusWirelessPowerChanged
10/27/14 12:28:28.000 AM kernel[0]: en1: BSSID changed to 20:e5:2a:01:6d:d4
10/27/14 12:28:28.293 AM sharingd[220]: 00:28:28.292 : SDStatusMonitor::kStatusWirelessPowerChanged
10/27/14 12:28:29.262 AM ntpd[629]: wake time set +0.185244 s
10/27/14 12:29:06.000 AM kernel[0]: pci pause: SDXC
10/27/14 12:29:08.760 AM spindump[15164]: Saved diag report for powerstats version com.apple.SystemStats.Daily to /Library/Logs/DiagnosticReports/powerstats_2014-10-27-002908_chicago.diag
10/27/14 12:29:15.000 AM kernel[0]: PM response took 2001 ms (26, powerd)
10/27/14 12:29:15.000 AM kernel[0]: ARPT: 52840.994260: AirPort_Brcm43xx::powerChange: System Sleep
10/27/14 12:29:15.000 AM kernel[0]: ARPT: 52840.994264: wl0: powerChange: *** BONJOUR/MDNS OFFLOADS ARE NOT RUNNING.
10/27/14 12:29:15.000 AM kernel[0]: hibernate image path: /var/vm/sleepimage
10/27/14 12:29:15.000 AM kernel[0]: efi pagecount 67
10/27/14 12:29:15.000 AM kernel[0]: hibernate_page_list_setall(preflight 1) start 0xffffff821273d000, 0xffffff8212858000
10/27/14 12:29:16.000 AM kernel[0]: hibernate_page_list_setall time: 708 ms
10/27/14 12:29:16.000 AM kernel[0]: pages 3471929, wire 316524, act 1495248, inact 293202, cleaned 0 spec 12, zf 81367, throt 0, compr 0, xpmapped 0
10/27/14 12:29:16.000 AM kernel[0]: could discard act 328987 inact 546271 purgeable 102010 spec 308308 cleaned 0
10/27/14 12:29:16.000 AM kernel[0]: hibernate_page_list_setall preflight pageCount 316524 est comp 50 setfile 717225984 min 2147483648
10/27/14 12:29:16.000 AM kernel[0]: AppleThunderboltNHIType2::prePCIWake - power up complete - took 193 us
10/27/14 12:29:16.000 AM kernel[0]: AppleThunderboltGenericHAL::earlyWake - complete - took 0 milliseconds
10/27/14 12:29:16.000 AM kernel[0]: [0x1f164c000, 0x19000]
10/27/14 12:29:16.000 AM kernel[0]: [0x11f685000, 0x460000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1f1745000, 0x20000]
10/27/14 12:29:16.000 AM kernel[0]: [0x11fb05000, 0x480000]
10/27/14 12:29:16.000 AM kernel[0]: [0x120005000, 0x200000]
10/27/14 12:29:16.000 AM kernel[0]: [0x11ff85000, 0x20000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1b465000, 0x3a0000]
10/27/14 12:29:16.000 AM kernel[0]: [0x120205000, 0x6c0000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1d3c5000, 0x40000]
10/27/14 12:29:16.000 AM kernel[0]: [0x11ffa5000, 0x20000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1208c5000, 0x100000]
10/27/14 12:29:16.000 AM kernel[0]: [0x120a25000, 0x1200000]
10/27/14 12:29:16.000 AM kernel[0]: [0x121c85000, 0x680000]
10/27/14 12:29:16.000 AM kernel[0]: [0x122385000, 0x3880000]
10/27/14 12:29:16.000 AM kernel[0]: [0x125da5000, 0x80000]
10/27/14 12:29:16.000 AM kernel[0]: [0x125e65000, 0x100000]
10/27/14 12:29:16.000 AM kernel[0]: [0x125fa5000, 0x680000]
10/27/14 12:29:16.000 AM kernel[0]: [0x11eb85000, 0x40000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1f1765000, 0x20000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1209c5000, 0x40000]
10/27/14 12:29:16.000 AM kernel[0]: [0x126625000, 0x480000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1f23e5000, 0x40000]
10/27/14 12:29:16.000 AM kernel[0]: [0x126aa5000, 0x180000]
10/27/14 12:29:16.000 AM kernel[0]: [0x122305000, 0x60000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1f2425000, 0x40000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1176a5000, 0x20000]
10/27/14 12:29:16.000 AM kernel[0]: [0x126c25000, 0x800000]
10/27/14 12:29:16.000 AM kernel[0]: [0x121c25000, 0x40000]
10/27/14 12:29:16.000 AM kernel[0]: [0x150805000, 0x2100000]
10/27/14 12:29:16.000 AM kernel[0]: [0x147d45000, 0x60000]
10/27/14 12:29:16.000 AM kernel[0]: [0x147645000, 0x20000]
10/27/14 12:29:16.000 AM kernel[0]: [0x152905000, 0x5e80000]
10/27/14 12:29:16.000 AM kernel[0]: [0x13c265000, 0x2900000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1412a5000, 0x4000000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1459a5000, 0x1680000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1470e5000, 0x80000]
10/27/14 12:29:16.000 AM kernel[0]: [0x134125000, 0x2900000]
10/27/14 12:29:16.000 AM kernel[0]: [0x136b05000, 0x1800000]
10/27/14 12:29:16.000 AM kernel[0]: [0x138345000, 0x780000]
10/27/14 12:29:16.000 AM kernel[0]: [0x138ae5000, 0x3780000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1295e5000, 0xe80000]
10/27/14 12:29:16.000 AM kernel[0]: [0x12a485000, 0x1980000]
10/27/14 12:29:16.000 AM kernel[0]: [0x12bee5000, 0x4100000]
10/27/14 12:29:16.000 AM kernel[0]: [0x132805000, 0xc00000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1334a5000, 0x100000]
10/27/14 12:29:16.000 AM kernel[0]: [0x1336c5000, 0x200000]
10/27/14 12:29:16.000 AM kernel[0]: [0x133925000, 0x800000]
10/27/14 12:29:16.000 AM kernel[0]: [0x147165000, 0x200000]
10/27/14 12:29:16.000 AM kernel[0]: [0x147445000, 0x80000]
10/27/14 12:29:16.000 AM kernel[0]: [0x147545000, 0x100000]
10/27/14 12:29:16.000 AM kernel[0]: [0x147685000, 0x80000]
10/27/14 12:29:16.000 AM kernel[0]: [0x147765000, 0x80000]
10/27/14 12:29:16.000 AM kernel[0]: [0x147825000, 0x100000]
10/27/14 12:29:16.000 AM kernel[0]: [0x147945000, 0x400000]
10/27/14 12:29:16.000 AM kernel[0]: [0x147de5000, 0x580000]
10/27/14 12:29:16.000 AM kernel[0]: [0x148385000, 0x80000]
10/27/14 12:29:16.000 AM kernel[0]: [0x148445000, 0x1300000]
10/27/14 12:29:16.000 AM kernel[0]: [0x149785000, 0xe80000]
10/27/14 12:29:16.000 AM kernel[0]: [0x14a865000, 0x280000]
10/27/14 12:29:16.000 AM kernel[0]: [0x14ab65000, 0x480000]
10/27/14 12:29:16.000 AM kernel[0]: [0x14b065000, 0x180000]
10/27/14 12:29:16.000 AM kernel[0]: [0x14b265000, 0x180000]
10/27/14 12:29:16.000 AM kernel[0]: [0x14b445000, 0x2180000]
10/27/14 12:29:16.000 AM kernel[0]: [0x14d625000, 0x900000]
10/27/14 12:29:16.000 AM kernel[0]: [0x14df65000, 0x380000]
10/27/14 12:29:16.000 AM kernel[0]: [0x14f105000, 0x1700000]
10/27/14 12:29:16.000 AM kernel[0]: [0x125c05000, 0x40000]
10/27/14 12:29:16.000 AM kernel[0]: [0x127425000, 0x1300000]
10/27/14 12:29:16.000 AM kernel[0]: [0x128845000, 0x80000]
10/27/14 12:29:16.000 AM kernel[0]: [0x128965000, 0xc80000]
10/27/14 12:29:16.000 AM kernel[0]: [0x59df05000, 0xdfe7000]
10/27/14 12:29:16.000 AM kernel[0]: [0x5abeec000, 0x3d019000]
10/27/14 12:29:16.000 AM kernel[0]: [0x158785000, 0x2f80000]
10/27/14 12:29:16.000 AM kernel[0]: [0x14a605000, 0x40000]
10/27/14 12:29:16.000 AM kernel[0]: [0x147725000, 0x20000]
10/27/14 12:29:16.000 AM kernel[0]: [0x45e65000, 0x7000]
10/27/14 12:29:16.000 AM kernel[0]: [0x0, 0x0]
10/27/14 12:29:16.000 AM kernel[0]: kern_open_file_for_direct_io(0) took 6 ms
10/27/14 12:29:16.000 AM kernel[0]: Opened file /var/vm/sleepimage, size 2147483648, partition base 0x0, maxio 2000000 ssd 1
10/27/14 12:29:16.000 AM kernel[0]: hibernate image major 1, minor 0, blocksize 4096, pollers 5
10/27/14 7:48:50.000 AM bootlog[0]: BOOT_TIME 1414421330 0

The warranty entitles you to complimentary phone support for the first 90 days of ownership.
If you bought the product in the U.S. directly from Apple (not from a reseller), you have 14 days from the date of delivery in which to exchange or return it for a refund. In other countries, the return policy may be different. If you bought from a reseller, its return policy applies.

Install Windows 8.1 Pro on Mac Mini Late 2014

I'm trying to install Bootcamp on my Mac Mini. Windows reports that it cannot install or create a partition on the drive after formatting the BOOTCAMP partition as NTFS.
This is my setup:
1. Mac Mini Late 2014 with 2TB Fusion Drive.
2. Windows 8.1 Pro x64 full version ISO downloaded from Microsoft Store.
3. Sandisk Extreme Flash Drive (I have tried both 16GB and 64GB).
4. Bootcamp partition = 500GB.
5. Other USB devices plugged in: Corded USB Mouse and Apple Extended Keyboard (both of which are required to enter the serial number and navigate the installer window).
6. No additional storage devices of any kind are connected aside from the internal Fusion drive and the installer drive.
7. Booting from the EFI portion of the Bootcamp created Windows installer.
I have read that I should try using a USB 2 flash drive rather than a USB 3 flash drive, so I will try that next. I fail to understand how this could make any difference.
If you have any other tips, please let me know.
I have installed or helped other people install bootcamp many times over the course of the past 2 years. Every single time it has caused endless headaches and literally weeks of wasted time.
I have read endless posts on what is causing these problems. I will consider summarising these for anyone else having the same problems. Everyone has their theory so far about this Bootcamp nightmare, but so far there doesn't appear to be any one magic solution.
Apple's inability to address the issue suggests that the problem may be with the Windows installer. Perhaps Microsoft is deliberately causing this?
I suspect the two most likely causes of these issues are the downloaded ISO or the Thumb Drive.
If you have any better idea, please let me know.
On another topic, how to I rename the NTFS partition back to BOOTCAMP? All options to rename this partition are greyed out in Disk Utility...
Cheers,
Paul

Paul@Sydney wrote:
7. Booting from the EFI portion of the Bootcamp created Windows installer.
The FAT32/NTFS partition is usually not adequate for an EFI install. You can delete the BCA-created partition and create a Disk Utility partition which is formatted as Free Space. This will be split into an MSR and MSD. Fusion drives create problems, especially if the BC partition lies outside the traditional MBR 2TB boundary.
Before you delete the BCA-created partition, please post the output of
diskutil list
diskutil cs list
sudo gpt -vv -r show /dev/disk0
sudo gpt -vv -r show /dev/disk1
I have read that I should try using a USB 2 flash drive rather than a USB 3 flash drive, so I will try that next. I fail to understand how this could make any difference.
Windows installers up to W8.1 do not have USB3 drivers. These are installed after Windows is installed and BC drivers are in place.
Apple's inability to address the issue suggests that the problem may be with the Windows installer. Perhaps Microsoft is deliberately causing this?
The requirements are pretty strict when installing Windows. Any deviations cause headaches and grief.
I suspect the two most likely causes of these issues are the downloaded ISO or the Thumb Drive.
The USB is usually the issue.
On another topic, how to I rename the NTFS partition back to BOOTCAMP? All options to rename this partition are greyed out in Disk Utility...
After Windows is fully installed and BC drivers are in place, log into Windows, right click on it and rename it on the Windows side. It cannot be renamed on the OSX side with diskutil renameVolume. Here is an example sequence. You cannot rename volume during the installation process.

Install Bootcamp on Mac Mini late 2014 Yosemite Fails?

Trying to install bootcamp with Win 8.1 pro on a Mac Mini (Late 2014) under Yosemite and get to the screen on Win 8 side which says 'Where do you want to install Windows?' and I choose the "Drive 0 Partition 4: BOOTCAMP" and the next button never becomes enabled.
There is a message saying "Windows can't be installed on drive 0 partition 4" and an addition message box which says "Windows cannot be installed to this hard disk space. Windows must be installed to a partition formatted as NTFS".
At this point I'm dead in the water -- cannot proceed.
Formatting the drive doesnt work and just screws up the whole process.
I've redone this quite a few times and end up in the same situation everytime.
I also tried with Win7 install I had but that failed completely and it never really proceeded after rebooting from Mac side.
Any ideas?
Is bootcamp busted on Yosemite? I dont easily have another machine I can try it on.
Is bootcamp busted on Mac Mini? Has anyone tried bootcamp on new late 2014 Mac Mini?
Thanks
James

Hi Steve
Its not a fusion drive. The full spec is
2.6GHz Dual-Core Intel Core i5 (Turbo Boost up to 3.1GHz)
16GB 1600MHz LPDDR3 SDRAM
1TB Serial ATA Drive @ 5400 rpm
Intel Iris Graphics
I wanted the size of the drive large as I'm going to use it for just a small amount of Mac work and a very large amount of Windows work.
I did actually click format during a number of the attempts I've tried. It generally formatted and left me no better advanced. Generally it would removed the word BOOTCAMP from the drive. I've even tried deleting the partition and reestablishing in -- that doesnt help either.
My latest attempt has seen that the whole bootcamp partitioning structure is truly busted. When I go back to the Mac and enter bootcamp assistant it says I cannot do anything now and tells me the partitions cannot be changed. Now I'm really not in a great position.
James

Performance Issues with Mac Mini (Late 2014)

Dear All,
We have few Mac Minis with below mentioned configuration in our organization.
Mac Mini (Late 2014)
Processor : 1.4GHz dual-core Intel Core i5 (Turbo Boost up to 2.7GHz) with 3MB on-chip shared L3 cache
Storage : 500GB (5400-rpm) hard drive
Memory : 4GB of 1600MHz LPDDR3 memory
Graphics : Intel HD Graphics 5000
Mac OS Version : 10.10.2 Yosemite
We are using these Mac Minis for iOS application development using Xcode, but now we are facing lots of performance related issues. We are sharing issue related details with you & want to get some help to improve our system performance.
1) System is running very slow & take a lot of time to Boot.
2) Some time it never boots & we need to press start button several time.
3) When system goes in Sleep mode, then it takes much time to come to display screen to type Password.
4) Sometimes the whole screen moves Downwards.
5) Sometimes while during coding using Xcode in Simulator it shows some kind of Error “Unexpectedly quit”
6) Xcode runs very slow & it take lots of time in switching between files.
7) While closing any open application it take lots of time & show activity indicator for very long time.
8) Sometimes it doesn’t support iPad when we connect it using USB cable.
Our development team is facing lots of issues using these Mac Minis, so please can anyone suggest us that how can we improve our system performance & is this configuration is ideal to run Mac OSx 10.10 Yosemite Series and to use it for iOS application development.
Please try to help us to solve these issues & try to share some valuable comments on it.
Thanks

Dear woodmeister50,
Here i am sharing required screenshots which you have suggested to share.
1. Open up activity monitor and select CPU. Post the top 5 procersses
and their percentage of CPU usage.
2. Then select Memory. Post the values listed in the box at the bottom
or you can post a screen shot that area.
Please analyze these Activity monitor logs & let us know if you want to share some feedback on that. We will also try to boot & run our system in safe mode.
Thanks

HT202856 Can the Mac Mini (Late 2014) support 4k display @ 60 Hz via the DisplayPort?

Dear Experienced Apple Guru,
Apple made it clear on the Tech Specs for the Mac Mini (Late 2014) that a 4k display can be supported via the HDMI port at 30 Hz. But, can we also be clear how many Hertz the Mac Mini can handle with a 4k display via the Mini DisplayPort (Thunderbolt 2)?
I have a site linked here saying that the DisplayPort 1.2 can handle up to nearly 20 Gbps, thus can handle 4k display at 60 Hz:
"DisplayPort version 1.2 can support video resolutions of up to 3840 x 2160 pixels (4K) at a refresh rate of 60 Hz, and it supports all common 3D video formats. In terms of bandwidth, it can manage 17.28 Gbps. Version 1.3, when it arrives, will support up to 8192 x 4320 (8K) resolution, or two simultaneous 4K streams. It will also double bandwidth to 32.4 Gbps.
Meanwhile, HDMI version 1.4 is the most common at the moment. This supports the same 4K resolution as DisplayPort 1.2, but at just 30 Hz (or 4096 x 2160 at 24 Hz). HDMI 2.0 is new on the scene in a few devices such as this Sony TV. This doubles the refresh rate to 60 Hz as well as increases bandwidth from 10.2- to 18 Gbps."
Thanks,
Trevalyn

That have enabled DP 1.2 on their monitor and used a DP 1.2 cable but still only get 30 Hz at 4K.
The MAC does not support MST

Sleep on the mac mini late 2014 strange behaviour

my system specs are:
Late 2014 mac mini.
16GB Ram
1TB Fusion drive.
Recently I decided to completely reformat my fusion drive and pop a clean copy of yosemite on. All seems well. I have power nap enabled and wake for network access turned off.
Recently my mac has been asleep as normal and waking up for power nap activities which is all normal. I sometimes look at the white led to know its ok as it is pulsing which is good. Last night and the night before that, the while light has been pulsing and then last night I saw that it was off. I was still able to wake the computer but noticed this in the console log:
04/04/2015 02:35:41.000 kernel[0]: WARNING: hibernate_page_list_setall skipped 29380 xpmapped pages
04/04/2015 02:35:41.000 kernel[0]: hibernate_page_list_setall preflight pageCount 265101 est comp 45 setfile 556793856 min 2147483648
04/04/2015 02:35:41.000 kernel[0]: [0x3e6d1000, 0x14000]
04/04/2015 02:35:41.000 kernel[0]: [0x324fe5000, 0x80000]
04/04/2015 02:35:41.000 kernel[0]: [0x506da5000, 0x180000]
04/04/2015 02:35:41.000 kernel[0]: [0x50ffc5000, 0x80000]
04/04/2015 02:35:41.000 kernel[0]: [0x5100a5000, 0x80000]
Then later that night I get this:
04/04/2015 02:35:41.000 kernel[0]: kern_open_file_for_direct_io(0) took 9 ms
04/04/2015 02:35:41.000 kernel[0]: Opened file /var/vm/sleepimage, size 2147483648, partition base 0x0, maxio 2000000 ssd 1
04/04/2015 02:35:41.000 kernel[0]: hibernate image major 1, minor 0, blocksize 4096, pollers 5
04/04/2015 06:35:40.000 kernel[0]: vm_compressor_record_warmup (3737 - 4831)
04/04/2015 06:35:40.000 kernel[0]: vm_compressor_flush - starting
04/04/2015 06:35:40.000 kernel[0]: vm_compressor_flush completed - took 3953 msecs
04/04/2015 06:35:40.000 kernel[0]: hibernate_flush_memory: buffer_cache_gc freed up 10281 wired pages
04/04/2015 06:35:40.000 kernel[0]: hibernate_alloc_pages act 87276, inact 11090, anon 201, throt 0, spec 31706, wire 287721, wireinit 207717
04/04/2015 06:35:40.000 kernel[0]: hibernate_setup(0) took 4531 ms
Normally and correct me if I am wrong power nap would cause the computer to wake every hour?
It doesn't explain why my mac goes into like a deep sleep but I am still able to wake it up. There is no process bar or anything to indicate that it has gone into safe sleep.
I have checked the hardware and there are no problems. Disk permissions there are no errors. everything seems ok?
I was wondering if anyone else with a mac mini late 2014 has or have been having the same problem?
Many thanks

You asked "Normally and correct me if I am wrong power nap would cause the computer to wake every hour?"
During Power Nap normal TM backups still happen so if you have Power Nap and default TM settings, TM will still backup every hour.
Otherwise I have no info on your other problems

Mac mini Late 2014 screen flicking

Just got the Mac mini Late 2014 a week ago. It serves me well except the screen flicks randomly.
I have connected Mac mini to two BenQ monitors, one via mini-display port HDMI adaptor (lets said this is port A), another one via mini-display port to HDMI or HDMI cable directly (tried both) (lets say this is port B or HDMI).
The issue is, screen from port B or HDMI flicks randomly, sometimes 1 or two times within a minute, sometimes even half hour or an hour without issue.
Connection with port A is always good, no flicking, I even switched two monitors, the problem still there, so it shouldn't relate to the monitor.
I also tried different mini-display to HDMI adaptor on port B, also tried different HDMI cable, the problem still exists.
I have no idea what happened here.
Maybe something not related, but I want to mention, When setting up the new Mac mini, I tried to migrate my old account on Macbook Pro (Mavericks) to Mac mini, but It was interrupted, (the user accunt was created, but then I manually migrated some other stuff manually), not sure if this interruption plays a part in this screen flicking issue.
Any idea? Thanks for any helps in advance.

Hi there bluemoonj,
I would recommend taking a look at the video troubleshooting steps found in the article below.
Apple computers: Troubleshooting issues with video on internal or external displays
-Griff W.

Acer K272HUL and Mac Mini (Late 2014)

Was wondering if anybody else has had issues with an Acer K272HUL monitor and a Mac Mini (Late 2014) when using HDMI as the cable connection?
The issues I am having are as follows:
The monitor won't come out of sleep mode when I use either the mouse of the keyboard. Instead I have to toggle the power on the monitor to re-detect the Mac's video source each time.
The brightness buttons on the keyboard have no effect on the monitors brightness. I don't get the OSD like I do when I change the volume.
I'm wondering if HDMI is somehow the factor here? Is it worth getting a Display Port cable?

For #1
Mac mini 2014 won't wake monitor via HDMI
For #2 most non-Apple monitors do respond to the Brightness controls on the KB
Mini display port usually works better than HDMI

HT201541 Mac mini Late 2014 Boot Camp Windows 7 sound issue

Hi,
I'm wondering if anyone can help me with my Mac mini (Late 2014) and Boot Camp (Windows 7). The problem I'm having is that there's no audio when I boot into Windows 7, though everything works fine under OS X. After installing Boot Camp and Windows, the audio worked perfectly up until yesterday, and now there's nothing. I've tried updating as well as uninstalling and reinstalling drivers, but this hasn't helped at all.
When I open Volume Mixer and Playback Devices, the sliders show that audio is playing, but I hear nothing - either from the built-in speaker or when I headphones.
The Device Status indicates that "This device is working properly" and that the drivers are up to date. Tthe following drivers are installed:
dmk.sys
HdAudio.sys
ksthunk.sys
portcls.sys
SysFxUI.dll
WMALFXGFXDSP.dll
Has anyone else encountered this issue, or does anyone have any tips on how I might fix this?

Is the volume Muted? The Mac has an Audio database of devices and volumes in NVRAM, so an SMC Reset or PRAM reset might help. Please see this link for appropriate keys Startup key combinations for Intel-based Macs - Apple Support.

Does mac mini (late 2014) supports dual-band wifi sharing?

Hello,
First of all, i'm not native speaker, so, please excuse my poor english.
I have a mac mini (late 2014) and use the wifi-sharing feature of yosemite.
(Ethernet is connected to Mac mini and other devices such as mac air are connected to Mac mini through wifi)
For wifi-sharing, channel 44 is used, and as i know, it is located on 5Ghz band.
By the way, i plan to buy a sony srs x7 bluetooth speaker which also supports airplay only on 2.4GHz wifi internet.
If i wanna connect that speaker to Mac-mini's hotspot, should i change the wifi-channel of mac-mini to 2.4GHz band? or, can mac mini provides wifi hotspot for both 2.4GHz and 5GHz simultaneously?

Bluetooth is a different network than the wifi network. BT is 2.4 GHz only while wifi cn be 2.4 and/or 5 GHz.
Your BT speakers will work fine using the BT capability of the Mac
Communications
Wi-Fi802.11ac Wi-Fi wireless networking; IEEE 802.11a/g/b/n compatible
BluetoothBluetooth 4.0 wireless technology
Ethernet10/100/1000BASE-T Ethernet (RJ-45 connector)

Usb3 errors on new mac mini (late 2014)

Similar Messages

Maybe you are looking for