[SOLVED] Drive/RAID Configuration for Proxmox - Advice/Guidance

[vshaulsk]

First: I would encourage you to read the documentation and watch some videos.......


Now you have to activate your storage "VM-Storage" and "Storage (for your backups, ISO images, etc...)"

Mine looks like this:


Select the disk you want: "VM-Storage" and click the initialize Disk with GPT

Once your disk is initialized you can create the file system you want: LVM, LVM Thin, ZFS (if applicable), mount it as a directory....



For VM Storage I use the LVM-Thin: Click on it and go to create disk

Select the disk and name the pool



Once you create the different type storage's, you can go to "datacenter"; "storage" and edit some properties if available (which type of files are stored on that storage type" ..... not all types of storage support everything: Iso images, backups, VM images, etc....

 

[Y0nderBoi]

I did read documentation and watch a number of videos. Most of which did not cover the concept of RAID and RAID configuration all that well. I read the wiki and thought that all I would need to do was create new directories for each RAID since directories seemed the most versatile form of storage.

With all that being said. I was able to successfully intiialize and create a thin-LVM for the VM-Storage RAID. However when I try to initialize the second RAID I get this error:

command '/sbin/sgdisk /dev/sdc -U R' failed: exit code 2



Any ideas as to what I should try?

 

[vshaulsk]

Hardware raid is configured outside the operating system and presents the raid volume as a single disk to the operating system. Your system sees it as just a single hard drive.

Now are you getting this error when you initialize the disk with GPT or during another step ?

Or are you trying to mount this volume as a directory ?

 

[ertanerbek]

Coul you try on shell

mkfs.ext4 /dev/sdc
wipefs -a /dev/sdc

That seems like Read Only raid pool...

 

[Y0nderBoi]

Hardware raid is configured outside the operating system and presents the raid volume as a single disk to the operating system. Your system sees it as just a single hard drive.

Now are you getting this error when you initialize the disk with GPT or during another step ?

Or are you trying to mount this volume as a directory ?

I get this error when trying to initialize the drive.

 

[Y0nderBoi]

Coul you try on shell

mkfs.ext4 /dev/sdc
wipefs -a /dev/sdc

That seems like Read Only raid pool...

Tried this and got the following outputs:
root@proxmox-ve:~# mkfs.ext4 /dev/sdc
mke2fs 1.44.5 (15-Dec-2018)
Creating filesystem with 117040640 4k blocks and 29261824 inodes
Filesystem UUID: bb405991-4aea-4fe7-b265-cc644ea5e770
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000

Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done

Then tried this and got the following output:
root@proxmox-ve:~# wipefs -a /dev/sdc
/dev/sdc: 2 bytes were erased at offset 0x00000438 (ext4): 53 ef



After all of that I was able to intialize the disk. So was the first command to make it an .ext4 format and the second command was to wipe it?

 

[Y0nderBoi]

And now even after initializing and creating I am unable to upload anything to the drives.


I am assuming that since I made the LVM I need to partition them in order to upload anything to it.

 

[vshaulsk]

Did you go to "datacenter"; "storage" and select what types of information are allowed on "Storage (promox-ve) ?

If it will not let you select anything, than you may want to just mount the disk as a standard directory

I use external storage through CIFS or NFS for backups and ISO images, so I am not very familiar how to setup a local store for those items.

You should be able to create containers and vm's and use the "VM.Storage.Thin" as your VM disk storage location

 

[Y0nderBoi]

Did you go to "datacenter"; "storage" and select what types of information are allowed on "Storage (promox-ve) ?

If it will not let you select anything, than you may want to just mount the disk as a standard directory

I use external storage through CIFS or NFS for backups and ISO images, so I am not very familiar how to setup a local store for those items.

You should be able to create containers and vm's and use the "VM.Storage.Thin" as your VM disk storage location

I checked. Default seems fine, as it only allows for Disk Images and Containers.


Then to mount it, would I just select the "Storage" drive, hit "Remove" and then re-add it as a directory?

 

[vshaulsk]

It looks like you have to mount the disk as a directory, which will allow you to select other storage types and enable the "upload" option.

You can try within "datacenter; Storage" to delete the LVM

Than see under "disks; directory" it will let you add the LVM and format it as ext4 or xfs


If that does not work, just wipe the LVM off the disk and than try adding it as directory again

 

[Y0nderBoi]

Removed it from the "datacenter; Storage". Checked under the "disks; directory" I still see it as a VG.

I was able to remove the Volume Group, but when I go to add it as a directory it says "No disk unused".

 

[ertanerbek]

Tried this and got the following outputs:
root@proxmox-ve:~# mkfs.ext4 /dev/sdc
mke2fs 1.44.5 (15-Dec-2018)
Creating filesystem with 117040640 4k blocks and 29261824 inodes
Filesystem UUID: bb405991-4aea-4fe7-b265-cc644ea5e770
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000

Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done

Then tried this and got the following output:
root@proxmox-ve:~# wipefs -a /dev/sdc
/dev/sdc: 2 bytes were erased at offset 0x00000438 (ext4): 53 ef



After all of that I was able to intialize the disk. So was the first command to make it an .ext4 format and the second command was to wipe it?

wipefs remove all disk format signature and gpt partition table from disk.. if that device was have another disk signature maybe cause of that proxmox can not be add that...

 

[Y0nderBoi]

Update:
So after much trial and error and googling. I simply removed the old LVM Group, then ran "sgdisk -Z /dev/sdc" on the drive. From there I was able to reinitialize the drive and add it is a directory where I can now upload files too it.

Thanks you @vshaulsk you have been a huge help.

 

[Faldiin]

I was having the same issue with this. Thank you for providing the command "sgdisk -Z /dev/sdc" as this resolved the same issue I was having.

 

[coderex]

Update:
So after much trial and error and googling. I simply removed the old LVM Group, then ran "sgdisk -Z /dev/sdc" on the drive. From there I was able to reinitialize the drive and add it is a directory where I can now upload files too it.

Thanks you @vshaulsk you have been a huge help.

I had same issue, thank you for your help, that command saved me