Upgrade goes well but not possible to update of modules

M*I*B · May 21st 2023

the upgrade to version 6x worked without error messages.

I proceeded according to a HowTo here from the forum (can't find it anymore), where among other things an "omv-salt stage run deploy" was recommended, then an "omv-upgrade" and finally an "omv-release-upgrade" to toast

The former was all green with no errors. Also the upgrade was ok as far as I can see, as was the release upgrade, which however had two warnings in between (something with grep and folder not found).

OMV 6 works so far, but I get a "500 - Internal Server Error" (see txt- file; to big to post it here) if I try to start the "Pending configuration changes" (see screenshot).

So about my less skill in linux I need a little help to solve that... Is there anybody?

230521, OMV Error 500 while update.txt

Maybe this is the point, the missing one? Just find is. Was'n shown in the former 5x version... So I have no idea what drive are missing

Is there a way to clean that up in any way? So it's not possible to simple delete/unmount them ...

macom · May 21st 2023

It seems there is a ntfs formatted drive missing. Is this correct?

In the screenshot the missing device is marked as "referenced". That means that there exists a shared folder pointing at that device. Remove that shared folder from any service. Then delete the shared folder. After that you should be able to delete the drive from the GUI.

M*I*B · May 21st 2023

... yes and no ...

The NTFS is a mobile USB3- Drive that I often use to transfer a bigger bunch of data; much faster then over the LAN.

Last I have forget to unmount the drive. That's while it's missing in the log. Meanwhile I have connect it and unmount it well so this "error" is gone.

The other missing I have no clue where is comes from. I have no "hanging" mounts and also no hanging "shares" nowhere...

And now?

macom · May 21st 2023

I am confused. Is the line with the missing device now gone?

M*I*B · May 21st 2023

öhhh nope

We are talking about two different things (I think so).

The only hint to "NTFS" I have found in the error-message (the TXT- file). That one is gone if I use "omv-salt stage run deploy" again...

So that's why I say "that" problem is gone due it based on my own stupidity

The other one with the "lost drive" is still present. Meanwhile I have try to insert a CD and also a CF-card what I sometimes use. But that#s also not this one...

EDIT say:

Just before I send this I hava trigger the update again... just for fun... But now all updates are well done without errors.

So "this" problem is also gone.

Just the only one with the lost drive stay like a Elephant ...

macom · May 21st 2023

Post the output of

omv-confdbadm read --prettify conf.system.filesystem.mountpoint

M*I*B · May 21st 2023

... japp, here it is:

Code

[
    {
        "comment": "",
        "dir": "/",
        "freq": 0,
        "fsname": "/dev/sdb1",
        "hidden": true,
        "opts": "noatime,nodiratime,errors=remount-ro",
        "passno": 1,
        "type": "ext4",
        "usagewarnthreshold": 85,
        "uuid": "79684322-3eac-11ea-a974-63a080abab18"
    },
    {
        "comment": "",
        "dir": "/srv/dev-disk-by-uuid-9e9ea5b0-27d9-4c40-a2f2-d8a002e0f3a2",
        "freq": 0,
        "fsname": "/dev/disk/by-uuid/9e9ea5b0-27d9-4c40-a2f2-d8a002e0f3a2",
        "hidden": false,
        "opts": "defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl",
        "passno": 2,
        "type": "ext4",
        "usagewarnthreshold": 85,
        "uuid": "18a1192c-ef5c-438c-9c43-b62e2a1a2fb2"
    },
    {
        "comment": "",
        "dir": "/srv/dev-disk-by-uuid-fd72314a-9b1a-4983-b5ef-02e1f0a797be",
        "freq": 0,
        "fsname": "/dev/disk/by-uuid/fd72314a-9b1a-4983-b5ef-02e1f0a797be",
        "hidden": false,
        "opts": "defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl",
        "passno": 2,
        "type": "ext4",
        "usagewarnthreshold": 85,
        "uuid": "19669966-0c2a-42aa-b647-6f85d222644c"
    },
    {
        "comment": "",
        "dir": "/srv/dev-disk-by-uuid-60746FA2746F79A4",
        "freq": 0,
        "fsname": "/dev/disk/by-uuid/60746FA2746F79A4",
        "hidden": false,
        "opts": "defaults,nofail,big_writes",
        "passno": 2,
        "type": "ntfs",
        "usagewarnthreshold": 85,
        "uuid": "74329f41-398e-4453-b32a-7d21bb742d17"
    }
]

Display More

macom · May 21st 2023

ok, probably the device name of the root filesystem has changed.

Please post the output of

lsblk

blkid

M*I*B · May 21st 2023

Part 1:

Code

NAME    MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda       8:0    0   7.3T  0 disk
└─md127   9:127  0   7.3T  0 raid1 /srv/dev-disk-by-uuid-fd72314a-9b1a-4983-b5ef-02e1f0a797be
sdb       8:16   0   3.6T  0 disk
├─sdb1    8:17   0    16M  0 part
└─sdb2    8:18   0   3.6T  0 part  /srv/dev-disk-by-uuid-60746FA2746F79A4
sdc       8:32   0   7.3T  0 disk
└─md127   9:127  0   7.3T  0 raid1 /srv/dev-disk-by-uuid-fd72314a-9b1a-4983-b5ef-02e1f0a797be
sdd       8:48   0   1.8T  0 disk
└─md0     9:0    0   9.1T  0 raid6 /srv/dev-disk-by-uuid-9e9ea5b0-27d9-4c40-a2f2-d8a002e0f3a2
sde       8:64   0   1.8T  0 disk
└─md0     9:0    0   9.1T  0 raid6 /srv/dev-disk-by-uuid-9e9ea5b0-27d9-4c40-a2f2-d8a002e0f3a2
sdf       8:80   0   1.8T  0 disk
└─md0     9:0    0   9.1T  0 raid6 /srv/dev-disk-by-uuid-9e9ea5b0-27d9-4c40-a2f2-d8a002e0f3a2
sdg       8:96   0   1.8T  0 disk
└─md0     9:0    0   9.1T  0 raid6 /srv/dev-disk-by-uuid-9e9ea5b0-27d9-4c40-a2f2-d8a002e0f3a2
sdh       8:112  0   1.8T  0 disk
└─md0     9:0    0   9.1T  0 raid6 /srv/dev-disk-by-uuid-9e9ea5b0-27d9-4c40-a2f2-d8a002e0f3a2
sdi       8:128  0   1.8T  0 disk
└─md0     9:0    0   9.1T  0 raid6 /srv/dev-disk-by-uuid-9e9ea5b0-27d9-4c40-a2f2-d8a002e0f3a2
sdj       8:144  0   1.8T  0 disk
└─md0     9:0    0   9.1T  0 raid6 /srv/dev-disk-by-uuid-9e9ea5b0-27d9-4c40-a2f2-d8a002e0f3a2
sdk       8:160  0 111.8G  0 disk
├─sdk1    8:161  0 110.8G  0 part  /
├─sdk2    8:162  0     1K  0 part
└─sdk5    8:165  0   975M  0 part  [SWAP]
sr0      11:0    1 624.5M  0 rom

Display More

Part 2:

Code

/dev/sdk1: UUID="3b083fc5-63be-4223-8433-5f290da0d13a" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="d9c2d5b5-01"
/dev/sdk5: UUID="1cef33c4-6fa3-4389-9671-a5f1cb6525a3" TYPE="swap" PARTUUID="d9c2d5b5-05"
/dev/sda: UUID="cb4bd60b-28ed-16b8-d5b6-0d15fb3452b8" UUID_SUB="45a5aebd-f205-610c-43fb-f9d78bf7f9a7" LABEL="SV-OMV-NAS:2x8tb" TYPE="linux_raid_member"
/dev/sdc: UUID="cb4bd60b-28ed-16b8-d5b6-0d15fb3452b8" UUID_SUB="5f421642-05ea-b9bb-8a17-43bee29aea62" LABEL="SV-OMV-NAS:2x8tb" TYPE="linux_raid_member"
/dev/sdi: UUID="1b709ca8-3129-c241-2467-2dd6143d2853" UUID_SUB="1885f70c-d32b-4118-e422-cfcfaf34db5e" LABEL="SV-OMV-NAS:0" TYPE="linux_raid_member"
/dev/sdh: UUID="1b709ca8-3129-c241-2467-2dd6143d2853" UUID_SUB="dd52a85e-b07c-3026-5c41-084c0fe209ad" LABEL="SV-OMV-NAS:0" TYPE="linux_raid_member"
/dev/sdg: UUID="1b709ca8-3129-c241-2467-2dd6143d2853" UUID_SUB="90a880a9-f59e-14ec-7d45-987ea0d8a30c" LABEL="SV-OMV-NAS:0" TYPE="linux_raid_member"
/dev/sde: UUID="1b709ca8-3129-c241-2467-2dd6143d2853" UUID_SUB="407e446b-a47d-cb07-45e7-ceb09c0ee993" LABEL="SV-OMV-NAS:0" TYPE="linux_raid_member"
/dev/sdd: UUID="1b709ca8-3129-c241-2467-2dd6143d2853" UUID_SUB="227376e3-1b1e-5ab5-9585-6399142bbf48" LABEL="SV-OMV-NAS:0" TYPE="linux_raid_member"
/dev/sdf: UUID="1b709ca8-3129-c241-2467-2dd6143d2853" UUID_SUB="a54476e8-287c-cf29-cc64-6a30aefc97a2" LABEL="SV-OMV-NAS:0" TYPE="linux_raid_member"
/dev/sdj: UUID="1b709ca8-3129-c241-2467-2dd6143d2853" UUID_SUB="3e63183d-e6ca-b6d0-7650-44a9ab5d6b44" LABEL="SV-OMV-NAS:0" TYPE="linux_raid_member"
/dev/sdb2: LABEL="WD-RED-4TB-1" BLOCK_SIZE="512" UUID="60746FA2746F79A4" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="63110a97-0a51-42fc-aece-3f0ca4d6e8e3"
/dev/md127: LABEL="2x8tb" UUID="fd72314a-9b1a-4983-b5ef-02e1f0a797be" BLOCK_SIZE="4096" TYPE="ext4"
/dev/md0: LABEL="RAID6" UUID="9e9ea5b0-27d9-4c40-a2f2-d8a002e0f3a2" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sr0: BLOCK_SIZE="2048" UUID="2007-08-11-11-39-00-0" LABEL="DVD-W" TYPE="iso9660"
/dev/sdb1: PARTLABEL="Microsoft reserved partition" PARTUUID="adc2c666-abeb-446d-b69f-7c1b57c9feaa"

Display More

macom · May 21st 2023

The root filesystem is now sdk1 with UUID

3b083fc5-63be-4223-8433-5f290da0d13a

Make a copy of the file /etc/openmediavault/config.xml

cp /etc/openmediavault/config.xml /etc/openmediavault/config.xml.bak

than edit the file with nano

nano /etc/openmediavault/config.xml

search for the mntent section with these values

Code

        "comment": "",
        "dir": "/",
        "freq": 0,
        "fsname": "/dev/sdb1",
        "hidden": true,
        "opts": "noatime,nodiratime,errors=remount-ro",
        "passno": 1,
        "type": "ext4",
        "usagewarnthreshold": 85,
        "uuid": "79684322-3eac-11ea-a974-63a080abab18"

and change the fsname to

Code

"fsname": "/dev/disk/by-uuid/3b083fc5-63be-4223-8433-5f290da0d13a",

save the file with Ctrl+x and y

M*I*B · May 21st 2023

... tadaaaaa

Thank you very much for that! That I never haven't solve by myself

Now it work's well like a charm... Great work!

By the way: Is there a way to use a simple name insteed of the UUID? Ok, meanwhile I know where the RAID or the Mirror is but using the UUID is brainbreaking sometimes ...

macom · May 21st 2023

You can create a symlink (symbolic link) to the mount point.

omv6:omv6_plugins:symlinks [omv-extras.org]

M*I*B · May 21st 2023

... ty for that hint! I will try that later; family-time right now ...

Upgrade goes well but not possible to update of modules

macom May 21st 2023

Participate now!