September 1, 20241 yr 刚组的新NAS，最开始怀疑是光威的内存问题，结果拿Memtest86+跑了三遍内存也没出一个错。CPU是N305，温度也在50-70°C之间，好像也没什么问题。 错误有一条，加粗下划线标出来了，不过我不懂啥意思，这会影响到NAS频繁死机吗？ Sep 1 22:00:56 Tower winbindd[6692]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Sep 1 22:00:56 Tower emhttpd: shcmd (63): /etc/rc.d/rc.avahidaemon restart Sep 1 22:00:56 Tower root: Stopping Avahi mDNS/DNS-SD Daemon: stopped Sep 1 22:00:56 Tower avahi-daemon[3564]: Got SIGTERM, quitting. Sep 1 22:00:56 Tower avahi-dnsconfd[3573]: read(): EOF Sep 1 22:00:56 Tower avahi-daemon[3564]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.31.99. Sep 1 22:00:56 Tower avahi-daemon[3564]: avahi-daemon 0.8 exiting. Sep 1 22:00:56 Tower root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Sep 1 22:00:56 Tower avahi-daemon[6757]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Sep 1 22:00:56 Tower avahi-daemon[6757]: Successfully dropped root privileges. Sep 1 22:00:56 Tower avahi-daemon[6757]: avahi-daemon 0.8 starting up. Sep 1 22:00:56 Tower avahi-daemon[6757]: Successfully called chroot(). Sep 1 22:00:56 Tower avahi-daemon[6757]: Successfully dropped remaining capabilities. Sep 1 22:00:56 Tower avahi-daemon[6757]: Loading service file /services/sftp-ssh.service. Sep 1 22:00:56 Tower avahi-daemon[6757]: Loading service file /services/smb.service. Sep 1 22:00:56 Tower avahi-daemon[6757]: Loading service file /services/ssh.service. Sep 1 22:00:56 Tower avahi-daemon[6757]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.31.99. Sep 1 22:00:56 Tower avahi-daemon[6757]: New relevant interface br0.IPv4 for mDNS. Sep 1 22:00:56 Tower avahi-daemon[6757]: Network interface enumeration completed. Sep 1 22:00:56 Tower avahi-daemon[6757]: Registering new address record for 192.168.31.99 on br0.IPv4. Sep 1 22:00:56 Tower emhttpd: shcmd (64): /etc/rc.d/rc.avahidnsconfd restart Sep 1 22:00:56 Tower root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Sep 1 22:00:56 Tower root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Sep 1 22:00:56 Tower avahi-dnsconfd[6766]: Successfully connected to Avahi daemon. Sep 1 22:00:56 Tower emhttpd: shcmd (74): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20 Sep 1 22:00:56 Tower kernel: loop2: detected capacity change from 0 to 41943040 Sep 1 22:00:56 Tower kernel: BTRFS: device fsid 0d0ef233-2e36-4b1f-a7aa-f3069e54ff0b devid 1 transid 4991 /dev/loop2 scanned by mount (6806) Sep 1 22:00:56 Tower kernel: BTRFS info (device loop2): first mount of filesystem 0d0ef233-2e36-4b1f-a7aa-f3069e54ff0b Sep 1 22:00:56 Tower kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm Sep 1 22:00:56 Tower kernel: BTRFS info (device loop2): using free space tree Sep 1 22:00:56 Tower root: Resize device id 1 (/dev/loop2) from 20.00GiB to max Sep 1 22:00:56 Tower emhttpd: shcmd (76): /etc/rc.d/rc.docker start Sep 1 22:00:56 Tower root: starting dockerd ... Sep 1 22:00:57 Tower avahi-daemon[6757]: Server startup complete. Host name is Tower.local. Local service cookie is 539763178. Sep 1 22:00:58 Tower avahi-daemon[6757]: Service "Tower" (/services/ssh.service) successfully established. Sep 1 22:00:58 Tower avahi-daemon[6757]: Service "Tower" (/services/smb.service) successfully established. Sep 1 22:00:58 Tower avahi-daemon[6757]: Service "Tower" (/services/sftp-ssh.service) successfully established. Sep 1 22:00:58 Tower kernel: Bridge firewalling registered Sep 1 22:00:58 Tower kernel: Initializing XFRM netlink socket Sep 1 22:00:59 Tower root: Error response from daemon: network with name br0 already exists Sep 1 22:00:59 Tower kernel: docker0: port 1(veth13bc9f0) entered blocking state Sep 1 22:00:59 Tower kernel: docker0: port 1(veth13bc9f0) entered disabled state Sep 1 22:00:59 Tower kernel: device veth13bc9f0 entered promiscuous mode Sep 1 22:00:59 Tower kernel: docker0: port 1(veth13bc9f0) entered blocking state Sep 1 22:00:59 Tower kernel: docker0: port 1(veth13bc9f0) entered forwarding state Sep 1 22:00:59 Tower kernel: docker0: port 1(veth13bc9f0) entered disabled state Sep 1 22:00:59 Tower emhttpd: shcmd (90): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 Sep 1 22:00:59 Tower kernel: loop3: detected capacity change from 0 to 2097152 Sep 1 22:00:59 Tower kernel: BTRFS: device fsid 414d502a-85b3-4e1b-9fdb-aaeb1aea96b9 devid 1 transid 42 /dev/loop3 scanned by mount (7341) Sep 1 22:00:59 Tower kernel: BTRFS info (device loop3): first mount of filesystem 414d502a-85b3-4e1b-9fdb-aaeb1aea96b9 Sep 1 22:00:59 Tower kernel: BTRFS info (device loop3): using crc32c (crc32c-intel) checksum algorithm Sep 1 22:00:59 Tower kernel: BTRFS info (device loop3): using free space tree Sep 1 22:00:59 Tower root: Resize device id 1 (/dev/loop3) from 1.00GiB to max Sep 1 22:00:59 Tower emhttpd: shcmd (92): /etc/rc.d/rc.libvirt start Sep 1 22:00:59 Tower root: Starting virtlockd... Sep 1 22:00:59 Tower root: Starting virtlogd... Sep 1 22:00:59 Tower root: Starting libvirtd... Sep 1 22:00:59 Tower kernel: tun: Universal TUN/TAP device driver, 1.6 Sep 1 22:00:59 Tower kernel: mdcmd (36): check correct Sep 1 22:00:59 Tower kernel: md: recovery thread: check P ... Sep 1 22:01:00 Tower dnsmasq[7520]: started, version 2.89 cachesize 150 Sep 1 22:01:00 Tower dnsmasq[7520]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset no-nftset auth cryptohash DNSSEC loop-detect inotify dumpfile Sep 1 22:01:00 Tower dnsmasq-dhcp[7520]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Sep 1 22:01:00 Tower dnsmasq-dhcp[7520]: DHCP, sockets bound exclusively to interface virbr0 Sep 1 22:01:00 Tower dnsmasq[7520]: reading /etc/resolv.conf Sep 1 22:01:00 Tower dnsmasq[7520]: using nameserver 223.5.5.5#53 Sep 1 22:01:00 Tower dnsmasq[7520]: using nameserver 8.8.4.4#53 Sep 1 22:01:00 Tower dnsmasq[7520]: using nameserver 114.114.114.114#53 Sep 1 22:01:00 Tower dnsmasq[7520]: read /etc/hosts - 2 names Sep 1 22:01:00 Tower dnsmasq[7520]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 names Sep 1 22:01:00 Tower dnsmasq-dhcp[7520]: read /var/lib/libvirt/dnsmasq/default.hostsfile Sep 1 22:01:00 Tower kernel: eth0: renamed from veth8ff0ced Sep 1 22:01:00 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth13bc9f0: link becomes ready Sep 1 22:01:00 Tower kernel: docker0: port 1(veth13bc9f0) entered blocking state Sep 1 22:01:00 Tower kernel: docker0: port 1(veth13bc9f0) entered forwarding state Sep 1 22:01:00 Tower rc.docker: busy_bartik: started succesfully! Sep 1 22:01:01 Tower kernel: br0: port 2(vnet0) entered blocking state Sep 1 22:01:01 Tower kernel: br0: port 2(vnet0) entered disabled state Sep 1 22:01:01 Tower kernel: device vnet0 entered promiscuous mode Sep 1 22:01:01 Tower kernel: br0: port 2(vnet0) entered blocking state Sep 1 22:01:01 Tower kernel: br0: port 2(vnet0) entered forwarding state Sep 1 22:01:27 Tower network: reload service: nginx Sep 1 22:01:35 Tower webGUI: Successful login user root from 192.168.31.222 Sep 1 23:53:58 Tower kernel: md: sync done. time=6779sec Sep 1 23:53:58 Tower kernel: md: recovery thread: exit status: 0 Sep 1 23:57:00 Tower webGUI: Successful login user root from 192.168.31.142 Sep 1 23:58:31 Tower ool www[31613]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Sep 1 23:58:34 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="31657" x-info="https://www.rsyslog.com"] start Sep 1 23:58:56 Tower ool www[31943]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Sep 1 23:58:59 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="31985" x-info="https://www.rsyslog.com"] start 再附上一个系统诊断记录，希望有大佬可以解惑，万分感谢！ tower-diagnostics-20240902-0009.zip
October 2, 20241 yr 晚了一個月, 不過我最近也遇到了死機問題, 單純紀錄一下 在我的情況log沒什麼用, 因為到死機時OS已經完全停掉了, 根本不會有log 寫上去 最後我是用safe mode, 一直連著顯示器, 之後死機時顯示器出了一些更底層的log, log中顯示是kernal panic了, 所以我猜大機例是硬件問題 最後我是內存, CPU, 主板一個個排查, 最終找到是其中一條內存有問題, 撥掉後只留一條沒問題的內存就沒事了
December 2, 20241 yr On 10/30/2024 at 5:09 PM, simear2004 said: 我这是属于怎么搞都不会死机系列😄 常时间运行4个docker+1个win10虚拟机 我最长时间好像是296天，然后忘记因为什么，是升级系统还是怎么样了忘了。之后就是经常性死了，死的莫名其妙，有几次是移动几百G视频从cache到阵列死，一度以为是cpu卡了，后来拷贝文件就观察cpu，温度不超过60度，占用率也50%以下，应该不是cpu的问题。回头我也跟楼上几位学学，拔内存试试，看看是不是内存的问题，我的机器，4个内存槽，插了4个牌子的内存😇
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.