Search results

  1. D

    [SOLVED] Installation problem - BootDevice not found

    @oguz I made some investigation and I'm sending you a bunch of screenshots, hope they help! I don't think it's an issue with the BIOS. 1) I installed Proxmox VE 6.1 from a USB stick on a brand new WD SSD and it didn't show up as a boot device: 2) Then I installed Debian 10.3 (everything in...
  2. D

    Can I use an uploaded ISO image from another node in the cluster?

    I've uploaded some popular linux .iso images to my first Proxmox VE: I Now I created a second node called proxmox2. Can I use the .iso images stored on the original 'proxmox' node to create a new VM from them? The second node only shows me local images: I know I can SCP the images over, I...
  3. D

    Connection Refused by ProxMox

    Ouch, I actually have to say it was my stupidity. I don't know how, I don't know why, I forgot to add port 8006 to my machine. Sorry for the confusion. I'm having the same problem and the only coincidence I can see is that it happened to me today for the first time and today I've installed a...
  4. D

    [SOLVED] Installation problem - BootDevice not found

    Hi, I have the same problem on an Asus Republic of Gamers laptop: 1) I boot Proxmox VE 6.1 (iso release 1) from a USB media 2) I install Proxmox on a brand new (unformatted) WD 500GB SSD drive 3) Everything goes fine, everything is super-fast (country, IP address, root pass) 4) But when I try...
  5. D

    USB drive becomes inaccessible after device changes from /dev/sda to /dev/sdb

    @LnxBil thanks. For me it was a secondary disk and the UUID of the disk remained the same (which I found strange) so actually after replugging /etc/fstab started just working.
  6. D

    USB drive becomes inaccessible after device changes from /dev/sda to /dev/sdb

    Hi @LnxBil - you are a genius, thanks! Confirming that detaching the Virtio virtual disk and reattaching it as SCSI worked! If it helps anyone, here is how to do it: For the record, my guest VM is Ubuntu 18.04.4 LTS
  7. D

    USB drive becomes inaccessible after device changes from /dev/sda to /dev/sdb

    Hi @LnxBil - the problem is actually present all the time, the virtual drive never ever connects to the guest. However, I opened /var/log/syslog on both the **host** and **guest** machines, then I've issued a cat /dev/vdb (which is the virtual disk) and below is the result - the lines in red...
  8. D

    USB drive becomes inaccessible after device changes from /dev/sda to /dev/sdb

    Hi @LnxBil - sure, here it is: 1) dmesg | grep -v mce - is totally empty on the Proxmox host. dmesg from the host is attached in the dmesg_host.txt file 2) dmesg from the guest is attached in the dmesg_guest.txt file 3) I'm sorry but what do you mean by 'Also please "run" into the problem in...
  9. D

    USB drive becomes inaccessible after device changes from /dev/sda to /dev/sdb

    Hi @LnxBil - thanks for your response. I was also afraid that the disk might have problems, although I don't see any indication in S.M.A.R.T. and it's a pretty new drive, the machine has never lost power. dmesg: (nothing else - just the following repeating indefinitely) [2734239.386950] mce...
  10. D

    USB drive becomes inaccessible after device changes from /dev/sda to /dev/sdb

    I have a problem with an external storage on Proxmox :( I added a USB drive storage to my proxmox a few months ago this way: 1) Connected USB drive to Proxmox machine and added as an LVM storage on /dev/sda: 2) Created a new 1000 GB virtual hard drive on it: Everything was working fine...
  11. D

    hibernate a VM via qm command

    @Jannoke Interesting approach! Do you issue it on the host machine or inside the VMs? Do you need to wait for a certain time after the 'echo' command?
  12. D

    Problem to assign vlan to vmbridge (Proxmox VE 6) / pve-bridge error 512

    For those who might run into the same problem, I confirm that the VLAN aware bridge worked for me. This is what I did: 1) WebUI -> DataCenter -> node (proxmox) -> System -> Network -> vmbr0 -> VLAN aware -> OK 2) Reboot proxmox 3) Stop VM 4) VM -> Hardware -> Network -> Edit -> VLAN ID...
  13. D

    hibernate a VM via qm command

    @Jannoke I did a small test and for me it did create a new volume: root@proxmox:~# qm suspend 103 --todisk 1 Logical volume "vm-103-state-suspend-2020-05-10" created. root@proxmox:~# qm resume 103 Resuming suspended VM activating and using 'local-lvm:vm-103-state-suspend-2020-05-10' as...
  14. D

    hibernate a VM via qm command

    @Jannoke Although I don't have any exact knowledge of this, this might be useful from the documentation: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_hibernate
  15. D

    MacBook Pro 2017 - ethernet connection via USB-C Hub

    I believe my fix could solve the original problem as well though. Ping @Soggir
  16. D

    MacBook Pro 2017 - ethernet connection via USB-C Hub

    Hi @matrix, This thread was created by another user (not me), can I mark still it as solved? Thanks!
  17. D

    MacBook Pro 2017 - ethernet connection via USB-C Hub

    SOLVED! I solved the problem using exactly these steps: 1) Run lsusb to see that my network interface is detected (note: this might take a few seconds after you plug in the device) 2) Run ip link show to see that the network interface is present (it's be something like enx………..) 3) Noted the...
  18. D

    hibernate a VM via qm command

    @masgo Yes, I think it does. I did: 1) qm suspend 100 --todisk 1 2) rebooted PVE 3) VM started automatically - lastlog from the VM showed last reboot about a month ago Therefore I think yes, it works like you described.
  19. D

    MacBook Pro 2017 - ethernet connection via USB-C Hub

    I have a similar issue. Connected a USB-C Gigabit network adapter to my laptop. lsusb Bus 004 Device 002: ID 0bda:8153 Realtek Semiconductor Corp.RTL8153 Gigabit Ethernet Adapter ip link show 1: lo 3: wlp2s0 13: tap101i0 14: fwbr101i0 ... Sorry I had to type in the info above so I haven't...