Search results for query: unknown filesystem

...... Found linux image: /boot/vmlinuz-6.8.12-19-pve Found initrd image: /boot/initrd.img-6.8.12-19-pve /usr/sbin/grub-probe: error: unknown filesystem. Found linux image: /boot/vmlinuz-6.8.12-15-pve Found initrd image: /boot/initrd.img-6.8.12-15-pve Found linux image...

Using an 8GB USB: - First attempt was with Rufus 4.11, similar to the issue I'm encountering now when I select graphical installation it will fail, haven't tried terminal. - Second attempt I reformat the USB, this time I used Etcher (balenaEtcher) and it will also fail when attempting to run...

This does not sound like the same issue as reported in this thread. Please check the systemd journal on the PBS side. Further, make sure you have enough memory available on the PBS and check the io pressure.

unfortunately I had another stall with the test kernel. root@pve:~# uname -r 6.17.11-4-test-pve

As can be read in https://forum.proxmox.com/threads/accidentally-increased-size-of-a-disk-for-a-client-how-do-i-decrease.178622/ I have had an accident with my setup when I tried to resize some of my LVs. I am left with two specific problems regarding size and a warning I do not understand...

Hello, I've been having stalls on PVE as well. I'm a new Proxmox user and I never installed it on the desktop I'm using. In my setup I have a PVE on a desktop with i5 Intel, 16GB RAM, an consumer ssd where I install pve, LXCs, VMS and PBS as an LXC and a WD Red 6TB HDD. PBS has 2 cores and 2GB...

Hi, I saw your post on a discord server, I was facing the same problem but used the suggestion at https://forum.proxmox.com/threads/start-unmanaged-container-from-the-web-ui.68727/post-308058 with a couple of modifications and that has got me most of the way to where I want to be - hope it helps...

Hi I need some help please. I am trying to get an oci container up and running. "searxng/searxng" and I get this error: () Logical volume "vm-100-disk-0" created. Logical volume pve/vm-100-disk-0 changed. Creating filesystem with 2621440 4k blocks and 655360 inodes Filesystem UUID...

Hey! Got this funny response when creating an oci container in Proxmox 9.1.1 "Formatting '/mnt/pve/Store4/images/101/vm-101-disk-0.raw', fmt=raw size=8589934592 preallocation=off Creating filesystem with 2097152 4k blocks and 524288 inodes Filesystem UUID: be563e9d-1bfb-49c0-b917-82be562b609a...

...disc in the pool. I have managed to add the new disc to the pool but now can replace the old disc, get "is in use and contains a unknown filesystem" Any help would be welcome root@mwnt:~# zpool status -v pool: rpool state: DEGRADED status: One or more devices is currently being...

...... Found linux image: /boot/vmlinuz-6.17.1-1-pve Found initrd image: /boot/initrd.img-6.17.1-1-pve /usr/sbin/grub-probe: error: unknown filesystem. Found linux image: /boot/vmlinuz-6.14.11-4-pve Found initrd image: /boot/initrd.img-6.14.11-4-pve Found linux image: /boot/vmlinuz-6.14.11-3-pve...

The container was created with a bytes-per-inode ratio of 16384. This is not enough for a larger volume as this would require 7222714368 inodes, but ext* supports only up to 4294967295. As there is no way to choose the filesystem on container creation, you should use mountpoints. I could also...

Hello all. New to Proxmox so I am not familiar with all of the screens.. However I believe and entry is missing on my New Proxmox setup.. This server has been running for about 3 weeks and first day back from vacation none of the VM are running or will start. Data-storage units are all...

Hello, Been a 'browser' here for a few years, and been using Proxmox for several, but just started a new server, and have this never-before-seen issue. As per title, not only the VMs, but all the drives are marked as unknown (the VM numbers are wonky because I'm moving VMs from another node...

Add Some Info: df -h root@pve20:~# df -h df: /run/pve/import/esxi/ESXi227/mnt: Transport endpoint is not connected Filesystem Size Used Avail Use% Mounted on udev 126G 0 126G 0% /dev tmpfs 26G 6.1M 26G 1% /run /dev/mapper/pve-root 94G...

Let's try to change that: root@pve:~# stat /rpool/data/subvol-101-disk-0/usr/sbin/newuidmap File: /rpool/data/subvol-101-disk-0/usr/sbin/newuidmap Size: 35288 Blocks: 42 IO Block: 35328 regular file Device: 0,60 Inode: 4044 Links: 1 Access: (0755/-rwxr-xr-x) Uid...

Thanks for responde, please show me.

In Proxmox when you add an iSCSI storage and the status shows as unknown, it usually means that Proxmox is not able to verify the availability of the target in the way it does for other storages like NFS or CIFS. This is by design. The Proxmox storage plugin for iSCSI does not actively mount or...

...but when manually booting in SuperGrub2 it gave errors for ALL of the OS's: "error: cannot unload referenced module," and "error: unknown filesystem." I'm hoping anyone can assist with getting PBS installed correctly on this machine. Thank you. **SOLVED** after 10 days with nobody's help...

Alright, I think I've downloaded the right repo (was a debian command, I'm running Ubuntu) Did the, Apt update, Apt upgrade and apt full-upgrade and ran these commands with the following output ip a curl -k https://localhost:8006 curl -k htts://[lan_ip_of_pve]:8006 systemctl |grep pve pveversion...