GUI shows filesystem as unmounted but online

Hello

Can anyone explain or help me find out what's going on here?

In the Workbench GUI under 'Storage > Filesystems' I have /dev/sdf1 showing as Online but not showing as Mounted and not showing Available and Used data.

/dev/sdf1 is not a primary drive. It's a 250GB SATA SSD, It has a single EXT4 filesystem on it and it's being used as a Docker drive.

The Workbench shows Docker is running but no containers are up.

If I ssh into the server as root and run

fsck -r /dev/sdf1

fsck from util-linux 2.38.1

e2fsck 1.47.0 (5-Feb-2023)

/dev/sdf1: clean, 133280/14655488 files, 18975302/58607505 blocks

/dev/sdf1: status 0, rss 3224, real 0.065613, user 0.051157, sys 0.007308

However the main login screen on the server shortly after boot shows some errors.

How best to resolve this?

---------EDIT---------

Ok, so a reboot, after backing up the files from /dev/sdf1, seems to have returned operations to normal. Puzzling.

Agreed. I do have a spare, and will try and find out how to do that with as little disruption as I can manage.

There's other weirdness going on though.

I just tried to do a long SMART check on all disks. Rebooted and now the SSD has been allocated /dev/sdg, is no longer mounted.

ssh terminal fsck goes like this:

------------------------------------------------------

root@openmediavault:/SSD# fsck /dev/sdg

fsck from util-linux 2.38.1

e2fsck 1.47.0 (5-Feb-2023)

ext2fs_open2: Bad magic number in super-block

fsck.ext2: Superblock invalid, trying backup blocks...

fsck.ext2: Bad magic number in super-block while trying to open /dev/sdg

The superblock could not be read or does not describe a valid ext2/ext3/ext4

filesystem. If the device is valid and it really contains an ext2/ext3/ext4

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

or

e2fsck -b 32768 <device>

Found a gpt partition table in /dev/sdg

------------------------------------------------------

Why would the device have changed to sdg from sdf?

And why previously was terminal allowing me to use the drive when Workbench was telling me it wasn't mounted?

fstab:

"

# /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/sde1 during installation

UUID=9b36022c-2b73-4b94-b2bb-53456657a0b7 / ext4 errors=remount-ro 0 1

# swap was on /dev/sde5 during installation

UUID=ce2a6927-fa22-44f9-8294-1394aad80d94 none swap sw 0 0

# >>> [openmediavault]

/dev/disk/by-uuid/35a47e11-1aa8-4377-95c9-152c61c299e8 /srv/dev-disk-by-uuid-35a47e11-1aa8-4377-95c9-152c61c299e8 btrfs defaults,nofail 0 2

/dev/disk/by-uuid/2c62bcbd-048f-41fa-9ff2-9c5a24846daa /srv/dev-disk-by-uuid-2c62bcbd-048f-41fa-9ff2-9c5a24846daa ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2

/srv/dev-disk-by-uuid-35a47e11-1aa8-4377-95c9-152c61c299e8/music/ /export/music none bind,nofail 0 0

/srv/dev-disk-by-uuid-35a47e11-1aa8-4377-95c9-152c61c299e8/videos/ /export/videos none bind,nofail 0 0

/srv/dev-disk-by-uuid-35a47e11-1aa8-4377-95c9-152c61c299e8/roms/ /export/roms none bind,nofail 0 0

#"

I'm reasonably sure I have done all filesystem mounting and shared folder creation via the UI rather than command line. I know that's the preferred way for OMV. I have set up a couple of symlinks via the shell while going through a docker installation guide.

My docker setup is a bit organic (read messy). I set it up with no prior knowledge of it by following guides when it was still being administered through Portainer in omv-extras. It could probably do with being set up from scratch anyway.

Quote from votdev

When does the mentioned message above occur? During boot?

Just after boot. It displays immediately after the OS login prompt. It isn't displaying now though.

Is there a log that's likely to contain all boot-time errors and warnings?

blkid:

/dev/sdd: UUID="aaf99d91-c874-dbc3-0ec7-122970ab3e04" UUID_SUB="490f6a8b-0b12-04a1-2eb6-3baa1ac28677" LABEL="openmediavault:0" TYPE="linux_raid_member"

/dev/sdb: UUID="aaf99d91-c874-dbc3-0ec7-122970ab3e04" UUID_SUB="f5110151-9307-0497-8d75-28e543596148" LABEL="openmediavault:0" TYPE="linux_raid_member"

/dev/md0: UUID="35a47e11-1aa8-4377-95c9-152c61c299e8" UUID_SUB="0fe6c128-f429-44f4-86ea-a363685c85aa" BLOCK_SIZE="4096" TYPE="btrfs"

/dev/sde: UUID="aaf99d91-c874-dbc3-0ec7-122970ab3e04" UUID_SUB="795a53cc-3c7b-df96-c9e4-2142deda181b" LABEL="openmediavault:0" TYPE="linux_raid_member"

/dev/sdc5: UUID="ce2a6927-fa22-44f9-8294-1394aad80d94" TYPE="swap" PARTUUID="41916acc-05"

/dev/sdc1: UUID="9b36022c-2b73-4b94-b2bb-53456657a0b7" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="41916acc-01"

/dev/sda: UUID="aaf99d91-c874-dbc3-0ec7-122970ab3e04" UUID_SUB="7f611cb4-4c0c-0e92-ea10-0682820650ef" LABEL="openmediavault:0" TYPE="linux_raid_member"

/dev/sdg1: UUID="2c62bcbd-048f-41fa-9ff2-9c5a24846daa" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0cb861fd-531c-4c89-815b-93e542b49e1c"

It became sdg after a reboot.