Search results

  1. J

    Renaming node -> volumes not reachable

    Hi Fiona! Can you please tell me exactly which files could be helpful? All I find is a /var/log/pve/tasks folder with tens of logfiles in it, whether for PVE or PBS... Is there way to fix this? Thanks for your help!
  2. J

    Renaming node -> volumes not reachable

    Yes, this folder is empty on the PBS server. Actually, there's a /mnt/datastore/backups folder on the PBS server, and a /mnt/pve/backups folder on the PVE, so I may has mistaken one for the other. However, both are totally empty (ls -al). It seems some operations were correctly performed in...
  3. J

    Renaming node -> volumes not reachable

    Surprinsingly... root@pbs:~# ls -al /mnt/datastore/datastore1 ls: cannot access '/mnt/datastore/datastore1': No such file or directory I SSHed into the PBS server and confirmed there's no datastore1 folder. There's however a 'backups' folder, but it's empty. This folder was normally used by...
  4. J

    Renaming node -> volumes not reachable

    Hi Fiona, Here's the output of the various commands you requested for PVE, probably too much... root@pbs:~# cat /etc/proxmox-backup/datastore.cfg datastore: datastore1 comment gc-schedule daily path /mnt/datastore/backups/datastore1 root@pbs:~# lvs File descriptor...
  5. J

    Renaming node -> volumes not reachable

    Hi Fiona, thanks for the information! I suspect sde1 is a USB disk which is used by a VM as a video files storage (Open Media Vault), so I won't bother you with this... Regarding PBS: The fingerprint has the correct value in storage.cfg. PVE is able to ping PBS. The datastore cannot be...
  6. J

    Renaming node -> volumes not reachable

    Thanks Fiona! Here's the command output: root@LAB-server1:~# lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda ├─sda1 │...
  7. J

    Renaming node -> volumes not reachable

    Hi @fiona, Here the outputs for the commands above: root@LAB-server1:~# pveversion -v proxmox-ve: 7.4-1 (running kernel: 5.15.158-2-pve) pve-manager: 7.4-19 (running version: 7.4-19/f98bf8d4) pve-kernel-5.15: 7.4-15 pve-kernel-5.13: 7.1-9 pve-kernel-5.4: 6.4-4 pve-kernel-5.15.158-2-pve...
  8. J

    Renaming node -> volumes not reachable

    Hi all, Any advice on this issue? Is there any way to "reattach" the backups + local-lvm volumes to the new names? Thanks in advance for any help!
  9. J

    Renaming node -> volumes not reachable

    Dear Community, On my lab servers, I decided to rename one node, which had already running VMs. I followed the instructions given in the video here: https://www.youtube.com/watch?v=2NzLYKRVRtk and managed to perform the renaming without any problem. However, I have some issues with existing...
  10. J

    Backup command fails at opening chunck store

    Hi all! Problem solved! But I didn't do anything! Just upgraded the system some days ago, rebooted and bam! backup is working again! I'll probably never know what was going on... Thanks to all for your help and advice!
  11. J

    Backup command fails at opening chunck store

    Hi all! Couldn't find time to shutdown and open the server... Is there any way to check the physical disks status from PVE interface?
  12. J

    [SOLVED] Reset passwords in a VM

    Great, this did the trick! Thanks a lot to all for your help!
  13. J

    [SOLVED] Reset passwords in a VM

    Dear Community, I'm facing an issue with an Ubuntu VM, which I didn't use for a long time: the password I carefully stored in my password manager is rejected by the system. I can't SSH into the VM as the SSH server has probably not been installed and I obviously can't use the "boot in recovery...
  14. J

    Backup command fails at opening chunck store

    Thanks for this analysis! A damaged disk is highly possible as the issue appeared after a power supply interruption! As far as I remember, the server uses an array of 1TB 2.5" disks working in RAID5 mode, so the damaged disk may have been rebuilt unless it's dead... I'll shut the serve down and...
  15. J

    Backup command fails at opening chunck store

    Here's the output of the commands on the PBS server: root@pbs:~# ls -lah /etc/systemd/system/mnt-datastore* -rw-r--r-- 1 root root 240 Aug 19 2021 /etc/systemd/system/mnt-datastore-backups.mount root@pbs:~# cat /etc/systemd/system/mnt-datastore-backups.mount [Unit] Description=Mount...
  16. J

    Backup command fails at opening chunck store

    Here's the information on storage, but unfortunately I don't remember how the datastore was setup (this is a home server I setup 3 years ago and it ran perfectly till the storm)...
  17. J

    Backup command fails at opening chunck store

    This is the point where the system stumbles on missing device: there's no /datastore in /mnt! I don't know why it's missing and how to mount it manually... Is there any command in the GUI that could force /mnt/datastore/backups/datastore1 to mount?
  18. J

    Backup command fails at opening chunck store

    Hi all, I've launched the command pve7to8 to prepare for upgrade and got the following warning: proxmox-backup-client failed: Error: unable to open chunk store 'datastore1' at "/mnt/datastore/backups/datastore1/.chunks" - No such file or directory (os error 2) WARN: storage 'backups' enabled...
  19. J

    Backup command fails at opening chunck store

    Hi Hannes, Whether on the PVE or PBS node, I get cannot access '/mnt/datastore/backups/datastore1': No such file or directory... The datastore folder has just vanished. Thanks for your help!
  20. J

    Backup command fails at opening chunck store

    Dear Community, I've recently noticed an error in the backup process of my Proxmox VE (v7.4-18) + BS server, following a power supply interruption (due to stormy weather). The exact message says ERROR: Backup of VM 1000 failed - VM 1000 qmp command 'backup' failed - backup connect failed...