Jazer

Members
  • Posts

    32
  • Joined

  • Last visited

Recent Profile Visitors

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

Jazer's Achievements

Noob

Noob (1/14)

2

Reputation

1

Community Answers

  1. Same here... anything new on this topic? 1920 is really bad for mac users, because the XDR display uses 1728 points (not pixels) in HiDPI mode.
  2. Coming from rc5 to rc6 - my qemu vm (Hackintosh) stopped working. Execution error internal error: qemu unexpectedly closed the monitor: 2023-05-23T11:48:06.730588Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2023-05-23T11:48:06.731428Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2023-05-23T11:48:06.731959Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2023-05-23T11:48:06.732633Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16] 2023-05-23T11:48:06.746784Z qemu-system-x86_64: -device {"driver":"virtio-9p-pci","id":"fs0","fsdev":"fsdev-fs0","mount_tag":"macos","bus":"pci.1","addr":"0x0"}: cannot initialize fsdev 'fsdev-fs0': failed to open '/mnt/user/macos': No such file or directory Any help on that?
  3. right... turns out to be memory issues
  4. Okay... some docker template files are missing. I don't know how that could happen, because I've not manipulated it manually. I guess something happend with the USB stick. Weird. Thx anyway!
  5. I tried it... I've removed the plugin and restarted (disabled/enabled) the docker service. Same result... no update possible.
  6. Sure... tower-diagnostics-20230415-2304.zip
  7. All containers worked fine with rc2 and where able to update without any issues. After installing rc3, the containers-images can't be updated anymore. Error: Configuration not found. Was this container created using this plugin? All containers where created with rc2. How to fix it?
  8. The network crashed not with the first kernel panic, but with the last. Weird. syslog
  9. Sure... tower-diagnostics-20230322-0923.zip
  10. Firefox & Chrome - running 6.12-rc.2 Temp Values are wrong... READS / WRITES are not changing, even parity is running. Processor temp is changing, but load ist stalled.
  11. From time to time, the dashboard is getting stalled. E.g. starting the parity sync "stops" in the dashboard after some time, but the process continues. Changes to temperature (seen on cosole) are also not reported anymore to the UI. How can I just restart the UI, without affecting the sync process?
  12. Okay... this is somehome wired and I need a little bit assistant to provide the recomended analyze data. The problem: After unspecific time (may take days or minutes after reboot) I get a kernel panic and my unraid server crashes the network. This means - as long as my ethernet cable is plugged in, all devices to my switch are not responding (dropped connection). As soon as I disconnect the cable (or do a hard reset), my network works again. Reconnecting the cable dropps all connections again - like a short cut. root@Tower:~# Message from syslogd@Tower at Mar 22 01:13:39 ... kernel:Kernel panic - not syncing: Fatal exception in interrupt client_loop: send disconnect: Broken pipe I'm running on 6.12-rc2 for testing on a new build (never tested 6.11.x with new build). My old 6.11.x server build works fine. tower-diagnostics-20230322-0923.zip
  13. But even if all selected, there are only two columns.
  14. After starting unRAID, I can connect using ssh for a while. After some hours/events, I can't establish new ssh connections anymore. The logs are fine (as I can guess). Old ssh connections are not disconnect and are working properly, but new ones are timed out. I'm not sure if this is 6.12 related - I'm testing on a brand new system. Mar 19 02:18:28 Tower sshd[8630]: Connection from 192.168.188.106 port 61207 on 192.168.188.111 port 22 rdomain "" Mar 19 02:18:28 Tower sshd[8630]: Accepted key RSA SHA256:xxx found at /root/.ssh/authorized_keys:2 Mar 19 02:18:28 Tower sshd[8630]: Postponed publickey for root from 192.168.188.106 port 61207 ssh2 [preauth] Mar 19 02:18:28 Tower sshd[8630]: Accepted key RSA SHA256:xxx found at /root/.ssh/authorized_keys:2 Mar 19 02:18:28 Tower sshd[8630]: Accepted publickey for root from 192.168.188.106 port 61207 ssh2: RSA SHA256:xxx Mar 19 02:18:28 Tower sshd[8630]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0) Mar 19 02:18:34 Tower kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P28191 } 5001439 jiffies s: 69 root: 0x0/T Mar 19 02:18:34 Tower kernel: rcu: blocking rcu_node structures (internal RCU debug): Mar 19 02:19:40 Tower kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P28191 } 5066975 jiffies s: 69 root: 0x0/T Mar 19 02:19:40 Tower kernel: rcu: blocking rcu_node structures (internal RCU debug): Mar 19 02:20:28 Tower sshd[8630]: pam_elogind(sshd:session): Failed to create session: Connection timed out Mar 19 02:20:28 Tower sshd[8630]: Connection closed by 192.168.188.106 port 61207 Mar 19 02:20:28 Tower sshd[8630]: Close session: user root from 192.168.188.106 port 61207 id 0 Mar 19 02:20:28 Tower sshd[8630]: pam_unix(sshd:session): session closed for user root Mar 19 02:20:28 Tower sshd[8630]: Transferred: sent 3848, received 3884 bytes Mar 19 02:20:28 Tower sshd[8630]: Closing connection to 192.168.188.106 port 61207