HI,
I would work on the proxmox command line:
your DVD-RW drive is attached to an enabled USB port on the proxmox server and is provided with enough power ;-)
first: what USB Drive <=> USB DVD-RW device? You can get it with the lsusb command:
lsusb
....
Bus 001 Device 002: ID 0e8d:1887...
Hi educruiser,
have a look at my last post: "now I more often work with external USB DVD-Burner (it's more easy ;-)"
With a USB DVD-RW drive you can do it with two klicks in the Proxmox WebGUI
And work with a burning Tool like CDBurnerXP where you have a better overview on the existing DVD...
Hi Dominik,
no, the backup isn't encrypted.
This command in the same directory works for the "qemu-server.conf.blob", an you get the whole text file
proxmox-backup-debug inspect file /srv/pbs4tpool/pbstore/vm/100/2022-04-19T23:45:02Z/qemu-server.conf.blob --decode -
EDIT:
now I try it on an...
one more question please:
In the new Version PBS 2.1.x the described solution above works for me
proxmox-backup-debug inspect file /srv/pbs4tpool/pbstore/vm/100/2022-04-19T23:45:02Z/qemu-server.conf.blob --decode -
but:
I'm looking for a way to read the pbs log files on command line, and...
Hi hughbiquitous,
thanks for the reply, and welcome on Proxmox Forum!
For me the above also was the first time working with iSCSI, also now I more often work with external USB DVD-Burner (it's more easy ;-)
Regards,
maxprox
Hi DHY,
have a look at this thread:
https://forum.proxmox.com/threads/simple-backup-method-to-usb-drive.21294/
for example:
1:
First you have to mount some usb disk
2:
backup your VM(s), for example:
vzdump 8206 --mode stop --compress lzo --dumpdir /var/lib/usbmount/sicherung/8200_zammad
(the...
perhaps the problem is solved found:
I had a deeper look to the LVM. The ''lvscan'' shows me two inactive LVs, and the ''vgchange -ay" is prohibited at first because a lv_tmeta in second because a lv_tdata.
After I deactivate both, the lv_tmeta and the lv_tdata, I can activat needed main LV...
Hello
I have a new small proxmox pve System on an old ACER / Gateway Server with an entry level ACER / Gigabyte Mainboard.
There is only one Container which does not start. A LVMthin Install, no ZFS.
The last thing I have done was to clone the Proxmox System SSD to a second and same SSD, 1:1...
Dank dir für den Hinweis, das müsste ich noch mal versuchen, kann sein dass ich bei diesen ersten Tests übersehen habe die Replikation raus zu nehmen...
Zur Zeit habe ich noch nicht DIE (für mich) passende Lösung zur Wiederherstellung des PromoxBackupServers, der bei mir als LXC Container läuft...
also have a look under "Hardware": BIOS, Display, Machine should be "Default", without dedicated drivers also SCSI Controller should be "Default"
CD/DVD "Do not yous any media"
Is the OS Type correct under the "Options" ?
...
Hi Gustavo,
I think it is because the boot device? Have a look under the VM Options and there under "Boot Order"
and start the VM under the Command-Line with "qm start VMID" there you get a long line in which you get the error, perhaps ....
try it
regards,
maxprox
I can not exactly explain the solution for it, because I've never been affected by this before.
But I would try this:
either what is in the wiki:
https://pve.proxmox.com/wiki/ZFS:_Tips_and_Tricks#Replacing_a_failed_disk_in_the_root_pool
under: "Grub boot ZFS problem" and...
ja, wie du schreibst: " in Summe eine bessere Haltbarkeit": SuperDOM= 32GB; IronWolf = 250GB das wäre knapp 8 (acht)! mal so viel "SuperDOMWPD" ;-)
und 34 TBW zu 300 bei der Seagate ist auch einiges. Sprich: wenn ich keine physischen Gründe habe, nehm ich doch lieber die Seagate.
HI,
OT: gibt es mit diesen Supermicro SuperDOM Teilen Erfahrung, wie lange die im Dauerbetrieb halten?
Wenn darauf "nur" das OS (Proxmox) läuft?
Im gegensatz zu günstigeren Standard SSDs mit 5 Jahren Garantie, haben die nur 2. und bereits eine günstige Crucial MX500 250GB hat eine 3mal so hohe...
NEIN, kann man vergessen.
Bitte nicht nach machen. Das funktioniert alles nicht wirklich. Mit dem von mir vorgeschlagenen (nicht funktionierenden) Workaround sind zwar anschließend noch alle Daten da. Beim neuen mounten des umbenannten logical volumes greift aber das problem mit den bind-mounts...
today I install the stable virtIO drivers, Version x.185
I control the installation of the correct Version in the VirtIO Balloon and Serial Driver, the SCSI pass Through controller, VirtIO Ethernet, and so on. Everything without any fault.
The Task manager say: it’s running as it should, also...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.