Posts by savellm

    Hi all,


    Just did a fresh install of 4.1.22 (got it to work) and did the updates to 4.1.23-1
    And when installing plugin or


    I get this message:
    Purging internal cache ...
    Restarting engine daemon ...
    Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f7ae77037b8>
    Traceback (most recent call last):
    File "/usr/lib/python3.5/weakref.py", line 117, in remove
    TypeError: 'NoneType' object is not callable
    Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f7ae77037b8>
    Traceback (most recent call last):
    File "/usr/lib/python3.5/weakref.py", line 117, in remove
    TypeError: 'NoneType' object is not callable


    Do I need to worry about this?


    I also received this email last night:
    CRON-APT RUN [/etc/cron-apt/config]: Sun Jul 7 00:07:59 BST 2019
    CRON-APT SLEEP: 1510, Sun Jul 7 00:33:09 BST 2019
    CRON-APT ACTION: 0-update
    CRON-APT LINE: /usr/bin/apt-get -o Acquire::http::Dl-Limit=25 update -o quiet=2
    W: Conflicting distribution: http://security.debian.org/debian-security stretch/updates InRelease (expected stretch/updates but got buster)
    W: Conflicting distribution: http://security.debian.org/debian-security stretch/updates InRelease (expected stretch but got buster)
    E: Failed to fetch http://security.debian.org/deb…es/main/source/Sources.xz Writing more data than expected (5344 > 1688)
    Hashes of expected file:
    - Filesize:1688 [weak]
    - SHA256:37f1c81dd7153f50c3b1498166a646665bae774ca7f93b04d3d88b6ce5e589cd
    Release file created at: Sat, 06 Jul 2019 19:28:25 +0000
    E: Failed to fetch http://security.debian.org/deb…/binary-amd64/Packages.xz
    E: Some index files failed to download. They have been ignored, or old ones used instead.

    So did that, then I messed up some stuff, so tried to wipe it and start again and now 4.1.3 is doing it too...


    Sigh.
    Once its in initramfs I have no idea how to fix it.


    EDIT: I'm wondering if I pull out all the other drives, and just have the SSD where I plan to install to, would this help?

    Hey guys,


    I'm going to start building a new server in the next week, starting this weekend.
    Is there any info on OMV5 as Debian Buster is due out I believe tomorrow.


    I havent been around for previous releases so I have no idea on how long it normally takes to release a next major version so please excuse my ignorance if this seems premature.


    I just want to decide, as I can wait a month or 2 before putting this server live, not really in a hurry. But if OMV5 is likely to be 3+ months away I might just do OMV4 now and upgrade later.


    I'm a bit OCD and like to do clean installs of major versions.

    Why x86? Is OMV only x86 right now?


    I like ZFS, but also like BTRFS. Also like how BTRFS is built in and maintained.
    Where as ZFS requires changing kernel and plugin and other maintenance factors.
    I'm also a bit worried about upgradeability when using ZFS especially as plugins.
    Feel like the direction and support is heading towards better BTRFS (which I used in synology and currently use in unRAID) so I'd rather not have to copy all my data off and rebuild again in 2/3 years.

    So wait if future is btrfs, wouldnt installing with btrfs now be beneficial?
    Or at least use it as a filesystem in a new build?


    I'm planning to do a 80tb build shortly but want to be prepared for the future, in the sense that when OMV goes to v5, I dont need to worry about my data in doing a fresh install.

    Besides smaller swap, that wont be a long term issue right?
    When a new OMV update comes out, would I have to keep removing ram to do the updates?
    Or once its installed and swap is created, thats it, and it wont change?

    Because I tried that and it didnt work with the UEFI installer.
    I need to go back and look into it again but just havent had the time and I can get the 4.1.3 installed no problem.

    Sweet thanks, I'll be sure to do a clone once I'm all setup and running and have the spare dom as a take over if one dies.
    Lastly @ryecoaaron still wondering on if there are any issues with removing ram, installing and putting ram back?

    Thanks @crashtest, I'll wait for @ryecoaaron for a reply about RAM limitations.


    Lastly the SATADoms I have are the SuperMicro SUPERDoms. They 'seem' to be more like little SATA devices more than glorified USB.
    I am happy to stand corrected, and happy to install the flashmemory plugin just didnt think it would be needed.


    If I did DD or clonezilla would it still clone the boot so it would make a 100% like for like and be able to boot from the spare device?

    Hey guys,


    I just received my 2x SATADOM 32GB drives. (I was planning on using FreeNAS)


    Is there a way I can use these for OMV? And mirror the drives incase ones dies we can just reboot and run off the backup?


    Lastly, I have 128gb ram, so I'll need to remove a bunch of ram in order to use the OMV installer, will there be any repercussions if I remove ram down to 16gb, install OMV, configure the mirror (if possible), and then reinstall the ram back to 128gb? Would this have any lasting negative effects?

    Compilation orgies made me lol.
    So I didnt do the kernel first and charged in to install zfs plugin:


    And its been stuck here for 10mins. I'll let it run but seems dead.
    Will trying again. Do I need to do proxmox kernel first then install plugin?

    What about using OpenZFS?


    But thanks, this really makes me rethink and I'm going to retest :)
    Really appreciate all these comments.


    Will there get better maintenance of ZFS? IE more GUI options like resliver and so on?
    If I do ZFS (I was testing FreeNAS) does it have all the auto snapshots and so on?
    Or does that need to be manually setup or is it not supported?