Hello,

Hey, for future, um, not well informed, admins. If you hose your local attached storage used by an SR, you may need to drop back and punt. This was a development xcp-ng host with an XOA instance using the locally attached storage for backups.

So, no significant loss if I need to drop the SR and re-set up a VDI for xoa-backups.

After forcing a reboot during an xcp-ng upgrade, I failed to repair the disk. I will not argue foreign the host to hardware reboot was stupid. That failed miserably; the LVM partition would not fsck, even after leaving it for days. Nor from GUI could I delete the SR - it would just spin and do nothing - not even an error message in the GUI logs.

So after a bit of research hand find a helpful post by @olivierlambert logging into the xcp-ng instance and:

xe sr-forget uuid=<<UUID of screwed up storage>>

I then recreated the VDI for the XOA instance. Finally, I checked to ensure the new VDI was attached, created a new ext4 partition for the xoa-backups, verified it mounted, and restarted the backups.

Please ask if you find yourself stuck and need any clarification on any of this.

Regards,

Bill

All,

For anyone that happens into this thread and wondered if the well known installer script was confirmed working correctly. It was fixed as noted above and tested on a fresh install, The rule of thumb, a bit tongue in cheek, when it comes to these files is:

• Leave the config in /etc[/xo]/xo-server/config.toml alone.
• Set the over rides in ~/.config/xo-server/config.toml home .
• Use only /etc[/xo]/xo-server/config.toml and you're on your own.

On the last point point I mean that you need ensure whatever you use there contains attributes for the original file plus your overrides. Copying the sample config packages/xo-server/sample.config.toml to /etc[/xo]/xo-server/config.toml may not capture all of the attributes that need to be set.

@julien-f If missed the spirit of this please, please correct me.

@julien-f @olivierlambert

Submitted PR to change attribute documented as 'host' to 'hostname'.
https://github.com/vatesfr/xen-orchestra/pull/4681

billgertz opened this pull request in vatesfr/xen-orchestra

closed fix(docs/configuration): `host` → `hostname` #4681

@olivierlambert @julien-f @Danp

Thanks to everyone for the clear, helpful support. Impressed.

@julien-f

Thanks, I'll lay my cards more directly on the table next time. Glad you're not taking it personally. I'll use that repo for PRs. Thanks again.

@julien-f

Again not trying to pick a fight but your own documentation says to use .xo-server.toml here when compiling from the sources.

Shouldn't this be changed from:

Now you have to create a config file for xo-server:

$ cd packages/xo-server
$ cp sample.config.toml .xo-server.toml

To something like:

Now you have to create a config file for xo-server:

$ cd packages/xo-server
$ cp sample.config.toml config.toml

This is what happened when the 3rd party script ran. I can submit PRs for the GitBook docs, but I don't see anyway of doing that from GitBooks. Is there a repo for this GitBook doc in which I can submit a PR? I'll be happy to submit a PR to the 3rd party script repo as well.

@julien-f

Along with .xo-server.toml as you pointed out earlier and I've experienced :-/. Thanks again for looking into this.

@julien-f @olivierlambert

Thanks for getting back to me, not trying to pick a fight. Loading config.toml.orig is not clear based on what the comments say:

# This file is automatically looking for at the following places:
# - `$HOME/.config/xo-server/config.toml`
# - `/etc/xo-server/config.toml`

xo-server is loading config.toml.orig that just doesn't seem to square with the comments. If it's documented elsewhere in the file and I just missed it please help me find it Just the same shouldn't this behavior be documented in https://xen-orchestra.com/docs/configuration.html? I can't be the only person to make .orig style backup copies before making changes?

@olivierlambert

Thanks again for the help, and will submit a PR but under which repo for the documentation? Looks like your using GitBook and I'm clueless on submitting PRs on GitBook. Is there some sort of way to submit changes to your doc set from within GitBook?

I ran into the problem anyway due to the load any toml behavior. xo-server startup loaded my backup of the original config (config.toml.orig). That was not really expected.

@olivierlambert @julien-f @Danp

Looks like the .xo-server.toml is installed by the the well known installer script, from xo-install.sh script:

.
.
.
echo -e "${INFO} Activating modified configuration file"
                mv $INSTALLDIR/xo-builds/xen-orchestra-$TIME/packages/xo-server/sample.config.toml $INSTALLDIR/xo-builds/xen-orchestra-$TIME/packages/xo-server/.xo-server.toml
.
.
.

Looks like we either need to document the 'load any toml' behavior or get the other script to declare uncle and let your script drop down the default config.