Renaming node -> volumes not reachable

No, sorry I didn't have time. It seems the link you posted doesn't work anymore. In any case, having somebody with Linux experience look over it might be the best option for you. As I can't guarantee I'll get around to it before the holidays.
 
OK, thanks Fiona for all your efforts!
One last question: do you have any idea if reverting the renaming process could help solving the issue?

Thanks for any help!
 
jlgarnier said:
OK, thanks Fiona for all your efforts!
One last question: do you have any idea if reverting the renaming process could help solving the issue?

Thanks for any help!
Click to expand...
I don't think it would. You need to find out what exactly happened within the PBS VM/from its perspective. I.e. why is the .chunks directory gone or where did it end up? You can still share the logs here of course, maybe somebody will have time to look through it.
 
Hi all!

I'm reviving this thread as I'm seeking additional advises. I gave up trying to understand why the previous 'backups' volume is not accessible anymore (due to some issue during a node renaming operation), but I'd like now to recreate the missing volume.

Here's the context:
  • The PVE 'datacenter' is using the volume 'backups', of type 'pbs'.
  • This volume is not accessible from the (one an only) node on this datacenter; clicking on the volume returns "error listing snapshots - 400 Bad Request (500)".
  • The PBS server uses a Datastore which is (obviously) not accessible either; clicking on Datastore returns "Error : unable to open chunk store at "/mnt/datastore/backups/datastore1/.chunks" - No such file or directory (os error 2)". as /mnt/datastore/backups/ is empty.
What I'd like
  • Recreate PBS' datastore; there's a 'Remove Datastore' button, but I didn't dare to use it yet...
  • Point the PVE backups to the new datastore
Is there any straightforward procedure to do so?

Thanks in advance for any help!
 
You must log in or register to reply here.
Top Bottom