Search results

Hi @ajpion , welcome to the forum. The system (Linux or Windows) allows for one default gateway. Any gateway beyond default one are not default by definition and need to be scoped for a particular subnet) destination. If your client and storage are on the same subnet - you don't need a...

Hi @mbaltera , welcome to the forum. There is no configuration option you can change as PVE does not use LIBVERT. The deploy tool should be talking PVE API, not underlying hypervisor (QEMU/KVM). Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

Get a backup first, then see if there are any available BIOS/firmware updates. Even if there are not, what you posted should not bother you too much. With the large amount of 3rd and 4th tier hardware out there, backed by generic BMC software - the OS is telling you that its not happy with what...

In the future, if you do decide to mount a device that might potentially disappear - you should use on the options discussed here: https://unix.stackexchange.com/questions/53456/what-is-the-difference-between-nobootwait-and-nofail-in-fstab Blockbridge : Ultra low latency all-NVME shared...

https://forum.proxmox.com/threads/storage-for-small-clusters-any-good-solutions.181106/#post-840048

The USB related line in your /etc/fstab is 6th from the top, including empty line preceding it. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hi @CptnBlues63 , Keep in mind that this is not PVE specific, but rather generic Linux administration. Any publicly available resource can generically guide through this with sufficiently detailed prompt. At a high level, either remove the systemd file: rm /etc/systemd/system/mnt-usb.mount Or...

It seems like you have a USB disk in your fstab/systemd, and that disk has either failed or is not available any more. This blocks the normal boot. Are you not able to enter the root password to access the rescue shell? You can follow this guide...

Hi @RodolfoRibeiro , thank you for clarifying. This matches my initial understanding of your situation. SAS and iSCSI are transfer and connectivity protocols. While the article I suggested is using iSCSI as example, once you are beyond basic storage connectivity, the concepts are the same...

CloudInit is an industry standard way to distribute templates that are compatible with all major cloud providers. While PVE is not a Cloud Infrastructure per se, it is a hypervisor that many cloud providers user. PVE has built-in support for minimal required CI, as well as an ability to supply...

According to Veeam documentation https://helpcenter.veeam.com/docs/vbr/userguide/pve_system_requirements.html?ver=13 it is compatible with 9.1 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Have you tried a different browser? A cloud virtual VM with various browsers? Tried to get a new server/VM on the same network and access BMC via CLI (if thats possible with OVH)? If all else fails, reach out to OVH support - a client error while trying to access hardware BMC of an OVH server...

Hi @tka222 , Given that your storage is FC based, the migration (presuming you mean live migration of VM between PVE hosts) does not carry a lot of data. Your best option is to create an LACP bond that provides a) redundancy for all traffic, most importantly cluster b) allows for some bandwidth...

Hi @RodolfoRibeiro , welcome to the forum! This topic is a common discussion point here on the forum. It is generally raised at least once a week, sometimes more. To address your questions: - Yes, many people run with this type of infrastructure in production - Yes, you can and should use...

In the PVE API here: https://pve.proxmox.com/pve-docs/api-viewer/#/nodes/{node}/disks/lvmthin and here: https://pve.proxmox.com/pve-docs/api-viewer/#/nodes/{node}/disks/wipedisk You can make a call to "Also wipe disks so they can be repurposed afterwards." I'd have to look to see how it is...

Removing an LVM slice (if VRTX-SSD is LVM based storage) is not enough to erase the data on the underlying disk. This has been discussed in the forum a few times, although I cant give you a link at this moment. You can check by running "lsblk" and 'blkid' on the hypervisor against the LVM slice...

If the pool ends at 249, then 240 is within the range. Pick an IP that is higher than 249 Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Thank you for the update @unsichtbarre . You can mark the thread as Solved, to keep the forum tidy, by editing the first message and selecting an appropriate subject prefix. Cheers Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

The file/location is not checked at the time of setting the option. It is possible that the config does not exist at the time of VM creation. One could dynamically generate the config on VM start. You will be notified at the time of VM start or migration if the CI config is missing...

You are the only person with full view and access to the system. You shared summary of what you think the system is and only partial snippets with us. There are a few possible theories, you can eliminate most of them by rebooting your host and observing what the system was able to re-establish...