OMV 5 on Goflex Net anyone?

So goal to revive this Goflex Net was to install OMV.

Have latest kernel and u-Boot.

Wiki instructions from late last year are for OMV 4. But the OMV forum has instructions for 5 here:

https://forum.openmediavault.org/index.php?thread/25062-install-omv5-on-debian-10-buster/

Has anyone else tried it by any chance?

My installation not sure if it even went through but now CMD is extremely slow. Getting 50-60% io wait in top, with kswapd0 as the to usage.

Wonder if this little thing is not enough or the USB stick is too slow? I'll try OMV 4 next but wondering...

Thanks in advance.

CyberPK has installed OMV5 on a larger NAS. The instruction is quite long so you might skip to the part where OMV5 is installed.

https://forum.doozan.com/read.php?2,28939,98649#msg-98649

Not sure if GoFlex Net has enough juice to run OMV5. Perhaps it is better to stay with OMV4 (proven to work with 128MB RAM).

-bodhi
===========================
Forum Wiki
bodhi's corner

Thanks. Obviously OMV5 doesn't work.

I grabbed an unused 256GB and used it on a USB2 case. Here's what I've done so far as I wasn't sure of the instructions for OMV4 since I already had the latest uBoot.

* Created 8Gb partition (primary, rootfs)
* Created 256Mb partition (swap, swap)
* Installed 4.12.1 root image
* Booted and upgraded kernel to 5.2.9
* Changed to systemd
* Added /run tmpfs to fstab (none /run tmpfs defaults,size=20M 0 0)
* Started the installation of OMV4

But now I'm noticing kswapd0 page allocation errors in the serial console

Google points to bugs in the kernel but could also be memory. Should I upgrade to the 5.6.5 kernel? Any ideas?

TIA.

su_A_ve Wrote:
-------------------------------------------------------
> Thanks. Obviously OMV5 doesn't work.
>
> I grabbed an unused 256GB and used it on a USB2
> case. Here's what I've done so far as I wasn't
> sure of the instructions for OMV4 since I already
> had the latest uBoot.
>
> * Created 8Gb partition (primary, rootfs)
> * Created 256Mb partition (swap, swap)
> * Installed 4.12.1 root image
> * Booted and upgraded kernel to 5.2.9
> * Changed to systemd
> * Added /run tmpfs to fstab (none /run tmpfs
> defaults,size=20M 0 0)
> * Started the installation of OMV4
>
> But now I'm noticing kswapd0 page allocation
> errors in the serial console
>
> Google points to bugs in the kernel but could also
> be memory. Should I upgrade to the 5.6.5 kernel?
> Any ideas?
>
> TIA.

Remove systemd. With swap on, sysvinit seems to work fine.

-bodhi
===========================
Forum Wiki
bodhi's corner

Started clean again. This time, I did not switched to systemd and did not add /run to fstab.

A few seconds after I start the OMV4 installation, I am still getting again kswap0 page allocation failures.

The installation did fail however:

Errors were encountered while processing:
 collectd
 openmediavault
E: Sub-process /usr/bin/dpkg returned an error code (1)

Collectd won't start - it says there's a configuration error.

Now, here's the thing - after I rebooted, collectd is still not working but I noticed systemd is running. It looks like omv installs it. If I try to remove it, OMV goes with it as well but got errors, so back to square one.

The only difference I'm doing with the OP is that I'm trying to run this out of the USB port, but with an USB2 HDD there. This shouldn't make any difference, or should it?

TIA.

su_A_ve Wrote:
-------------------------------------------------------
> Started clean again. This time, I did not switched
> to systemd and did not add /run to fstab.
>
> A few seconds after I start the OMV4 installation,
> I am still getting again kswap0 page allocation
> failures.
>
> The installation did fail however:
>
>

> Errors were encountered while processing:
>  collectd
>  openmediavault
> E: Sub-process /usr/bin/dpkg returned an error
> code (1)
>

>
> Collectd won't start - it says there's a
> configuration error.
>
> Now, here's the thing - after I rebooted, collectd
> is still not working but I noticed systemd is
> running. It looks like omv installs it. If I try
> to remove it, OMV goes with it as well but got
> errors, so back to square one.
>
> The only difference I'm doing with the OP is that
> I'm trying to run this out of the USB port, but
> with an USB2 HDD there. This shouldn't make any
> difference, or should it?
>
> TIA.

Is there swap file or swap partition in fstab?

-bodhi
===========================
Forum Wiki
bodhi's corner

Yes.

I have a 256mb swap partition.

I started from scratch one more time... And OMV4 NOW WORKS!

Noticed a couple of things. I already had the latest uBoot

When adding swap, the instruction say 'default' instead of 'defaults' - I added /run as well:

LABEL=swap swap swap defaults 0 0
none /run tmpfs defaults,size=20M 0 0

Don't miss modifying hostname and adding it to /etc/hosts. In my case, I used the static IP address I'm using

192.168.0.10 goflexnet.lan goflexnet

Noticed some delays in getting correct time after reboot, so changed the ntp servers:

# Change ntp to US Pools
server 0.us.pool.ntp.org iburst
server 1.us.pool.ntp.org iburst
server 2.us.pool.ntp.org iburst
server 3.us.pool.ntp.org iburst

OMV does need systemd and looks like there's a couple of dependencies that are needed so I also installed it.

apt-get install systemd
# add to /boot/uEnv.txt
custom_params=init=/bin/systemd

Edited 1 time(s). Last edit at 04/27/2020 01:19PM by su_A_ve.

Update - so I'm running OMV on a 256GB drive on USB.

sda1 is rootfs
sda2 is swap
sda3 is data

But it looks like the whole drive needs to be wiped in order to create and/or add a file mount under sda3?

TIA.

Never mind. There's a few different ways on using additional space on the system disk.

I used the raid method.

# Create new file system in additional space - Using /dev/sdb here
# fdisk /dev/sdb (create new partition using rest of disk)
# Format ext4
mkfs.ext4 -L Data1 /dev/sdb3
# Create raid partition via cmd line
mdadm /dev/md100 --create --force --level=linear --raid-devices=1 /dev/sdb3
# Then it shows under OMV GUI. Mount it and assign as share

I did get OMV5 installed in the end. But it was taking up all memory and kept having issues mounting drives and timeouts.

Went back to OMV4 and this is now running good for a few days. Backed up about 750Gb of movies and photos.