Non existing partition

1. offizieller Beitrag

    Greetings,

    I created a btrfs pool with two ssds (sda & sdb). The pool is working fine. OMV is saying that sda1 exists and is somehow missing, which I don't understand. As you can see, lsblk shows sda1 does not exist. Is it safe to delete this entry from the file system list?


    Thanks in advance



    • Offizieller Beitrag

    Possibly that entry corresponds to a disk removed without previously unmounting. Do you remember doing this?

    If you have no more connected disks than the BTRFS pool on sda and sdb and OMV on sdc, it should be safe to remove that line.

  • chente

    Hat das Label OMV 5.x hinzugefügt.

    Thanks for the reply. I tried to mount it but it gave errors. I didn't think it was mounted, but apparently, it was. The mount point no longer exists in the system. I noticed it did appear in /etc/fstab. I removed it from there thinking this would fix the issues but it is still showing.

    Update:


    I reformatted the external drive as btrfs and was able to mount it. I also deleted the nonexistent /dev/sda1 ext4 portion through the webGUI. (see attached image).


    Everything seems to be as it should, HOWEVER, I still cannot find a way to remove or even find the CE7* device on the system. GREP returns a bunch of stuff in proc/sys/net and proc/sys/vm directories.


    On top of that, when I 'apply' the configuration the system bugs out and reboots.


    This is all very troubling and unstable. I'm inclined to reinstall OMV and try to reconnect to the current working file systems and re-setup the shares. That will be a ton of work, however, and would prefer to fix what is wrong with the current filesystem setup.

    Run this and post the output:

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

    I was able to remove references to the missing drive and also found this post which describes how to remove the mntent entry in the config.xml file. This seems to fix the issue with the missing file systems above. At least they no longer show in the menu.


    I can't, however, get the drive to properly mount. After removing the 'missing' filesystems, I plugged the external drive back in (Seagate Expansion Desk) and tried to mount it. This results in another system reboot.


    This is the output of Soma's command with the drive unplugged after a reboot.

    I did manage to mount the file system earlier but 'applying' the configuration resulted in a system reboot loop. I ended up 'reverting' the mount. The entry here seems to be a vestige of that previous mount.


    By the way, the drive works fine on other computers. It also worked fine temporarily before the configuration was 'applied'. I do not think there is anything wrong with the drive.


    Thanks again.

    You mean the drive with error is this:

    Zitat von verlyn13

    After removing the 'missing' filesystems, I plugged the external drive back in (Seagate Expansion Desk) and tried to mount it.


    And that this is still showing after you booted without it plugged???

    Code
        {
        "dir": "/srv/dev-disk-by-id-usb-Seagate_Expansion_Desk_NA8EL6S6-0-0-part1",
        "freq": 0,
        "fsname": "/dev/disk/by-id/usb-Seagate_Expansion_Desk_NA8EL6S6-0:0-part1",
        "hidden": false,
        "opts": "defaults,nofail",
        "passno": 2,
        "type": "btrfs",
        "uuid": "cc92231e-ecde-4f67-94bf-d12907bdd8d2"
    }



    What is the output of:

    ls -al /dev/disk/by-uuid/

    Zitat

    And that this is still showing after you booted without it plugged???

    That is correct.


    Though this morning I was greeted with the 'apply configuration' screen again. I was not sure what configuration it was referring to so I reverted. Now the output of omv-confdbadm read --prettify conf.system.filesystem.mountpoint


    does not show the drive. My guess was there was some delay from when I tried to mount it before? Not sure.




    Output of ls -al /dev/disk/by-uuid/ is

    Code
    total 0
drwxr-xr-x 2 root root 140 Dec  7 07:51 .
drwxr-xr-x 7 root root 140 Dec  7 07:51 ..
lrwxrwxrwx 1 root root  10 Dec  7 07:51 51513067-c7c1-4b03-bf61-40dbd6e63662 -> ../../sda1
lrwxrwxrwx 1 root root   9 Dec  7 07:51 57a423cb-19b3-463d-899b-1563396dc1b0 -> ../../sdg
lrwxrwxrwx 1 root root   9 Dec  7 07:51 8fd7be99-ff9e-4de2-8ab0-e87f53e145c8 -> ../../sdb
lrwxrwxrwx 1 root root  10 Dec  7 07:51 b1a097fc-260c-4a72-8e62-66c9ac664c85 -> ../../sdh1
lrwxrwxrwx 1 root root  10 Dec  7 07:51 b6c67988-6afe-4ab5-ace6-c2096b1bd259 -> ../../sda5


    output of lsblk is



    This all looks good and normal as far as I can tell. I don't understand the fickle nature of the system when I try to plug in and mount the seagate external drive.



Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden