VMware Cloud Community
jkasalzuma
Enthusiast
Enthusiast

Update VSAN configuration taking a long time

Has anyone else experienced the "Update VSA Configuration" tasks that runs after enabling vSAN on the hosts taking a long time?

So far my tasks are running against 3 hosts and have taken 45 minutes thus far and still going. I don't remember it running this long in the beta. I am running the 5.5up1 bits on a fresh build that I wiped disks prior to rebuilding and this is a brand new 5.5up1 vCenter Appliance. There is nothing left of the beta.

It hasn't timed out after 45 minutes so I'm guessing that's a good thing.

I see no activity on the disks either so not sure if they are being zero'd or something along that line.

Any ideas? I'll update this post if something changes...

53 Replies
jkasalzuma
Enthusiast
Enthusiast

I am unable to generate logs. I keep getting the same PSOD. The odd thing is that the PSOD only occurs when VSAN has been enabled. Investigating the PSOD looks to possibly related to NICs but I can't confirm that.

Reply
0 Kudos
philzy
Enthusiast
Enthusiast

Have the same issue. Upgraded from working beta to nonworking GA and now don't have any VSAN.

I'm lucky it's a client lab. Client is waiting VSAN for more than 6 month 😞

Tried to use IDE in BIOS, rather than AHCI but with the same result.

Let's wait for fix.

Reply
0 Kudos
depping
Leadership
Leadership

philzy wrote:

Have the same issue. Upgraded from working beta to nonworking GA and now don't have any VSAN.

I'm lucky it's a client lab. Client is waiting VSAN for more than 6 month 😞

Tried to use IDE in BIOS, rather than AHCI but with the same result.

Let's wait for fix.

If your client is waiting for VSAN I would suggest buying disk controllers which are on the HCL. This is by far the fastest way of getting the environment up and running and also the most secure/reliable way.

Reply
0 Kudos
philzy
Enthusiast
Enthusiast

It was a part of hardware optimization for vdi infrastructure.

Also HCL list is very small till now.

Reply
0 Kudos
depping
Leadership
Leadership

philzy wrote:

It was a part of hardware optimization for vdi infrastructure.

Also HCL list is very small till now.

There are close to 100 disk controllers on the HCL with at least 25 by LSI which should fit in most hosts... "small" is relative I would say Smiley Happy

Reply
0 Kudos
philzy
Enthusiast
Enthusiast

Good idea, but not for a bunch of dedicated servers with no customization opportunity.

Sorry.

AHCI-fix needed 🙂

Reply
0 Kudos
depping
Leadership
Leadership

philzy wrote:

Good idea, but not for a bunch of dedicated servers with no customization opportunity.

Sorry.

AHCI-fix needed 🙂

I understand, that is being looked at, but will take time hence I said if there is an immediate need your customer will need to look for a different solution

Reply
0 Kudos
drewdubber
Contributor
Contributor

Was there any update for the AHCI issue or is one planned?  I'd like to try out VSAN in my home lab but I have an Supermicro 6026TT system which means ICH10R is as good as I can get for now!

Reply
0 Kudos
elgwhoppo
Hot Shot
Hot Shot

The AHCI fix was implemented with the beta refresh in 11/2013. Installing the latest 5.5.0 U1 build should not have the AHCI bug.

Virtual SAN Beta Refresh Updates | VMware vSphere Blog - VMware Blogs

VCDX-Desktop
Reply
0 Kudos
drewdubber
Contributor
Contributor

Thanks very much for the super quick response - much appreciated.

Reply
0 Kudos
philzy
Enthusiast
Enthusiast

Elgwhoopo! You are wrong!

The ahci bug is in place. After upgrade or fresh install you got non working VSAN. The 5.5.0 u1 do not have ahci support. Use beta version for your lab.

Reply
0 Kudos
elgwhoppo
Hot Shot
Hot Shot

The only mention of AHCI in the 5.5.0 U1 release notes is this:

Virtual SAN Issues

  • You cannot hot unplug storage disks claimed by the Advance Host Controller Interface (AHCI) driver when the disks are part of a Virtual SAN disk group
    The AHCI driver claims data or SSD storage disks that are connected to SATA ports on the motherboard or through AHCI-enabled storage adapters. If the disks are claimed by the AHCI driver and are part of a Virtual SAN disk group, you cannot hot unplug them from the ESXi host. If you do so, the host will not be able to detect the disks after you reconnect them.

    This issue is resolved in this release.

Source: VMware ESXi 5.5 Update 1 Release Notes

So in short Philzy, what documentation/blogs/release notes/experience do you have that you're basing this claim from? Seems a bit daft to think that they'd break a function they just fixed in the refresh.

VCDX-Desktop
Reply
0 Kudos
depping
Leadership
Leadership

No one broke anything on purpose. However, the AHCI controller is not supported today and there are (as far as I am aware) still issues with it. At least, that is what I have witnessed in my lab. Maybe kmadnani can comment on a potential future fix.

Duncan

------------

Book out soon: Essential Virtual SAN: Administrator's Guide to VMware VSAN (VMware Press Technology)

Reply
0 Kudos
elgwhoppo
Hot Shot
Hot Shot

This is good information to have. I think I will try installing the U1 update fresh in my lab; it's curious to me that there's a resolved issue relating to AHCI controllers in the U1 release notes if support was officially pulled.

Would love to see "not supported but works" status for AHCI controllers. I get that VMware can't stand behind hardware that hasn't been certified for use given the criticality of data protection, but us labbers would love to see it working on our whiteboxes whether its supported or not. Thanks for posting up guys.

VCDX-Desktop
Reply
0 Kudos
admin
Immortal
Immortal

As Duncan mentioned, we are in the process of fixing the issue found in AHCI - expect support in the near future.

Reply
0 Kudos
hodsonc
Contributor
Contributor

Is there any status update on this?

Reply
0 Kudos
PaulRitchie
Contributor
Contributor

This is Crazy.... Been dealing with this same problem for 2 months... Using 3 Shuttle SH87r6's identical hardware across the board.. Worked perfectly in BETA and now im dead in the water with over 4k worth of useless "Vmware Lab" equipment. ..#FeelingAwesomeAboutWastingMoney

Reply
0 Kudos
PaulRitchie
Contributor
Contributor

Maybe a dumb question but...Someone mentioned using BETA instead-- How is that possible? When i attempt to use it, it tells me my "trial" is expired..

Reply
0 Kudos
philzy
Enthusiast
Enthusiast

TO PaulRitchie:

You have 4 opportunities:

1. Return to Beta version (it's very simple). VMware KB:     Reverting to a previous version of ESXi after a failed upgrade  

2. Buy any SAS-adapter on LSI-chipset 2308 for example http://www.newegg.com/Product/Product.aspx?Item=N82E16816118114 (170$) and no problems with HCL - VMware Compatibility Guide: vsan

3. Try Vmware Vsphere 6.0 Beta2 - https://communities.vmware.com/community/vmtn/beta/vsphere-beta

4. Or just reinstall Beta version on esxi-host with GA-keys for both esxi-hosts and VCenter

You can use a key from GA version it doesn't have any checks.

Beta keys are expiable.

Reply
0 Kudos
PaulRitchie
Contributor
Contributor

Thanks Philzy

I cant do #1- Im so far removed from that- new insall after new install etc.

#2- thats another 600.00 bucks for my home lab.. just to be able to use VSAN for 60 days.. A synology NAS would be a better use for that $$ but thanks for the link- at least i know where to go if i want to go that route

#3 - I cant get to that link at all..i get "access to this place or content is restricted......."

#4 - I can give that a shot, im just floored that BETA worked and the release version doesnt..

Reply
0 Kudos