Just to let you know about what's happening.
I figure it out that in the boot time, on disk controller menu, I had to get the physical disk and create a virtual disk with them.
So, the disk controller management the virtual disk.
After i did it, on proxmox the command line "fdisl -l" show a...
Yes. It Doesn't work.
Execute that and it doesn't work too.
I create a gpt on the disk, make no diference
# cfdisk /dev/sdc
so, I create a partition type Linux system on the disk and make no diference again
Do I need to restart node?
I will to test some other things, if anybody remember...
I need to add a disk to create a OSD to CEPH.
I put SSD on server, and its appear by command line:
# fdisk -l
But on de GUI of Proxmox doesn't show the disk.
Which command line am i missing?
Great !!
But, I have one question about a thing.
I need to add a disk to create a OSD to CEPH.
I put SSD on server, and its appear by command line:
# fdisk -l
Disk /dev/sdc: 4 TiB, 4398058045440 bytes, 1073744640 sectors
Disk model: 100E-00
Units: sectors of 1 * 4096 = 4096 bytes...
Sorry for wakup an old topic.
But, the steps writing by @mir, do they still work in current version (proxmox 6)?
If so, do steps above work in the oposit situation (virtio to iscsi)?
This problem happened in our cluster where hot VMs are. If it had happened in a test environment I would not be so nervous.
I was updating the nodes, and in my case, the problem only happened when the last node was disconnected. This node I would not upgrade but remove from the cluster.
I'm in a similar situation.
I'm using version 5.4.5.
When I shutdown one of the nodes all the vms also turned off and only became active again after turning on the power of the node.
My architecture with 6 nodes:
An Iscsi Storage: Using LVM to share the disk between nodes - 8T
An Iscsi...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.