Posts by Dejh0n

    So in live Debian and typing ‘sudo sfdisk -l’

    I get a list of all the drive I expect (10 drives).

    After doing a fsck on each of the drives I get this:

    now I am unsure what to do..


    I realized with the issue I had before I reset the BIOS during all this and it disabled the HBA.

    I’ve now turned it back on and now get:

    After installing parted and printing the output for my OS drive I get:

    in the live image I tried "df -h" and no disk has shown up besides the USB stick

    Nevermind, when I try lsblk -o they start to show up.

    Is it going to matter if all data and parity drives are connected via an HBA card?

    My main OS / persistent storage drive is the only SATA connected drive


    OK, so when I boot into a live version I can't see any HDD attached, however I can choose to boot form a HDD in the BIOS boot menu..

    okay. will give that a go. Should I be using a 'live' version of Debian? Because this version is asking to install and create a root partition.

    Should I just be executing a shell in the installer environment?

    Alright, I have Debian 10 installed and booted from a USB stick on the NAS.

    Now what?

    I'm happy to have a few commands to try if it will speed things up?

    What they do, and what I should be looking for would be incredibly helpful so I can actually learn while trying to fix this..

    Nothing more.

    I left it overnight and tried again and now get this:

    I can try boot a Debian OS tonight. Any particular flavor?

    Hi everybody,

    So I’m completely stuck.

    I’m using OMV 5.10 and MergerFS+SnapRAID for HDD management/pooling.

    I have 1 dedicated HDD used for the OS and portainer data etc.

    I recently bought another HDD and installed it as a second parity drive and ran a full scrub twice over the last few days and all seemed happy.

    I then tried to deal with my failing data HDD and replace it with another the same size.

    I powered down my system and unplugged the faulty drive and plugged the replacement in and OMV would not boot.

    I thought, maybe I need to unplug the new drive then boot and add it via GUI. No luck.

    Then I powered down, put back in the failing drive (unreadable sectors) where it was and still nothing. So then I unplugged in the new second parity drive with the old Data drive plugged in as before and still nothing.

    Now I’m stuck and don’t know how to fix my issue(s).

    OMV will not boot into recovery mode either not matter which option I try.

    Would someone please help me out here?

    The different recovery modes all seem to get stuck on different arguments every time..


    So I followed that down and found what appeared to be a 6.5G log file.

    After opening the folder up in FileZilla and finding a config file, I saw it was for transmission.

    So I copied the file to my computer and then deleted it from the folder.

    I then rebooted the system and BOOM everything came up and started working near instantly.

    Thank you for the guidance on this

    And further:

    root@Optimus:~# du -sh /var/lib/docker/containers/6e201ea2cd22203fa59e6454039bec83f5d965584239c46a880ad5c2fd161a6b/*
    6.5G /var/lib/docker/containers/6e201ea2cd22203fa59e6454039bec83f5d965584239c46a880ad5c2fd161a6b/6e201ea2cd22203fa59e6454039bec83f5d965584239c46a880ad5c2fd161a6b-json.log
    4.0K /var/lib/docker/containers/6e201ea2cd22203fa59e6454039bec83f5d965584239c46a880ad5c2fd161a6b/checkpoints
    8.0K /var/lib/docker/containers/6e201ea2cd22203fa59e6454039bec83f5d965584239c46a880ad5c2fd161a6b/config.v2.json
    4.0K /var/lib/docker/containers/6e201ea2cd22203fa59e6454039bec83f5d965584239c46a880ad5c2fd161a6b/hostconfig.json
    4.0K /var/lib/docker/containers/6e201ea2cd22203fa59e6454039bec83f5d965584239c46a880ad5c2fd161a6b/hostname
    4.0K /var/lib/docker/containers/6e201ea2cd22203fa59e6454039bec83f5d965584239c46a880ad5c2fd161a6b/hosts
    4.0K /var/lib/docker/containers/6e201ea2cd22203fa59e6454039bec83f5d965584239c46a880ad5c2fd161a6b/mounts
    4.0K /var/lib/docker/containers/6e201ea2cd22203fa59e6454039bec83f5d965584239c46a880ad5c2fd161a6b/resolv.conf
    4.0K /var/lib/docker/containers/6e201ea2cd22203fa59e6454039bec83f5d965584239c46a880ad5c2fd161a6b/resolv.conf.hash

    Because I am unsure / not confident in what I’m doing!

    But thanks for the tip, followed that and I got:

    tried the following:

    root@Optimus:/# df -h /
    Filesystem Size Used Avail Use% Mounted on
    /dev/sdj2 19G 19G 0 100% /

    Going down the rabbit hole here...

    root@Optimus:/# df -h /mnt
    Filesystem Size Used Avail Use% Mounted on
    /dev/sdj2 19G 19G 0 100%

    Thanks for the reply.

    Here is my results:

    "Cleaning Up dockers"


    docker system df


    root@Optimus:~# docker system df
    Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

    Then moved onto "moving locker storage"

    and got the following:

    root@Optimus:~# cat /etc/docker/daemon.json


    "runtimes": {

    "nvidia": {

    "path": "nvidia-container-runtime",

    "runtimeArgs": []




    Portainer or any of my services are not running..