Ken Cunningham
Member
Parallels can't find BOOTCAMP hard drive after reboot
I use a BOOTCAMP partition for parallels. I have several hard disks on my Mac. I set up Parallels to start at login, unattended.
However, when the computer has a power outage and reboots, Parallels misplaces the BOOTCAMP partition, 'can't find Hard Drive 1' and won't boot. Stopping the VM, reselecting the BOOTCAMP partition in the config parameters, and restarting the VM fixes the problem. However, I need this to happen automatically because I need Parallels to be running on the Mac at all times unattended.
Looking at the Parallels configuration file and looking at the output from "df" in the terminal, issue seems that the disk identification for the BOOTCAMP partition changes between boots ( e.g. /dev/disk0s3 on one boot, /dev/disk2s3 on another boot ). This appears to be confusing Parallels at bootup.
Any ideas? It's kludgy, but perhaps a script with 'df' and 'awk' might identify the right disk ID, and this could be written into the parallels defaults somewhere prior to parallels booting? Hopefully the Parallels people might think of a better way than that...
Ken
I use a BOOTCAMP partition for parallels. I have several hard disks on my Mac. I set up Parallels to start at login, unattended.
However, when the computer has a power outage and reboots, Parallels misplaces the BOOTCAMP partition, 'can't find Hard Drive 1' and won't boot. Stopping the VM, reselecting the BOOTCAMP partition in the config parameters, and restarting the VM fixes the problem. However, I need this to happen automatically because I need Parallels to be running on the Mac at all times unattended.
Looking at the Parallels configuration file and looking at the output from "df" in the terminal, issue seems that the disk identification for the BOOTCAMP partition changes between boots ( e.g. /dev/disk0s3 on one boot, /dev/disk2s3 on another boot ). This appears to be confusing Parallels at bootup.
Any ideas? It's kludgy, but perhaps a script with 'df' and 'awk' might identify the right disk ID, and this could be written into the parallels defaults somewhere prior to parallels booting? Hopefully the Parallels people might think of a better way than that...
Ken
Last edited: