segator

Members
  • Posts

    159
  • Joined

  • Last visited

Posts posted by segator

  1. Seems we can not run kubernetes natively on unraid if we don't enable docker.

    I would like to separate docker containers from kubernetes containers, if I run k3s automatically configure a containerd instance

    but I got this error.

    ERRO[2021-05-29T20:59:52.102559272+02:00] RunPodSandbox for &PodSandboxMetadata{Name:metrics-server-86cbb8457f-cszbj,Uid:89b03757-5da6-4d20-a140-9544f5c940db,Namespace:kube-system,Attempt:0,} failed, error  error="failed to create containerd task: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: rootfs_linux.go:118: jailing process inside rootfs caused: pivot_root invalid argument: unknown"

     

    Seems something is missing in unraid OS, maybe someone can help me to discover what is missing.

  2. Hi, trying to use this tool to build kernel with some modules enabled for networking but the docker image tag 6.8.3 doesn't exists anymore I think and if I use latest then 

    --One or more Stock Unraid v6.9.0 files not found, downloading...---
    ---Download of Stock Unraid v6.9.0 failed, putting container into sleep mode!---
    Even my unraid is at 6.8.3 

     

    also my other question is how i execute the makemenu to choose the modules?

     

    Thanks!

  3. I have 2 baremetal UNraid with their license.

    (the second one is a fusion of a NAS + desktop pc) it works well but i lose some performance for gaming and I tired so I want to move the UNRAID to the first box (already with unraid but as VM) to isolate version and permissions.

    How can i move my license to the VM without even use pendrive? I supose it is fine somehow to dump my pendrive to a img file and then load the img file to the VM? but then license will fails?

    what should I do?

  4. oh.. sorry what a newbie I am...
    yes says smart ok, so I supose if in the future some issues are detected I will be notified as any disk in the array, right¿?

    BTW someone tried ZFS over USB disks? is that a crazy idea? i am out of space on my rack server :( and i'm considering buying a 4slots usb enclosure. any other idea if not?

  5. Memory issue fixed increasing blocksize in the dataset to 1M ashift=12 disabled dedup and compression on not needed volumes (like multimedia vols)

    -15GB of usage. 

     

    @Marshalleq which error you have, running latest beta with gaming VM and ZFS RC2 (NAS + DEsktop PC all in one) all working fine after my fixes with the memory.

     

    in your logs I saw you have disabled the xattr? 

    • Like 1
  6. yes I remember readed about 1gb per TB of data in my case I have 10.4T of data thats then 10.4GB of ram

     

    so If I sum my VM ram + arc + dedup 
    24

    12

    11

    means out of ram tootally.. 

    nevertheless I reduced now to

    20

    8

    11

    and i'm still on 0gb of free ram :S

  7. in my case have a lot of benefits because the type of data I store on my volume.

    I build code and archive all the builds so the deduplication ratio is so high as the diference between build are a couple of kb.

     

    Anyway as far as I understood, teorically when linux need memory, ZFS free some memory of the arc cache, but its seems its not doing this, could be?

     

    also, do you know how this parameters affect when using ZFS on unraid?

    reccommended values in tip & tweak unraid plugin are:

    vm.dirty_background_ratio = 2 %
    vm.dirty_ratio = 3 %

     

  8. how is this possible?

    i have 24gb for the VM

    10GB for ARC cache

    and running nextcloud with redis and mysql and some rubish dockers.

     

    how can I see the real ram usage of ZFS? (arc + metadata cache + dedup.. )

    I have 10.4TB on my zfs vol btw

  9. Hey using from a couple of weeks ZFS on unraid with gaming VM as primary desktop pc (nas + desktop pc all in one), it works fine but sometimes unraid decides to kill my VM because "out of memory" i assigned 16gb of ram to the VM and the host have 64gb of ram, I think zfs is not cleaning enough fast the arc memory when other containers reclaim memory and then kernel decides to kill my VM :(

    i can fix it using hugepages but i don't like it because then its memory that ZFS can not use it when the VM is shutted down (that at the end is the 90% of the time), I tried to limit ZFS arc with echo 12884901888 >> /sys/module/zfs/parameters/zfs_arc_max but same :(

     

  10. is still spaming on my log :(

     

    Oct 3 12:11:48 segator-unraid emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin install https://raw.githubusercontent.com/doron1/unraid-sas-spindown/master/sas-spindown.plg
    Oct 3 12:11:48 segator-unraid root: plugin: running: anonymous
    Oct 3 12:11:48 segator-unraid root: plugin: creating: /usr/local/emhttp/plugins/sas-spindown/README.md - from INLINE content
    Oct 3 12:11:48 segator-unraid root: plugin: setting: /usr/local/emhttp/plugins/sas-spindown/README.md - mode to 644
    Oct 3 12:11:48 segator-unraid root: plugin: creating: /usr/local/bin/unraid-spinsasdown - from INLINE content
    Oct 3 12:11:48 segator-unraid root: plugin: setting: /usr/local/bin/unraid-spinsasdown - mode to 755
    Oct 3 12:11:48 segator-unraid root: plugin: creating: /usr/sbin/smartctl.wrapper - from INLINE content
    Oct 3 12:11:48 segator-unraid root: plugin: setting: /usr/sbin/smartctl.wrapper - mode to 755
    Oct 3 12:11:48 segator-unraid root: plugin: creating: /etc/rsyslog.d/99-spinsasdown.conf - from INLINE content
    Oct 3 12:11:48 segator-unraid root: plugin: setting: /etc/rsyslog.d/99-spinsasdown.conf - mode to 644
    Oct 3 12:11:48 segator-unraid root: plugin: running: anonymous
    Oct 3 12:11:48 segator-unraid sas-spindown plugin: Installing a wrapper for smartctl...
    Oct 3 12:11:48 segator-unraid sas-spindown plugin: Installing syslog hook for SAS device spindown...
    Oct 3 12:11:49 segator-unraid kernel: mdcmd (1518646): spindown 4
    Oct 3 12:11:49 segator-unraid kernel: md: do_drive_cmd: disk4: ATA_OP e0 ioctl error: -5
    Oct 3 12:11:49 segator-unraid kernel: mdcmd (1518647): spindown 7
    Oct 3 12:11:49 segator-unraid emhttpd: error: mdcmd, 2721: Input/output error (5): write
    Oct 3 12:11:49 segator-unraid emhttpd: error: mdcmd, 2721: Input/output error (5): write
    Oct 3 12:11:49 segator-unraid kernel: md: do_drive_cmd: disk7: ATA_OP e0 ioctl error: -5
    Oct 3 12:11:50 segator-unraid rsyslogd: [origin software="rsyslogd" swVersion="8.1908.0" x-pid="27295" x-info="https://www.rsyslog.com"] start
    Oct 3 12:11:51 segator-unraid kernel: mdcmd (1518648): spindown 4
    Oct 3 12:11:52 segator-unraid SAS Assist v0.5[27387]: spinning down slot 4, device /dev/sdd (/dev/sg3)
    Oct 3 12:11:54 segator-unraid SAS Assist v0.5[27435]: spinning down slot 7, device /dev/sdg (/dev/sg6)
    Oct 3 12:11:56 segator-unraid emhttpd: error: mdcmd, 2721: Input/output error (5): write
    Oct 3 12:11:56 segator-unraid kernel: md: do_drive_cmd: disk4: ATA_OP e0 ioctl error: -5
    Oct 3 12:11:56 segator-unraid kernel: mdcmd (1518649): spindown 7
    Oct 3 12:11:58 segator-unraid SAS Assist v0.5[27517]: spinning down slot 4, device /dev/sdd (/dev/sg3)
    Oct 3 12:12:02 segator-unraid emhttpd: error: mdcmd, 2721: Input/output error (5): write
    Oct 3 12:12:02 segator-unraid kernel: md: do_drive_cmd: disk7: ATA_OP e0 ioctl error: -5
    Oct 3 12:12:03 segator-unraid kernel: mdcmd (1518650): spindown 4
    Oct 3 12:12:04 segator-unraid SAS Assist v0.5[27826]: spinning down slot 7, device /dev/sdg (/dev/sg6)
    Oct 3 12:12:06 segator-unraid emhttpd: error: mdcmd, 2721: Input/output error (5): write
    Oct 3 12:12:06 segator-unraid kernel: md: do_drive_cmd: disk4: ATA_OP e0 ioctl error: -5
    Oct 3 12:12:06 segator-unraid kernel: mdcmd (1518651): spindown 7
    Oct 3 12:12:08 segator-unraid SAS Assist v0.5[27904]: spinning down slot 4, device /dev/sdd (/dev/sg3)