Beiträge von canadavault

Zitat von macom

I have an HC2 (same XU4-based HW, but for 1x 3.5" drive) and omv-release-upgraded to OMV7. Works well.

I have the exact same machine as you! Could you elaborate it for me to upgrade mine, please?

Why don't you upgrade the linux kernel version from 4.4.xxx to 5.10.xx?
It may help to resolve your problem on nanopim4v2.

Zitat von crashtest

Whatever you're comfortable with is the way you should go.

Thank you for your comment on this.

Zitat von gderf

You will need to expand the partition and expand the filesystem to have an 8TB fully usable disk.

And then maybe I can use 'gparted' to expand the partition after cloning through dd?

Zitat von crashtest

You can use Rsync for a full disk to disk copy - mirror.

I was thinking of dd instead of Rsync.
I am going to replace current 4TB disk on Odroid-hc2 with new 8TB.
Odroid-hc2 has only one USB port for external disk.
You still recommend Rsync in my situation?
Thanks for your reply.

Hi,

My 4TB data disk is nearing full capacity on my Odroid Hc2.
I am waiting for my new 8TB disk ordered couple of days ago.
My concern is how I should replace both disks new and old.
How can I clone old disk to new one and then use the old disk as is.
I am planning to configure another openmediavault using old 386 pc laying around.

Thanks in advance for any help.

@votdev Thanks a lot! I have got it fixed after updating into 5.2.7-1 now. You guys are great as always!!

Looks like I am having the same issue.
So omv5 is still unreliable yet?

Hi, when click 'Shared Folders' I get this.
Please help!

Error #0:
OMV\Rpc\Exception: Invalid RPC response. Please check the syslog for more information. in /usr/share/php/openmediavault/rpc/rpc.inc:187
Stack trace:
#0 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('ShareMgmt', 'getList', Array, Array, 3)
#1 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()
#2 {main}

Zitat von macom

Are you using /sharedfolders/xxxxx instead of /srv/dev-disk-by-labe-yyy/xxxx in docker or plugins? That might cause this issue.

Cannot create shared folder on new or existing drive

Thank you for your quick help.
Actually I couldn't even create a shared folder with that name.

When I add an rsync module on Odroid hc2 I get an error message like this:
can it be straightened?

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-appdata.mount' 2>&1' with exit code '1': Assertion failed on job for sharedfolders-appdata.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/bgstatus2u...', '/tmp/bgoutputkx...')
#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(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#14 {main}

Zitat von gderf

What you can do is use an unofficial method to upgrade your OMV 4.x installation to OMV 5. See:

What if I have zfs data with 4.xx Proxmox kernel?
Thank you in advance.

Zitat von kirkdis

I would choose V4 over 5

Hi kirkdis,

At last I have succeeded installing omv5 on Nanopim4v2 with 2 sata hdds using armbian 5.99 minimal image developed by remarkable gurus from here on an Armbian forum. Others who have purchased nanopim4v2 may also refer to this forum.

Zitat von smellslikemichigan

I had the same problem with my new Nanopi M4V2. How did you go about getting it to work?

Everything is a mess now. Not all that used to be now. First of all, OMV-Extras for all SBC is in horrible situation, especially for OMV 5.x.

Zitat von kirkdis

Ok, I don't really know much about Linux but the OMV4 is also possible to be installed on other distros... But I can't help with that maybe anyone else out there can support with that. Formfactorwise the V2 will fit inside my case design. But thanks for the feedback. Will help others much to keep out of trouble.

Thank you for your kind response. Fortunately, I have succeeded in installing OMV5 through Rockpi4B Armbian on the Nanopi M4V2 yesterday and it worked. The same cpu and ram seems to have been possible. So now I am waiting for the power supply for the Sata Hat.

Zitat von kirkdis

So you are good to go with the newer version but it would be helpful if you share your experience in case you have cloned this setup with the new nanopi M4V2. Thanks..

I got Nanopi m4v2 1 week ago but I found it is really messed up...not bootable from sd cards, not working wifi and utterly incompatible with any sbc images of old Nanopi-m4 such as openmediavault and armbians. They say it is because of the new LPDDR4.

Same problem here.
Could this be solved?

Zitat von KM0201

Did you refresh your browser? Try holding Cntrl and hitting the reload button (assuming you're using Chrome)

Thanks for your reply.It worked.

Zitat von acecombat2

The filesystems section came back with the following update from 4.1.16-1 to 4.1.16-2.

Mine isn't back yet after the update. Anyone having the same problem?

Zitat von gderf

The part of Plex that should be installed to a data drive is its metadatbase library. If you are using a Plex docker, this location is set via the /config Container path.

I have found that I stupidly made my system drive to be full with lots of plex metadata. Is there still any chance to move them all into the data drives?