• iscsi shows "No Storage Repositories Detected"

    Unsolved Compute
    6
    0 Votes
    6 Posts
    110 Views
    okynnorO
    I have since tried a little more digging, The error seems to suggest that the block drive SR is not available/file not found? The iscsi block drive is sitting inside a TrueNAS scale server snapshot backups too. But let me know if I"m doing this correctly as per the command below to try to use the xe pbd-plug command to solve this issue or not: [15:25 xenserver-tiger ~]# xe sr-list name-label="iSCSI virtual disk storage2" uuid ( RO) : 7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f name-label ( RW): iSCSI virtual disk storage2 name-description ( RW): host ( RO): xenserver-tiger type ( RO): lvmoiscsi content-type ( RO): user [15:27 xenserver-tiger ~]# xe pdb-list sr-uuid=7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f Unknown command: pdb-list For usage run: 'xe help' [15:28 xenserver-tiger ~]# xe pbd-list sr-uuid=7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f uuid ( RO) : d4050fae-ec84-efac-62a1-d3d62b4fb879 host-uuid ( RO): 3986c16a-a9e0-4ebf-83a0-4438d8bd5916 sr-uuid ( RO): 7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f device-config (MRO): SCSIid: 36589cfc000000dca3287604eb99e625a; targetIQN: iqn.2005-10.org.freenas.ctl:scuzzy-ng2; target: 192.168.1.5; port: 3260 currently-attached ( RO): false [15:28 xenserver-tiger ~]# xe pbd-plug uuid=d4050fae-ec84-efac-62a1-d3d62b4fb879 Error code: SR_BACKEND_FAILURE_47 Error parameters: , The SR is not available [opterr=no such volume group: VG_XenStorage-7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f], [15:29 xenserver-tiger ~]# tail -n 50 /var/log/SMlog | grep -i -E "error|exception|47|opterr" Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread] FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-scsid/36589cfc000000dca3287604eb99e625a' Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread] ): EXCEPTION <class 'FileNotFoundError'>, [Errno 2] No such file or directory: '/dev/disk/by-scsid/36589cfc000000dca3287604eb99e625a' Nov 20 15:29:46 xenserver-tiger fairlock[3380]: /run/fairlock/devicemapper sent '70710 - 10994.070830647' Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread] Error in SR.after_master_attach Input/output error Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread] ***** generic exception: sr_attach: EXCEPTION <class 'xs_errors.SROSError'>, The SR is not available [opterr=no such volume group: VG_XenStorage-7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f] Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread] opterr='no such volume group: %s' % self.vgname) Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread] ***** LVM over iSCSI: EXCEPTION <class 'xs_errors.SROSError'>, The SR is not available [opterr=no such volume group: VG_XenStorage-7f968d45-56dd-a6aa-83d2-bd33dd2a8e5f] Nov 20 15:29:46 xenserver-tiger SM: [70710][MainThread] opterr='no such volume group: %s' % self.vgname)
  • XCP-ng 8.3 updates announcements and testing

    Pinned News
    814
    1 Votes
    814 Posts
    1m Views
    A
    @vxgmichel @lmolina Pools updated, working so far. Rolling reboot failed because of backup (CR) conflicts. CR backups cause RPU to fail. RPU causes CR backups to fail.
  • Missing vdi which is a base for a delta

    Unsolved Backup
    18
    0 Votes
    18 Posts
    1k Views
    poddingueP
    @blueh2o I think the two things you saw fit together, at least going by what I see in the mirror code. The 1 differencing tag only says that this one backup's disk is a delta, which is normal for an incremental; the key sits further back in the chain, which I think is why the health check could still rebuild the whole ~280 GiB disk. And as I wrote a few posts up, the mirror reads the parent of each delta on Ark and then asks each target whether it already has it, so last night's error would mean the Synology is missing d08f1acc for that one VM (fb7fca7d), not that Ark is broken. That brings us back to Florent's suggestion from the older thread, deleting that VM's most recent backups on the Synology so they get sent again, though I can't tell you why the Synology lost that base in the first place. At least it's down to one VM out of 56 last night, against 16 in October.
  • Backups in OX v6

    Backup
    8
    3
    0 Votes
    8 Posts
    237 Views
    poddingueP
    @flakpyro from your screenshot and a look at the code, I think the VM name is already stored on each of those "backup VM" tasks, but the XO 6 task list just shows the generic label instead, so it might be a small change rather than a big missing piece (I haven't checked whether the side panel shows it). It could be worth its own post on feedback.vates.tech so it gets votes. The closest one I found is about the job's detail panel rather than the task list: https://feedback.vates.tech/posts/60/xo6-backup-summary-is-a-stacked-jumbled-and-cryptic
  • 0 Votes
    2 Posts
    56 Views
    poddingueP
    I tried your steps on a lab XOA running 6.10, and I could reproduce it, but only once I had unpinned the side panel. With the panel pinned (the pin button at the top of the panel), switching tabs left it alone in my test, so that might do as a workaround for now. Did you unpin it at some point, or is your browser window on the narrow side? From a quick look at the code, I think the open or closed state of that panel is kept in the browser's local storage, which all tabs of the same site share, so one tab closing it closes it for the others, though I may be misreading it. You have the steps written down already, so I'd pass them to @Team-XO-Frontend; whether it's meant to work that way is their call, not mine.
  • 1 Votes
    5 Posts
    528 Views
    lmolinaL
    Hello, the current update candidate includes fixes related to this issue. Note that it is still under testing.
  • packer plugin signing key

    Infrastructure as Code
    4
    0 Votes
    4 Posts
    457 Views
    poddingueP
    @enkaskal I need to correct my reply above, I got two things wrong. The plugin is ours after all: ddelnano/packer-plugin-xenserver is the repo's old address, it moved to vatesfr/packer-plugin-xenserver (where you filed #212), and GitHub just redirects the old link, which I read on our IaC docs page and jumped to the wrong conclusion. The key isn't missing either, I just didn't look in the right place: it's the signing key the Terraform Registry lists for vatesfr/xenorchestra, so you can fetch it from there. curl -s https://registry.terraform.io/v1/providers/vatesfr/xenorchestra/0.41.2/download/linux/amd64 \ | jq -r '.signing_keys.gpg_public_keys[0].ascii_armor' > xenorchestra-signing.asc gpg --import xenorchestra-signing.asc gpg --verify packer-plugin-xenserver_v0.12.0_SHA256SUMS.sig packer-plugin-xenserver_v0.12.0_SHA256SUMS On my machine the last command reports a good signature from 0DD2E92A7A0F682BC29F87073084D82948625D89, still a key in Dom Delnano's name from before the move. I'm honestly not sure how much trust that gives you beyond "the registry vouches for the same key", so I'd leave that part to the folks on #212 who know the release side better than me. Sorry for the detour.
  • 0 Votes
    6 Posts
    147 Views
    C
    @poddingue said: Do your hosts have public IP addresses on their management interface? I'm asking because the XOSTOR docs carry a warning about that setup (here) : according to them, the LINSTOR satellites listen on port 3366 without authentication, and an outside party can connect to them and get in the way of the real controller. If yours are reachable from outside, I think a different address each time would fit that, but I haven't checked it against a setup like yours. Thanks for offering to keep the cluster in that state for a bit. I'd point @Team-Storage at it before you reboot anything, since they're much better placed than me to say what's worth collecting. Does it look like you need to examine anything? I'm okay keeping it as-is for another day or two, but it would be good to know.
  • backup mail report says INTERRUPTED but it's not ?

    Unsolved Backup
    125
    5
    0 Votes
    125 Posts
    50k Views
    T
    @Pilow, I saw your update that the affected backups show SUCCESS in XOA, are present on the remote, and have been restored successfully. Given that, your suggestion about the report being generated before the final status is available seems reasonable. Bastien’s delay test looks like a useful way to check that. You mentioned the first day after applying it was clear, although with the issue appearing intermittently, it would probably take several days of reports to know whether it helped. I also saw your later test: one- and two-second delays still produced interrupted reports, while three seconds appeared to work over two days. The team has since merged a five-second delay. If you’re still seeing the original mismatch, can you confirm whether your current XO build includes that change? That would help establish whether there’s another timing issue, or whether the fix simply hasn’t reached the installation yet. For the next occurrence, it may help to keep the email timestamp and the run log for that same job, particularly if only one VM in a larger job is marked interrupted in the report. Posting those alongside the XO version would give the team something specific to compare. On a related note, Mail Backup X could be useful as a separate routine if you also want backups of your email accounts. It’s a convenient tool that works across the spectrum and is compatible with IMAP-based email accounts, offers incremental backups and encryption support.
  • 9 Votes
    67 Posts
    19k Views
    C
    @benapetr That's great - thank you for clarifying - really looking forward to the next release!
  • 0 Votes
    19 Posts
    992 Views
    poddingueP
    Thanks, both of you, for putting the tests on the GitHub issue (https://github.com/vatesfr/xen-orchestra/issues/10741). Florent and the devs have everything in one place now. @frb94, sorry the NFS side pushed you back to Veeam for the VM backups. I can't promise anything on timing, but I'll keep an eye on the issue and post here if it moves.
  • 0 Votes
    15 Posts
    399 Views
    O
    @jr-m4 hello, thanks for your feedback, I've gathered your feedback and will work with our designer to improve the UX/UI. Thanks again for testing
  • Slow SR Creation

    Unsolved Management
    15
    1
    0 Votes
    15 Posts
    2k Views
    I
    @tjkreidl everything looks normal. I also shared SOS report with @goulven I hope I'll get a feedback on slowness.
  • 🛰️ XO 6: dedicated thread for all your feedback!

    Pinned Xen Orchestra
    334
    7 Votes
    334 Posts
    230k Views
    coolsport00C
    @julienXOvates Superb Julien. I figured it was in your really long list that you all are working on. Appreciate the response!
  • xoa kernel update crash the VM ! linux-image-6.1.0-55

    Unsolved Management
    4
    2 Votes
    4 Posts
    153 Views
    poddingueP
    Thanks for the heads-up, @Pilow. In case someone finds this later, Debian tracks it as bug #1154101, an ext4 regression in kernel 6.1.192-1, which installs as -55. They marked it fixed in 6.1.192-2 on 16 November. That one installs as linux-image-6.1.0-56-amd64, so it's the -56 in your proxy screenshot. The XOA in my test lab never picked up -55, and apt-cache policy there already offers 6.1.192-2 as the next kernel. I think unattended-upgrades will jump straight to the fixed one, but I haven't watched it do that. If you put the hold in place, you'll want sudo apt-mark unhold linux-image-amd64 once you're on -56. Otherwise, if I understand holds correctly, the box stops getting kernel updates, including the security ones. It might be worth a mention to @Team-XO-Backend too, since XOA installs these kernels on its own.
  • Full backup failure when upgrading XOce

    Unsolved Backup
    13
    0 Votes
    13 Posts
    386 Views
    P
    @acebmxer said: So when you used my script it worked aside from the backup hiccup? Yes, so far what I have tested. Seems like You put some effort int this one, keeping my fingers crossed It' using node v24.22.3
  • New Tools 9.2.445 update failure

    Unsolved Management
    5
    1
    0 Votes
    5 Posts
    270 Views
    F
    @dinhngtu I will mention that the package was deployed via windows SCCM deployment tools so that may have also played a part in leaving the old product code behind. After running the above script we were able to deploy 9.2.445 via SCCM without issue and no old product codes were left behind.
  • MFA for console access

    Unsolved XCP-ng
    2
    0 Votes
    2 Posts
    182 Views
    poddingueP
    I haven't tried Duo on a host myself, so this comes from reading an 8.3 dom0 rather than from experience. The first thing I'd watch is that XAPI checks the root password through PAM as well. /etc/pam.d/xapi just includes system-auth, so my guess is that a Duo module placed in system-auth would make every password login to XAPI (XO's connection to the pool, xe -pw, XO Lite) ask for a factor it can't give. The physical console is less simple than it looks too: tty1 runs xsconsole, and on my 8.3 host it checks root against the password-auth PAM service by handing over just the password, so I'd expect a module that asks a second question to make that login fail rather than prompt. Also worth knowing before an audit: software from outside the XCP-ng repos isn't supported in dom0 (https://docs.xcp-ng.org/installation/requirements), and as far as I can tell from rpm, /etc/pam.d/xapi isn't marked as a config file, so an update would put it back. Anyone who has been through this for real will know more than me.
  • 0 Votes
    5 Posts
    337 Views
    poddingueP
    If I follow your excerpts, there are two different problems stacked here. One is the LinstorSR attach giving up on what looks like a one-second controller hiccup, which is the @Team-Storage side. The other is xenopsd leaving state behind on both hosts after the failed sync point 4, so that every later run trips over it. I think that half belongs to the toolstack people rather than storage, so I'm adding @Team-XAPI-Network too. I can't judge either part myself, so I'll leave it with them.
  • Backup failures after VHD to QCOW2 conversion

    Unsolved Backup
    8
    0 Votes
    8 Posts
    516 Views
    poddingueP
    Thanks for sharing those. I can't read SMlogs well enough to add anything useful myself, so this is really one for @Team-Storage. One thing though: if I read the link right, it expires on 23 November, so it would be good if someone grabbed the files before then.