[SOLVED] Can't mount drives in host using fstab in ProxMox 7.0-8

P

PixelGordo

Member
May 13, 2017
5
0
21
57
Good afternoon

I have no problems mounting drives (regular ext4 or ext 4 over software RAID 5) from command line by just using "mount /dev/my_device /my_directory" but when I try to do it in fstab, nothing seems to work.

My fstab lines look like:


Code: 
# Long term data
UUID=6eb7958e-67d6-4b17-a298-06b47dbd63c3  /mnt/data  ext4  defaults,nobootwait,nofail  0 2

# Temporal drive
UUID=f5ae6e64-7a18-4229-9add-fe9c1ed9bc7e  /mnt/temp  ext4 defaults,nobootwait,nofail  0 2

When I try to test-mount them using "mount -a", I get:

Code: 
mount: /mnt/temp: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error.

Any idea of what could be wrong?
 
You said its a software raid, mdadm?
If it is - then you should not be mounting direct disk sdX anything, it should be /dev/mdxx something

If you show community what is working, vs only whats not working as well as things like:
lsblk
fdisk -l
lsscsi

it might be easier to help you
 
For reference, these lines were working fine in ProxMox 4

Code: 
# Temp drive
#-----------
UUID=f5ae6e64-7a18-4229-9add-fe9c1ed9bc7e  /mnt/temp  ext4  defaults,noatime,nobootwait,nofail  0  0

# Data raid
#----------
UUID=6eb7958e-67d6-4b17-a298-06b47dbd63c3  /mnt/data  ext4  defaults,noatime,nobootwait,nofail  0  0

Here you have the output of "lsblk -f"

Code: 
NAME                         FSTYPE            FSVER    LABEL     UUID                                   FSAVAIL FSUSE% MOUNTPOINT
sda                                                                                                                   
└─sda1                       linux_raid_member 1.2      jupiter:0 f64791b0-a216-820d-40be-6f9161570eb2               
  └─md0                      ext4              1.0                6eb7958e-67d6-4b17-a298-06b47dbd63c3               
sdb                                                                                                                   
└─sdb1                       linux_raid_member 1.2      jupiter:0 f64791b0-a216-820d-40be-6f9161570eb2               
  └─md0                      ext4              1.0                6eb7958e-67d6-4b17-a298-06b47dbd63c3               
sdc                                                                                                                   
└─sdc1                       linux_raid_member 1.2      jupiter:0 f64791b0-a216-820d-40be-6f9161570eb2               
  └─md0                      ext4              1.0                6eb7958e-67d6-4b17-a298-06b47dbd63c3               
sdd                          ext4              1.0                76a48b85-2088-4542-aca6-a9146522709f               
└─sdd1                       ext4              1.0                f5ae6e64-7a18-4229-9add-fe9c1ed9bc7e

..and here the output of "fdisk -l"


Code: 
Disk /dev/sda: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: HGST HDN724040AL
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: 85C8A8D9-FC18-450A-8AA7-15EB1E3CA743

Device     Start        End    Sectors  Size Type
/dev/sda1   2048 7814037134 7814035087  3.6T Linux filesystem


Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: HGST HDN724040AL
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: 3E0B3E5D-5986-4639-8F28-311F6AD384AB

Device     Start        End    Sectors  Size Type
/dev/sdb1   2048 7814037134 7814035087  3.6T Linux filesystem


Disk /dev/sdd: 1.82 TiB, 2000397852160 bytes, 3907027055 sectors
Disk model: ST2000DL003-9VT1
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: 0x62fad42a

Device     Boot Start        End    Sectors  Size Id Type
/dev/sdd1        2048 3907027054 3907025007  1.8T 83 Linux


Disk /dev/sdc: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: HGST HDN724040AL
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: 5AE8B23B-1942-46BA-B279-C43A8CAC1ADA

Device     Start        End    Sectors  Size Type
/dev/sdc1   2048 7814037134 7814035087  3.6T Linux filesystem


Disk /dev/md0: 7.28 TiB, 8001302822912 bytes, 15627544576 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
 
Last edited:
Problem found... after launching dmesg | grep EXT I found many errors similar to:

Code: 
[ 6963.321907] EXT4-fs (sdd1): Unrecognized mount option "nobootwait" or missing value

It seems nobootwait is now deprecated and the equivalent modern options are "nofail,x-systemd.device-timeout=1"

Regards
 
You must log in or register to reply here.
Top Bottom