Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This script work nicely.

My 8TB WD Red HDD work nicely for years now. But few weeks ago, I moved my Windows SSD from the optical cage to PCIe card, then this "won't mount after warm reboot issue" come back. Even I move the SSD back to the optical cage still nil help.

I tried the pin 3 fix, also nil help for this HDD. So, it's something else for this particular model's HDD.

Anyway, your script now make me can perform "restart" again, no need to shutdown -> cold boot.

Excellent!
 
I realise this is an old thread, but I have written an AppleScript app that will perform a 'cold restart' - this may be of use to some of you - I attach both the App and the Script here... You may need to edit the times to match your system.

Here is a code signed version of the Cold Restart App. You will need to allow the App full disk access, and allow the App to control System Events (in Accessibility). Please let me know if it doesn't work for you...
 

Attachments

  • ColdRestart.zip
    129 KB · Views: 167
  • Like
Reactions: h9826790
Here is a code signed version of the Cold Restart App. You will need to allow the App full disk access, and allow the App to control System Events (in Accessibility). Please let me know if it doesn't work for you...
Tested a few times, this version doesn't work for me (full disk access, and the control System Events allowed)

Switched back to the previous version, then it works again.
 
Could you tell me exactly what happens? Do you get any warning messages? I think maybe you have to remove the instance of 'Full Disk Access' and then reapply it? It's strange - it works fine for me (the latest version)...
When I double click the run the latest version, it asks me to run or quit (same as the previous version). Then ask me to enter admin password (also same as the previous version). No other warning.

But after the cMP shutdown, it won't auto restart (I waited for more than a min. The old version restart in few seconds). I tested a few times.
 
I realise this is an old thread, but I have written an AppleScript app that will perform a 'cold restart' - this may be of use to some of you - I attach both the App and the Script here... You may need to edit the times to match your system.
Thank you for this script. The App version of the script works nicely! However I cant get the script version to work (it just sits frozen) I would like to adjust the cold restart time (it takes a minute to cold restart on my machine)
 
This post closely follows a previous ASC thread:

https://discussions.apple.com/thread/8338922

I have had a very similar problem with a Mac Pro 5,1 (2012), running either Yosemite (10.10.5) or High Sierra (10.13.3) off of SSD or HDD. Upon restart or option-restart, the system will not mount the following disks:

6TB WD Black WD6002FZWZ

8TB HGST He8 HUH728080ALE600

8TB WD Red (white labeled OEM version WD80EMAZ)

Other details:

- On cold boot or option-boot, all of these drives will mount, and all the drives work great.

- The effect is the same with three different systems: Yosemite HFS on SATA 3 sled, High Sierra APFS on PCI card, and Yosemite on a startup volume partition on the WD Red.

- None of the hard drives are formatted involving a Logical Volume Group (this was a red herring in the ASC thread).

- One of the effected drives (WD Red) has a 2TB partition with Yosemite on it. Upon option-restart, this partition shows up on the option screen and is selectable. If selected, the system gets part way through startup, then a grey circle with line through it appears. This would seem to imply the problem is not a time-out waiting for the drives to spin up as has been suggested in the ASC thread. Rather something is causing the drives to shut down or unmount part way through startup (including the startup partition).

- 2 of the 3 drives are SATA 3.3 compliant and have a remote power-off on pin 3. But in all cases pin 3 is manually taped off (and the problem does not occur on cold restart), so I am sure it is not a PWDIS issue.

Anyone know what causes this, or have a workaround? It's important that I be able to remotely restart this machine, and not be limited to cold rebooting manually in person each time a restart is required.
Has anyone figured this out yet, I just upgraded my 5,1 to High Sierra, and noticed that I have the exact same problem with 2 6TB drives, they boot up on a cold bootup, but never after a reboot.
 
Hi, I just upgraded to Mojave from HS with a new SSD and this is now happening to me. It was all fine before the upgrade (same drives). Now: warm restart = drive disappears. Shutdown and Power on = drive is there. This is a data drive, not a boot/system drive. Only happens to my 4TB WD Black in Tray 1. Identical drive in Tray 3 is unaffected.

As someone mentioned earlier, maybe the warm reboot happens too quickly to mount the drive in tray 1.

For me this is a minor annoyance, but hoping a fix is discovered soon.
 
I realise this is an old thread, but I have written an AppleScript app that will perform a 'cold restart' - this may be of use to some of you - I attach both the App and the Script here... You may need to edit the times to match your system.
Hi. Could you please explain to me how to use the app and the script file. When I run the app my 5,1 simply shuts down and doesn’t restart.
Thanks.
 
I realise this is an old thread, but I have written an AppleScript app that will perform a 'cold restart' - this may be of use to some of you - I attach both the App and the Script here... You may need to edit the times to match your system.
Hi. I have tried this with my Mac Pro 5,1 but when I run the app it simply shuts down. How do I achieve a cold restart with the app and the script?
Thanks.
 
I realize it's been a while since this original post, but I am now seeing similar behavior with a PCIe card. It's a Highpoint R1104 NVMe card with 4 x 4TB blades in a Mac Pro 5,1. If the computer is cold-booted, the NVMe blades show up in diskutil list and work flawlessly at PCI 2.0 speed (individually or in software raid). But if the computer is warm restarted, the PCIe card is not even recognized by the system as being attached. I'm not sure this is part of the same phenomenon, but if it is, it's not unique to the internal SATA 2 interface.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.