Hi there,
I just install a Lite-On iHBS212 BlueRay Drive. The drive replaced the original SuperDrive and was installed using the Upper SATA connector. The unit works fine for a while but after awhile the unit turns-off completely. The eject key doesn't work, The System Profiler doesn't show anything on the SATA port. The Disk Utility doesn't show up the disc inserted.
Is anyone experience this before?
It looks like the OS is turning the HDDs to save energy and for some reason this unit doesn't get back...
To turn on the drive I need to reboot the machine.
If the drive is in use, this will not happen until get's in idle mode after use.
Any help will be really appreciated.
My Machine is a MacPro 2011 6x2 Core @ 2.93HGz. It has all the HDD bays used. All DIM memories are used too (32GB ram), The secondary Front SATA is used with a SDD too. Most of the time, this machine is operating a full CPU capacity (24 hyperthreads) I'm mentioning this because it may be possible that is a power supply problem (although this is the only unit that behaves in this way)
Thanks in advance
I just install a Lite-On iHBS212 BlueRay Drive. The drive replaced the original SuperDrive and was installed using the Upper SATA connector. The unit works fine for a while but after awhile the unit turns-off completely. The eject key doesn't work, The System Profiler doesn't show anything on the SATA port. The Disk Utility doesn't show up the disc inserted.
Is anyone experience this before?
It looks like the OS is turning the HDDs to save energy and for some reason this unit doesn't get back...
To turn on the drive I need to reboot the machine.
If the drive is in use, this will not happen until get's in idle mode after use.
Any help will be really appreciated.
My Machine is a MacPro 2011 6x2 Core @ 2.93HGz. It has all the HDD bays used. All DIM memories are used too (32GB ram), The secondary Front SATA is used with a SDD too. Most of the time, this machine is operating a full CPU capacity (24 hyperthreads) I'm mentioning this because it may be possible that is a power supply problem (although this is the only unit that behaves in this way)
Thanks in advance