@stormi Now that you mention that, I did perform an ISO upgrade I should not have performed would I known. Remember a few posts above. My bad...
Posts made by ThierryC01
-
RE: XCP-ng 8.3 beta π
-
RE: XCP-ng 8.3 beta π
Yeah... point is, the mounting point has been deleted and the fstab overwritten during the updates... as I mentioned in my post above.
-
RE: XCP-ng 8.3 beta π
@Tristis-Oris Except that your method is to create the SR, mine already exists, is full of .iso files and could be wiped doing your method!!! The SR exists, I can see the list of files that should be there but it is marked as "disconnected".
-
RE: XCP-ng 8.3 beta π
@Tristis-Oris Well, this is how local disks are mounted right?
-
RE: XCP-ng 8.3 beta π
I applied the very last batch of XCP-ng 8.3 updates and after a smart reboot (which took forever to complete and did not resume all my VM automatically), I have lost my ISO storage: the folder "/ISO" has been deleted by the update and the fstab has been overwritten. This is becoming annoying, I never ever had to "repair" anything related to my storage in my 20 years of using Vmware Esx but this is already the second time I have to do it in my 2 years of using XCP-ng and the very first time an update deletes a mounting point. I understand 8.3 is still a beta, hence my feedback.
-
RE: XCP-ng 8.3 beta π
@stormi said in XCP-ng 8.3 beta :
@ThierryC01 said in XCP-ng 8.3 beta :
For your information, the connection error icon in "Settings"-->"Remotes" that appears when entering a wrong password once, then connecting anyway afterwards with the correct password is still present after all the 8.3 updates.
Is this an XCP-ng issue?
After the latest XOA update, the annoying error icon is gone! So it was an XOA issue
-
RE: XCP-ng 8.3 beta π
For your information, the connection error icon in "Settings"-->"Remotes" that appears when entering a wrong password once, then connecting anyway afterwards with the correct password is still present after all the 8.3 updates.
-
RE: XCP-ng 8.3 beta π
@stormi Thanks for your help, my VMs are back online but there is no more stats in the tab "stats" for any VM and the host, the log page gives this error multiple times:
vm.stats { "id": "3c807c46-bfdc-f33a-5954-4de92bcf3f08", "granularity": "seconds" } { "message": "Unable to get the true granularity: 5", "name": "FaultyGranularity", "stack": "FaultyGranularity: Unable to get the true granularity: 5 at XapiStats._getAndUpdateStats (file:///opt/xen-orchestra/packages/xo-server/src/xapi-stats.mjs:305:13) at Api.#callApiMethod (file:///opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:445:20)" }
-
RE: XCP-ng 8.3 beta π
@stormi said in XCP-ng 8.3 beta :
Everyone: we are about to release XCP-ng 8.3 Beta 2!
It was delayed by one month due to the UEFI issues discussed above, now fixed.
The last thing we need is your feedback on the updated installation ISO: https://updates.xcp-ng.org/tmp/xcp-ng-8.3.0-beta2-test3.iso
I hope I have more success than with the test2 ISO for which I don't remember getting any feedback
Hi,
I have updated my xcp-ng 8.3 beta 1 with this xcp-ng-8.3.0-beta2-test3.iso and while it boots, I have lost all my VMs and no SR are recognized, I am left with a just a server that sits on its own and I cannot connect an oldest XOA to it. If you need more info (logs, anything) tell me now as I really need my VMs back, I think I should be able to revert to the previous version if the backup worked. I only have one homelab server so this is the situation where you kind of update your live prod...
Before upgrading, I applied all the 8.3 patches that were pushed recently.
-
RE: XCP-ng 8.3 beta π
@archw That is weird, I did the 8.3 beta patch bulk updates and no problem at all with all my uefi VMs. They don't have secure boot enabled.
-
RE: XCP-ng 8.3 beta π
@florent on the 8.3 beta1 with the latest XOA available I have tested the creation of a new NFS remote with success.
I tried to create a new SMB connection with a wrong password to test the edit and it worked perfectly, the only thing is that the alert that showed up during the wrong password connection does not disappear once the connection is established with a correct password even after multiple page refresh, disable, enable, refresh.
-
RE: XCP-ng 8.3 beta π
@laurentm No, for some stupid reason, the LVM volume was 100% full and I could not write any disk configuration nor expand the volume until I got rid of some logs.gz. All this happened during an update of XOA, I think there should be some safeguard in Linux to avoid such situation.
I will install a new XOA VM somewhere else as a backup since the container does not update to the latest commit. I hope they could sync the backup configuration.
-
RE: XCP-ng 8.3 beta π
Okay... I have to apologize for the pollution of this topic, I was running a container version of XOA (Xen Orchestra, commit 422a2) which I use in emergency cases such as my actual up to date XOA VM which crashed due to an LVM issue and was trying to restore. I managed to get my actual XOA VM running and everything is fine, no problem whatsoever, all backups are here using the XOA VM, available to restore and all. I really feel bad for wasting everyone's time. I will update my emergency XOA container from now on, I thought that all information were stored on the Xcp-ng server, good to know.
-
RE: XCP-ng 8.3 beta π
@florent That is the theory yes, but in reality, editing the password fails.
-
RE: XCP-ng 8.3 beta π
@olivierlambert That is not true, a remote folder is still a remote folder and we should be able to backup any VM wherever we need/want. The issue here is when the login fails once, there is no way to edit the logon password and succeed. It was working very well until I upgraded from 8.2 to 8.3 and then had to restore a VM from backup. No grudge here, just a fact.
What I call a mumble jumble naming of folder is just that every VM is identified by a uuid in the same folder if all backups are stored in the same place which makes it difficult to sort should we need to either use a backup on another platform or delete to regain disk space.
I am just fighting to get a basic feature working: edit the password of a connection without having to delete the record and start over.
-
RE: XCP-ng 8.3 beta π
@florent I found the source of the problem, I already had it when I was trying the backup feature in 8.2 and it is with the remote settings: if there is a logon issue, there is no way to edit the password, save and go with it, you have to re-create the remote entirely which is extremely frustrating. For some reason, the password encryption does not behave as expected, when, editing the password, it is replaced by "obfuscated-xxxxxxx unique ID xxxxxxx" so it cannot work.
The message I get when trying to connect to a remote folder or just after editing the password and save
The obfuscated password displayed when editing
And the error log for the logon attempt with the correct password:
remote.test { "id": "365964ae-ea3c-41a5-80eb-0c5eb595f01d" } { "messageName": "session_setup_step2", "params": {}, "message": "STATUS_LOGON_FAILURE (0xC000006D) : The attempted logon is invalid. This is either due to a bad username or authentication information.", "code": "STATUS_LOGON_FAILURE", "name": "Error", "stack": "Error: STATUS_LOGON_FAILURE (0xC000006D) : The attempted logon is invalid. This is either due to a bad username or authentication information. at SMB2Forge.request (/etc/xen-orchestra/node_modules/@marsaud/smb2/lib/tools/smb2-forge.js:22:15) at /etc/xen-orchestra/node_modules/@marsaud/smb2/lib/tools/smb2-connection.js:108:11 at Object.<anonymous> (/etc/xen-orchestra/node_modules/@marsaud/smb2/lib/tools/message.js:15:15) at Socket.<anonymous> (/etc/xen-orchestra/node_modules/@marsaud/smb2/lib/tools/smb2-forge.js:71:31) at Socket.emit (events.js:400:28) at Socket.emit (domain.js:475:12) at Socket.patchedEmit [as emit] (/etc/xen-orchestra/@xen-orchestra/log/configure.js:118:17) at addChunk (internal/streams/readable.js:293:12) at readableAddChunk (internal/streams/readable.js:267:9) at Socket.Readable.push (internal/streams/readable.js:206:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23) at TCP.callbackTrampoline (internal/async_hooks.js:130:17)" }
-
RE: XCP-ng 8.3 beta π
@stormi I edited the fstab to mount my ISO SR and it is back online. Next time, I will remember to backup this file too before any upgrade.
-
RE: XCP-ng 8.3 beta π
@florent Remote is connected all the time, it is a NAS and each VM has its own folder otherwise it is just a mess of mumble jumble folder names that no one knows which VM it is. Refreshing the backup jobs or restore page does nothing.