Debug Proxmox issues
This tutorial explain, how you can give us all information, we need to start debugging your proxmox issues.
2 minute read
All of the commands below are run trough SSH on the proxmox machine.
Export all script
Connect to your proxmox vm
nano gather_info.shCopy the following and paste it into your terminal:
#!/bin/env bash echo "==================================" echo "EXPORTING DATA, PLEASE WAIT" # Delete old sysinfo run echo "Step 1.1" rm -r /tmp/sysinfo 2> /dev/null # Create sysinfo directory echo "Step 1.2" mkdir /tmp/sysinfo 2> /dev/null # Get all VM's echo "Step 2" pvesh get /cluster/resources --type vm --output-format json > /tmp/sysinfo/vm.json 2> /dev/null # Get all network interfaces echo "Step 3" cat /etc/network/interfaces > /tmp/sysinfo/network.txt 2> /dev/null # Get VM configs echo "Step 4.1" mkdir /tmp/sysinfo/vm_config 2> /dev/null echo "Step 4.2" cp /etc/pve/qemu-server/* /tmp/sysinfo/vm_config/ 2> /dev/null # Get all connected usb devices echo "Step 5" lsusb -v > /tmp/sysinfo/lsusb.txt 2> /dev/null # Get all pci devices echo "Step 6" lspci -vvv -k > /tmp/sysinfo/lspci.txt 2> /dev/null # Get system hardware echo "Step 7" lshw -json > /tmp/sysinfo/lshw.json 2> /dev/null # Get disk info echo "Step 8" lsblk > /tmp/sysinfo/lsblk.txt 2> /dev/null # Get all ips echo "Step 9" ip a > /tmp/sysinfo/ipa.txt 2> /dev/null # Compress sysinfo echo "Step 10" currentTime=$(date --rfc-3339=ns | sed 's/:/-/g' | sed 's/ /_/g') XZ_OPT=-9 tar -cpJf /root/$currentTime.tar.xz /tmp/sysinfo 2> /dev/null echo "==================================" echo "FINISHED EXPORTING DATA" echo "COPY $currentTime.tar.xz to your PC"Press Ctrl+O and Enter to save the file
Press Ctrl+X to exit nano
bash gater_info.shWait for the program to finish
Copy the .tar.xz file to your pc. (If you are using MobaXterm, you can use the file viewer on the left and drag the file to your Desktop)
- Alternatively you can you can of course use any other file transfer program, supporting SCP or the scp command itself
Send the .tar.xz file to our support
Karbon300 specific
If you are working on a Karbon300, there is an issue, that the external network interfaces are incorrectly labelled.
Below is the correct interface mapping:
1→1
2→3
3→2
Last modified February 17, 2023: update (#208) (ea731fc)