XO 5.72 Storage Maintenance

jefftee

Hmmm... I seem to have painted myself into a corner using the new SR maintenance mode...

I run XO as a VM under XCP-NG and used XO to enable maintenance mode on the storage, without thinking in advance that my XO instance would not be able to disable maintenance mode!

I've tried to "xe vm-start name-label=xo" but it fails, presumably because its VDIs have been disconnected by the XO storage maintenance mode.

Going forward, I can prevent this by moving my XO instance VDIs to another SR, before I enable maintenance mode on the SR, but now that I've created a mess, how can I get my XO VM running again to disable maintenance mode on the SR?

Thanks

Danp

@jefftee You should be able to regain access to your SR using xe commands.

Use xe sr-list to find the UUID of the SR
xe sr-param-get uuid=<SR UUID> param-name=other-config will give you the contents of other-config (substitute the UUID you found above for "<SR UUID>"
Find the value of unpluggedPbds from above command
xe pbd-plug uuid=<PBD UUID From Above> will replug the PBD
xe sr-param-clear uuid=<SR UUID> param-name=other-config will clear the contents of other-config

jefftee

@Danp Thank you for the reply, but unfortunately I see no parameter named unpluggedPbds in other config:

xe sr-list

uuid ( RO)                : d9b6d7eb-36cc-dd18-d031-4f470963f747
          name-label ( RW): truenas1_iscsi0
    name-description ( RW): iSCSI SR [192.168.5.2 (iqn.2005-10.org.freenas1.ctl:freenas1-iscsi0; LUN 0: 10000001: 2 TB (FreeNAS))]
                host ( RO): <shared>
                type ( RO): lvmoiscsi
        content-type ( RO): 

xe sr-param-get uuid=d9b6d7eb-36cc-dd18-d031-4f470963f747 param-name=other-config

xo:maintenanceState: {"timestamp":1657297413067}; auto-scan: false

It seems that maintenanceState is set to the time I disabled the SR, but not sure how to proceed.

Any ideas?

Danp

@jefftee When I checked, mine had additional parameters --

xo:maintenanceState: {"timestamp":1657301646912,"shutdownVms":{},"unpluggedPbds":["9cfecf3a-47c2-9ec4-ae09-c348808b8f79"]}

Since your doesn't contain that, you may be fine with skipping that step.

Note: my other-config didn't contain any additional settings, you may need to readd auto-scan: false if that is important to your setup.

geoffbland

Could you install your XO VM on a completely different host/hypervisor - for example, on Hyper-V on you PC?

I have one XO VM running on my XCP-NG pool and another XO VM running on an UNRAID server - just for these kind of situations.

jefftee

@geoffbland Hi, thanks for the reply... That's what I wound up doing, installing XO from source on a Raspberry PI that I had. I used it to restore my XO image from backup, once I did that I had to restore all of my guests (12 of them total).

I could never figure out how to get my SR out of maintenance mode, so I wound up creating a new SR and restored each backup to the new SR. All back to normal after restoring the backup. Thank god XO backup works so well!

I learned the hard way that I need to move my XO disks to local storage before I enter maintenance mode for my iSCSI SR... Oh well, lesson learned!