Phantom FS in config-xml and in other places

Hello, guys! After switching to OMV6, I noticed floating problem with phantom FS.

Floating - I don't know what action or config produce it. But I caught the problem twice and had have to clean reinstall.

Installation method: on server debian with several unfree drivers.

Installed and configured: users, ssh, disks, FS, shared dirs, smb, portainer, plugins (nut, minidlna, flashmemory, diskstat, cputemp, kvm, sharerootfs)

I suppose guilty sharerootfs or kvm

So, one day I've get pending update in web UI.

It's mistake to:

- ignore it

- revert it

- applay it

because i've got stub system after it. System mounted with flag "errors=remount-ro", so after salt deploy phantom changes, system goes read-only mode. No sudo privileges, reboot only from physical button.

What there was in changes? New mntent with 79684322-3eac-11ea-a974-63a080abab18 uuid.

cd /etc/openmediavault
ls 
# config.xml  config.xml.0001  php.ini
diff -c config.xml config.xml.0001

*** config.xml  2022-03-09 14:07:25.804882643 +0300
--- config.xml.0001     2022-03-09 14:07:25.804882643 +0300
***************
*** 415,420 ****
--- 415,430 ----
          <usagewarnthreshold>85</usagewarnthreshold>
          <comment>noxMnt</comment>
        </mntent>
+       <mntent>
+         <uuid>79684322-3eac-11ea-a974-63a080abab18</uuid>
+         <fsname>/dev/sda6</fsname>
+         <dir>/</dir>
+         <type>ext4</type>
+         <opts>noatime,nodiratime,errors=remount-ro</opts>
+         <freq>0</freq>
+         <passno>1</passno>
+         <hidden>1</hidden>
+       </mntent>
      </fstab>
      <shares>
        <!--

Joke in that there was not such device:

enot@stone:/etc/openmediavault$ lsblk -f
NAME   FSTYPE FSVER LABEL        UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda
└─sda1 ext4   1.0   nox          defeb500-44b5-4d90-90de-5f38c2eb66dd  937.8G     0% /srv/dev-disk-by-uuid-defeb500-44b5-4d90-90de-5f38c2eb66dd
sdb
├─sdb1 ntfs         Recovery     C800668300667878
├─sdb2 vfat   FAT32              BA68-3968                              66.1M    31% /boot/efi
├─sdb3
├─sdb4 ntfs         winOs        3CB2429EB2425D10
├─sdb5 vfat   FAT32 NO_LABEL     157E-FEB0
├─sdb6 ext4   1.0   nixOs        78d29736-9098-4dc8-b617-7dd0bd881b5c   72.4G     7% /
└─sdb7 swap   1                  d6400408-c4f0-4500-8321-c7f926ac1bf8                [SWAP]
sdc
├─sdc1 ntfs         winData      794E09230EB2CBC2
└─sdc2 ext4   1.0   nixData      5df3d4ad-0414-4018-a3c9-bd248ee5fa4c    2.8T    10% /srv/dev-disk-by-uuid-5df3d4ad-0414-4018-a3c9-bd248ee5fa4c
sdd
└─sdd1 ext4   1.0   nixBkup      b2f9a5d4-ea0f-44d0-9ce9-d72536fbdcb0    1.7T     0% /srv/dev-disk-by-uuid-b2f9a5d4-ea0f-44d0-9ce9-d72536fbdcb0

Right choice is just delete config.xml.0001 and reboot.

After that, I tried to configure storage for KVM.

In dialogue at KVM -> Pools -> Add -> Path I get error

Zitat

Failed to execute XPath query '//system/fstab/mntent[uuid='79684322-3eac-11ea-a974-63a080abab18']'. a few seconds ago

Nice, yes? Of cource there were nothing with such guid in fstab or config.xml.

Strange solution: remove plugin sharerootfs - it'll also remove KVM and some cache. After that - install KVM again.

So, problem had gone.

Zitat von ryecoaaron

That "phantom" entry is added by the sharerootfs plugin and not causing any problems - https://github.com/openmediava…-sharerootfs.postinst#L32

The KVM plugin depends on sharerootfs. That is why it is removed when you remove the sharerootfs plugin.

Yep, I understand this.

Zitat von ryecoaaron

That "phantom" entry is added by the sharerootfs plugin and not causing any problems

Can't agree with this.

On my setup

there was such scenario of problem:

- plugin register new FS in config update

- web UI show pending updates

- applying updates deploy changes to fstab and etc

- web UI show "missing" FS in grid Storage -> File System

- system (not OMV, all OS) goes to read-only mode

Maybe it'll be less painfull to get disk uuid with currnet Os, than use hardcode?

For support aim there will be option to use hardcoded FS label.

Zitat von ryecoaaron

Post: sudo omv-showkey mntent And if you enabled the devices column in the Filesystem tab, what device is missing?

I would be happy to help. But now, after cleaning the reinstall, the problem does not appear with all aspects.

If delete plugins, reboot, install plugins, reboot, there will be missing FS, but

- without pending updates

- without broken fstab

Response of sudo omv-showkey mntent is

                   <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>def42379-ed5f-4c4c-b350-ef40ff1ec7a0</uuid>
    <fsname>/dev/disk/by-uuid/5df3d4ad-0414-4018-a3c9-bd248ee5fa4c</fsname>
    <dir>/srv/dev-disk-by-uuid-5df3d4ad-0414-4018-a3c9-bd248ee5fa4c</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>nixData</comment>
  </mntent>
  <mntent>
    <uuid>1a399a63-22b3-4629-aebc-882a3f710b09</uuid>
    <fsname>/dev/disk/by-uuid/b2f9a5d4-ea0f-44d0-9ce9-d72536fbdcb0</fsname>
    <dir>/srv/dev-disk-by-uuid-b2f9a5d4-ea0f-44d0-9ce9-d72536fbdcb0</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>nixBkup</comment>
  </mntent>
  <mntent>
    <uuid>7dddfdd2-32e6-455d-a747-d8f1d41090a3</uuid>
    <fsname>/dev/disk/by-uuid/defeb500-44b5-4d90-90de-5f38c2eb66dd</fsname>
    <dir>/srv/dev-disk-by-uuid-defeb500-44b5-4d90-90de-5f38c2eb66dd</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>noxMnt</comment>
  </mntent>
  <mntent><uuid>79684322-3eac-11ea-a974-63a080abab18</uuid><fsname>/dev/sdb6</fsname><dir>/</dir><type>ext4</type><opts>noatime,nodiratime,errors=remount-ro</opts><freq>0</freq><passno>1</passno><hidden>1</hidden></mntent></fstab>

Zitat von ryecoaaron

if you enabled the devices column in the Filesystem tab, what device is missing?

There is just blank cells

Zitat von ryecoaaron

I have a feeling this is caused by having an additional partition on the OS drive that is mounted (especially considering the OS partition is not first and a data partition is). I don't have any systems setup this way. I would file a bug report but Volker might say this is an unsupported config.

Sadly.
I saw a note on the prerequisites about using a whole disk.

But I thought this was done for the convenience of installation by users who are not ready to engage in partitioner.

Zitat von KM0201

Personally, I like insulating the OS from the data, so I don't keep anything on my data drive

Thank you, I understand why users need to separate storages.
And I understand that I can move the winOs partition to another ssd and stretch the current partition with Debian
My sadness is that this will take time and effort.. if I want to have a backup machine with dualboot

Zitat von ryecoaaron

You dual boot your NAS with Windows? Why?

I calm my paranoia with the ability to boot into Windows

My whole family switched to laptops. They are good in a lot of aspects. But if something breaks, then the service center usually diagnoses the problem for a long time.

Exactly for this case that I keep the x86 PC: I can open Windows-specific programs on it and continue working.

Even if such an opportunity is needed once in 2 years, I prefer to save the partition and grub entry.