Posts made by G I Jones

@pmoncho Directly to HD

@pmoncho Thank you. The only thing I haven't tried that you listed yet is the Dell ESXi 6.7 U2 version part. Trying that now.

@marcinozga said in ESXi 6.7 Troubleshooting:

@G-I-Jones said in ESXi 6.7 Troubleshooting:

@marcinozga said in ESXi 6.7 Troubleshooting:

@G-I-Jones said in ESXi 6.7 Troubleshooting:

@marcinozga said in ESXi 6.7 Troubleshooting:

@G-I-Jones said in ESXi 6.7 Troubleshooting:

@marcinozga @marcinozga said in ESXi 6.7 Troubleshooting:

What's the VM version of guest?

Windows Server 2016 or later (64-bit)

I guess I wasn't clear. I meant hardware compatibility version, it should be ESXi 6.7 Update 2 and later (VM version 15).

6.7.0 Update 3 (Build 15160138)

"ESXi 6.7 virtual machine" is all it says

You should have an option to upgrade VM compatibility to 15. You should also have an option to select it when creating new machine.

I only get these. Does that mean perhaps the installer for ESXi for Host was out of date? My boss installed it and I can't be sure it was the right one.

@marcinozga said in ESXi 6.7 Troubleshooting:

@G-I-Jones said in ESXi 6.7 Troubleshooting:

@marcinozga said in ESXi 6.7 Troubleshooting:

@G-I-Jones said in ESXi 6.7 Troubleshooting:

@marcinozga @marcinozga said in ESXi 6.7 Troubleshooting:

What's the VM version of guest?

Windows Server 2016 or later (64-bit)

I guess I wasn't clear. I meant hardware compatibility version, it should be ESXi 6.7 Update 2 and later (VM version 15).

6.7.0 Update 3 (Build 15160138)

"ESXi 6.7 virtual machine" is all it says

@marcinozga Sure thing. Why do you recommend Paravirtual, and VMXNET 3?

@marcinozga said in ESXi 6.7 Troubleshooting:

@G-I-Jones said in ESXi 6.7 Troubleshooting:

Is hardware virtualization enabled in guest CPU?

It is enabled on host, if that's what you meant.

Expand guest CPU configuration, it's a checkbox there.

@marcinozga said in ESXi 6.7 Troubleshooting:

@G-I-Jones said in ESXi 6.7 Troubleshooting:

@marcinozga @marcinozga said in ESXi 6.7 Troubleshooting:

What's the VM version of guest?

Windows Server 2016 or later (64-bit)

I guess I wasn't clear. I meant hardware compatibility version, it should be ESXi 6.7 Update 2 and later (VM version 15).

6.7.0 Update 3 (Build 15160138)

@marcinozga @marcinozga said in ESXi 6.7 Troubleshooting:

What's the VM version of guest?

Windows Server 2016 or later (64-bit)

Is hardware virtualization enabled in guest CPU?

It is enabled on host, if that's what you meant.

What's SCSI controller and network type?

LSI Logic SAS - VM Network, E1000e, Auto Mac which has been reserverd via DHCP

You should have VMware paravirtual and VMXNET 3

I changed this to what you recommended but no change.

And obvious, are VMware tools installed in guest?

I do.

Ideally I'd like to see screenshot of assigned hardware configuration of that guest.

As some of you might know, I'm relatively new at Virtualization. With that being said I've just built a VM in the following environment:

• ESXi 6.7 Update 3
• Dell PowerEdge R840 with 8CPU & Xeon Gold 5122 processor
• 64-bit Windows Server 2016 w/GUI (Desktop Experience)

I'm having all kinds of issues.

Accessing network drives is working fine, but right clicking any file locks the VM up. Trying to open any files prompts me that "This app can't run on your PC" as if to say it's not 64-bit. Trying to copy said files to the desktop of the VM via RDP results in extremely long transfer times which mostly fail.

Allocations as follows:

• 2 Cores
• 30GB RAM
• 3TB HDD

I know this isn't a lot of information to go off of, as I've omitted many variables, but I honestly don't know what's even relevant.

Where would you start to troubleshoot this? I'm very close to deleting the VM and trying again in assumption that the install was bust.

In this case would the definition of "encryption" be relevant? It's pretty vague as is. This is super fucked at any rate. I hope all the bad things in life happen to that company and only that company.

I really don't follow your explanation. You've managed to boot into Windows to see and HP installer? where did this Windows boot environment come from?

@Dashrender - I was able to install Windows from a Microsoft ISO that I had, as my initial issue was seeing the partitions, this bootable (HP gave me) gave me the necessary drivers to do such. After Windows was installed, I was then able to open the same bootable USB (HP gave me) and there was a HP Installer included. I opted not to run it because the likelihood of it being bloatware.

A vendor image, is normally an enhanced/changed/updated version of the standard Windows install ISO. It's updated by the vendor to include drivers (often needed to boot/install/see the storage) and other vendor related junkware, and sometimes third party crap.

Most of use around here avoid using vendor images because of the second and third things listed there, but that does sometimes leave us in a pickle.

Appreciated.

No, not cool. You never want a vendor image.

@JaredBusch So this bootable only included raid drivers for windows to see the partitions it seems. I was able to see the partitions and delete them to install new OS from my Win10 DVD. After Windows booted there was an HP installer on that disk as well, but I just skipped running it as I assumed it was just bloatware. When you say vendor image, in this instance, what could be different besides the bloatware part? Are we talking outdated RAID drivers or default drivers used by Windows, and wouldn't those drivers update as soon as you ran an obligatory "Check for Updates"?

Trying to be better and you guys are really helping, so I appreciate the input.

Aww - Clonezilla isn't considered a Linux distro - it's really just a tool - one that happens to use Linux to boot the system (because the Clonezilla tool itself is not bootable).

think of it like this the calculator tool on Windows - the code for it on a USB stick is useless, it can't do anything, but, if you boot the system from Windows, then the code can run under windows. Clonezilla is the same.

@Dashrender Ah. Thanks for the clarification. Sorry for the late reply.

They are providing you with a Windows 10 ISO that you can put on a USB stick and boot/install from that includes the RAID driver? Cool!

Basically. And yes, very cool.

@Dashrender said in HP Z440’s Bricked Hard:

@G-I-Jones said in HP Z440’s Bricked Hard:

@Dashrender It's a Linux Bootable. Or that's what Google told me.

lol - oh.. well, yeah it is, err... but.. so?

if you're thinking that you could use Clonezilla to see if the drives are available to Clonezilla - OK I suppose that makes sense, but not seeing the drive in Clonezilla wouldn't tell you anything, i.e. not seeing it in Clonezilla doesn't mean you have hardware problems.

No, Pete was saying SOP was to use Linux bootable to wipe raid sigs and drive partitions. I'm just trying to learn which Linux distros are preferred as I'm new to the idea and the list of Linux disto's are lengthy.

@Dashrender said in HP Z440’s Bricked Hard:

@G-I-Jones said in HP Z440’s Bricked Hard:

@Pete-S So just to be clear, you recommend just downloading the C612 driver and loading that during OS install wizard?

Maybe, maybe not - if the C612 driver is the RAID driver, then yes, that's what you want to put on the USB stick (unzipped) and provide to Windows during install.

But if that's just a chipset driver, and the RAID is something else, you'll need to get the RAID driver itself, and put that on the USB stick.

@Dashrender I was thinking that might be the case. I'm just going to go with the bootable they gave me for now, but will look into adjusting fire for future endeavors.

@Dashrender It's a Linux Bootable. Or that's what Google told me.

@Pete-S Yeah, that's the kind of advice I need as I'm all about expanding my arsenal but have next to zero experience booting into Linux. I was mulling through the list and it seems Clonezilla (which I remember @Dashrender mentioning several times before) is the most popular for these sorts of things. would you recommend the same?