File systems section does not see previously created file systems (EXT4) which were created in after OMV7 reinstallation OMV7

1st Official Post
    Environment:

    - OS Debian 12

    Precondition:

    - none

    Steps to reproduce:

    1. Install openmediavault

    Code
    apt install openmediavault

    2. Go to section "Strage -> Disks"

    3. Create Disks1 and Wipe on Safety mode

    4. Go to section "Strage -> File Systems"

    5. Create and moun a file system for Disks1 in EXT4

    6. Go to section "Services -> SMB -> Settings" and Enabled SMB service

    7. Go to section "Services -> SMB -> Shares" and create Shares for Disks1

    8. Uninstall openmediavault

    Code
    apt purge openmediavault

    9. Delete all dependencies folders for OMV7

    10. Install openmediavault


    Сause Uninstall and Install openmediavault see:

    502 Bad Gateway after update OMV 5 --> 6 --> 7 · Issue #1943 · openmediavault/openmediavault
    Please only open an issue here, when advised by a moderator in openmediavault forum. Requests for support and questions shall be addressed first to…
    github.com

    Code
    apt install openmediavault
    Actual result:

    - In section "Strage -> File Systems" does not see previously created file systems (EXT4)

    Expected result:

    - In section "Strage -> File Systems" see previously created file systems (EXT4)

    • Official Post

    I would blame this on a bad upgrade from omv 6 to 7. I have upgraded dozens of times and ext4 filesystems always mount. I'm guessing the fix6to7upgrade script (search the forum) would've fixed your issue. Purging and reinstalling OMV shouldn't have changed ext4 filesystem recognition.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Quote from ryecoaaron

    I would blame this on a bad upgrade from omv 6 to 7. I have upgraded dozens of times and ext4 filesystems always mount. I'm guessing the fix6to7upgrade script (search the forum) would've fixed your issue. Purging and reinstalling OMV shouldn't have changed ext4 filesystem recognition.

    ryecoaaron,


    the same problem was in the version OMV5

    - in section "Strage -> Disks" - two disks are present (see scrinshot)

    - in section "Strage -> File Systems" - two disks are absent (see scrinshot)



    In this case, if you create a file system two disks are absent too

    • Official Post

    That is because your sata device is presenting the OS with the same serial number for both drives. This is bad behavior. OMV 5 may have allowed it but this is not a bug in OMV 7.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post
    Quote from ryecoaaron

    That is because your sata device is presenting the OS with the same serial number for both drives.

    Good spotting.


    Vitaly1985 This duplicate serial ID problem is often seen here in the forum and is caused by USB/SATA adapters with chipsets that do no bypass the original serial ID of the disks. How are the disks connected?


    Previously a user has reported that problem here. OMV is bypassing this firmware bug of several controllers via UDEV rules. You can fix the problem with your own UDEV rule or by replacing the hardware with a controller that does not have such a bug or which is already included in the OMV UDEV rules.

    Quote from votdev

    Good spotting.


    Vitaly1985 This duplicate serial ID problem is often seen here in the forum and is caused by USB/SATA adapters with chipsets that do no bypass the original serial ID of the disks. How are the disks connected?


    Previously a user has reported that problem here. OMV is bypassing this firmware bug of several controllers via UDEV rules. You can fix the problem with your own UDEV rule or by replacing the hardware with a controller that does not have such a bug or which is already included in the OMV UDEV rules.

    Sata, see screenshots up

    • Official Post
    Quote from Vitaly1985

    Sata, see screenshots up

    Via PCI extender or directly on the motherboard?


    Regardless how the disks are connected, they seem to have the same serial number which causes problems because this serial number is part of the device file which is used to access the disk. If there are two, the system does not know which disk is meant.

    This is a general problem and does not only apply to OMV.

    Quote from votdev

    Via PCI extender or directly on the motherboard?


    Regardless how the disks are connected, they seem to have the same serial number which causes problems because this serial number is part of the device file which is used to access the disk. If there are two, the system does not know which disk is meant.

    This is a general problem and does not only apply to OMV.

    Two disks connected directly on the motherboard for sata (kabel) + power kabel at the block power

    Quote from votdev

    Please post the output of the command for both disks.

    Code
    # udevadm info --query=all --name=<DEVICEPATH>

    E.g. udevadm info --query=all --name=/dev/sda

    Disk1


    root@nas-omv:~# udevadm info --query=all --name=/dev/sdb

    P: /devices/pci0000:00/0000:00:0f.0/ata5/host4/target4:0:0/4:0:0:0/block/sdb

    M: sdb

    U: block

    T: disk

    D: b 8:16

    N: sdb

    L: 0

    S: disk/by-id/ata-TOSHIBA_HDWD110_114BABHFS

    S: disk/by-path/pci-0000:00:0f.0-ata-1

    S: disk/by-id/wwn-0x5000039fc2c52703

    S: disk/by-path/pci-0000:00:0f.0-ata-1.0

    S: disk/by-diskseq/2

    Q: 2

    E: DEVPATH=/devices/pci0000:00/0000:00:0f.0/ata5/host4/target4:0:0/4:0:0:0/bloc>

    E: DEVNAME=/dev/sdb

    E: DEVTYPE=disk

    E: DISKSEQ=2

    E: MAJOR=8

    E: MINOR=16

    E: SUBSYSTEM=block

    E: USEC_INITIALIZED=3616935

    E: ID_ATA=1

    E: ID_TYPE=disk

    E: ID_BUS=ata

    E: ID_MODEL=TOSHIBA_HDWD110

    E: ID_MODEL_ENC=TOSHIBA\x20HDWD110\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\>

    E: ID_REVISION=MS2OA8R0

    E: ID_SERIAL=TOSHIBA_HDWD110_114BABHFS

    E: ID_SERIAL_SHORT=114BABHFS

    E: ID_ATA_WRITE_CACHE=1

    E: ID_ATA_WRITE_CACHE_ENABLED=1

    E: ID_ATA_FEATURE_SET_HPA=1

    E: ID_ATA_FEATURE_SET_HPA_ENABLED=1

    E: ID_ATA_FEATURE_SET_PM=1

    E: ID_ATA_FEATURE_SET_PM_ENABLED=1

    E: ID_ATA_FEATURE_SET_SECURITY=1

    E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0

    E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=152

    E: ID_ATA_FEATURE_SET_SMART=1

    E: ID_ATA_FEATURE_SET_SMART_ENABLED=1

    E: ID_ATA_FEATURE_SET_PUIS=1

    E: ID_ATA_FEATURE_SET_PUIS_ENABLED=0

    E: ID_ATA_FEATURE_SET_APM=1

    E: ID_ATA_FEATURE_SET_APM_ENABLED=0

    E: ID_ATA_DOWNLOAD_MICROCODE=1

    E: ID_ATA_SATA=1

    E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1

    E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1

    E: ID_ATA_ROTATION_RATE_RPM=7200

    E: ID_WWN=0x5000039fc2c52703

    E: ID_WWN_WITH_EXTENSION=0x5000039fc2c52703

    E: ID_PATH=pci-0000:00:0f.0-ata-1.0

    E: ID_PATH_TAG=pci-0000_00_0f_0-ata-1_0

    E: ID_PATH_ATA_COMPAT=pci-0000:00:0f.0-ata-1

    E: ID_PART_TABLE_UUID=e320b427-3cac-48cb-ac96-6038455e58d0

    E: ID_PART_TABLE_TYPE=gpt

    E: DEVLINKS=/dev/disk/by-id/ata-TOSHIBA_HDWD110_114BABHFS /dev/disk/by-path/pci>

    E: TAGS=:systemd:

    E: CURRENT_TAGS=:systemd:


    lines 38-60/60 (END)

    E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=152

    E: ID_ATA_FEATURE_SET_SMART=1

    E: ID_ATA_FEATURE_SET_SMART_ENABLED=1

    E: ID_ATA_FEATURE_SET_PUIS=1

    E: ID_ATA_FEATURE_SET_PUIS_ENABLED=0

    E: ID_ATA_FEATURE_SET_APM=1

    E: ID_ATA_FEATURE_SET_APM_ENABLED=0

    E: ID_ATA_DOWNLOAD_MICROCODE=1

    E: ID_ATA_SATA=1

    E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1

    E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1

    E: ID_ATA_ROTATION_RATE_RPM=7200

    E: ID_WWN=0x5000039fc2c52703

    E: ID_WWN_WITH_EXTENSION=0x5000039fc2c52703

    E: ID_PATH=pci-0000:00:0f.0-ata-1.0

    E: ID_PATH_TAG=pci-0000_00_0f_0-ata-1_0

    E: ID_PATH_ATA_COMPAT=pci-0000:00:0f.0-ata-1

    E: ID_PART_TABLE_UUID=e320b427-3cac-48cb-ac96-6038455e58d0

    E: ID_PART_TABLE_TYPE=gpt

    E: DEVLINKS=/dev/disk/by-id/ata-TOSHIBA_HDWD110_114BABHFS /dev/disk/by-path/pci-0000:00:0f.0-ata-1 /dev/disk/by-id/wwn-0x5000039fc2c52703 /dev/disk/by-path/pci-0000:00:0f.0-ata-1.0 /dev/disk/by-di>

    E: TAGS=:systemd:

    E: CURRENT_TAGS=:systemd:




    Disk2


    root@nas-omv:~# udevadm info --query=all --name=/dev/sdc

    P: /devices/pci0000:00/0000:00:0f.0/ata6/host5/target5:0:0/5:0:0:0/block/sdc

    M: sdc

    U: block

    T: disk

    D: b 8:32

    N: sdc

    L: 0

    S: disk/by-path/pci-0000:00:0f.0-ata-2.0

    S: disk/by-diskseq/3

    S: disk/by-path/pci-0000:00:0f.0-ata-2

    S: disk/by-id/wwn-0x5000039fc2c52707

    S: disk/by-id/ata-TOSHIBA_HDWD110_114BABMFS

    Q: 3

    E: DEVPATH=/devices/pci0000:00/0000:00:0f.0/ata6/host5/target5:0:0/5:0:0:0/block/sdc

    E: DEVNAME=/dev/sdc

    E: DEVTYPE=disk

    E: DISKSEQ=3

    E: MAJOR=8

    E: MINOR=32

    E: SUBSYSTEM=block

    E: USEC_INITIALIZED=3668802

    E: ID_ATA=1

    E: ID_TYPE=disk

    E: ID_BUS=ata

    E: ID_MODEL=TOSHIBA_HDWD110

    E: ID_MODEL_ENC=TOSHIBA\x20HDWD110\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20

    E: ID_REVISION=MS2OA8R0

    E: ID_SERIAL=TOSHIBA_HDWD110_114BABMFS

    E: ID_SERIAL_SHORT=114BABMFS

    E: ID_ATA_WRITE_CACHE=1

    E: ID_ATA_WRITE_CACHE_ENABLED=1

    E: ID_ATA_FEATURE_SET_HPA=1

    E: ID_ATA_FEATURE_SET_HPA_ENABLED=1

    E: ID_ATA_FEATURE_SET_PM=1

    E: ID_ATA_FEATURE_SET_PM_ENABLED=1

    E: ID_ATA_FEATURE_SET_SECURITY=1

    E: ID_ATA_FEATURE_SET_SECURITY_ENABLED=0

    E: ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN=148

    E: ID_ATA_FEATURE_SET_SMART=1

    E: ID_ATA_FEATURE_SET_SMART_ENABLED=1

    E: ID_ATA_FEATURE_SET_PUIS=1

    E: ID_ATA_FEATURE_SET_PUIS_ENABLED=0

    E: ID_ATA_FEATURE_SET_APM=1

    E: ID_ATA_FEATURE_SET_APM_ENABLED=0

    E: ID_ATA_DOWNLOAD_MICROCODE=1

    E: ID_ATA_SATA=1

    E: ID_ATA_SATA_SIGNAL_RATE_GEN2=1

    E: ID_ATA_SATA_SIGNAL_RATE_GEN1=1

    E: ID_ATA_ROTATION_RATE_RPM=7200

    E: ID_WWN=0x5000039fc2c52707

    E: ID_WWN_WITH_EXTENSION=0x5000039fc2c52707

    E: ID_PATH=pci-0000:00:0f.0-ata-2.0

    E: ID_PATH_TAG=pci-0000_00_0f_0-ata-2_0

    E: ID_PATH_ATA_COMPAT=pci-0000:00:0f.0-ata-2

    E: ID_PART_TABLE_UUID=3468f4e0-71d9-4861-bbc4-4b9b631186dd

    E: ID_PART_TABLE_TYPE=gpt

    E: DEVLINKS=/dev/disk/by-path/pci-0000:00:0f.0-ata-2.0 /dev/disk/by-diskseq/3 /dev/disk/by-path/pci-0000:00:0f.0-ata-2 /dev/disk/by-id/wwn-0x5000039fc2c52707 /dev/disk/by-id/ata-TOSHIBA_HDWD110_11>

    E: TAGS=:systemd:

    E: CURRENT_TAGS=:systemd:

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login