Power up failed - Can't restart Local

Support
1

I had to hard restart my MacBook and after that Local won’t start up. I can’t get the local machine running or any of the sites. I get this error in the local-by-flywheel.log file:

Jul 14, 2017, 8:54 AM CDT - info: [main/menu] Unable to restart Docker Machine.
Jul 14, 2017, 8:54 AM CDT - info: [renderer/CheckEnvPage] Check system promise response: [ undefined, ‘machine-halted’ ] machine-halted
Jul 14, 2017, 8:54 AM CDT - info: [main/docker-machine] Checking Boot2Docker.iso hash
Jul 14, 2017, 8:54 AM CDT - info: [main/docker-machine] Running /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Jul 14, 2017, 8:54 AM CDT - info: [main/docker-machine] Starting “local-by-flywheel”…
Jul 14, 2017, 8:54 AM CDT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed…
Jul 14, 2017, 8:54 AM CDT - warn: [main/docker-machine] Unable to start the VM: /usr/local/bin/VBoxManage startvm local-by-flywheel --type headless failed:
Jul 14, 2017, 8:54 AM CDT - warn: [main/docker-machine] VBoxManage: error: Could not open the medium ‘/Users/xxxxxx/.docker/machine/machines/local-by-flywheel/disk.vmdk’.
Jul 14, 2017, 8:54 AM CDT - warn: [main/docker-machine] VBoxManage: error: VMDK: inconsistency between grain table and backup grain table in ‘/Users/xxxxxx/.docker/machine/machines/local-by-flywheel/disk.vmdk’ (VERR_VD_VMDK_INVALID_HEADER).
Jul 14, 2017, 8:54 AM CDT - warn: [main/docker-machine] VBoxManage: error: VD: error VERR_VD_VMDK_INVALID_HEADER opening image file ‘/Users/xxxxx/.docker/machine/machines/local-by-flywheel/disk.vmdk’ (VERR_VD_VMDK_INVALID_HEADER)
Jul 14, 2017, 8:54 AM CDT - warn: [main/docker-machine] VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MediumWrap, interface IMedium
Jul 14, 2017, 8:54 AM CDT - warn: [main/docker-machine]
Jul 14, 2017, 8:54 AM CDT - warn: [main/docker-machine] Details: 00:00:00.048709 Power up failed (vrc=VINF_SUCCESS, rc=NS_ERROR_FAILURE (0X80004005))

2

Hi Jon,

So sorry for the trouble!

Can you please open Terminal and run the following?

vboxmanage internalcommands repairhd ~/.docker/machine/machines/local-by-flywheel/disk.vmdk
3

Got this error:
VBoxManage: error: No file format specified and autodetect failed - please specify format: VERR_NOT_SUPPORTED

4

Please try:

vboxmanage internalcommands repairhd ~/.docker/machine/machines/local-by-flywheel/disk.vmdk -format VMDK
5

Ran that. Reopened Local and clicked on Restart Local Machine. Then after it was spinning I saw this in the log:

Jul 14, 2017, 10:27 AM CDT - warn: [main/docker-machine] Unable to start the VM: /usr/local/bin/VBoxManage startvm local-by-flywheel --type headless failed:
Jul 14, 2017, 10:27 AM CDT - warn: [main/docker-machine] VBoxManage: error: Could not open the medium ‘/Users/xxxxx/.docker/machine/machines/local-by-flywheel/disk.vmdk’.
Jul 14, 2017, 10:27 AM CDT - warn: [main/docker-machine] VBoxManage: error: VMDK: inconsistency between grain table and backup grain table in ‘/Users/xxxxx/.docker/machine/machines/local-by-flywheel/disk.vmdk’ (VERR_VD_VMDK_INVALID_HEADER).
Jul 14, 2017, 10:27 AM CDT - warn: [main/docker-machine] VBoxManage: error: VD: error VERR_VD_VMDK_INVALID_HEADER opening image file ‘/Users/xxxxx/.docker/machine/machines/local-by-flywheel/disk.vmdk’ (VERR_VD_VMDK_INVALID_HEADER)
Jul 14, 2017, 10:27 AM CDT - warn: [main/docker-machine] VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MediumWrap, interface IMedium
Jul 14, 2017, 10:27 AM CDT - warn: [main/docker-machine]
Jul 14, 2017, 10:27 AM CDT - warn: [main/docker-machine] Details: 00:00:00.037992 Power up failed (vrc=VINF_SUCCESS, rc=NS_ERROR_FAILURE (0X80004005))

6

I noticed there is another error right before those lines. The time difference is because I’m still troubleshooting.

Jul 14, 2017, 11:07 AM CDT - info: [main/index] Existing Pressmatic data does not exist.
Jul 14, 2017, 11:07 AM CDT - info: [main/check-system] Check System: Docker Machine:

7

In that case, there’s one more thing you can try:

  1. Download the binary under “Attachments” on this page: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1023856
    • The binary that doesn’t mention Linux or Windows is the one you want for macOS. At the time of writing it’s 1023856-vdiskmanager-3.0.2.zip
  2. After downloading and extracting it, run the following (assuming it’s unzipped in the Downloads folder) in Terminal:
~/Downloads/vmware-vdiskmanager -R ~/.docker/machine/machines/local-by-flywheel/disk.vmdk

Then, you can try running Local again.

Update for macOS Catalina users:

The attachment on the page above is a 32-bit binary which Catalina no longer supports.

To get a 64-bit version of vmware-vdiskmanager, you can try the following:

  1. Install Homebrew if it isn’t already
  2. Run brew cask install vmware-fusion and enter your password when prompted
  3. Run
    vmware-vdiskmanager -R ~/.docker/machine/machines/local-by-flywheel/disk.vmdk
  4. Try to open Local

If you no longer have any need for VMWare Fusion, remove the cask by running brew cask remove vmware-fusion

8

I ran the command an it was successful:

The virtual disk, ‘/Users/xxxxx/.docker/machine/machines/local-by-flywheel/disk.vmdk’, was corrupted and has been successfully repaired.

So that did the trick. Thank you!

1 Like
9

Spoke too soon. When I start any site I can’t view the site. I get a “ERR_CONNECTION_REFUSED” in Chrome when I visit the dev URL. I don’t see any errors in the apache log for the site, same for mysql or php logs. Even the log for local looks alright. Here it is:

Jul 14, 2017, 1:09 PM CDT - info: [main/docker-machine] Machine “local-by-flywheel” was started.
Jul 14, 2017, 1:09 PM CDT - info: [main/docker-machine] Waiting for SSH to be available…
Jul 14, 2017, 1:09 PM CDT - info: [main/docker-machine] Detecting the provisioner…
Jul 14, 2017, 1:09 PM CDT - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the docker-machine env command.
Jul 14, 2017, 1:09 PM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Jul 14, 2017, 1:09 PM CDT - info: [main/set-docker-env] Received Docker Machine env.
Jul 14, 2017, 1:09 PM CDT - info: [main/docker-machine-nfs] NFS Mount Status
{ error: null,
stdout: ‘tmpfs on / type tmpfs (rw,relatime,size=917696k)\nproc on /proc type proc (rw,relatime)\nsysfs on /sys type sysfs (rw,relatime)\ndevpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)\ntmpfs on /dev/shm type tmpfs (rw,relatime)\nfusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)\n/dev/sda1 on /mnt/sda1 type ext4 (rw,relatime,data=ordered)\ncgroup on /sys/fs/cgroup type tmpfs (rw,relatime,mode=755)\ncgroup on /sys/fs/cgroup/cpuset type cgroup (rw,relatime,cpuset)\ncgroup on /sys/fs/cgroup/cpu type cgroup (rw,relatime,cpu)\ncgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,relatime,cpuacct)\ncgroup on /sys/fs/cgroup/blkio type cgroup (rw,relatime,blkio)\ncgroup on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)\ncgroup on /sys/fs/cgroup/devices type cgroup (rw,relatime,devices)\ncgroup on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer)\ncgroup on /sys/fs/cgroup/net_cls type cgroup (rw,relatime,net_cls)\ncgroup on /sys/fs/cgroup/perf_event type cgroup (rw,relatime,perf_event)\ncgroup on /sys/fs/cgroup/net_prio type cgroup (rw,relatime,net_prio)\ncgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,relatime,hugetlb)\ncgroup on /sys/fs/cgroup/pids type cgroup (rw,relatime,pids)\nxxx.xxx.xx.x:/Users on /Users type nfs (rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=1,acregmax=1,acdirmin=1,acdirmax=1,hard,nolock,proto=tcp,port=2049,timeo=70,retrans=3,sec=sys,local_lock=all,addr=xxx.xxx.xx.x)\n/dev/sda1 on /mnt/sda1/var/lib/docker/aufs type ext4 (rw,relatime,data=ordered)\n’,
stderr: ‘’,
hasUsers: [ ‘xxx.xxx.xx.x:/Users’ ] }
Jul 14, 2017, 1:09 PM CDT - info: [main/docker-machine] checking IP
Jul 14, 2017, 1:09 PM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Jul 14, 2017, 1:09 PM CDT - info: [main/docker-machine] checked IP xxx.xxx.xx.xxx

Jul 14, 2017, 1:09 PM CDT - info: [main/set-docker-env] Received Docker Machine env.

10

Ok, so it looks like the 2 sites are running in Local but they actually aren’t. When I click stop the sites just spin and here is the dump from Local’s log when that happens.

Jul 14, 2017, 2:47 PM CDT - info: [main/stopSite] Stopping site: running mydumper
Jul 14, 2017, 2:47 PM CDT - warn: [main/index] Unhandled Rejection at: Promise Promise {
{ Error: (HTTP code 500) server error - Container 27d2b9d292e2e93a24a7ff2e3b56875b0fc74c7a6375b204827f8c387d2e6b32 is not running
at /Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:239:17
at getCause (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:269:7)
at Modem.buildPayload (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:238:5)
at IncomingMessage. (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:214:14)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
reason: ‘server error’,
statusCode: 500,
json: { message: ‘Container 27d2b9d292e2e93a24a7ff2e3b56875b0fc74c7a6375b204827f8c387d2e6b32 is not running’ } } } reason: Error: (HTTP code 500) server error - Container 27d2b9d292e2e93a24a7ff2e3b56875b0fc74c7a6375b204827f8c387d2e6b32 is not running
at /Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:239:17
at getCause (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:269:7)
at Modem.buildPayload (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:238:5)
at IncomingMessage. (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:214:14)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
Jul 14, 2017, 2:47 PM CDT - info: [main/stopSite] Stopping site: running mydumper
Jul 14, 2017, 2:47 PM CDT - warn: [main/index] Unhandled Rejection at: Promise Promise {
{ Error: (HTTP code 500) server error - Container 0dbbdfade1f669532f4bf230a215847b904d7d05f3689856524d68da4a1e4a1b is not running
at /Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:239:17
at getCause (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:269:7)
at Modem.buildPayload (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:238:5)
at IncomingMessage. (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:214:14)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
reason: ‘server error’,
statusCode: 500,
json: { message: ‘Container 0dbbdfade1f669532f4bf230a215847b904d7d05f3689856524d68da4a1e4a1b is not running’ } } } reason: Error: (HTTP code 500) server error - Container 0dbbdfade1f669532f4bf230a215847b904d7d05f3689856524d68da4a1e4a1b is not running
at /Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:239:17
at getCause (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:269:7)
at Modem.buildPayload (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:238:5)
at IncomingMessage. (/Applications/Local by Flywheel.app/Contents/Resources/app.asar/node_modules/docker-modem/lib/modem.js:214:14)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)

11

Can you try going to Help » Restart Local’s Machine? This should reinitialize Docker after repairing the disk.

12

NEED HELP URGENTLLY PLEASE HELP ME

Failed to open a session for the virtual machine vm .

Could not open the medium ‘/Users/macuser/VirtualBox VMs/vm/HDP_2.6.5_vmware_85-disk1_1.vmdk’ .

VMDK: inconsistency between grain table and backup grain table in ‘/Users/macuser/VirtualBox VMs/vm/HDP_2.6.5_vmware_85-disk1_1.vmdk’ (VERR_VD_VMDK_INVALID_HEADER).

VD: error VERR_VD_VMDK_INVALID_HEADER opening image file ‘/Users/macuser/VirtualBox VMs/vm/HDP_2.6.5_vmware_85-disk1_1.vmdk’ (VERR_VD_VMDK_INVALID_HEADER).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MediumWrap
Interface: IMedium {4afe423b-43e0-e9d0-82e8-ceb307940dda}