Search results for query: unknown filesystem

My PC has a B660 chipset and there is only one Intel USB controller which is in the same IOMMU group as System RAM and lacks available reset mechanism. Actually I could passthrough the intel USB controller and use it with all basic USB 2.0 functions work as expected. But USB 3.0 could only work...

mount: /proc/fs/nfsd: unknown filesystem type 'nfsd'. what? where's the nfsd modu.... oh dear. I'm a moron. This system was previously set up for ganesha. which requires the nfsd module blacklisted. problem solved. Thank you for shoving my nose in it :)

Hello everybody, After tinkering a little big with PBS, I have uninstalled it and installed PVE too in my second node. Then I have tried to set up replication between both of my nodes. Everthing worked well at the end. Then I tried migrating a CT and a VM to my new node. After that, in the web...

Jup, you got 3 types of storages. LVM for the root filesystem ("local"), LVM-Thin for VMS/LXCs ("local-lvm"), then your big ZFS storage on pool ZFS-Data and then another LVM or LVM-Thin storage on sdg. You can't combine ZFS / LVM/ LVM-Thin. You use a raidz1 pool which can'T be expanded yet. If...

...restarting my server, it doesn't boot anymore GRUN loading.. Welcome to GRUB! error: no such device: 542d67217ce82747. error: unknown filesystem. grub rescue> Can anybody give me support, what to do now? I've found some information in the internet, but I'm not sure if they are applicable to...

Hi, I'm having the same issue with an array of 12 4tb HGST drive. How can I spot the drive that is the culprit? I've passed that command to all my drives: sgdisk --zap-all /dev/sd'n' Thanks! root@pbs:~# time proxmox-backup-debug api get /nodes/localhost/disks/list --skipsmart 1...

Thanks for your feedback. I think that was always the case though? IIRC (did not verified) one had to pass --ostype unmanaged to the pct create call, are you sure you created your "old" unmanaged CTs without that option?

I activated the test repository, updated and rebooted the node. The fresh created managed LXCs do start if firewall is checked and unchecked. There are some errors/warnings in the log. The "old" unmanaged LXCs do also start now if firewall is checked and unchecked. There are some...

Guess what: Toggling "firewall" in LXC 206 makes the container starting or fail starting. Cross check: Toggling "firewall" in the newly created container LXC 104 also makes the container starting or fail starting. But enabling "firewall" for the net1 interface in LXC 207 does not make the...

Thanks that makes more sense, so for my current disk the path is then /dev/disk/by-path/pci-0000:00:05.0-scsi-0:0:0:1. I'm running debian cloud image as stated and it uses cloud-init 20.4.1 but it seems the following doesn't work disk_aliases: #Found a bug saying the name should be disk not...

...mount an external drive to one of my Proxmox nodes. I added it to /etc/fstab, but when I run "mount -a", I get the following error: "mount: /mnt/externaldrive: unknown filesystem type 'extfat'." I tried installing/updating exfat-fuse and exfat-utils, but still same error. Any help is...

Yes i configured one repo to test hardware acceleration to bypass to linux container. Did an apt update and installed one package and deleted it again. I dont remeber which one this was. root@proxmox:~# apt show base-files Package: base-files Version: 12.3 Status: install ok installed Priority...

Hallo, Meine Proxmox Instanz hat jetzt ewig perfekt funktioniert und ich war immer auf latest unterwegs, sobald ein Update zu machen war. So auch heute, wo eine Menge an Updates waren, habe ich diese durchgeführt. Wie dann im cmd popup ein GRUB installer daher kam, hab ich etwas Panik bekommen...

...from a catastrophic power failure and running into dead ends... hoping someone can help. My PVE node was booting to a grub - unknown filesystem error. I was able to run fsck on /pve/root and bring it back to bootable but running into this problem: # lvconvert --repair /dev/pve/data The...

Hi, in this case it's expected unfortunately, because pvestatd (which is responsible for collecting status information) will get stuck when trying to query the hanging NFS mount. We are planning to rewrite pvestatd in the future to make it more robust in such scenarios. But hanging NFS mounts...

Hello everyone So, somehow, I was able to get the system to not crash. I'm still not entirely sure what I did differently, but I do have a suspicion. For future reference if anyone wants to experience the rush of hundreds of lost TiB as well and fancies to run an rm -rf /var/lib, here's a...

...from sdd to sdc... On the second host it is excatly the same. Never had this before. :~# mount /dev/sdc1 /mnt/ mount: /mnt: unknown filesystem type 'LVM2_member'. ##pvscan pvscan /dev/sdd: open failed: No medium found PV /dev/sdb VG ceph-2de4f3c5-7f5f-442d-b1d0-3c78790aa08b...

So I'm having a strange issue after following steps in #6 above. I removed a PBS datastore (named "backup") and now trying to recreate - I was testing creation of an encrypted destination for PVE backups. I have removed the existing datastore: systemctl disable...

ceph health details [/B] root@node2:~# ceph health detail HEALTH_WARN 1 filesystem is degraded; 1 MDSs report slow metadata IOs; 6 osds down; 2 hosts (2 osds) down; Reduced data availability: 484 pgs inactive, 52 pgs down, 29 pgs peering; Degraded data redundancy: 24966/267340 objects...

Just in case it helps: ceph -s root@node2:~# ceph -s cluster: id: cfa7f7e5-64a7-48dd-bd77-466ff1e77bbb health: HEALTH_WARN 1 filesystem is degraded 1 MDSs report slow metadata IOs 6 osds down 2 hosts (2 osds) down...