T13:03:55.495Z cpu8:449766)megasas_slave_configure: do not export physical disk devices to upper layer. T13:03:55.463Z cpu8:449766)Vol3: 647: Couldn't read volume header from control: Invalid handle Target: :p0:sataboy2:019153caĬan anyone provide further information on what I may be missing here?
#Target disk mode not showing up how to
So I have been looking around in the CLI and here is some further info (not sure how helpful but hey, I learned how to do it): I then rescanned and nothing is showing up under connected devices.
#Target disk mode not showing up software
I then went to storage adapters and enabled software initiator, set the network to vswitch3 (vmk1), dynamically discovered my storage and then the target name showed up in the static. I have some Nexsan Sataboys around my lab and have easily hooked them up in the past.
I started to get some storage errors when bringing up new VMs, so it's time to add on.
0 kommentar(er)
