After installing updates: 0 bytes free, Control domain memory = 0B

Dataslak

@Dataslak
I am late to a meeting with customers. I would much rather stay in the office to work with this. But when I come back in a couple of hours I will eagerly check for a recipe/howto on what to do next, and then carefully follow those.
I am very optimistic now. Thank you all for assisting and to @olivierlambert for the big development today.

olivierlambert

So now we know the problem, the next step will be to solve it

Let's check what's going on in /boot with a ls -la /boot

nikade

@olivierlambert said in After installing updates: 0 bytes free, Control domain memory = 0B:

You have an issue: I'm pretty sure you are using Xen 4.13 while using the 4.17 tooling around, causing this problem. So the question is "why are you booting on 4.13?". Double check your Grub menu when you boot, to see that you actually boots on Xen 4.17

Nice catch, this is what community is all about

Dataslak

@olivierlambert
I love and respect your attitude

Agree wholeheartedly with @nikade

olivierlambert

So /boot/xen.gz is pointing to xen-4.17.3-4.gz, which sounds correct. So why you are still running on Xen 4.13? It's like you did not reboot, but since you showed me the Grub menu, I'm assuming you already did

It would be interesting to compare the existing xen file and see if it's the right one from our repo. Something is fishy here

olivierlambert

Can you md5sum xen-4.17.3-4.gz

From the mirror & RPM, I have f011721be0c7b57563e29ed282558da3

olivierlambert

Adding @yann in the loop in case I'm missing something obvious

yann

@Dataslak what does lsblk -o name,mountpoint,label,size,uuid show?

Dataslak

@olivierlambert

Dataslak

@yann
Hello Yann, thank you for pitching in.

yann

@Dataslak can you please request a commandline from GRUB (hit c on the boot menu), and issue the following commands:

echo $root
search --label --set root root-eqjpzg
echo $root

olivierlambert

Also a cat /proc/mdstat in the Dom0 would help.

Dataslak

@yann

Info: I am mirroring two M.2 SSDs ! Software RAID established by the installation routine of v8.3.
Could the mirror be broken and cause this somehow?

Dataslak

@olivierlambert said in After installing updates: 0 bytes free, Control domain memory = 0B:

Also a cat /proc/mdstat in the Dom0 would help.

Please forgive my ignorance: How do I execute this command in Dom0 ?

I've read https://wiki.xenproject.org/wiki/Dom0 and it helped a little. Do I run the command in the console within XOA?

yann

@Dataslak so it is choosing to "boot from the 1st disk of the raid1", we could try to tell him to boot from the 2nd one:

on the grub menu hit e to edit the boot commands
replace that search ... line with set root=hd1,gpt1
then hit Ctrl-x to boot

olivierlambert

@Dataslak Dom0 is "the host" (if you think it's the host it's not really but anyway), ie the machine you are connected to and showing results since the start

Dataslak

@yann
Wohoo!!
All VMs came up!
Host is not in maintenance mode.
Control domain memory = 12GiB
Stats are back
Etc....

As far as I can see (which is limited) everything looks good?

How can I see the status of the RAID1 and see if the mirror is intact ?

Dataslak

@olivierlambert
Thank you for explaining to me. I will look more into details when (if) I find time

Ah - I see you were ahead of me !

How can I interpret this? Raid1 OK? Synched? Ready to deal with a single drive failure?

How will XO inform me if one of the drives fails? Will I have to scour through logs, or will there be a clear visible notice in the interface?

olivierlambert

That's the problem. Your RAID1 lost the sync. And so it continued to boot on the disk out of sync, loading the old Xen from the boot while the rest (root partition) was up to date.

Dataslak

@olivierlambert
Since this happened on six servers simultaneously when applying updates through XO I guess we may have found an error ?

If so then all of this was not in vain, and I can be happy to have made a tiny tiny contribution to the development of 8.3 ?

Will the modification of the Grub boot loader be safe to apply to all remaining 5 servers? Or should I do some verification on each before applying it?

Is the modification of Grub what I will have to do if a drive fails? Change that one line from set root=hd1,gpt1 to set root=hd0,gpt1 or something?