Search results

After much searching & trial and error, I don't believe there is any way to actually purge the packages. The problem is this "pveceph" command is a black box. We have no idea what it is actually doing in the background. In the end, I removed the OSDs one by one. Here is the procedure to do...

Ok, I now have this working (mostly). It appears the pveceph create <diskname> command simply aliases to sgdisk -Z <diskname> then ceph-disk prepare --bluestore <diskname> then finally ceph-disk activiate <diskname> Here are the commands I've used. In this example I'm preparing "sda" for use as...

I didn't purge any packages, because I don't know which packages to purge. I installed these packages by typing "pveceph install --version luminous" This "pveceph" command is a black box. Is it possible to get a list of things this command does? The doc page for this command...

I thought that’s what pveceph stop and pveceph purge are supposed to do - but I digress. So after I run those 2 commands - what don I need to do to well and truely purge ALL the config? OSDs, Crush maps, data on disks - it can all go. I’m happy to start setup from scratch.

Hi Alwin, I have completely disabled ceph authentication for now for troubleshooting. Our Ceph network is also isolated (its a daisy chained network) an we're looking for max performance. I followed the instructions at the end of this howTo https://pve.proxmox.com/wiki/Ceph_Server But when I...

Nothing, the OSD is running just fine. When I list all my ceph OSDs, the OSD is shown at the bottom of the list; it has no relation to anything else in the cluster. In fact it’s so broken now that if I go into ceph cluster view, I can’t even see my hosts in there. It just shows one node-...

I want to figure out what went wrong here The whole reason I'm here now is that I had a working ceph setup, I deleted it but when I went to re-add the OSDs, one of the OSDs just wouldn't show up. Who/what is responsible for creating the initial CRUSH map?

Alright... I've managed to get the monitors and managers created (using ceph luminous) But when I go to view OSDs, I don't see my host names in there like I did earlier; I only see "default". My crush map doesn't have any of my hosts in it either: # begin crush map tunable choose_local_tries...

So I completely messed up my ceph config in my test environment. I read that running "pveceph stop" then "pveceph purge" will remove all config & data. So I did. Then I went to the Ceph guide (https://pve.proxmox.com/wiki/Ceph_Server#Ceph_on_Proxmox_VE_5.1) and began creating my cluster again...

Is that likely to help if I don't have any zfs voulumes on my systems at all? My boot volume is ext4/LVM, and my data volumes are ceph/ext4.

Right, I went through those threads you linked but a lot of it went over my head. What is the root cause of this?

Ok... I have resolved this. Turns out you also have to go to /etc/pve/nodes And remove the folder by the name of your node to fully remove it from the WebGUI. Anyone else think this should really be in the documentation? Or did I do something wrong here and mess this up?

We only started using proxmox from 4.1, and by then it was already LXC so I suppose it was "Fresh".

That information is in my post above but I'll put it here again: # pveversion --verbose proxmox-ve: 5.1-38 (running kernel: 4.13.13-5-pve) pve-manager: 5.1-43 (running version: 5.1-43/bdb08029) pve-kernel-4.13.4-1-pve: 4.13.4-26 pve-kernel-4.13.13-5-pve: 4.13.13-38 libpve-http-server-perl...

A few months ago one of my nodes (3 node cluster) failed. I replaced it with a new machine at around the same time, then added another node. (So now we have 1 dead node, 4 live nodes). I went through this documentation to remove the node...

Vasu, do you know the root cause of this issue. I had a read of that thread and it doesn't look like this is the same issue? You're using ZFS but I am just using EXT4. My proxmox node is still responsive inside the cluster (I can access the consoles of running VM/CT). However I cannot log into...

A host reboot has resolved this but I'd like to know why this is happening... as you can imagine the host has other VMs and CTs running on it and restarting the host is a bit of a pain.

Hi, I am running a 3-node cluster. I stopped a container to make some changes to the hardware. When I went to power it back on, I couldn't. When I press the "start' button, I get a spinning 'Please wait' thing for a while. Then eventually it says "Timed Out". I ssh'ed into the host itself...

Hi All I've got Proxmox 5.1 running as a VMWare ESXi guest. So far everything seems OK. I need to run several Linux CT and one Windows 2012 R2 VM. I have so far set up a single VM on ESXi and installed proxmox on top. It's all working properly, and I've followed the "Nested Virtualization...

Unfortunately due to no stable release of ceph being available on 5.0 or 5.1, I can't quite upgrade just yet. Is there a solution that doesn't involve using those commands? I don't have them on 4.4.