Posts by johndoe86x

    After clicking apply after creating an NFS share, I was greeted with this error:

    After which, I could not SSH, access the web gui due to a Bad Gateway error. I was forced to manually reboot the system. Once the system was back up and I logged into the webgui, I reverted the changes and all seems to be fine. Upon attempting to redo the NFS configuration, I was greeted with the same error. This is remarkably similar to an error I had some time ago when creating a new ZFS dataset here: BAD GATEWAY in WebUI and ZFS pool is blank

    The error I received there was Failed to open file (filename=/tmp/bgstatus5TEgLM, mode=r). While not the exact same filename, it was still a problem within the tmp folder. Is there a correlation? I'm beginning to think I'm having php permissions specific problems.

    It looks like you were able to replicate my experience, exactly. Something that I forgot to mention is that I received that error initially when I left the mountpoint blank. I assumed the / mountpoint was inside of the pool, and would place the virus filesystem inside the root of the pool instead of the root folder. It had been awhile since I had created a ZFS object. Thank you for being so diligent in this.

    So, I'm not entirely sure that the problem was with the mountpoint in the ZFS plugin. Once I had all my data backed up as mentioned in previous post, I ran the #zfs destroy TPool/virus command and rebooted. Upon reboot, I was asked to apply the configuration changes in the WebUI. I did so and was greeted with the Bad Gateway error again. I rebooted once more (this time via hardware reset button) and then chose to "Revert" the changes rather than apply them. Now all seems to be working fine. I'm going to mark this as resolved.

    Thank you for your detailed response. I have an 8 disk pool that is a stripe of mirrors or the ZFS equivalent of RAID10.

    Yes, you have assumed correctly. The main pool was called TPool. And I have several filesystem objects inside of it named "nas", "movies", "tv", etc. I added another filesystem object aptly named "virus" for the purpose of storing quarantined objects via clamav.

    So the fields entered in the GUI were:
    Object type: Filesystem
    Prefix: I don't recall this one
    Name: virus
    Mountpoint: /

    Please let me know what other information I can provide. I have accessed the physical machine after a reboot via the recovery option in grub and have root access.

    Sent from my Pixel 2 using Tapatalk

    Edit: I've got an external hard drive and am performing an rsync backup at the moment in case I need to obliterate everything. I was able to start the ZFS service and mount the external hard drive.

    Thanks @subzero79, I'd rather not erase the disks as they have a lot of data and my latest backup isn't so current. I'm assuming that when I have physical access to the terminal, I'll be able to change the mountpoint. I just don't quite know the command for that, yet. I was hoping for some feedback from this community in that regard.

    I wouldn't have any issue wiping out OMV if that would help me keep my ZFS pool's data intact, but I'd be worried that the same issue would be present once I tried to re-import the pool after a fresh install. I'm almost positive there is a simple fix regarding fixing the mountpoint, but I'm a bit wary to try something that could cause the system or my data to be irrecoverable. Is there a ZFS specialist I need to get in contact with on here?

    Edit: For clarity, the main pool is located properly as are several subsystems. The most recent one is the one that I messed up.

    I recently added another object to my ZFS pool. Rather than the mountpoint being /TPool/newObject, I accidentally set the mountpoint as /. Once this applied, I lost access to the WebUI, and I can't navigate the ZFS pool via SSH. How would I reverse this? Thanks.

    Edit: I actually can't SSH into the machine any more, either.

    Hello, I use the same TV tuner Hauppage for the VDR pluging in OMV 3.x. I had only to install firmware-linux-nonfree to make this device visible by VDR. It works with OMV 2.x too.

    Thank you for your reply! I'll give this a shot when I get home.

    Edit: Unfortunately I still wasn't able to get this up and running. I also could not get VDR to see it. Any additional input would be appreciated.

    Hello, all, I'd like to take advantage of the new Plex DVR/Live TV system by hooking up my antenna and Hauppauge WinTV-dualHD. The device is listed as compatible for both Plex DVR and Linux here:…-DVR-Devices-and-Antennas

    There are instructions for installing the PPA under Ubuntu here: Obviously, this is Debian, and the PPA's don't work precisely the same. I attempted to modify the /etc/apt/sources.list with:

    deb yakkety main
    deb-src yakkety main

    I then installed the 4.8 linux-image-mediatree and linux-headers-mediatree. The install seemed successful, but I still can't see the tuner under the Plex screen. Any advice would be greatly appreciated.

    Debian has typically used an active root user where Ubuntu does not. This means you would su to the root user to execute root commands on Debian/OMV and use sudo to execute root commands on Ubuntu. A lot of people think using sudo is safer but I don't have a strong opinion either way. sudo is a requirement of OMV though...

    Ah, OK, I suppose it's a difference in philosophies, then. I've read multiple opinions on how to navigate through a system, but I personally try not to do too many things as root as I've really screwed myself over in the past by modifying or deleting things as a root user; whereas I would have gotten a request for elevated privileges if I was just my normal user.

    Hope you have a backup because OMV 3.x does not work with Debian 9 Stretch at all and this would be a nightmare to rollback. The fact that you had stable in your sources.list instead of jessie means your system would upgrade to Debian 9 as soon as Debian 9 was marked stable. You must have installed Debian manually since the OMV installer doesn't use stable in sources.list. So, there is nothing OMV could do to prevent this.

    Thanks for your response @ryecoaaron, I believe the problem lies within the fact that I had doctored the sources.list with netselect. I hadn't considered it changing the mirrors altogether in that manner. Unfortunately, my latest clonezilla backup is quite old. It looks like I'll simply be doing a reinstall. I'll mark this as resolved.

    I SSH'd into my box and did the normal sudo apt-get update && sudo apt-get upgrade to notice a slew of updates. Some of them did not want to cooperate, so I did a sudo apt-get dist-upgrade as I knew that Debian 9 was officially released. Many of the upgrades asked about the local configuration file and let me choose to keep the local file or the maintaner's version. I chose to keep the local file instead of the maintainer's version for each instance.

    I am now left with OMV in a very unusable state. SSH still works, but the WebGUI is broken, Samba is broken, Plex, Syncthing, BitTorrent, etc. are all broken. Thankfully, I can still browse my files in ZFS, so I can backup my data. Any help would be greatly appreciated.

    You're correct in that OMV1 to OMV3 is not possible. However, I went from OMV1 to OMV2 to OMV3. Deleted the plugins, then reinstalled the plugins. Everything seems to be working fine, now. Thank you for your response!

    Because my friend likes to never touch his NAS, he had been sitting on OMV1 for the past few years and came to me for help when certain packages no longer worked. I now have him on OMV3, when I attempt to run an update.. I am greeted with this. Any help would be fantastic. Thank you!

    W: GPG error erasmus InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7E7A6C592EF35D13
    W: GPG error erasmus InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7E7A6C592EF35D13

    Edit: Fixed by running sudo apt-key adv --keyserver --recv-keys 7E7A6C592EF35D13

    Updated 2: I believe I have everything solved. I took the following steps.

    • Delete the database folder as specified in the plugin - took a long time
    • Attempt to reinstall the plugin - fail
    • Manually create a new database folder with open permissions
    • Attemp to reinstall the plugin - fail
    • Install plexmediaserver from the command line - success
    • Attempt to reinstall the plugin - success
    • Attempt to enable the plugin - fail
    • Attempt to enable the plugin - success
    • Ponder why the heck it worked the second time

    Update: I have updated him to OMV3, deleted all the old plugins and attempted to purge them to the best of my knowledge. I am still getting an error during the Plex install:

    I'm trying to help a buddy of mine out with his OMV Plex installation. He told me that he was having trouble with the plugin. He let me remote into his box and poke around. He was apparently running OMV 1.0 and attempted to manually install the latest plex.deb file. I have since then upgraded him to 2.0 with the latest omv extras and attempted to purge the leftover plex cruft. However, I am getting errors when trying to install:

    Notice the red arrow, if I scroll up it is the same error repeated over and over. I have full remote access but no physical access. If someone could walk me through getting this situated then I'd greatly appreciate it. Thank you!

    Yeah, something's broken pretty badly. Time to hook up a keyboard and monitor and see what's happening.

    Since the OMV system thought the Movies share was /dev/sda1, it's possible something went in and nuked your install drive. If that's the case, the good news is, all your actual data should still be intact. But you may need to reinstall.

    I hadn't considered that... I actually started another thread here since the errors are now not necessarily ZFS related. Would you mind taking a gander? I've got a new ISO image downloading now just in case. The odd thing is I can access my sabznbd, sickrage, couchpotato, and transmission webgui.