No all disks used, new installation, Hetzner

sobranie · Sep 30, 2022

Hello, I am new to proxmox and I am trying to setup a new enviroment on a dedicated server from Hetzner.

I used to setup proxmox using installimage provided by them.

I have 4 disks 480GB each one, but in the proxmox panel I can see available space only 958GB.

I am not an expert on Linux and general server management, so if we can guide me how to fix that will be perfect.

Code:

root@Proxmox-VE ~ # lvs
  LV   VG  Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  root vg0 -wi-ao---- 15.00g
  swap vg0 -wi-ao----  6.00g

Code:

root@Proxmox-VE ~ # pvs
  PV         VG  Fmt  Attr PSize   PFree
  /dev/md1   vg0 lvm2 a--  893.00g 872.00g

Code:

root@Proxmox-VE ~ # fdisk -l

Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: XF1230-1A0480
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: 0x6825b7ba

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sda1          2048   1050623   1048576   512M fd Linux raid autodetect
/dev/sda2       1050624 937701039 936650416 446.6G fd Linux raid autodetect


Disk /dev/sdc: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: SAMSUNG MZ7LM480
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: dos
Disk identifier: 0xa39babf5

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sdc1          2048   1050623   1048576   512M fd Linux raid autodetect
/dev/sdc2       1050624 937701039 936650416 446.6G fd Linux raid autodetect


Disk /dev/sdb: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: Micron_5100_MTFD
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: 0x280062f6

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sdb1          2048   1050623   1048576   512M fd Linux raid autodetect
/dev/sdb2       1050624 937701039 936650416 446.6G fd Linux raid autodetect


Disk /dev/sdd: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: SAMSUNG MZ7LM480
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: dos
Disk identifier: 0x7dce0399

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sdd1          2048   1050623   1048576   512M fd Linux raid autodetect
/dev/sdd2       1050624 937701039 936650416 446.6G fd Linux raid autodetect


Disk /dev/md1: 893.01 GiB, 958858788864 bytes, 1872771072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes


Disk /dev/md0: 511 MiB, 535822336 bytes, 1046528 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-root: 15 GiB, 16106127360 bytes, 31457280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes


Disk /dev/mapper/vg0-swap: 6 GiB, 6442450944 bytes, 12582912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes

Code:

root@Proxmox-VE ~ # df -h
Filesystem            Size  Used Avail Use% Mounted on
udev                  126G     0  126G   0% /dev
tmpfs                  26G  1.2M   26G   1% /run
/dev/mapper/vg0-root   15G  4.9G  9.1G  36% /
tmpfs                 126G   52M  126G   1% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
/dev/md0              485M  177M  283M  39% /boot
/dev/fuse             128M   16K  128M   1% /etc/pve
tmpfs                  26G     0   26G   0% /run/user/0

Thank you very much for your help.

Matthias. · Sep 30, 2022

I'd guess that's because of your RAID setup.
What's the output of mdadm --detail /dev/md1?

sobranie · Sep 30, 2022

Matthias. said:
I'd guess that's because of your RAID setup.
What's the output of mdadm --detail /dev/md1?

Here you go

Code:

root@Proxmox-VE ~ # mdadm --detail /dev/md1
/dev/md1:
           Version : 1.2
     Creation Time : Thu Sep 29 20:22:17 2022
        Raid Level : raid6
        Array Size : 936385536 (893.01 GiB 958.86 GB)
     Used Dev Size : 468192768 (446.50 GiB 479.43 GB)
      Raid Devices : 4
     Total Devices : 4
       Persistence : Superblock is persistent

     Intent Bitmap : Internal

       Update Time : Fri Sep 30 11:25:48 2022
             State : active
    Active Devices : 4
   Working Devices : 4
    Failed Devices : 0
     Spare Devices : 0

            Layout : left-symmetric
        Chunk Size : 512K

Consistency Policy : bitmap

              Name : rescue:1
              UUID : ba2c4274:fa1d5101:a85a48cd:b7ffbe4d
            Events : 1768

    Number   Major   Minor   RaidDevice State
       0       8       34        0      active sync   /dev/sdc2
       1       8       18        1      active sync   /dev/sdb2
       2       8        2        2      active sync   /dev/sda2
       3       8       50        3      active sync   /dev/sdd2

Matthias. · Sep 30, 2022

Then that's expected : )

Have a look at the "Space efficiency" in https://en.wikipedia.org/wiki/Standard_RAID_levels#Comparison, which is 1 - 2/n, in your case 1-2/4 = 0.5. In other words, you have 4*480GB = 1920GB. With 0.5 space efficiency this is 1920*0.5=960 GB.

sobranie · Sep 30, 2022

Matthias. said:
Then that's expected : )

Have a look at the "Space efficiency" in https://en.wikipedia.org/wiki/Standard_RAID_levels#Comparison, which is 1 - 2/n, in your case 1-2/4 = 0.5. In other words, you have 4*480GB = 1920GB. With 0.5 space efficiency this is 1920*0.5=960 GB.

Thank you very much but what can I do in that case? Server is empty.

Matthias. · Sep 30, 2022

According to the hetzner docs https://docs.hetzner.com/robot/dedicated-server/operating-systems/installimage/#variables, you can choose the disk setup in the installimage.
Probably easiest to just install anew and this time don't select RAID

Make sure you actually know what that means for your system, though.

sobranie · Sep 30, 2022

Matthias. said:
According to the hetzner docs https://docs.hetzner.com/robot/dedicated-server/operating-systems/installimage/#variables, you can choose the disk setup in the installimage.
Probably easiest to just install anew and this time don't select RAID
Make sure you actually know what that means for your system, though.

Got it,

So RAID 0 and a daily backup on a separate server would be ok for a production server.

Neobin · Oct 1, 2022

sobranie said:
Got it,

So RAID 0 and a daily backup on a separate server would be ok for a production server.

If it is okay for you, to lose all the data on the raid and having a nonoperational server (software-wise) in case any one of the disks fails and you can afford the downtime until the drive is physically replaced and to restore the whole backup or maybe even need to reinstall and setup/configure the whole system from scratch first (depending how your backup looks like and what actually is possible on a dedicated (Hetzner) server), yeah sure...

But normally raid-0 is definitely not okay in a production server, even more if it is the main storage with the OS and all on it and not only some (really needed) fast scratch storage.

Of course, requirements differ. Just be aware of the possible consequences.

sobranie · Oct 1, 2022

Neobin said:
If it is okay for you, to lose all the data on the raid and having a nonoperational server (software-wise) in case any one of the disks fails and you can afford the downtime until the drive is physically replaced and to restore the whole backup or maybe even need to reinstall and setup/configure the whole system from scratch first (depending how your backup looks like and what actually is possible on a dedicated (Hetzner) server), yeah sure...

But normally raid-0 is definitely not okay in a production server, even more if it is the main storage with the OS and all on it and not only some (really needed) fast scratch storage.

Of course, requirements differ. Just be aware of the possible consequences.

Thanks, I have decided to keep the RAID 6 for my drives. I am just curious what is the possibility of a hard drive to fail and what is the procedure to restore server in case that happens.

Search

Search

No all disks used, new installation, Hetzner

sobranie

New Member

Matthias.

Proxmox Retired Staff

sobranie

New Member

Matthias.

Proxmox Retired Staff

sobranie

New Member

Matthias.

Proxmox Retired Staff

sobranie

New Member

Neobin

Distinguished Member

sobranie

New Member

We value your privacy