NFS Storage Creation

Sivakumar

New Member
Jan 15, 2020
7
0
1
46
Hello,

there are 2 request.

Request 1- I have around 15 standalone host in the Proxmox cluster. when I try to add the additional host to cluster as 16th Host, where all my existing 15 hosts are become unavailable. So I removed the cluster service ( including quorum) and managing each host as a separate GUI at this moment. what could be the reason ?

Request 2 - When I manage the proxmox host separately without cluster. How do we add the existing NFS storage to specific proxmox host (without using the datacenster) ?
complete steps would be appreciated.

Thanks in advance

Regards
SK
 
Hi!

Ad 1) Do you have more detailed information about your breaking cluster? Starting with
Code:
pveversion -v
pvecm status
Unavailable meaning running but looking shut down for Proxmox VE?

Ad 2) Storages for Proxmox VE are always created on the datacenter level. For single nodes this works fine too. What you can do is setting the nodes property for a setting:
List of cluster node names where this storage is usable/accessible. One can use this property to restrict storage access to a limited set of nodes.
Is this a sufficient alternative for you?
 
Hi!

Ad 1) Do you have more detailed information about your breaking cluster? Starting with
Code:
pveversion -v
pvecm status
Unavailable meaning running but looking shut down for Proxmox VE?

Ad 2) Storages for Proxmox VE are always created on the datacenter level. For single nodes this works fine too. What you can do is setting the nodes property for a setting:

Is this a sufficient alternative for you?

Unavailabe means, VMs are runnung. but not able to manage cluster host all togather in GUI under Datacenter. we are separately accessing the each host and doing all admin task.


Ad1 : pveversion -v

root@ERLDPRX009:~# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-14
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191002-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-2
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2



Ad 2: pvecm status ( we stopped the cluster service, I mean removed the cluster service ) because of the issue.

root@ERLDPRX009:~# pvecm status
Error: Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!