Problem with mounted hard drive after restore

[Noobie]

Hello everyone,

Unfortunately, I've had a mishap and need your help.

I have an LXC container running an SMB server. I imported a backup from it. Now there is a small question mark on the “SMB_Node_200 (pve)” storage device, and when I go to the storage device, I see nothing and get the message: storage ‘SMB_Node_200’ is not online (500).

Unfortunately, I don't remember how I mounted/created the “SMB_Node_200 (pve)” disk. I think I must have mounted it as a disk in “200 (lcx-SMB)” or shared a folder in front of it. Then I must have shared a folder starting from “200 (lcx-SMB)” and mounted it as a network drive in “Datacenter.”





However, when I look at the command history for “200 (lcx-SMB),” the folder shared on the SMB server does not exist (backup was up to date).



Are the files gone now? What information do you need to help me if necessary?

Thank you very much in advance!

 

[niteshadow]

You probably lost all the data in the container. Look for "vzdump" files in the container data and check used size to make sure.
It's bad form to have the target backup device be a vm/ct on the host server.
You could accidentally wipe the data of the container, maybe inadvertently backing up ct 200 onto itself ???
If the intention is to keep backups on the pve host, you could have simply used a "local" storage or a directory.
Otherwise a networked backup storage should be on another machine, like a NAS.

 

[Noobie]

Hi

thanks @niteshadow for your input. Unfortunately the files are to small. So i think the datas are lost...

I have another question:
I installed Proxmox on a 2 TB SSD. However, I cannot use the full 2 TB. The local disk only has 120 GB for backups, etc.

Is there a way to expand this?

 

[niteshadow]

Is that the boot drive ?
I think it defaults to LVM and it is possible to expand it.
Personally I don't create VM/CT on the boot drive , but I had to expand a few times (32GB boot drive).
If I remember correctly the default does not allocate all the available disk space.
Check the physical/logical volumes to see available space. You can then extend the volume and resize the file system.

 

[stamox]

Hello,
It depends on how you organized the disk. Does it use LVM?
can you run lsblk and drop here?

 

[alexskysilk]

you created a circular dependency. your host is dependent on a datastore served by a guest, but the guest needs the host to run.

I would begin by disabling the SMB_NODE_200 datastore. Next, make sure the container is running, the storage is available, and the nfs service is running. Then attempt to MANUALLY mount the share on the host. once that is successful you SHOULD be able to re-enable the datastore.

Once all is running, consider the wisdom of doing this instead of just mounting the store locally on the host and be done with it.

 

[Noobie]

All right. How would you set up a Proxmox system? Two hard drives, one for data (lxc, backups,...) and the other for the basic system?

Can I separate the 2tb ssd afterwards?

@alexskysilk Unfortunately this did not work

 

[Noobie]

And Here is the output of lsblk

 

[niteshadow]

Generally I use one or two small disks for Proxmox; if it's big enough, it can also be used for local backups. Your "local" storage can handle backups (no need to complicate with an CT setup).
For me data is VMs and containers; these will be on another disk (or preferably mirrored disks).

Backups should be sent to an external system, such as a NAS (using NFS for example).
The local backup is nice but generally you don't want to rely on backups on the host server. You will loose those easily when you have a bad config or source disk fails.

 

[alexskysilk]

All right. How would you set up a Proxmox system?

payload on the host. you can share directories to your containers as mountpoints. Instead of your data living INSIDE a VM logical volume, it can live on your normal filesystem (eg, /srv/my_important_data)

For me data is VMs and containers; these will be on another disk (or preferably mirrored disks).

Can I separate the 2tb ssd afterwards?

that makes things easier and safer, but the approach remains the same. In general you want to avoid comingling your boot and payload storage.

@alexskysilk Unfortunately this did not work

What didnt?