Wrong partition names in shared folders list (sda is sdb)

zedoc · Apr 17th 2023

Hi, i've noticed that the partitions names are not the same in OMV in Storage/Disk and Storage/Files Systems
i have 3 drives listed in Storage/Disk

But sdb1 is switched with sda1 in Storage/Files Systems (and one is listed twice)

my fstab:

Code

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=4458c0b4-6db0-44b9-81eb-2afc7c22f112 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=73f22072-820a-41d0-a923-64bcef496e5b none            swap    sw              0       0
# >>> [openmediavault]
/dev/disk/by-uuid/fd74e55a-a46f-4441-af9d-ee01ba56f6ce          /srv/dev-disk-by-uuid-fd74e55a-a46f-4441-af9d-ee01ba56f6ce      ext4    defaults,nofail>
/dev/disk/by-uuid/2d390a3f-5b15-4842-9bed-4aa3107daec9          /srv/dev-disk-by-uuid-2d390a3f-5b15-4842-9bed-4aa3107daec9      ext4    defaults,nofail>
/srv/dev-disk-by-uuid-2d390a3f-5b15-4842-9bed-4aa3107daec9/appdata/             /sftp/mexx/appdata     none    bind,rw,nofail  0 0
/srv/dev-disk-by-uuid-2d390a3f-5b15-4842-9bed-4aa3107daec9/downloads/           /sftp/mexx/downloads   none    bind,rw,nofail  0 0
/srv/dev-disk-by-uuid-2d390a3f-5b15-4842-9bed-4aa3107daec9/media/               /sftp/mexx/media       none    bind,rw,nofail  0 0
/srv/dev-disk-by-uuid-2d390a3f-5b15-4842-9bed-4aa3107daec9/watch/               /sftp/mexx/watch       none    bind,rw,nofail  0 0
/srv/dev-disk-by-uuid-2d390a3f-5b15-4842-9bed-4aa3107daec9/backups/             /sftp/mexx/backups     none    bind,rw,nofail  0 0
/srv/dev-disk-by-uuid-fd74e55a-a46f-4441-af9d-ee01ba56f6ce/appdatabackup/               /sftp/mexx/appdatabackup       none    bind,rw,nofail  0 0
/srv/dev-disk-by-uuid-fd74e55a-a46f-4441-af9d-ee01ba56f6ce/backupsbackup/               /sftp/mexx/backupsbackup       none    bind,rw,nofail  0 0
/srv/dev-disk-by-uuid-fd74e55a-a46f-4441-af9d-ee01ba56f6ce/downloadsbackup/             /sftp/mexx/dowloadsbackup      none    bind,rw,nofail  0 0
/srv/dev-disk-by-uuid-fd74e55a-a46f-4441-af9d-ee01ba56f6ce/mediabackup/         /sftp/mexx/mediabackup none    bind,rw,nofail  0 0
/srv/dev-disk-by-uuid-fd74e55a-a46f-4441-af9d-ee01ba56f6ce/watchbackup/         /sftp/mexx/watchbackup none    bind,rw,nofail  0 0
# <<< [openmediavault]

Display More

blkid:

Code

root@nasXXX:/# sudo blkid
/dev/sda1: LABEL="DATABACKUP" UUID="fd74e55a-a46f-4441-af9d-ee01ba56f6ce" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="55f2965a-ef37-4c2e-9293-9dbf037fecc1"
/dev/sdb1: LABEL="DATAGLOUB" UUID="2d390a3f-5b15-4842-9bed-4aa3107daec9" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0e89d9b5-94ed-42ce-a3e1-86eea4670a03"
/dev/sdc1: UUID="4458c0b4-6db0-44b9-81eb-2afc7c22f112" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="d1f74ed3-01"
/dev/sdc5: UUID="73f22072-820a-41d0-a923-64bcef496e5b" TYPE="swap" PARTUUID="d1f74ed3-05"

lsblk:

Code

root@nasXXX:/# lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0   3,6T  0 disk
└─sda1   8:1    0   3,6T  0 part /srv/dev-disk-by-uuid-fd74e55a-a46f-4441-af9d-ee01ba56f6ce
sdb      8:16   0   3,6T  0 disk
└─sdb1   8:17   0   3,6T  0 part /srv/dev-disk-by-uuid-2d390a3f-5b15-4842-9bed-4aa3107daec9
sdc      8:32   0 238,5G  0 disk
├─sdc1   8:33   0  21,9G  0 part /
├─sdc2   8:34   0     1K  0 part
└─sdc5   8:37   0     2G  0 part [SWAP]

sudo fdisk -l:

Code

root@nasXXX:/# sudo fdisk -l
Disk /dev/sda: 3,64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: ST4000DM004-2CV1
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: 5078927D-ED50-49ED-9774-0356423925C3


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: WDC WD40EFRX-68N
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: A77DCCA6-A6AF-4726-BD05-56D22677ECF6


Device     Start        End    Sectors  Size Type
/dev/sdb1   2048 7814035455 7814033408  3,6T Linux filesystem




Disk /dev/sdc: 238,47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: SSD 256GB
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: 0xd1f74ed3


Device     Boot    Start      End  Sectors  Size Id Type
/dev/sdc1           2048 46012415 46010368 21,9G 83 Linux
/dev/sdc2       46012416 50214911  4202496    2G  5 Extended
/dev/sdc5       46014464 50214911  4200448    2G 82 Linux swap / Solaris

Display More

Labels and UUIDs are fine in shared folders but sda is sdb...

Well..I'm i missing something?

macom · Apr 17th 2023

Did you try to clear your browser cache or to force reload with Ctrl+Shift+R?

zedoc · Apr 17th 2023

Yes, tried with Brave and Firefox, caches cleared but same result.

macom · Apr 17th 2023

Device names like sda/sdb can change between boots. That is why OMV mounts filesystem bei UUID which do not change.

But that you have two time sda1 is strange.

zedoc · Apr 17th 2023

Yes it is showing two sda1 in the dashboard also...

i'm using rsync to auto-backup my shared folders to the backup drive, for now it seems to work despite the fact that partition name (sda/sdb) is "inverted" with the drives labels in Storage/shared folders but yes two sda1 is a bit strange...

macom · Apr 17th 2023

What is the output of

omv-showkey mntent

zedoc · Apr 17th 2023

Here it is

Code

root@nasXXX:/# sudo omv-showkey mntent
<mntent>
<uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
<fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>
<dir>/xxx/yyy/zzz</dir>
<type>none|ext2|ext3|ext4|xfs|jfs|iso9660|udf|...</type>
<opts></opts>
<freq>0</freq>
<passno>0|1|2</passno>
<hidden>0|1</hidden>
<usagewarnthreshold>xxx</usagewarnthreshold>
<comment>xxx</comment>
</mntent>
<mntent>
<uuid>5e93711d-3529-4d28-bfe0-d25dc6e7c573</uuid>
<fsname>/dev/disk/by-uuid/fd74e55a-a46f-4441-af9d-ee01ba56f6ce</fsname>
<dir>/srv/dev-disk-by-uuid-fd74e55a-a46f-4441-af9d-ee01ba56f6ce</dir>
<type>ext4</type>
<opts>defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl</opts>
<freq>0</freq>
<passno>2</passno>
<hidden>0</hidden>
<usagewarnthreshold>85</usagewarnthreshold>
<comment></comment>
</mntent>
<mntent>
<uuid>24fb47f2-f362-4d43-90bc-c445014a9c86</uuid>
<fsname>/dev/disk/by-uuid/2d390a3f-5b15-4842-9bed-4aa3107daec9</fsname>
<dir>/srv/dev-disk-by-uuid-2d390a3f-5b15-4842-9bed-4aa3107daec9</dir>
<type>ext4</type>
<opts>defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl</opts>
<freq>0</freq>
<passno>2</passno>
<hidden>0</hidden>
<usagewarnthreshold>85</usagewarnthreshold>
<comment></comment>
</mntent>
<mntent>
<uuid>79684322-3eac-11ea-a974-63a080abab18</uuid>
<fsname>/dev/sda1</fsname>
<dir>/</dir>
<type>ext4</type>
<opts>errors=remount-ro</opts>
<freq>0</freq>
<passno>1</passno>
<hidden>1</hidden>
</mntent>

Display More

macom · Apr 17th 2023

Quote from zedoc

Code

<mntent>
<uuid>79684322-3eac-11ea-a974-63a080abab18</uuid>
<fsname>/dev/sda1</fsname>
<dir>/</dir>
<type>ext4</type>
<opts>errors=remount-ro</opts>
<freq>0</freq>
<passno>1</passno>
<hidden>1</hidden>
</mntent>

This is the problem. OMV "thinks" sda1 is the root fs, but actually it is sdc1 now.

Make a backup of

/etc/openmediavault/config.xml

then open the file with nano and change in the section above sda1 by

/dev/disk/by-uuid/4458c0b4-6db0-44b9-81eb-2afc7c22f112

Then save the file and run

omv-salt deploy run fstab monit

Similar issue here

Post

Missing root filesystem after update

Since I updated OMV from 6.0.20 to 6.3.3 and linux kernel from 5.1x to 6.0 I have two problem.
1. A missing file system shown on the WebGUI.
2. Is the Docker/Portainer 5.23 "bug" already cured with docker-ce and docker-ce-cli downgrade

Only the mountpoint visible which is the root (/).
Looking through the filesystem list, it really says that the root system is missing.
Although everything works in my opinion, it's quite confusing.

forum.openmediavault.org/wsc/index.php?attachment/29032/
…

Kinsiinoo

Mar 11th 2023

zedoc · Apr 17th 2023

Another weird thing i've found is that backup folders have disappeared using sftp client but showing in ssh!

Code

root@nasXXX:/srv/databackup/appdatabackup# ls
authelia     dashboard    fireshare  Heimdall       loki         nextclouddb    picoshare   pwndrop          session     transmission  WikiJS
bookstack    diun         freshrss   homeassistant  media        nodered        pingvin     remotely         snapdrop    uptime-kuma   wireshark
calibre      docker       Gotify     homebridge     meshcentral  openvas        pinry       rustdesk         snippetbox  vaultwarden   wordpress
calibre-web  duckdns      grafana    influxdb       mosquitto    openvasbackup  portainer   scrutinyanalogj  swag        wallabag      wordpressdb
codeserver   duplicati    guacamole  Jellyfin       navidrome    photoprism     prometheus  seafile          syncthing   webtop        zigbee2mqtt
collabora    filebrowser  hassconf   librespeed     nextcloud    phpMyAdmin     promtail    seafile-mariadb  tailscale   whoogle

using SFTP client (cyberduck or Transmit)

macom · Apr 17th 2023

That is probably because the sharerootfs plugin does not work properly as the fsname is wrong. Will hopefully be fixed when you do the change above.

zedoc · Apr 17th 2023

Thanks macom

changed <fsname> by:

Code

<mntent>
<uuid>79684322-3eac-11ea-a974-63a080abab18</uuid>
<fsname>/dev/disk/by-uuid/4458c0b4-6db0-44b9-81eb-2afc7c22f112</fsname>
<dir>/</dir>
<type>ext4</type>
<opts>errors=remount-ro</opts>
<freq>0</freq>
<passno>1</passno>
<hidden>1</hidden>
</mntent>

Looks better now

Folders are back in SFTP also

Wrong partition names in shared folders list (sda is sdb)

Participate now!

Tags