Latest activity
-
JJohannes S reacted to UdoB's post in the thread Unterstützung für Proxmox VE 8 endet am 2026-08-31 with
Like.
Nur der Vollständigkeit halber, weil es bisher nicht erwähnt wurde: https://pve.proxmox.com/wiki/Upgrade_from_8_to_9 ...beschreibt das Vorgehen sehr detailliert :-) -
JJohannes S reacted to TErxleben's post in the thread Unterstützung für Proxmox VE 8 endet am 2026-08-31 with Like.
Ich würde den kompletten übergeordneten Ordner sichern. Frißt kein Brot und eine evtl. überflüssige Sicherung von kompletten Konfigurationseinstellungen tut nicht weh. Gilt nur, sofern du diesen nicht schon meintest und nur ein unglückliches Bild...
-
Sspencerh replied to the thread Proxmox Automated Installation DHCP issue.Hi, I just wanted to chime in and say that I'm having the same issue; it doesn't get DHCP in time but if I run `dhclient` immediately I get my IP(s).
-
Ffmar replied to the thread Network lost on Host when bridging physical interface.Im facing the same issue on hetzner robot while reinstalling an old proxmox on the same hardware. Did you end up fixing this? If so, could you provide your config for reference?
-
JJohannes S replied to the thread Datastore synced with Rclone broken?.It's possible, that doesn't make it a great idea. Regarding PBS sync only transfers chunks not already present on the target
-
Ddoma2k reacted to lanceh's post in the thread PBS: error fetching datastores - 401 Unauthorized (500) with Like.
The fix is to create an admin user shown in this video. You will then have no connection errors between the VE and PBS servers https://www.youtube.com/watch?v=aonFqwn-sa4
-
Oostseereiter1 replied to the thread Unterstützung für Proxmox VE 8 endet am 2026-08-31.ich habe den kompletten proxmox-config gesichert.
-
TTmanok replied to the thread Proxmox VE 9.2 – sporadic iSCSI NOP timeouts / DID_TRANSPORT_DISRUPTED with Dell PowerVault ME5 and Intel E810.Hey Everyone, I think there's something pretty overlooked here: Dell's ME5 documentation explicitly says that for iSCSI usage you must have symmetric flow control enabled on the interfaces. If the E810 and ME5 aren't agreeing properly on pause...
-
Oolivluca replied to the thread Datastore synced with Rclone broken?.see also https://forum.proxmox.com/threads/pbs-mounting-windows-smb-share-as-datastore.113164/post-835628 mmmh...
-
Aalexskysilk replied to the thread ZFS on SAN LUN(s).this is true, but have you ever implemented it? its slow as molasses. mdadm parity raid... brrr. THAT is brave. also, there is no "self healing" of any kind. This has the same problems as a HA zfs filer. the only "upside" is that you dont have...
-
BBu66as reacted to TErxleben's post in the thread Unterstützung für Proxmox VE 8 endet am 2026-08-31 with Like.
Ich würde den kompletten übergeordneten Ordner sichern. Frißt kein Brot und eine evtl. überflüssige Sicherung von kompletten Konfigurationseinstellungen tut nicht weh. Gilt nur, sofern du diesen nicht schon meintest und nur ein unglückliches Bild...
-
Ttotoxaraymond reacted to Impact's post in the thread Impossible to boot any VMs or container after Clonezilla backup, from original drive with Like.
Check pct start 107 --debug. Clonezilla (by default) tends to not clone the LVM-Thin part properly if you use that. I generally clone via dd through the installer's shell.
-
Ttotoxaraymond reacted to gfngfn256's post in the thread Impossible to boot any VMs or container after Clonezilla backup, from original drive with Like.
If you put the original SSD in the host, does it boot correctly? AFAIK Clonezilla will not alter the source drive at all. Your thread title suggests that the ORIGINAL SSD will not boot. (If this is not the case, change the title to reflect this)...
-
Ttotoxaraymond reacted to Impact's post in the thread Impossible to boot any VMs or container after Clonezilla backup, from original drive with Like.
Seems like your thin volumes are broken. I can't really explain why CloneZilla would have caused this for the source disk. I'd restore the guests from backups.
-
Ttotoxaraymond reacted to gfngfn256's post in the thread Impossible to boot any VMs or container after Clonezilla backup, from original drive with Like.
Change the title to reflect this. (Possibly: "Impossible to boot any VMs or container after Clonezilla backup, from original drive") I concur, this is probably not caused by Clonezilla cloning. However there is a chance that an already failing...
-
Ttotoxaraymond reacted to gfngfn256's post in the thread Impossible to boot any VMs or container after Clonezilla backup, from original drive with Like.
I assume you mean to include CTs & VMs starting correctly after host boot. Do you at least recall, if that drive was always sdg. Your above ouput of storage.conf above does not seem to reflect any zfs storage (at least in the Proxmox backend)...
-
Ttotoxaraymond replied to the thread Impossible to boot any VMs or container after Clonezilla backup, from original drive.the letter might have changed when i removed 2 failing drives. But it also changed a few months ago when I added new drives for a ZFS pool. This ZFS is not seen by proxmox. One of my VMs is a TrueNAS instance, the disked are passed by Proxmox to...
-
Oolivluca replied to the thread Datastore synced with Rclone broken?.btw, the storage box is also mountable with cifs
-
Oolivluca replied to the thread Datastore synced with Rclone broken?.while I don't think that using sshfs is a great idea, I'd like to know if, network wise, a pbs sync is as intensive as a pbs backup. After all rsync is quite good in transferring only the changes. Because it's simpler and because the...
-
JJohannes S replied to the thread Datastore synced with Rclone broken?.again why? Then you need a working PBS for restore, sonething you wouldn't need with another tool like kopia, restic or rsnapshot. These tools are also more storage-agnostic. PBS is the best tool for vm/lxc backups and rather bad for anything else.