[Solved] Constant harddrive related errors with fresh installation

lamigo · 9. Februar 2019

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

Externer Inhalt www.youtube.com

Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.

Durch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt.

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:

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:

I get this error:

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!

tkaiser · 9. Februar 2019

Have you checked SMART status and there especially attribute 199?

lamigo · 9. Februar 2019

This seems to be the status of 199 in SMART 199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0

Here is a picture as well:

Is that normal?

tkaiser · 9. Februar 2019

Zitat von lamigo

199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0

A value of 0 (at the right) is fine. This attribute can be used with a lot of HDDs to spot cable/connector problems that result in all sorts of strange symptoms. But seems it's fine in your installation.

lamigo · 9. Februar 2019

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

Code

Error #0:
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; systemctl restart 'sharedfolders-Media.mount' 2>&1' with exit code '1': Assertion failed on job for sharedfolders-Media.mount. in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 1)
#1 /usr/share/php/openmediavault/system/systemctl.inc(160): OMV\System\SystemCtl->exec('restart', NULL, false)
#2 /usr/share/openmediavault/engined/module/sharedfolders.inc(66): OMV\System\SystemCtl->restart()
#3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleSharedfolders->startService()
#4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusX9...', '/tmp/bgoutputXE...')
#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#9 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
#11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#12 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#13 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#14 {main}

Alles anzeigen

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

Adoby · 9. Februar 2019

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.

lamigo · 9. Februar 2019

Updating the OMV and then running fsck -A -M -R -y seems to have fixed it. Thank you!

Jetzt mitmachen!