JIll
Members
-
Joined
-
Last visited
-
晚了一個月, 不過我最近也遇到了死機問題, 單純紀錄一下 在我的情況log沒什麼用, 因為到死機時OS已經完全停掉了, 根本不會有log 寫上去 最後我是用safe mode, 一直連著顯示器, 之後死機時顯示器出了一些更底層的log, log中顯示是kernal panic了, 所以我猜大機例是硬件問題 最後我是內存, CPU, 主板一個個排查, 最終找到是其中一條內存有問題, 撥掉後只留一條沒問題的內存就沒事了
-
same, updated remotely then discovered that remote not working anymore connected a display locally to the server and boot with gui I found that the bonding was set to "Yes" in network setting which resulting network failure, I have to : manually set the Bonding of eth0 to "No" > apply click "port up" of eth1 > apply reconfig both network cards done currently work great after reconfiguration
-
Save my life, thanks bro
-
First of all, sorry for my bad English. The power button of my server is located on the top of my machine and my cat always accidently (in purpose?) short press the power button, resulting my unraid to shutdown. In 6.9.2, I commented a line in /etc/acpi/acpi_handler.sh to disable the power button action, worked fine. After upgrading to 6.10-RC3 today and I discover that this method is not working anymore. (my cat had shutdown my server twice today) Below is my acpi_handler.sh ======== #!/bin/sh # Default acpi script that takes an entry for all actions IFS=${IFS}/ set $@ case "$1" in button) case "$2" in # power) /sbin/init 0 ;; *) logger "ACPI action $2 is not defined" ;; esac ;; *) # logger "ACPI group $1 / action $2 is not defined" ;; esac ========
