Unofficial Plugin Repo for 0.5 Sardaukar, 1.0 Kralizec, 2.0 Stoneburner, 3.0 Erasmus, 4.0 Arrakis

Please update phpvirtualbox support to 5.1.8 with my github repo.
https://github.com/shom/phpvirtualbox

I'm having trouble withsickbeard too other than sonarr: it seem's that I can't find it! Do I need to enable and other repository other than mono?

Seems like the openmediavault-openvpn.postinst is broken...

addgroup --quiet \
                 --system \
                 openvpn

This line drops an error if the group openvpn is already there - so adding a check before might be good.

ryecoaaron,
i think that backports repo list must include non-free also, but now it is only include main and contrib.
Because some users wants to install fresh firmware...

I cannot find openmediavault-remoteshare plugin on omv3. Where is it?

Zitat von ryecoaaron

This was intentional. I wanted to add it without upgrading any packages from backports. Adding non-free would upgrade the firmware even if you were still using the standard kernel. If you need it, you can edit the repo in the repo tab.

Ok.

Zitat von ryecoaaron

I rewrote the remoteshare plugin completely. Since it has no upgrade path, I gave it a new name - remotemount

Thanks, But plugin does not have webdav

ryecoaaron, i cannot upgdate last remoteshare plugin.
Many thanks

no need to update now, you just update when OMV 3.0.60 is release

Zitat von luxflow

no need to update now, you just update when OMV 3.0.60 is release

I'm not updating doing a new install of OMV 3.0.58 and getting that error for a few plugins.
Emby, Greyhole, Remoteshare is there a workaround??

Zitat von ryecoaaron

Emby - Yes, manually install it. It is easy. Read the big emby thread.

Greyhole - Nope. Not unless someone ports it.

Remoteshare - Use remotemount. There is no upgrade path though

Thanks for the reply

I'm using OMV 2/3 in a VM's trying to get comfortable with it before I move my setup off WHSv2.
Do you know when OMV 3 will be officially out of beta release.

Thanks

Hopefully this is the right place to raise a bug report for OMV-Extras

OMV-Extras kernel tab 'Set as default boot kernel' button corrupts my /etc/default/grub file eating it line by line whenever I change the default boot kernel

Initially I had:

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
...

I selected a different default kernel and ended up with:

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'


GRUB_DEFAULT=2\nGRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
...

Changing back to the original kernel and another line was eaten:

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'


GRUB_DEFAULT=0\nGRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
...

and so on :

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'


GRUB_DEFAULT=2\nGRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
...

My NAS box is running OMV 3.0.59 erasmus, 64-bit AMD 4.7.0 backport kernel and omvextrasorg 3.4.15. (I'm using the 4.7 kernel because I use btrfs on my disks and want to use the most recent btrfs-progs that is currently available)

Sophie x

Zitat von ryecoaaron

You must have installed Debian from a non-OMV ISO? Most of the entries in the OMV default grub file are commented out. omv-extras is fixed now.

Yes, I performed a minimal Debian Jessie install and applied OMV on top of it. I did it this way because I'm using an NVME SSD for my system drive but my BIOS doesn't recognise it so I have a boot partition on a USB FLASH stick and I needed to manually assign partitions to accomplish this configuration.

Thank you for fixing OMV-Extras
Sophie x

Hi Guy,

i'm using omg 3.0.59 with manualy installation of jessie.
Cased by using uefi boot on my dell t20.

I'm crashed my system, now i need to reinstall the system.

But now i'm not able to install the back port kernel.
on the old 3.0.59 installation it was working out of the box after adding the omv-extras.

This is the error message:

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; omv-mkconf omvextras installbackports': Install backports 4.8.0-0.bpo.2 kernel and headers Reading package lists...

Did i do anything wrong?

Edit:
Is it possible that there is something wrong mit the repo?
I'm just active the testing repo and got an error, no packages out of the testing repo where shown.

Cheers Robert