sn0wd0g

Members
 View Profile  See their activity

  • Posts

    11

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

sn0wd0g's Achievements

Noob

Noob (1/14)

0

Reputation

  1. sn0wd0g
    That is not the case for me as I do not use btrfs.
  2. sn0wd0g
    I had a new crash today, as Ive switched back from 6.11.5 to 6.12.6. I've got a new diagnostics just when the load was rising. I was checking the docker stats right at that moment, and all containers seemed ok from the stats overview. none of them was created a cpu load and memory was within the limits. zabox-diagnostics-20240108-1006.zip
  3. sn0wd0g
    This time it crashed in a couple of hours, but I was able to get the diagnostics when it all started. zabox-diagnostics-20240105-0441.zip
  4. sn0wd0g started following [6.12.6] Server hangs and hard rebot is the only usable option
  5. sn0wd0g
    The server freezes every few days and can only be restarted from the button. The same behavior is happening since 6.12.1 with all versions until 6.12.6. I have tested all releases from 6.12.1 until the latest and have always reverted back to 6.11.5 which seems very stable. I cannot generate the diagnostics as the server is not responsive. This is the current status according to "top" top - 18:07:33 up 2 days, 23:16, 4 users, load average: 536.77, 541.29, 476.42 Tasks: 1183 total, 17 running, 1166 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.1 us, 93.4 sy, 0.0 ni, 0.0 id, 5.2 wa, 0.0 hi, 0.3 si, 0.0 st MiB Mem : 31832.8 total, 920.7 free, 12348.8 used, 18563.3 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 17504.5 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 163 root 20 0 0 0 0 R 71.1 0.0 611:48.68 kswapd0 4640 root 20 0 0 0 0 R 54.3 0.0 9:28.53 kworker/u24:8+loop2 31161 root 20 0 0 0 0 R 53.3 0.0 8:40.87 kworker/u24:7+loop2 20072 root 20 0 0 0 0 R 48.7 0.0 9:13.94 kworker/u24:4+loop2 26796 root 20 0 0 0 0 R 47.4 0.0 7:45.40 kworker/u24:3+loop2 30526 root 20 0 0 0 0 R 46.4 0.0 8:01.16 kworker/u24:10+loop2 18845 root 20 0 0 0 0 I 44.4 0.0 7:31.15 kworker/u24:5-btrfs-endio 11327 root 20 0 0 0 0 R 40.5 0.0 8:01.96 kworker/u24:21+loop2 23368 root 20 0 0 0 0 R 40.1 0.0 7:38.71 kworker/u24:26+loop2 9418 root 20 0 0 0 0 R 39.8 0.0 4:52.91 kworker/u24:18+loop2 9318 root 20 0 0 0 0 I 39.5 0.0 9:07.26 kworker/u24:13-btrfs-endio 23350 root 20 0 0 0 0 R 38.8 0.0 7:40.69 kworker/u24:25+loop2 11799 root 20 0 0 0 0 R 35.9 0.0 8:20.71 kworker/u24:6+loop2 11324 root 20 0 0 0 0 I 35.2 0.0 8:11.04 kworker/u24:20-btrfs-endio 23839 root 20 0 0 0 0 I 34.9 0.0 4:46.69 kworker/u24:28-btrfs-endio 28572 root 20 0 0 0 0 I 34.9 0.0 8:26.47 kworker/u24:1-btrfs-endio 10287 root 20 0 0 0 0 I 34.2 0.0 9:01.77 kworker/u24:0-btrfs-endio 16594 root 20 0 0 0 0 R 32.2 0.0 8:56.59 kworker/u24:14+btrfs-endio 23779 root 20 0 0 0 0 I 30.9 0.0 5:43.96 kworker/u24:27-btrfs-endio 21281 root 20 0 0 0 0 I 30.6 0.0 6:03.77 kworker/u24:12-btrfs-endio 19565 root 20 0 0 0 0 I 29.9 0.0 8:21.53 kworker/u24:24-btrfs-endio 9319 root 20 0 0 0 0 I 28.9 0.0 9:18.39 kworker/u24:17-btrfs-endio 18390 root 20 0 0 0 0 R 26.0 0.0 10:05.56 kworker/u24:9+loop2 11333 root 20 0 0 0 0 R 21.1 0.0 8:33.80 kworker/u24:23+loop2 553 root 20 0 0 0 0 I 14.8 0.0 8:30.42 kworker/u24:2-btrfs-endio-meta Syslog is also attached syslog Memtest was successful. Docker is running with ipvlan. Diag generated after system reboot. zabox-diagnostics-20240104-1910 2.zip
  6. sn0wd0g
    On a previous crash I have tried to connect via my phone and a vm.. it made no difference. as it hangs especially while preclearing a disk, I think it is related to this plugin or maybe the unassigned devices.
  7. sn0wd0g
    That is the client I am connecting from
  8. sn0wd0g
    Thanks. I'll revert to 6.11.1 when I'm done with the preclear and I'll update the other thread if I identify something new. Before the preclear I had just one crash while running unraid for a couple of days. While preclear is running, the crashes happen more often.
  9. sn0wd0g
    Hi, The issue has occurred twice with Unraid 6.11.1. To me it looks related to disk preclear. Yesterday I have started a preclear and today the WebUi was showing 502. I have rebooted the system and started a new preclear. 2 hours later, the Webui was showing 502. I have reverted to 6.10.3 to see if it has a different outcome. Attached is the diagnostic Thank you. zabox-diagnostics-20221012-0658.zip
  10. sn0wd0g started following Software Guard Extensions support in Kernel and QEMU and [Support] ich777 - AMD Vendor Reset, CoralTPU, hpsahba,...
  11. sn0wd0g
    The Kernel included in 6.10RC2 has SGX support but it is not compiled with it. /usr/src/linux-5.14.15-Unraid/.config # CONFIG_X86_SGX is not set sgx is also supported by the 6.2.0 QEMU. Would there be a chance to get SGX in the final 6.10?
  12. sn0wd0g
    yes, Intel SGX. The scope of it is to launch VMs with sgx support. I have compiled the qemu with sgx support, but it is not compiled into kernel, hence my problem. I have tested it with 6.10Rc2
  13. sn0wd0g
    will the container be available for 6.10? I would like to enable SGX.