[SOLVED] Timed out waiting for device /dev/pve/data on freshly installed PVE

[emoxam]

I've installed PVE from proxmox-ve_7.4-1.iso
setted up 25.0 to maxroot
did

mkfs.ext4 /dev/pve/data

and added

/dev/pve/data /opt/st ext4 errors=remount-ro 0 0

to my /etc/fstab

now when i restart my server i got an error
Timed out waiting for device /dev/pve/data
And i must enter password, run

mount -a

and run

exit

On the first server i don't have such problems.. what did i miss ?

 

[gfngfn256]

/dev/pve/data /opt/st ext4 errors=remount-ro 0

Not sure but maybe you need to add another space & zero at the end (no fsck) so maybe:

/dev/pve/data /opt/st ext4 errors=remount-ro 0 0

BTW Your attached image of the journal isn't showing.

 

[emoxam]

Not sure but maybe you need to add another space & zero at the end (no fsck) so maybe:

/dev/pve/data /opt/st ext4 errors=remount-ro 0 0

BTW Your attached image of the journal isn't showing.

pardon, one zero was a mistake while pasting to the forum.
Sure there are two zeroes. I already fixed it.

Image was about the "cmap_initialize failed" it's i guess corosync and i don't think corosync could be usefull here..

 

[emoxam]

It's freshly installed PVE..

 

[gfngfn256]

Have you completely removed the LVM thin-pool before replacing with your ext4 FS? See here.

Also make sure your /etc/pve/storage.cfg & all VM's config files etc. don't make references based on the default installation LVM thin-pool.

 

[emoxam]

Have you completely removed the LVM thin-pool before replacing with your ext4 FS? See here.

Also make sure your /etc/pve/storage.cfg & all VM's config files etc. don't make references based on the default installation LVM thin-pool.

I didn't understand what exactly can i do ?
I deleted thin LVM but i don't have any /dev/sda4 to use.
And i have /dev/sda3 with the size near size of my hdd.

 

[gfngfn256]

I deleted thin LVM but i don't have any /dev/sda4 to use.
And i have /dev/sda3 with the size near size of my hdd.

Not sure what you refer to as /sda4.

/sdaX as you probably know are physical partitions on the disk /sda. Normally you would probably have three partitions so /sda1 , /sda2 & /sda3 with the last one being your "userspace". That "userspace" can be further divided/alloted into PVs (physical volumes) LVs (logical volumes) thin-pools etc. At the "lowest level" you have an FS (file-system). You seem to have chosen not to have an LVM-thin pool.

Lets first see what you do have.

Post output (within code-tags) of the following:

lsblk
pvs
vgs
lvs

 

[emoxam]

Not sure what you refer to as /sda4.

/sdaX as you probably know are physical partitions on the disk /sda. Normally you would probably have three partitions so /sda1 , /sda2 & /sda3 with the last one being your "userspace". That "userspace" can be further divided/alloted into PVs (physical volumes) LVs (logical volumes) thin-pools etc. At the "lowest level" you have an FS (file-system). You seem to have chosen not to have an LVM-thin pool.

Lets first see what you do have.

Post output (within code-tags) of the following:

lsblk
pvs
vgs
lvs

Seems like that's the way

lvremove pve/data
lvcreate -l100%FREE pve -n data
mkfs.ext4 /dev/pve/data

Why PVE installation creates a thin volume ? Why not to do thick from the start ?

 

[gfngfn256]

Why PVE installation creates a thin volume

Checkup/search on the advantages of a thin-volume & also check how Proxmox uses its various defined-storages & you will quickly see the reasoning behind that decision. Maybe start here.

Anyway looks like your issue is solved. Maybe tag mark the thread-title with [SOLVED], (upper right hand corner under title).