proxmox and sdb1 3TB no reboot

[reloaded]

Hello everyone.

I tried riding on a raid Proxmox 10 with 3.6 TB of space. But it has been impossible because of the limitation of 2 TB.

Therefore I Proxmox mounted on a 100GB partition smaller without problems, but when mounting the remaining partition of 3.5 TB system I used the GNU parted.

With which I have defined a partition of 3.5 TB and mounted without problems.

The problem then to have everything perfectly set up and has been formatted to restart my Proxmox. Does not start in any case and I've tried different configurations.

I guess a more sdb1 disk does not have to give Proxmox boot problems.

My questions are as follows:

Is there a way to install partitioned Proxmox than 2TB?

Why, when I define a new partition in SDB (sdb1) everything works fine but on reboot Proxmox not start?

Do I have to change something in the boot Proxmox for my new partition boot?

clarification: My new partition, not a boot partition, it's just a data partition, so do not understand why Proxmox not start because the partition is perfect Proxmox SDA.

Thanks you all

 

[tom]

so you can mount the partition manually but its not mounted after reboot? did you added it on /etc/fstab? post the output of /etc/fstab.

 

[JustaGuy]

Is there a way to install partitioned Proxmox than 2TB?

I have a similar configuration and this is how it's working.

There's a small drive on sda and Proxmox is installed to that.
Also is a > 3TB drive in the host on sdb.

The partition size of sdb1 is 2TB.
The partition size of sdb2 is < 1.5TB.

I don't know why, the Proxmox installer would complete but it wouldn't boot afterward... unless I started over with the 3TB drive being disconnected from the machine completely during installation.

After Proxmox installed it booted into the small drive. Then I shutdown and added the 3TB drive, which had been partitioned already, but were not formatted- all zeros.

Next reboot Proxmox started properly, and I added the 2 large disks as LVM storages via the web interface.

These are the config files that were generated by Proxmox when it was done, I didn't have to edit any of it:


/etc/pve/storage.cfg

dir: local
    path /var/lib/vz
    content images,vztmpl,rootdir

lvm: LDatastore0-vm
    vgname LDatastore0
    shared
    content images

lvm: LDatastore1-vm
    vgname LDatastore1
    shared
    content images

/etc/fstab

# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext3 defaults 0 1
UUID=3f392555-f729-4qed-989a-d638a3p784bx /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0

 

[reloaded]

the contents of my fstab is as follows:

# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext3 defaults 0 1
UUID=a448179a-89f1-4e4c-b754-cbc9b44368dc /dev/md0 /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0


should I include anything else in my fstab?

if this is how I should include? knowing that the new drive is sdb1

Thank you very much for your help

 

[reloaded]

amplio la información:

esto es lo que realizo para crear la partición con "parted"

cuando finalizo la partición está creada, si reinicio en este momento Proxmox no arranca.

alguna idea?

backup:/# parted /dev/sdb
GNU Parted 1.8.8
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel gpt
(parted) print
Model: Adaptec data (scsi)
Disk /dev/sdb: 3941GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags

(parted) mkpart primary 1 3941G
(parted) print
Model: Adaptec data (scsi)
Disk /dev/sdb: 3941GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 17.4kB 3941GB 3941GB primary

(parted)

 

[JustaGuy]

This doesn't look right to me:

UUID=a448179a-89f1-4e4c-b754-cbc9b44368dc /dev/md0 /boot ext3 defaults 0 1

should I include anything else in my fstab?

Assuming that /dev/md0 has a UUID of a448179a-89f1-4e4c-b754-cbc9b44368dc, then this entry is incorrect (view the UUID of /dev entries with the command blkid to verify).

I've never seen both methods of defining the device on the same line at the same time (UUID=foo & /dev/foo then mountpoint), I think that's incorrect.

As long as that UUID is the right one, I would change that line to be without the '/dev/md0' part to allow the system properly access the /boot partition.

UUID=a448179a-89f1-4e4c-b754-cbc9b44368dc /boot ext3 defaults 0 1

I think this is too large for PVE to deal with:

mkpart primary 1 3941G

I would split that into 2 partitions < 2TB each just to be on the safe side, then use LVM to re-join them if you want. I keep them seperate personally.

mkpart primary 1 2000G
mkpart primary 2 1941G

 

[reloaded]

Good morning and foremost thank you very much everybody,

At the end I have partitioned into two partitions, since I see very difficult to get Proxmox have partitions larger than 2TB.

That would be fine by Proxmox enable it to these partitions larger than 2 TB.


Thank you very much again.