Proxmox + Hetzner

project

New Member
Oct 7, 2016
4
0
1
26
Hello,

I am currently having trouble with adding an additional disk to Proxmox to use as storage for my VM's. With Hetzner, you have to go through a install configuration which includes partitioning your disks appropriately which is where I'm stuck. It naturally attempts to use Software RAID 1 but I went ahead and disabled it because I have no need for that and it also puts my second disk in use. Well, regardless of whether or not I install the Proxmox image without Software RAID 1 configuration, the second disk is still in use therefore not allowing me to follow the tutorials around the internet on adding an additional disk to Proxmox for storage. The disks I have are 2 x 2TB HDD's.

Is there anyone who has experience with Hetzner's dedicated servers and can assist me with this? Please don't respond with a link to a wiki guide on how to add an additional disk; I've tried everything possible.

I do:
Code:
pvcreate /dev/sdb1

It returns:
Code:
Can't open /dev/sdb1 exclusively.  Mounted filesystem?

I do:
Code:
fdisk -l

It returns:
Code:
Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xac24224d

Device     Boot   Start        End    Sectors  Size Id Type
/dev/sda1          2048    1050623    1048576  512M 83 Linux
/dev/sda2       1050624 3907027119 3905976496  1.8T 8e Linux LVM

Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 2F6E354E-F023-40EC-B90F-A2E161FB6454

Device     Start        End    Sectors  Size Type
/dev/sdb1   2048 3907029134 3907027087  1.8T Linux filesystem

Disk /dev/mapper/vg0-root: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/md127: 511.4 MiB, 536281088 bytes, 1047424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/vg0-swap: 4 GiB, 4294967296 bytes, 8388608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/vg0-tmp: 5 GiB, 5368709120 bytes, 10485760 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/vg0-home: 1.8 TiB, 1941325217792 bytes, 3791650816 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Thank you!
 
Last edited:
It returns:
Code:
Can't open /dev/sdb1 exclusively. Mounted filesystem?
You need to check what is holding your sdb1 partition, maybe a simple reboot is already everything you need.