Solved

Esxi after raw mappings, some disks not available

Posted on 2014-02-01
2
276 Views
Last Modified: 2014-02-03
Hi,

I recently did some raw mappings on my esxi. Now esxi is now acting strangely by showing some disks as dead whereas they are not (checked that by removing these disks and testing in other system.

Please advise howto do a sanity check/remove loose ends.

J.
0
Comment
Question by:janhoedt
2 Comments
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 39826869
If you have "mapped RAW disks" to local disks this is an un-supported feature of the Hypervisor, and "anything can happen".

VMware will not support this function, as the product is being used beyond it's design specification.

It's possible that the drive paths have changed, been altered, and the path to that original mapped disk is no longer available and hence a dead path.

I would check the /var/log/vmkernel.log on the ESXi server, and check it it's complaining about claim paths not found, or dead paths.
0
 

Author Closing Comment

by:janhoedt
ID: 39830325
Then I won t use raw mappings anymore. Performance was much lower then expected .  Running Synology on hp NL 40 is my solution. It has support for ssd cache so I can (not tried yet) use the ssd s in the sharkoon and thus optimize speed.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
VMware Vsphere Database Redundancy 1 56
ESX 6.0 Best Practices for datastore size 5 121
Weird issue with VMWare ESXi 6 host 3 53
HP H221 HBA with P2000 trouble configuring 4 37
If we need to check who deleted a Virtual Machine from our vCenter. Looking this task in logs can be painful and spend lot of time, so the best way to check this is in the vCenter DB. Just connect to vCenter DB(default DB should be VCDB and using…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …

766 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question