Create filesystem error communication failure

  • I'm a few days busy with setting up my Pine64 NASCase with a ROCKPro 64 4GB SBC together with a 3TB WD Red HDD for a few days now, but I got the error "communication failure" everytime I want to create a filesystem under [Storage - File Systems]


    I see there are a few topics in the past regarding this (javascript 60 seconds?) error, but it seems it's still not solved!?


    Earlier topic(s):
    communication failure


    From this tracker: :
    https://github.com/openmediavault/openmediavault/issues/78


    I debugged the system, see the logging in the txt attachment

    Code
    monit stop omv-engined
    omv-engined -d -f

    Meanwile the GUI showed this:


    In this topic New User Guide - Getting Started with Openmediavault 4 & 5 I read:


    **Notice to SBC users** OMV4 on SBC's is no longer supported.
    OMV5, for SBC's, should be build in accordance with one of the guides in this -> post.**


    Should I use OMV5 on the Pine64 NASCase with a ROCKPro 64 4GB SBC ?


    Pine64 hints to use OMV from https://github.com/ayufan-rock64/linux-build/releases/
    This is OMV version 4.1.32-1 (Arrakis)
    0.9.14: gitlab-ci-linux-build-159, released this on 28 Aug 2019


    I'm using Safari on a MacBook Air


    How to create a File System on the 3TB WD Red HDD to use it as my NAS drive?


    Create filesystem error communication failure.txt

  • on my search to an solution:


    https://linuxforums.org.uk/index.php?topic=10742.0


    Code
    parted /dev/sda
    (parted) print
    (parted) mklabel msdos
    (parted) mkpart primary ext4 1 -1
    (parted) print
    quit






    root@NAS-rockpro64:~#

  • on my search to an solution:


    https://linuxforums.org.uk/index.php?topic=10742.0


    Code
    parted /dev/sda
    (parted) print
    (parted) mklabel msdos
    (parted) mkpart primary ext4 1 -1
    (parted) print
    quit


    It seems HDD > 3GB are a problem with unix/linux:


    https://askubuntu.com/question…ition-table-imposed-error

  • on my search to an solution:


    https://linuxforums.org.uk/index.php?topic=10742.0


    Code
    parted /dev/sda
    (parted) print
    (parted) mklabel msdos
    (parted) mkpart primary ext4 1 -1
    (parted) print
    quit


    It seems HDD > 3GB are a problem with unix/linux:


    https://askubuntu.com/question…ition-table-imposed-error

  • It seems HDD > 3GB are a problem with unix/linux:

    The referenced article is 8 years old. I don´t believe that this is still true. Here are a lot of users with hdd´s bigger than 3GB. Is there any old data on the WD drive? If not, then you should wipe the drive before creating a file system on it.

    OMV 3.0.100 (Gray style)

    ASRock Rack C2550D4I C0-stepping - 16GB ECC - 6x WD RED 3TB (ZFS 2x3 Striped RaidZ1) - Fractal Design Node 304 -

    3x WD80EMAZ Snapraid / MergerFS-pool via eSATA - 4-Bay ICYCube MB561U3S-4S with fan-mod

  • I´m a little bit confused about the msdos partition table. The disk is bigger than 2 TB. Therefore I had expected a GPT format and no msdos format.

    OMV 3.0.100 (Gray style)

    ASRock Rack C2550D4I C0-stepping - 16GB ECC - 6x WD RED 3TB (ZFS 2x3 Striped RaidZ1) - Fractal Design Node 304 -

    3x WD80EMAZ Snapraid / MergerFS-pool via eSATA - 4-Bay ICYCube MB561U3S-4S with fan-mod

    • Offizieller Beitrag

    Use faster SD card and make sure flashmemory plugin is installed.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

  • After enableling System - Notification in OMV I receive these e-mails:


    ==============================================


    monit alert -- Does not exist rrdcached


    Does not exist Service rrdcached


    Date: Fri, 31 Jan 2020 16:55:09
    Action: restart
    Host: NAS-Rockpro64
    Description: process is not running


    Your faithful employee,
    Monit


    ==============================================


    monit alert -- Does not exist collectd


    Does not exist Service collectd


    Date: Fri, 31 Jan 2020 16:55:09
    Action: restart
    Host: NAS-Rockpro64
    Description: process is not running


    Your faithful employee,
    Monit


    ==============================================


    monit alert -- Exists rrdcached


    Exists Service rrdcached


    Date: Fri, 31 Jan 2020 16:55:10
    Action: alert
    Host: NAS-Rockpro64
    Description: process is running with pid 7458


    Your faithful employee,
    Monit


    ==============================================


    monit alert -- Exists collectd


    Exists Service collectd


    Date: Fri, 31 Jan 2020 16:55:10
    Action: alert
    Host: NAS-Rockpro64
    Description: process is running with pid 7488


    Your faithful employee,
    Monit


    ==============================================


    Anacron job 'cron.weekly' on NAS-Rockpro64


    /etc/cron.weekly/openmediavault-update-smart-drivedb:
    mesg: ttyname failed: Inappropriate ioctl for device


    ==============================================


    Anacron job 'cron.weekly' on NAS-Rockpro64


    /etc/cron.weekly/openmediavault-update-smart-drivedb:
    mesg: ttyname failed: Inappropriate ioctl for device


    ==============================================



    With earlier installations I received the similar e-mails...

    • Offizieller Beitrag

    mesg: ttyname failed: Inappropriate ioctl for device

    I think this should be solved if you updated your system. If not, search the forum for this error message. There is an easy fix.

    Under Plugins, Anacron plugin is not installed, should it be automatically installed after enabling Notifications?

    No. Anacron is not linked to notifications. Anacron is used to execute commands on servers that are not always on, so that a scheduled job runs after the server is available again.

  • I think this should be solved if you updated your system. If not, search the forum for this error message. There is an easy fix.


    This is after first install, directly after enabling Notifications
    So should be fixed in OVM source-code!?


    In the installation proces I update my systems after installing, but it's not ok to send system failures after first install ;)

  • Use faster SD card and make sure flashmemory plugin is installed.

    Flash Memory 4.2.1 is installed by default


    Why is a Format of the HDD obligated?



    As I formatted the 3TB WDD with EXT4 without problems...
    There is a File System on it, Mounting should be enough if you aks me!?




    How to get the HDD available in OMV without the Formatting problems I experience?
    Manually done in "fstab" I read about...?

Jetzt mitmachen!

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