XCP-ng 8.3 public alpha 🚀
-
@jhansen I'd suggest booting off some Linux rescue disk and just redoing all the partitions manually. I ran into an upgrade issue once on a Dell box because of some stupid little extra utility partition they had in there. See: http://xenserver.pl/author/tobias-kreidl
Look for "The (In)famous Dell Utility Partition." -
@olivierlambert
Unfortunately, I only keep the latest version of the iso files. I have the xcp-ng-8.2.1.iso here and I think that was it, but it could also have been the previous version. -
@jhansen Any old Linux distribution recovery-like boot disk should work, as long as you can get to the partitioning app.
-
@tjkreidl
Mayby you are on the right trace.
It is a Dell Server.
This time i will wipe the disk before installation.
As the Data is on other disk i will try to mount then afterwards.
Thanks -
@tjkreidl
Do you think a simple reseize of the different partition will do it? -
@jhansen said in XCP-ng 8.3 public alpha
:@tjkreidl
Mayby you are on the right trace.
It is a Dell Server.
This time i will wipe the disk before installation.
As the Data is on other disk i will try to mount then afterwards.
ThanksI am willing to bet you got bitten by the Dell utility partition disk issue. And, yes, best to wipe it out. Or delete it and redo one of the other partitions. But frankly, you will really want the new 36.5 GB total layout with the dual 18GB partitions, etc., that was mentioned above. You will want the right order of partitions to match what the XCP-ng installation wants to do at some point, but it should redo the layout I hope once you get rid of that extra Dell partition. Check out what I did in my article referenced above:
"The solution was simply to delete that sda1 partition altogether using fdisk and re-install. Deleting the partition can be performed live on the host prior to the installation process." -
@tjkreidl
Naturally partition and filesystem. -
@tjkreidl
Just got an idea, but will it work?
wipe disk
Fresh installation
Restore Metadata from XO Backup
Will that work? -
@jhansen If you have the full metadata, I would think that's possible. What about any VM backups, custom network settings, etc.? Lots to make sure you have before anything that drastic.
-
@tjkreidl
Although it's my test lab, I have a backup of everything. I'm something of a burned child with many years of bad experience.
Unfortunately it would take a few days to play everything back.
But I'll get a new SSD and give it a try.
But first thanks for the help, I'll write if it worked.
Regards Joerg -
@stormi Finally updated my two host playlab from 8.2.0 fully patched to 8.3.0-alpha2 using the ISO method followed by installing available patches using XO from source.
As boring as it is, I have nothing to report other than that the update of my low-tech hosts has worked (Dell Optiplex 9010, Intel i5-3550 CPU, 32GB RAM, Intel S3700 100GB SSD for boot, Samsung 860 EVO 500GB SSD for local SR, Intel X520-DA1 10G). You wouldn't believe it, but sometimes boring is good
.I'll report back if anything comes up in day-to-day operations
. -
@jhansen said in XCP-ng 8.3 public alpha
:@tjkreidl
Although it's my test lab, I have a backup of everything. I'm something of a burned child with many years of bad experience.
Unfortunately it would take a few days to play everything back.
But I'll get a new SSD and give it a try.
But first thanks for the help, I'll write if it worked.
Regards JoergSounds good, Joerg. Good luck!
-
@olivierlambert
Hello
So now the 8.3 is running with all updates.
Where the old partition table came from is still a mystery to me but it could be something to do with Dell Utility as tjkreidl assumed.
No idea....
I took all disks out of the server and wiped the boot disk with zeros and then installed a new fresh 8.2.1. Now I also had the 18GB partitions.
I then did a metadata restore via XO. (the trick with renaming the backup folder from the old UUID to the UUID of the new installation)
All disks back in the server and then all VM and functions of the server checked, everything ok.
USB stick with the 8.3 version in - and the update ran without any problems. Then yum update, no problems here either.
All VMs are running.
I've only noticed one thing so far:
I set up one of my 10GBit network cards with SR-IOV, which no longer worked. I deleted it and created a new one, then it worked again. I have 2 Intel I350 gigabit adapters in the server, they can no longer do SR-IOV.
Now it's time to stress test the server with Windows, Linux, databases and video conversion. I'll let the CPU's run at 70-80% load for a week and also let the network cards and disk sweat. We'll see.Thanks again for the help.
Greetings JörgTest server:
Dell Poweredge R730
2 x Xenon E5-2698v4 (40 pyk+40 ht)
512GB RAM
2 x I350 Gigabit and 2 x X540 10 Gigabit adapters
1 x NVidia Gforce RTX 2070S for GPU support
1 x 512GB SSD for boot disk
2 x 512 SSD for dmcache
5 x 8 TB Harddisk in Raid5 for VM -
@tjkreidl
Hello again,
thanks for your help, you put me on the right path.
I wrote to Olivier what I dit.
Greetings Jörg -
@jhansen Great news! Maybe the SR-IOV issue is driver-related - is there a newer driver available or perhaps some setting in the BIOS?
And, yes, I bet wiping all the old partitions made a big difference.
-
@tjkreidl
Yes I believe that too -
Great news!
-
I just upgraded a virtual Test-Cluster from 8.2 to 8.3-Alpha and afterwards had on one console that it told me that I don't have a management Interface and even no network interfaces. Am "Emergency Network Reset" did not change anything .
After checking everything, network was working, even ping was working ... I remembered my problem with the certificates I mentioned here already in November and yes, it was just the same problem with the old too short certificate
But this leads me to the new "problem":
Couldn't the xsconsole be improved to give a better hint than "no network interfaces"?
Because it really means something like: Could't establish a connection to the master.Oh and one more thing:
Is it by design that I cannot login to XO Light on the VM that is not the master?
It just tells me "An error has occured"
... Ah just check the return value and it says error: "HOST_IS_SLAVE"
This could also be improved or automatically redirect to the master as it contains the IP of the master in the response ... or in the end it might be good to be able to login if the master is not available for troubleshooting -
Adding @pdonias for the XO Light question, however and FYI, you can't do anything without a master, that's the only place where you can call the XAPI. If you lose your master for good, you need to promote a slave to master so you can get back querying the XAPI.
-
@olivierlambert said in XCP-ng 8.3 public alpha
:you need to promote a slave to master so you can get back querying the XAPI.
Yes I know, I mean a limited access mode or as you said, to make it master would be one task for troubleshooting that could be done if you could login (with warnings), generate/checking/exporting logfiles etc ... (and all you can do on xsconsole, see MAC addresses etc ...)
