OMV V3.xx Erasmus X86_64 LTS kernels

    • Offizieller Beitrag

    I just filled my drive when compiling. So, I will have to start over.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    You are answering questions from make oldconfig. Hitting enter taking the defaults is fine. If it says (new), you most likely don't need it. If you aren't sure, include it. It just makes the kernel bigger.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I just compiled my own kernel 4.6.4, and it working! :D
    It took 30 mins to be done.


    uname -aLinux server 4.6.4 #1 SMP Wed Jul 13 18:33:30 EDT 2016 x86_64 GNU/Linux
     openmediavault 2.2.5 all  


    Code
    linux-headers-4.6.4_1.0.NAS_amd64.deb
    11M     linux-headers-4.6.4_1.0.NAS_amd64.deb
    linux-image-4.6.4_1.0.NAS_amd64.deb
    51M     linux-image-4.6.4_1.0.NAS_amd64.deb


    One error that I notice is showing on boot up:

    Code
    iptables v1.4.14: can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
    Perhaps iptables or your kernel needs to be upgraded.


    Am I going to answer all these 400 questions again whenever I compile the kernel?

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    Einmal editiert, zuletzt von tinh_x7 ()

    • Offizieller Beitrag

    If your keep the .config file, you won't have to unless you move to a new kernel version. Look through the .config for iptables/nat to see what

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I have the old config.
    Should I copy the old config to the new config ?


    Code
    lsmod | grep ip
    xt_multiport           16384  3
    iptable_filter         16384  1
    ip_tables              28672  1 iptable_filter
    x_tables               28672  3 ip_tables,xt_multiport,iptable_filter

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    • Offizieller Beitrag

    You need to keep the .config file. Once you copy the config file from /boot/ and do make oldconfig, the .config file is updated. Keep using that file and not the config file from /boot/ anymore. If you use the file from /boot/, you will have lots of questions to answer again when using make oldconfig

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • My server is currently offline, so I can't see them.
    I thought you talking about the .config and .config.old from by built kernel folder.
    Are they the same from /boot/ ?
    Where do I copy the .config file from /boot/ to ?

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    • Offizieller Beitrag

    I'm confused. I guess I don't know how you are building this kernel. When I say .config, that is the only file I am talking about and since I don't know what folder you are using, I don't mention the folder. Definitely not .config.old. Didn't you copy in your config from /boot/ to the compile folder before compiling? It isn't called .config in /boot. It is called something like config-4.5.0-0.bpo.2-amd64.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I think you meant this : cp /boot/config-$(uname -r) .config
    Yes, I did copied it.



    I built my kernel under my home user sub directory.

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    2 Mal editiert, zuletzt von tinh_x7 ()

    • Offizieller Beitrag

    Yep, that is what I meant. And after you answer all those questions, the .config file is changed. So, if you don't want to answer all those questions when moving to a new version of the kernel, keep using that .config file. Don't copy in the config from /boot/ every time you compile a new kernel.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    I don't use iptables but it looks like you need to modprobe iptable_nat
    If that works, I would change it from a module to a compiled in driver in make menuconfig (change M to Y).

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Ok, I'll try that tonight.
    Thanks.


    I think this is the section:


    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

  • I just recompiled the kernel today...
    I have overwritten the .config from make menuconfig, then it goes straight the compilation process, but if I save it as a different name, then it force me to answer the old menuconfig.
    I have to answers twice.


    So, if compile a new kernel, instead copy the config from boot, I just load my existing .config in the make menuconfig, right?


    This is what I got at the end of the compiling process.

    Code
    dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    7 Mal editiert, zuletzt von tinh_x7 ()

    • Offizieller Beitrag

    make menuconfig doesn't load the config. You don't even have to execute make menuconfig if you don't have any changes to make.


    apt-get install libfile-fcntllock-perl will fix the warning

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • So, if I just copy the /boot/config---name.... that I want to use, then do make menuconfig, it should be fine ?
    Some users say it's a proper way to do make menuconfig then make oldconfig, but to me it seems redundant.
    What do you think?

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    • Offizieller Beitrag

    make oldconfig should come before make menuconfig. If you execute make oldconfig, you don't have to use make menuconfig unless you want to change something.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    Never tried. If you don't want to answer the questions, just use make olddefconfig before make menuconfig.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!