Weird, i thought it was being mapped to my second drive this whole time.

Is there a way for me to delete the existing SR and recreate it under the second drive i have?

@Danp

[21:41 xcpng ~]# df -h
Filesystem                                                                                                 Size  Used Avail Use% Mounted on
devtmpfs                                                                                                   1.4G   20K  1.4G   1% /dev
tmpfs                                                                                                      1.4G  208K  1.4G   1% /dev/shm
tmpfs                                                                                                      1.4G  9.4M  1.4G   1% /run
tmpfs                                                                                                      1.4G     0  1.4G   0% /sys/fs/cgroup
/dev/nvme0n1p1                                                                                              18G   17G     0 100% /
xenstore                                                                                                   1.4G     0  1.4G   0% /var/lib/xenstored
/dev/nvme0n1p3                                                                                             512M  3.0M  509M   1% /boot/efi
/dev/nvme0n1p5                                                                                             3.9G  219M  3.5G   6% /var/log
/dev/mapper/XSLocalEXT--710681af--cb0f--65bf--7593--5c3be2151f62-710681af--cb0f--65bf--7593--5c3be2151f62  938G  130G  761G  15% /run/sr-mount/710681af-cb0f-65bf-7593-5c3be2151f62
tmpfs                                                                                                      269M     0  269M   0% /run/user/0

Hi All,

Started using xcp-ng recently and still learning the ins and outs of it. I do the updates manually via the shell and I get this error:

yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Excluding mirror: updates.xcp-ng.org
* xcp-ng-base: mirrors.xcp-ng.org
Excluding mirror: updates.xcp-ng.org
* xcp-ng-updates: mirrors.xcp-ng.org


One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

    1. Contact the upstream for the repository and get them to fix the problem.

    2. Reconfigure the baseurl/etc. for the repository, to point to a working
       upstream. This is most often useful if you are using a newer
       distribution release than is supported by the repository (and the
       packages for the previous distribution release still work).

    3. Run the command with the repository temporarily disabled
           yum --disablerepo=<repoid> ...

    4. Disable the repository permanently, so yum won't use it by default. Yum
       will then just ignore the repository until you permanently enable it
       again or use --enablerepo for temporary usage:

           yum-config-manager --disable <repoid>
       or
           subscription-manager repos --disable=<repoid>

    5. Configure the failing repository to be skipped, if it is unavailable.
       Note that yum will try to contact the repo. when it runs most commands,
       so will have to try and fail each time (and thus. yum will be be much
       slower). If it is a very temporary problem though, this is often a nice
       compromise:

           yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Insufficient space in download directory /var/cache/yum/x86_64/7/xcp-ng-base
   * free   0
   * needed 100 k

I find it weird because last week everything was fine. I did a clean up with yum clean all and removed the var/cache/yum directory and its still persistant. Any suggestions?