Papa_TJ Posted February 7 Share Posted February 7 Hello, recently I upgraded my HDD in my Unraid server. seems like once a day the array is stopping. How do I start my diagnostics? Below is a copy of the log file thanks, Dave text error warn system array login Feb 7 12:09:10 MediaNAS root: realtime =none extsz=4096 blocks=0, rtextents=0 Feb 7 12:09:10 MediaNAS emhttpd: mounting /mnt/cache Feb 7 12:09:10 MediaNAS emhttpd: shcmd (12412): mkdir -p /mnt/cache Feb 7 12:09:10 MediaNAS emhttpd: shcmd (12413): mount -t btrfs -o noatime,space_cache=v2 /dev/nvme0n1p1 /mnt/cache Feb 7 12:09:10 MediaNAS kernel: BTRFS info (device nvme0n1p1): using crc32c (crc32c-intel) checksum algorithm Feb 7 12:09:10 MediaNAS kernel: BTRFS info (device nvme0n1p1): using free space tree Feb 7 12:09:10 MediaNAS emhttpd: shcmd (12414): mount -o remount,discard=async /mnt/cache Feb 7 12:09:10 MediaNAS kernel: BTRFS info (device nvme0n1p1): enabling ssd optimizations Feb 7 12:09:10 MediaNAS kernel: BTRFS info (device nvme0n1p1: state M): turning on async discard Feb 7 12:09:11 MediaNAS emhttpd: shcmd (12416): /usr/sbin/zfs mount -a Feb 7 12:09:11 MediaNAS emhttpd: shcmd (12417): sync Feb 7 12:09:11 MediaNAS emhttpd: shcmd (12418): mkdir /mnt/user0 Feb 7 12:09:11 MediaNAS emhttpd: shcmd (12419): /usr/local/bin/shfs /mnt/user0 -disks 6 -o default_permissions,allow_other,noatime Feb 7 12:09:11 MediaNAS shfs: FUSE library version 3.12.0 Feb 7 12:09:11 MediaNAS emhttpd: shcmd (12420): mkdir /mnt/user Feb 7 12:09:11 MediaNAS emhttpd: shcmd (12421): /usr/local/bin/shfs /mnt/user -disks 7 -o default_permissions,allow_other,noatime -o remember=0 Feb 7 12:09:11 MediaNAS shfs: FUSE library version 3.12.0 Feb 7 12:09:11 MediaNAS emhttpd: shcmd (12424): /usr/local/sbin/update_cron Feb 7 12:09:12 MediaNAS root: Delaying execution of fix common problems scan for 10 minutes Feb 7 12:09:12 MediaNAS unassigned.devices: Mounting 'Auto Mount' Devices... Feb 7 12:09:12 MediaNAS emhttpd: Starting services... Feb 7 12:09:12 MediaNAS emhttpd: shcmd (12426): /etc/rc.d/rc.samba restart Feb 7 12:09:12 MediaNAS winbindd[6629]: [2024/02/07 12:09:12.604465, 0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler) Feb 7 12:09:12 MediaNAS winbindd[6629]: Got sig[15] terminate (is_parent=1) Feb 7 12:09:12 MediaNAS wsdd2[6626]: 'Terminated' signal received. Feb 7 12:09:12 MediaNAS nmbd[6616]: [2024/02/07 12:09:12.604497, 0] ../../source3/nmbd/nmbd.c:59(terminate) Feb 7 12:09:12 MediaNAS nmbd[6616]: Got SIGTERM: going down... Feb 7 12:09:12 MediaNAS winbindd[6631]: [2024/02/07 12:09:12.604508, 0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler) Feb 7 12:09:12 MediaNAS winbindd[6631]: Got sig[15] terminate (is_parent=0) Feb 7 12:09:12 MediaNAS wsdd2[6626]: terminating. Feb 7 12:09:12 MediaNAS winbindd[6790]: [2024/02/07 12:09:12.604590, 0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler) Feb 7 12:09:12 MediaNAS winbindd[6790]: Got sig[15] terminate (is_parent=0) Feb 7 12:09:13 MediaNAS rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="25496" x-info="https://www.rsyslog.com"] start Feb 7 12:09:15 MediaNAS root: Starting Samba: /usr/sbin/smbd -D Feb 7 12:09:15 MediaNAS smbd[25681]: [2024/02/07 12:09:15.811688, 0] ../../source3/smbd/server.c:1741(main) Feb 7 12:09:15 MediaNAS smbd[25681]: smbd version 4.17.12 started. Feb 7 12:09:15 MediaNAS smbd[25681]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Feb 7 12:09:15 MediaNAS root: /usr/sbin/nmbd -D Feb 7 12:09:15 MediaNAS nmbd[25683]: [2024/02/07 12:09:15.824784, 0] ../../source3/nmbd/nmbd.c:901(main) Feb 7 12:09:15 MediaNAS nmbd[25683]: nmbd version 4.17.12 started. Feb 7 12:09:15 MediaNAS nmbd[25683]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Feb 7 12:09:15 MediaNAS root: /usr/sbin/wsdd2 -d -4 Feb 7 12:09:15 MediaNAS wsdd2[25697]: starting. Feb 7 12:09:15 MediaNAS root: /usr/sbin/winbindd -D Feb 7 12:09:15 MediaNAS winbindd[25698]: [2024/02/07 12:09:15.880707, 0] ../../source3/winbindd/winbindd.c:1440(main) Feb 7 12:09:15 MediaNAS winbindd[25698]: winbindd version 4.17.12 started. Feb 7 12:09:15 MediaNAS winbindd[25698]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Feb 7 12:09:15 MediaNAS winbindd[25700]: [2024/02/07 12:09:15.882977, 0] ../../source3/winbindd/winbindd_cache.c:3117(initialize_winbindd_cache) Feb 7 12:09:15 MediaNAS winbindd[25700]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Feb 7 12:09:15 MediaNAS emhttpd: shcmd (12430): /etc/rc.d/rc.avahidaemon restart Feb 7 12:09:15 MediaNAS root: Stopping Avahi mDNS/DNS-SD Daemon: stopped Feb 7 12:09:15 MediaNAS avahi-dnsconfd[6678]: read(): EOF Feb 7 12:09:16 MediaNAS root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Feb 7 12:09:16 MediaNAS avahi-daemon[25753]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Feb 7 12:09:16 MediaNAS avahi-daemon[25753]: Successfully dropped root privileges. Feb 7 12:09:16 MediaNAS avahi-daemon[25753]: avahi-daemon 0.8 starting up. Feb 7 12:09:16 MediaNAS avahi-daemon[25753]: Successfully called chroot(). Feb 7 12:09:16 MediaNAS avahi-daemon[25753]: Successfully dropped remaining capabilities. Feb 7 12:09:16 MediaNAS avahi-daemon[25753]: Loading service file /services/sftp-ssh.service. Feb 7 12:09:16 MediaNAS avahi-daemon[25753]: Loading service file /services/smb.service. Feb 7 12:09:16 MediaNAS avahi-daemon[25753]: Loading service file /services/ssh.service. Feb 7 12:09:16 MediaNAS avahi-daemon[25753]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.24.249. Feb 7 12:09:16 MediaNAS avahi-daemon[25753]: New relevant interface br0.IPv4 for mDNS. Feb 7 12:09:16 MediaNAS avahi-daemon[25753]: Network interface enumeration completed. Feb 7 12:09:16 MediaNAS avahi-daemon[25753]: Registering new address record for 192.168.24.249 on br0.IPv4. Feb 7 12:09:16 MediaNAS emhttpd: shcmd (12431): /etc/rc.d/rc.avahidnsconfd restart Feb 7 12:09:16 MediaNAS root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Feb 7 12:09:16 MediaNAS root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Feb 7 12:09:16 MediaNAS avahi-dnsconfd[25764]: Successfully connected to Avahi daemon. Feb 7 12:09:16 MediaNAS emhttpd: shcmd (12442): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 50 Feb 7 12:09:17 MediaNAS avahi-daemon[25753]: Server startup complete. Host name is MediaNAS.local. Local service cookie is 3743503000. Feb 7 12:09:17 MediaNAS kernel: loop2: detected capacity change from 0 to 104857600 Feb 7 12:09:17 MediaNAS kernel: BTRFS: device fsid cc829b36-9a8d-4e82-80b8-99b724f00d7d devid 1 transid 6314974 /dev/loop2 scanned by mount (25843) Feb 7 12:09:17 MediaNAS kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm Feb 7 12:09:17 MediaNAS kernel: BTRFS info (device loop2): using free space tree Feb 7 12:09:17 MediaNAS kernel: BTRFS info (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0 Feb 7 12:09:17 MediaNAS kernel: BTRFS info (device loop2): start tree-log replay Feb 7 12:09:17 MediaNAS kernel: BTRFS info (device loop2): checking UUID tree Feb 7 12:09:17 MediaNAS root: Resize device id 1 (/dev/loop2) from 50.00GiB to max Feb 7 12:09:17 MediaNAS emhttpd: shcmd (12444): /etc/rc.d/rc.docker start Feb 7 12:09:17 MediaNAS root: starting dockerd ... Feb 7 12:09:17 MediaNAS avahi-daemon[25753]: Service "MediaNAS" (/services/ssh.service) successfully established. Feb 7 12:09:17 MediaNAS avahi-daemon[25753]: Service "MediaNAS" (/services/smb.service) successfully established. Feb 7 12:09:17 MediaNAS avahi-daemon[25753]: Service "MediaNAS" (/services/sftp-ssh.service) successfully established. Feb 7 12:09:20 MediaNAS kernel: BTRFS warning (device loop2): csum failed root 5 ino 37139751 off 0 csum 0x5150c7e2 expected csum 0xcc90ad49 mirror 1 Feb 7 12:09:20 MediaNAS kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 9, gen 0 Feb 7 12:09:20 MediaNAS kernel: BTRFS warning (device loop2): csum failed root 5 ino 37139751 off 0 csum 0x5150c7e2 expected csum 0xcc90ad49 mirror 1 Feb 7 12:09:20 MediaNAS kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 0, rd 0, flush 0, corrupt 10, gen 0 Feb 7 12:09:21 MediaNAS kernel: Bridge firewalling registered Feb 7 12:09:21 MediaNAS kernel: Initializing XFRM netlink socket Feb 7 12:09:24 MediaNAS root: Error response from daemon: network with name br0 already exists Feb 7 12:09:24 MediaNAS rc.docker: connecting binhex-nzbget to network br0 Feb 7 12:09:25 MediaNAS emhttpd: shcmd (12458): /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 Feb 7 12:09:25 MediaNAS kernel: loop3: detected capacity change from 0 to 2097152 Feb 7 12:09:25 MediaNAS kernel: BTRFS: device fsid eb6ea2d7-c706-4118-86bb-4efe2e1b2492 devid 1 transid 10523 /dev/loop3 scanned by mount (26834) Feb 7 12:09:25 MediaNAS kernel: BTRFS info (device loop3): using crc32c (crc32c-intel) checksum algorithm Feb 7 12:09:25 MediaNAS kernel: BTRFS info (device loop3): using free space tree Feb 7 12:09:25 MediaNAS root: Resize device id 1 (/dev/loop3) from 1.00GiB to max Feb 7 12:09:25 MediaNAS emhttpd: shcmd (12460): /etc/rc.d/rc.libvirt start Feb 7 12:09:25 MediaNAS root: Starting virtlockd... Feb 7 12:09:25 MediaNAS root: Starting virtlogd... Feb 7 12:09:26 MediaNAS rc.libvirt: change virbr0 to bridge in /etc/libvirt/qemu/Ubuntu 22.04 Desktop.xml Feb 7 12:09:26 MediaNAS root: Starting libvirtd... Feb 7 12:09:26 MediaNAS kernel: tun: Universal TUN/TAP device driver, 1.6 Feb 7 12:09:26 MediaNAS kernel: mdcmd (36): check correct Feb 7 12:09:26 MediaNAS kernel: md: recovery thread: check P ... Feb 7 12:09:26 MediaNAS dnsmasq[27039]: started, version 2.89 cachesize 150 Feb 7 12:09:26 MediaNAS dnsmasq[27039]: 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 Feb 7 12:09:26 MediaNAS dnsmasq-dhcp[27039]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Feb 7 12:09:26 MediaNAS dnsmasq-dhcp[27039]: DHCP, sockets bound exclusively to interface virbr0 Feb 7 12:09:26 MediaNAS dnsmasq[27039]: reading /etc/resolv.conf Feb 7 12:09:26 MediaNAS dnsmasq[27039]: using nameserver 192.168.24.1#53 Feb 7 12:09:26 MediaNAS dnsmasq[27039]: read /etc/hosts - 3 names Feb 7 12:09:26 MediaNAS dnsmasq[27039]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 names Feb 7 12:09:26 MediaNAS dnsmasq-dhcp[27039]: read /var/lib/libvirt/dnsmasq/default.hostsfile Feb 7 12:09:28 MediaNAS kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint. Feb 7 12:09:28 MediaNAS kernel: nvidia-uvm: Loaded the UVM driver, major device number 238. Feb 7 12:09:28 MediaNAS tips.and.tweaks: Tweaks Applied Feb 7 12:09:28 MediaNAS unassigned.devices: Mounting 'Auto Mount' Remote Shares... Feb 7 12:09:28 MediaNAS unassigned.devices: Using Gateway '192.168.24.1' for Remote Shares. Feb 7 12:09:28 MediaNAS unassigned.devices: Waiting 5 secs before mounting Remote Shares... Feb 7 12:09:35 MediaNAS rc.docker: Plex-Media-Server: started succesfully! Feb 7 12:09:38 MediaNAS nmbd[25687]: [2024/02/07 12:09:38.851737, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Feb 7 12:09:38 MediaNAS nmbd[25687]: ***** Feb 7 12:09:38 MediaNAS nmbd[25687]: Feb 7 12:09:38 MediaNAS nmbd[25687]: Samba name server MEDIANAS is now a local master browser for workgroup HOME on subnet 192.168.24.249 Feb 7 12:09:38 MediaNAS nmbd[25687]: Feb 7 12:09:38 MediaNAS nmbd[25687]: ***** Quote Link to comment
itimpi Posted February 7 Share Posted February 7 2 hours ago, Papa_TJ said: How do I start my diagnostics? Not quite sure what you are asking. The information in the link describes how to get standard diagnostics via GUI or command line. The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot. It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field. Quote Link to comment
Recommended Posts
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.