[Solved] Constant harddrive related errors with fresh installation

  • I'm running a fresh 4.1.3 installation. Followed this tutorial:


    I have an 250GB SSD where the OMV is installed and an additional 1TB HDD.
    This 1TB HDD was used in windows environment before, but after OMV installation I did a secure wipe of it from the OMV UI.


    This is how the filesystem looks at the moment:


    omv_filesystem.PNG


    Everything works fine until this point, but I get an error when I try to create a shared folder.


    When I try to create a shared folder named "Media" like this:
    omv_sharedfolder.PNG



    I get this error:
    omv_sharedfolder_error.PNG


    Full error:

    Code
    Error #0:
    OMV\Exception: Failed to create the directory '/srv/dev-disk-by-id-ata-ST1000DM003-1SB10C_Z9A269YD-part1/Media': in /usr/share/openmediavault/engined/rpc/sharemgmt.inc:323
    Stack trace:
    #0 [internal function]: OMVRpcServiceShareMgmt->set(Array, Array)
    #1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
    #2 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('set', Array, Array)
    #3 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('ShareMgmt', 'set', Array, Array, 1)
    #4 {main}


    I have tried to wipe the drive again, but when I try I get this error instead: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; blockdev --rereadpt '/dev/sdb' 2>&1' with exit code '1': blockdev: ioctl error on BLKRRPART: Device or resource busy


    Error details below:


    Code
    OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; blockdev --rereadpt '/dev/sdb' 2>&1' with exit code '1': blockdev: ioctl error on BLKRRPART: Device or resource busy in /usr/share/openmediavault/engined/rpc/diskmgmt.inc:273
    Stack trace:
    #0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMVRpcServiceDiskMgmt->{closure}('/tmp/bgstatus6i...', '/tmp/bgoutputyr...')
    #1 /usr/share/openmediavault/engined/rpc/diskmgmt.inc(277): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
    #2 [internal function]: OMVRpcServiceDiskMgmt->wipe(Array, Array)
    #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
    #4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('wipe', Array, Array)
    #5 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('DiskMgmt', 'wipe', Array, Array, 1)
    #6 {main}

    I somehow feel that this is hard-drive related, but I can't tell exactly how. Any guidance is appreciated. Thank you!

  • If I ignore the previous error and just close the window and press "Apply"-button I get this error:


    omv_ignore.PNG


    Any idea what else could be the cause of all these errors?

  • The obvious assumption is that the hdd is bad.


    But that might be a side effect from bad cables and connections or bad or insufficient power. Try to change or at least disconnect and reconnect cables and power supply and/or remove accessories that may consume power. Try with a different hdd.


    If you want to try to wipe again, make sure to unmount the filesystems on the drive first.


    You can also try to check the hdd from the command line.


    Do a search for "fsck check hdd."


    Also make sure that OMV is OK. Update it. And/or reinstall.

    Be smart - be lazy. Clone your rootfs. This help is Grateful™.
    OMV 4: 9 x Odroid HC2 + 1 x Odroid HC1 + 1 x Raspberry Pi 4

Participate now!

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