[SOLVED] Issue booting after upgrade 3.4 to 4

I

ilia987

Well-Known Member
Sep 9, 2019
284
14
58
39
Just finished upgraded with no errors\warnings and after reboot i have a problem:

gui is not working (black page) and in the journalctl -b i get :
Bash: 
...

Apr 12 17:46:04 pbs1 systemd[2036]: Startup finished in 219ms.
Apr 12 17:46:04 pbs1 systemd[1]: Started user@0.service - User Manager for UID 0.
Apr 12 17:46:04 pbs1 systemd[1]: Started session-1.scope - Session 1 of User root.
Apr 12 17:46:04 pbs1 sshd[2026]: pam_env(sshd:session): deprecated reading of user environment enabled
Apr 12 17:46:07 pbs1 chronyd[1692]: Selected source 185.18.207.158 (2.debian.pool.ntp.org)
Apr 12 17:46:07 pbs1 chronyd[1692]: System clock TAI offset set to 37 seconds
Apr 12 17:47:00 pbs1 proxmox-backup-proxy[1715]: lookup_datastore failed - unable to open chunk store at "/media/wd2-14t/.chunks" - No such file or directory (os error 2)
Apr 12 17:47:00 pbs1 proxmox-backup-proxy[1715]: unable to start datastore verification job v-d41bab1d-75fa - unable to open chunk store at "/media/wd2-14t/.chunks" - No such file or directory (os error 2)
the last two lines repeating every one minute

the storage is disconnected (it is a usb drive and can be deleted)


i can try to delete it proxmox-backup-manager datastore remove <name>, but does this action correct?


fixed this issue- modified datastore.cfg and verification.cfg (removed old data store)
 
Last edited:
ilia987 said:
Just finished upgraded with no errors\warnings and after reboot i have a problem:

gui is not working (black page) and in the journalctl -b i get :
Bash: 
...

Apr 12 17:46:04 pbs1 systemd[2036]: Startup finished in 219ms.
Apr 12 17:46:04 pbs1 systemd[1]: Started user@0.service - User Manager for UID 0.
Apr 12 17:46:04 pbs1 systemd[1]: Started session-1.scope - Session 1 of User root.
Apr 12 17:46:04 pbs1 sshd[2026]: pam_env(sshd:session): deprecated reading of user environment enabled
Apr 12 17:46:07 pbs1 chronyd[1692]: Selected source 185.18.207.158 (2.debian.pool.ntp.org)
Apr 12 17:46:07 pbs1 chronyd[1692]: System clock TAI offset set to 37 seconds
Apr 12 17:47:00 pbs1 proxmox-backup-proxy[1715]: lookup_datastore failed - unable to open chunk store at "/media/wd2-14t/.chunks" - No such file or directory (os error 2)
Apr 12 17:47:00 pbs1 proxmox-backup-proxy[1715]: unable to start datastore verification job v-d41bab1d-75fa - unable to open chunk store at "/media/wd2-14t/.chunks" - No such file or directory (os error 2)
the last two lines repeating every one minute

the storage is disconnected (it is a usb drive and can be deleted)


i can try to delete it proxmox-backup-manager datastore remove <name>, but does this action correct?
Click to expand...
It looks like pbs is trying to connect to the datastore that is missing. Can you reconnect the drive ?
 
ilia987 said:
probably not, i prefer to delete this storage, in the future ill make a new one, probably an s3 one
Click to expand...
PBS has the concept of a removable datastore, Those can be mounted/unmounted after a sync job.
Verify, Prune and Garbage Collection jobs are skipped if the removable datastore is not mounted when they are scheduled. Sync jobs start, but fail with an error saying the datastore was not mounted. The reason is that syncs not happening as scheduled should at least be noticeable.
Click to expand...
https://pbs-hetzner.croit.io:8007/docs/storage.html#removable-datastores
 
You must log in or register to reply here.
Top Bottom
Back