Wrong disk

R

RigPah

New Member
Sep 20, 2024
9
0
1
On my first setup I had only one ssd disk on which I installed a MC server. Worked fine until I put 2 more mirrored disks in the server and now ProxMox thinks MC is installed on the NEW disks. Can't find any where to tell ProxMox that it is using the wrong disk and set it back to the first disk, How do I do that?

Getting this message: TASK ERROR: unable to activate storage 'VDisk1' - directory is expected to be a mount point but is not mounted: '/mnt/pve/VDisk1'
 
Last edited:
Why did you post the error if you don't think it is related?

ETA: You have given just about zero information about your configuration so whatever people offer will be a guess. Show us the output of "lsblk" for example. What steps have you taken and what output did you get? How did you create the mirror?
 
Last edited:
Have NO idea if it is related. It sure shouldn't be. Only put more disks in the server and after reboot ProxMox can't find my first vdisk.

Never said I created a mirror. Said I put 2 more mirrored disks in it. This is normally possible without interfering with existing disks.
Said I got an error message on my first disk after installing these new disks. The message says that the VM can't start. This means NO lsblk.

I haven't taken any other steps than what I described. I asked because I hoped to figure out what steps to take.
 
Well, that is a little new info. Proxmox can't find your first disk and the VM won't start.

It really sounds like the disks were mounted by name (e.g. /dev/sda) rather than by id and adding new disks changed the enumeration. That or the administrator got confused and mounted things in the wrong place.
 
Did you have declared your mountpoint with uuid partition ? If not, do that before all.
 
I created the VM a few months ago and it worked fine until I put more disks in the server. What can I do/try?
 

Attachments

  • ProxMox.jpg
    ProxMox.jpg
    253.4 KB · Views: 14
  • ProxMox2.jpg
    ProxMox2.jpg
    220.7 KB · Views: 14
  • ProxMox3.jpg
    ProxMox3.jpg
    243.1 KB · Views: 13
Hey,
how did you have initiated your disk??
you haven’t any gpt schemas on your vdisk
 
BobhWasatch said:
Please log in to your server command line (console or ssh) and post the output of "lsblk" and "cat /etc/fdisk". Then we can help figure out what goes where. If you can't do that it is very hard to help you.
Click to expand...
Want to say /etc/fstab I think x')
 
BobhWasatch said:
Please log in to your server command line (console or ssh) and post the output of "lsblk" and "cat /etc/fdisk". Then we can help figure out what goes where. If you can't do that it is very hard to help you.
Click to expand...
As I mentioned earlier - The VM won't start so this is not really an option.
 
Pifouney said:
Hey,
how did you have initiated your disk??
you haven’t any gpt schemas on your vdisk
Click to expand...
I did a setup in the BIOS and ProxMox recognized it when I created the VM so I just selected it and used a part of it as a virtual drive in the VM and it worked fine for a few months until I put more disks in it.
 
Last edited:
No. I didn't know you were talking PVE host. Would naturally have gone there if I knew.

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 55.4G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 512M 0 part /boot/efi
└─sda3 8:3 0 54.9G 0 part
├─pve-swap 252:0 0 6.8G 0 lvm [SWAP]
├─pve-root 252:1 0 24G 0 lvm /
├─pve-data_tmeta 252:2 0 1G 0 lvm
│ └─pve-data-tpool 252:4 0 15.3G 0 lvm
│ └─pve-data 252:5 0 15.3G 1 lvm
└─pve-data_tdata 252:3 0 15.3G 0 lvm
└─pve-data-tpool 252:4 0 15.3G 0 lvm
└─pve-data 252:5 0 15.3G 1 lvm
sdb 8:16 0 931G 0 disk
└─sdb1 8:17 0 931G 0 part /mnt/pve/one-tb
sdc 8:32 0 2.7T 0 disk
└─sdc1 8:33 0 2.7T 0 part /mnt/pve/three-tb
 
Yeah, I would like to see the outputs @Pifouney asked for. Because it really looks like you have done more than you let on. You've got a couple of disks mounted but no storage defined for them, plus the disk you do have a storage defined for seems to either not exist or be mounted somewhere else. Maybe /mnt/pve/one-tb used to be /mnt/pve/VDisk1?

I am not seeing any disks that are not mounted, which is what I would expect if you had just "plugged in a disk".
 
Last edited:
  • Like
Reactions: Pifouney
This is what it says:
Disk /dev/sda: 55.38 GiB, 59458453504 bytes, 116129792 sectors
Disk model: PERC H710
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C22AD1E2-DC5D-422F-A4DB-47B87096C60A

Device Start End Sectors Size Type
/dev/sda1 34 2047 2014 1007K BIOS boot
/dev/sda2 2048 1050623 1048576 512M EFI System
/dev/sda3 1050624 116129758 115079135 54.9G Linux LVM


Disk /dev/sdb: 931 GiB, 999653638144 bytes, 1952448512 sectors
Disk model: PERC H710
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4D8979E6-1AED-47DF-AE93-3D4F80FD8A64

Device Start End Sectors Size Type
/dev/sdb1 2048 1952448478 1952446431 931G Linux filesystem


Disk /dev/sdc: 2.73 TiB, 3000034656256 bytes, 5859442688 sectors
Disk model: PERC H710
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A5EFC6ED-E566-4684-909E-ED296045B263

Device Start End Sectors Size Type
/dev/sdc1 2048 5859442654 5859440607 2.7T Linux filesystem


Disk /dev/mapper/pve-swap: 6.75 GiB, 7247757312 bytes, 14155776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-root: 24.03 GiB, 25799163904 bytes, 50388992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
 
OK.
2 choices for U:

- Create a directory storage in your WebUI and select yours mountpoint (/mnt/1tb /tree-tb)
-Destroy actual partition, and initialise them with lvm.
DO NOT INITIALISE them with zfs, you gonna loose yours data.(perc h710)
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom