Please Help - File System Gone Missing Overnight

  • Hi all,


    overnight, my filesystem has become "missing" according to the omv gui. The Disk itself is still present (even after scanning) in the disks' menu.

    I can see the "base" Folders of my shared folders when I ssh to my machine, but all my data is missing... My Backup drive is literally arriving tomorrow :(


    I don't care much about fixing it to run with omv again; I can set that up from scratch, no problem. But I really need my data back!


    I only tried restarting a couple of times and (un-)plugging the disk so far, as I didn't want to break anything else.


    Logs of omv: https://pastebin.pl/view/852cfab1 (192.168.8.159 is another omv instance on another device, not sure why this is referenced here…)

    It is installed natively on a surface Laptop 3


    Please let me know if I should provide anything else, thanks!

  • votdev

    Approved the thread.
  • Quote

    I can see the "base" Folders of my shared folders when I ssh to my machine

    I think this is created by my docker instances, as only the Config etc. parts (which are generated) exist. So, probably the whole /srv/dev-xxxx folder is not "real" but only setup by docker

  • If the system rebooted without mounting the disks and docker started to write files inside the mount oint directories, our disks will not be mounted because the mount point is not empty.


    what does mount tell you?

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • Thank you for your answer; that makes sense.


    mount output is:


  • mount output continued (no idea why it's this long)


    Code
    overlay on /var/lib/docker/overlay2/ce5309ed382fd0ba9363048395c88741e7c4afdec3a11fb1a18a9615782602e8/merged type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/FXZTJRKNWDUQOIBFTFCWS4XOOR:/var/lib/docker/overlay2/l/YLPITE46WVJMQH3UODAYRFKOFL:/var/lib/docker/overlay2/l/7Q5UUOQD6DC37LN6YL4T4OBCXC:/var/lib/docker/overlay2/l/F6Y7LP46U5CWHAXHNO5BJXQ2WX:/var/lib/docker/overlay2/l/2LGR2USXGVTS5VJBZO2DXXT7E6:/var/lib/docker/overlay2/l/PVP7JFMAK376P37NV2OE6WH2H6:/var/lib/docker/overlay2/l/ZOJGYK32TWSNFZENDIUFTXXK7C:/var/lib/docker/overlay2/l/ZPB4CEPQLLI5WG7ED6RGM6Z2P5,upperdir=/var/lib/docker/overlay2/ce5309ed382fd0ba9363048395c88741e7c4afdec3a11fb1a18a9615782602e8/diff,workdir=/var/lib/docker/overlay2/ce5309ed382fd0ba9363048395c88741e7c4afdec3a11fb1a18a9615782602e8/work)
    overlay on /var/lib/docker/overlay2/d4029e1325bdd6a04d8b5e6c04a420580762048692abdfc26d491c809d56526a/merged type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/P6EBZWMK7T4OB252D2AG5FH3Z4:/var/lib/docker/overlay2/l/7YA44VIH2SLGGMJU5WUS75AMFL:/var/lib/docker/overlay2/l/NXGI4P24DGHPPHB5G65L7RLXHV:/var/lib/docker/overlay2/l/Y4JE5LURXEYIRZO5WRUESMF3H7:/var/lib/docker/overlay2/l/NHETB6QOCXWVKG5NKRYIQH3X4J:/var/lib/docker/overlay2/l/F6WFARKGFPVX27CRPXEI3J7DRS:/var/lib/docker/overlay2/l/22FF53HRB4WTF2VDN5UPPVR3RN:/var/lib/docker/overlay2/l/Q25JW367ZRMNZ7JHRG7OZYMBYG:/var/lib/docker/overlay2/l/LTYN6T7SILH454GJVYNQOSAJ2V:/var/lib/docker/overlay2/l/GQCE4EV6RSUGTN24V73GXEE3OH:/var/lib/docker/overlay2/l/BR7UVQWFS6IYGCE4KNJB7PKE52,upperdir=/var/lib/docker/overlay2/d4029e1325bdd6a04d8b5e6c04a420580762048692abdfc26d491c809d56526a/diff,workdir=/var/lib/docker/overlay2/d4029e1325bdd6a04d8b5e6c04a420580762048692abdfc26d491c809d56526a/work)
    overlay on /var/lib/docker/overlay2/fdcc438a1138d8a5b942a9e60ca157e317a9fe036ae0cb71b275dde3600db1e4/merged type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/QUUC2RTYN6FM6LGX6SK434GJQS:/var/lib/docker/overlay2/l/WDS2LYBWB3XFNHM66B7F4CP3SP:/var/lib/docker/overlay2/l/EN2WXKMI5MN2SGZPQTH6MJAJQF:/var/lib/docker/overlay2/l/NHETB6QOCXWVKG5NKRYIQH3X4J:/var/lib/docker/overlay2/l/F6WFARKGFPVX27CRPXEI3J7DRS:/var/lib/docker/overlay2/l/22FF53HRB4WTF2VDN5UPPVR3RN:/var/lib/docker/overlay2/l/Q25JW367ZRMNZ7JHRG7OZYMBYG:/var/lib/docker/overlay2/l/LTYN6T7SILH454GJVYNQOSAJ2V:/var/lib/docker/overlay2/l/GQCE4EV6RSUGTN24V73GXEE3OH:/var/lib/docker/overlay2/l/BR7UVQWFS6IYGCE4KNJB7PKE52,upperdir=/var/lib/docker/overlay2/fdcc438a1138d8a5b942a9e60ca157e317a9fe036ae0cb71b275dde3600db1e4/diff,workdir=/var/lib/docker/overlay2/fdcc438a1138d8a5b942a9e60ca157e317a9fe036ae0cb71b275dde3600db1e4/work)
    overlay on /var/lib/docker/overlay2/6e3fbb81597adec32018a3f6566cf83f2f39e3ac6364daed84eeebefdfa6acaa/merged type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/XBTC6YEK3FVGVLGJ6UI2F2K4LF:/var/lib/docker/overlay2/l/P2H2HEJFWKQNMQY72CNQ2OZHSR:/var/lib/docker/overlay2/l/W4AHWSAJUC5OMEGFQPGL4OSFS4:/var/lib/docker/overlay2/l/V5WSHS46EQHZGXSHP3SQAAHH6E:/var/lib/docker/overlay2/l/LZ6KYV2JV34JF4XKZF67U2FJCX:/var/lib/docker/overlay2/l/FPDUCYBPDR43LI5WA5XY3WXLZZ:/var/lib/docker/overlay2/l/OD66ZFHBRBKKZR2JMBK6BIVW7J:/var/lib/docker/overlay2/l/QTNJFFH5P7CTFF435AW4L7WFDQ:/var/lib/docker/overlay2/l/QAPG74X4IRLVRYUHGQD32VHLNV:/var/lib/docker/overlay2/l/QKNZMIIUP5EZVFTS5GYGYH3WUT,upperdir=/var/lib/docker/overlay2/6e3fbb81597adec32018a3f6566cf83f2f39e3ac6364daed84eeebefdfa6acaa/diff,workdir=/var/lib/docker/overlay2/6e3fbb81597adec32018a3f6566cf83f2f39e3ac6364daed84eeebefdfa6acaa/work)
    overlay on /var/lib/docker/overlay2/6caea4b81da2af84f68a3501fd5ba65bbb4c2214addfca23f398b03da78c0651/merged type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/L4D2XM6YZFSGNETMPDLDNVVTSE:/var/lib/docker/overlay2/l/ZMSMXQUI44MADI2ARI4OC642VT:/var/lib/docker/overlay2/l/4SKMQTQZQBXNDF32UAJPQO6FUT:/var/lib/docker/overlay2/l/B7P6ERN32OXVX7U7ELR7AMDUOG:/var/lib/docker/overlay2/l/7HJX5TUODKDP5W6ZRW3IB53BS6:/var/lib/docker/overlay2/l/E6SWQO3DCINOSLBYX4NCIBLK7M:/var/lib/docker/overlay2/l/A4HJ3RGIZG7KQL5AVIPOWJ6YQV:/var/lib/docker/overlay2/l/ZHAJINHHI6TGJHLTAU2437TT2F:/var/lib/docker/overlay2/l/NU6BZXPY66LJAJTDUJBMLBXZYP,upperdir=/var/lib/docker/overlay2/6caea4b81da2af84f68a3501fd5ba65bbb4c2214addfca23f398b03da78c0651/diff,workdir=/var/lib/docker/overlay2/6caea4b81da2af84f68a3501fd5ba65bbb4c2214addfca23f398b03da78c0651/work)
  • mount output continued 2

  • The Disk itself is still present (even after scanning) in the disks' menu.

    According to your mount, you only have nvme drive shown.


    What and how is the drive that's missing connected to the system?


    And the output of blkid && lsblk

    Also cat /etc/fstab

  • Oops sorry, I forgot to plug the disk in again before mount :S


    (after reboot)

    mount

  • mount cont.

  • blkid


    Code
    /dev/nvme0n1p1: UUID="C839-C24F" TYPE="vfat" PARTUUID="f6bbf71c-b1e4-40a8-a312-362286af619d"
    /dev/nvme0n1p2: UUID="533d4cd4-c694-44c0-96cd-298650c759c5" TYPE="ext4" PARTUUID="0f2826d9-bda5-4feb-a5f4-b9e9198c1c7d"
    /dev/nvme0n1p3: UUID="27cfad1c-4365-4dcd-beae-a84b24998bc7" TYPE="swap" PARTUUID="bd10875c-b52d-4d3b-a9c1-3d6d613cdfcd"
    /dev/nvme0n1: PTUUID="117da594-6e58-4147-be9a-a17c35821b9f" PTTYPE="gpt"



    lsblk


    Code
    NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
    sda           8:0    0   5.5T  0 disk 
    nvme0n1     259:0    0 119.2G  0 disk 
    |-nvme0n1p1 259:1    0   512M  0 part /boot/efi
    |-nvme0n1p2 259:2    0 117.8G  0 part /
    `-nvme0n1p3 259:3    0   977M  0 part [SWAP]


    cat /etc/fstab



    drive is connected via the original usb cable


    thanks!

  • You can try mount -a to see if it mounts.

    The sda is referenced on the fstab so, it should mount.

  • sudo fdisk -l /dev/sda

    Code
    Disk /dev/sda: 5.5 TiB, 6001175125504 bytes, 11721045167 sectors
    Disk model: Expansion Desk  
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  • Sorry to say but there's no partition table showing on the drive.

    AFAIK, even if you try to initialize the drive with a new partition table, ALL data will be gone.


    Maybe try googleFU to see if something can be recovered.

    This is way over my pay-grade, sorry.

  • I can not add anything to what Soma said. You will have to contact a professional disk recovery company or try your google foo.

    There are programs out there which will analyse disks to guess what has been on it, but I can't help here.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

Participate now!

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