Posts by cody00

    Anyone having issues on a recent update for virtual box? Specifically the ext-pack-installer?
    Any tips on how to correct.. safely?

    The following packages have unmet dependencies:
    virtualbox-ext-pack-installer : Depends: virtualbox (>= 5.1.26) but 5.1.14-dfsg-1 is to be installed or
    virtualbox-5.0 (>= 5.1.26) but it is not installable
    E: Unable to correct problems, you have held broken packages.

    Trying to install Duplicati and am receiving the following error.

    The following packages have unmet dependencies:
    openmediavault-duplicati : Depends: duplicati but it is not going to be installed
    E: Unable to correct problems, you have held broken packages.
    <<< *************************************

    I think I have all testing settings selected and I have Updated and Apt-Clean on "OMV-Extras" also.
    Any suggestions?

    Thank you for this trapexit. My libfuse is 2.9. I noticed an updated through OMV today to 2.9.3 which is not quite the 2.9.4 recommended on your page. Based upon ryecoaaron's post, I would assume the safe approach is to wait and only update through OMV vs manually updating to a newer libfuse.

    I recently switched from AUFs to Mergerfs for Union File System. Over a week span, I had two instance where the file system shutdown. If I was to go to "Physical Disk" it would show all of the drives as N/A. None of the applications that used those UFS disk would work until I rebooted. After digging into the syslogs, I found the following.

    May 23 20:45:01 OMV /USR/SBIN/CRON[11560]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1)
    May 23 20:45:01 OMV rrdcached[2739]: Received FLUSHALL
    May 23 20:45:53 OMV kernel: [154612.471549] Plex Media Serv[11892]: segfault at 0 ip 00007fd3caaa82e0 sp 00007fd3bc3fe9d0 error 4 in[7fd3caa96000+24000]
    May 23 20:45:59 OMV collectd[5259]: statvfs(/media/9c8471a3-0952-46d4-9e54-b644c0a471dd) failed: Transport endpoint is not connected
    May 23 20:46:09 OMV collectd[5259]: statvfs(/media/9c8471a3-0952-46d4-9e54-b644c0a471dd) failed: Transport endpoint is not connected
    May 23 20:46:19 OMV collectd[5259]: statvfs(/media/9c8471a3-0952-46d4-9e54-b644c0a471dd) failed: Transport endpoint is not connected

    All SMART test on HDDs are showing good health. Does anyone have any direction I could go with this one?

    Additional Info:…-crash-with-ubuntu-14-04/

    Kind Regards,

    Thanks tekkb. Creating bootable flashdrive now for it.

    If the memtest checks out.. I think I have discovered it is a very specific plex problem with syncing to iPad mini remotely. I found an active post on the plex forum where they are churning through this problem.

    Thanks again for the recommendation tekkb. Will post back results.

    Has anyone had any experience with resolving or understanding out of memory errors. It has been plaguing me for sometime with random system crashes.

    I have 32GB of ram in my machine
    *12GB is reserved for a Windows 8 Virtual Box Machine
    *1.5GB is reserved for a linux Virtual Box Machine.

    It seems that the server crashes anytime I try to sync a movie through Plex

    Is there some setting in plex or in the system that I can adjust to prevent the issue from happening? Can I limit the amount of memory that plex or sabnzb extraction is using. I feel those are the two big one.s

    Screenshot of my system log during crash is attached. Everything below line is before the crash.

    Kind Regards,

    I have my system hooked up to tv via HDMI. I did check this during the first crash and nothing would come up on the screen. I tried to SSH via putty as I normally do and and no response. The only thing that gives a response is a ping.
    Any other type of logs or areas I could look in for this?

    Hi All,
    My OMV has recently started crashing and I'm trying to find out why. The crash seems to completely bring the system down but I can still ping the IP. I cannot see the web interface or communicate with any of the services.

    Here is a problematic snippit from the syslog. It seems that everytime it crashes, it happens just after this php session clean and mkgraph line.
    OMV 1.9

    Aug 12 11:33:03 OMV watchdog[4030]: hardware wartchdog identity: Software Watchdog
    Aug 12 11:33:28 OMV monit[3841]: Starting monit HTTP server at [localhost:2812]
    Aug 12 11:33:28 OMV monit[3841]: monit HTTP server started
    Aug 12 11:33:28 OMV monit[3841]: 'localhost' Monit started
    [b]Aug 12 11:39:01 OMV /USR/SBIN/CRON[4518]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
    Aug 12 11:45:01 OMV /USR/SBIN/CRON[4563]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1)
    Aug 12 11:45:01 OMV rrdcached[2904]: Received FLUSHALL[/b]
    Aug 12 12:00:01 OMV /USR/SBIN/CRON[5022]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1)
    Aug 12 12:00:01 OMV rrdcached[2904]: Received FLUSHALL

    I have been using the diff script in snapraid as a nightly CRON job for some time. I usually ignore the nightly emails and realized it has been failing with the following error. This has been happening since May 31st. I have not done any major changes since then.

    /var/lib/openmediavault/cron.d/userdefined-e1bad3fb-7b13-4daa-9603-fc05d9a6cc27: 4: /var/lib/openmediavault/cron.d/userdefined-e1bad3fb-7b13-4daa-9603-fc05d9a6cc27: /usr/local/bin/omv-snapraid-diff: not found

    What does this mean?

    Kind Regards,

    For Documentation and hopefully helping someone in the future....

    I recently receive an I/O error while trying to write to the pooled drive. At first glances, I thought my drive was failing but it turns out it was another .wh.wh.<foldername> causing the problem. I removed this file, rebooted, and the problem was resolved.

    On a note about erasing .wh.wh files. A friend of mine has the exact same setup with omv aufs. He came across a problem and took it to the extreme. He removed all .wh.wh (not just the opq) files on the system as a test. Nearly a month later and he has not experienced any problems.