ozool

Seemingly healthy VMDK virtual drive showing as crashed

Recommended Posts

My ESXi-based Xpenology system (DSM 6.2-23739 1.03a2) is now showing Disk1 as 'Crashed'.

Disk1 is actually a vmdk file hosted on ESXi which seems to be healthy.

Clicking the 'Health Info' button returns 'Access Error. An Error occurred when accessing this drive...'

 

Is there any way to restore access to the disk in DSM?

Share this post


Link to post
Share on other sites

Normally my disks show as "Healthy" in green text but occasionally I get them in Red and it says "Failing" or something like that but it still works. Only one time have I gotten a VMDK that actually reported as crashed even though ESXi showed everything is fine. I think I got it working again by removing the VMDK from the machine, rebooting and then adding it again, rebooting. That VMDK was then available to "Repair" the now degraded storage pool with.

 

If that doesn't work, assuming this VMDK is part of a storage pool with RAID 1, 5, etc... maybe delete the VMDK then create a new one and rebuild the array onto that? Backup data first of course before trying any of the above.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.