Search results

Anyone got any ideas what the missing disk is and how to fix it. root@ubuntu:/# update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.13.19-4-pve Found initrd image: /boot/initrd.img-5.13.19-4-pve /usr/sbin/grub-probe: error: disk...

Followed to https://pve.proxmox.com/wiki/Recover_From_Grub_Failure guide and fixed the part which was now wrong , but now totally stuck : sudo vgscan Found volume group "pve" using metadata type lvm2 ubuntu@ubuntu:~$ sudo vgchange -ay 26 logical volume(s) in volume group "pve" now active...

good try on the proxmox boot tool , on a fully working system I tried following the guide with just a couple of changes , eg the mount points sda2 to boot/efi and the grub install and install didn't kill it , them tried the proxmox-boot-tool , and that didn't kill my system . So now it's the...

Thank you , I've spent a full day going nowhere , so I will try that on my test machine and make sure it doesn't do any thing stupid like deleting the LVM partition .

Thanks , from what they say that looks correct it makes 3 partition , I've looked at all the what to do with a grub fault on debian and don't think any would work. but I'm not sure how to use it on a dead system. The created partitions are: a 1 MB BIOS Boot Partition (gdisk type EF02) a 512 MB...

The recover from grub failure most be wrong ? I've loaded proxmox on a second machine to workout how to fix it and made a couple of VMs on it. I don't think from all I've read you can't mount a bios boot partition sda1 ? I think it should be sda2 ? root@pve:~# lsblk -o +FSTYPE,UUID /dev/sda*...

I've been told I made a double post on how to fix my problem , which is not really the same question I asked at first . O.K something stupid today while trying to use gpu passthrough which locked it up. after a reboot I got the grub recover screen and started following this ...

is the igpu reserving a large amount ram ? , by default my deskmini reserves 4gb for the igpu which is not needed .

Do you have issues with it, or is it just that it gets logged? no I can't see any problem and frigate is not reporting any errors other than syslog is just a few minutes worth of thousands repeated with the same error. no not tried the kernel 5.15 , I've found I can fix the error for a while...

Just started getting this error in the last few day , I think it is my frigate nvr using hardware encoding which is give me this problem. I'm using frigate inside proxmox which as not given me a problem before , so don't know if it frigate or Debian AMD igpu . Not install any extra drivers so...

o.k , so I need to edit eg "/etc/pve/nodes/pve/lxc/110.conf" ? , any clues what to add or which part of the manual ?

o.k , so in pve / system / network / you should have made a linux bridge to bridge enp2s0 interface to vmbr0 or it would have been made by default .

looking at your screen where is vmbr0 ? , on mine it is that which gets the ip address not the enp2s0 interface .

I'm looking into if I can converting my linux VMs running Emby and Home assistant into lxc containers. But I need to pass a usb zstick with Home assistant and pass a full zfs hard drive to Emby . A lxc container doesn't look to be as versatile as a VM with only memory , CPUs , and disk space...

have you checked with a ip a and tested if enp2s0 is the correct interface name and it is in /etc/network/interfaces. I added a nvme drive and after I added the drive the drive would not come up and after I lot of playing I found that it had change my interface from enp1s0 to enp2s0. So after...

use eg , qm set 102 -scsi2 /dev/disk/by-id/ata-xxxxxxxxxxxxxxxxxxxxxxxxxx first you need to find the disks id by ,"ls -l /dev/disk/by-id" , then which VM to send it too eg 102 , the scsi2 the second drive , if you need more repeat and increase the scsi number .

I think the answer is a definate YES , I did same thing of wanting to increase the size of the hard drive so closed down all the VMs and backed them up to my NAS. If you have added a hard drive directly to a VM with eg "qm set 104 -scsi1 /dev/disk/by-id/xxxxxxxxxxxxxxxx" you need to do it again...

I've compared your hardware configs to my windows 11 working setup and the only difference is in the EFI disk size at the end , mine says 4m yours says 528k the rest is more or less the same.

a Deskmini x300 with a Ryzen 5700g 8 core , 64 gb ram , 1 x 4 tb ssd , 1 x 1 tb ssd , 1 x 2tb nvme , 1 x 8tb backup drive . ( the power boost switched off in bios , all core 4.8ghz max) VM1 = Emby server , utorrent server VM2 = Home assistant + it's own docker apps VM3 = docker running pi-hole...

I've tried my 8 core , 16 threads and get all 16 Virtual cores in windows.