Search results

Update: Powering off seems to have the LXC backup complete in 30 mins: INFO: starting new backup job: vzdump 113 --remove 0 --compress lzo --mode snapshot --node HPProliantDL360PGen8 --storage FourteenTBExpansionUSB4 INFO: Starting Backup of VM 113 (lxc) INFO: Backup started at 2021-01-17...

Yes, I suppose it is on. I'm not sure what overhead there can be? Really frustrating to have upgraded to 1 Gbp/s and only get 22 MB/s. If I really needed to I can connect it directly to another computer with USB 3 but it defeats the purpose of shared networked storage.....

I am downloading directly from a Proxmox host. I've not seen this option in the BIOS before - I would need to schedule a period to turn the host off and pull out the HDD to trigger BIOS screens. Even weirder, a lot of disk read is happening but not the same transfer speed (you'd expect after...

I am getting roughly just under 1 Gbps/s on this test, but when I try and download a file from server on the network via a USB (3.0) HDD, I expect at least USB 3 speeds. Everything is connected to the 1 GB network, all nodes have 1 GB connection, so why does my download only get 5-10 MB/s...

I passed though my USB device to a Windows VM and God knows why, Windows thought the USB device was a hard drive that needed repairing. The process was interrupted (sigh). I put the drive to an actual computer and can't open it. Windows reports the drive structure is corrupted and unreadable...

You were right, that there was an issue with local. I moved away to a NFS and the problem was resolved. :)

I have a backup job that's been trying to run for over 15 hours. Backups for this LXC has been killed manually for over a week now because it doesn't finish. There's no local location (with enough space) except NFS drives. The LXC is only 30-38 GB's in size and the same NFS drives work for...

I've checked the target HDD and the disk (image) does exist. WARNING: You have not turned on protection against thin pools running out of space. WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full. Logical...

Glad it helped.

I've not seen this error before. This is a newly connected drive, restart probably won't solve this one: command '/usr/bin/qemu-img info '--output=json' /mnt/pve/SWAPFourTBExpansion/images/106/vm-106-disk-3.qcow2' failed: got timeout could not parse qemu-img info command output for...

pct restore --rootfs 8 102 vzdump-lxc-102-2021_01_08-08_30_02.tar.zst -storage local-lvm I had to make the disk larger, although I do not know why.

Creating filesystem with 786432 4k blocks and 196608 inodes Filesystem UUID: b091a25d-4e2d-4506-8f0f-88e70c6cb0a3 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Allocating group tables: 0/24 done Writing inode tables: 0/24 done...

Suddenly my LXC's (on one node) lost their networking. I checked /etc/network/interfaces and any change was overridden. I set the DNS up in proxmox, no change. If I do: ip route add default via - followed by the gateway all is fine, but after a reboot it is gone. I don't know why this is...

I'm suddenly running into this problem and when I restart the LXC's/nodes I need to run this manually?

If this comes up again I will try this. I believe it was a mixture of issues including changing device name for the mount. I'm marking this as closed.

The disk was the easiest - the recovery ISO wouldn't connect to a shared network drive from another remote Windows PC on the network. FTP/NFS is not supported/not working. This issue is resolved using the disk. Normally, with a proper OS, NFS/FTP, etc would be fine, and I wouldn't be asking this.

Correct, I managed to get NFS sharing working. It's a bit tempermental though and I often need to restart nodes. And it seems everytime I need to run on startup to share to other nodes?: exportfs -a && systemctl restart nfs-kernel-server Any idea why? Have I failed to create a service that...

It would be, but I am not running a FULL OS. That wouldn't work. The drive is tiny and I can't access explorer. I'm not making it complicated, my recovery system isn't a full OS, and I can only mount a disk, ISO or network drive (I tried, couldn't). This is the only option: Separate disk it...

It's Windows based. Whatever I do, I suppose I'll be mounting a disk on linux? (NTS)? Since disk mounting on Linux is a bit... confusing for me, would it be easier to setup a Windows VM, mount a new disk, add data, detach and add it to the VM I need it on?

Correct. I cannot add the USB to the VM, I added a disk separately to another VM, but couldn't seem to mount it to add some data to put. Any pointers for this?