Papa_TJ

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]: *****

I set up a folder on my cache drive and I pointed the syslog to that folder. is this the correct setup for executing syslog? I also noticed that my server has been online for 3 plus days but I just started it via the start button. I thought that this was funny so I looked for a sleep setting and found that there is a sleep setting that was not activated in the last version. This sleep setting setting must have been setup during my recent upgrade of my unraid server.

attached is my syslog file. please let me know if there is any crash data in it. the server won't stay on for more than 24 hours now. thank you. syslog

Hello all, I recently upgraded from 6.9 to 6.11. Now my server shuts down within 24 hours of boot up. Where should I start to troubleshoot?

Thank you Theruck, I think you are talking about setting my cache drive up so that data is copied to it and then move to storage on the spinning drives with mover. I get how to use this method, I was just wondering if there is a way to do what I asked in my post. seems as though the server is already caching to memory but maybe limited. I am just wondering if there is a way to increase the cache. thanks.

Hello, I am wondering if there is a way to adjust the amount of data that can be cached to memory during heavy file transfers to my server. I copy Large files from my desktop to my server on a regular basis over my gigabit network. My Unraid server has 64 gigs of ram and I am running 15 terabytes of disk space over 5ea 3 terabyte drives and of course the parity drive and a I-9 10900k CPU. The file sizes that I normally transfer are 40 to 100 gigs. I get full network speed for about 2 to 3 gig of transfer then it drops to whatever speed the drives can write. Is there a way to increase the cache buffer on the Unraid server to allow for a 40 or so gigs to cache in server ram while the drives are continuing to write? if this is possible, is there a limit? I could drop another 64 gigs onto the server and cache up to 80 or 90 gigs. this would allow me to disconnect my laptop from my network much faster.

First of all I will say that I am not a power user of Unraid so please bare with me. I have moved all files form my cache and I have made sure that this share does not use cache drive but when I add new files to this share they end up on the cache drive again. Can someone please tell me what setting to look for to enforce that files will written to array instead of cache?

I found a backup that I had done where I used the user script backup. from there I was able to restore one of my VM's. I don't seem to have the XML for the other VM machines so I am wondering can I use the XML for the machine that I did find and point it toward one of the other VM images that I have?

OK so I have done a little more reading about the libvirt.img file and I did find the file in the location suggested above. I am not sure how to check to see if the file is corrupt so if someone can suggest a method for this I would appreciate it. I loaded an Ubuntu desktop vm after my windows VM disappeared and it is working fine. looking to see if the libvirt.img file also contains the xml for ubuntu. I would guess if this is the case then the file is not corrupt. I guess it still could have bad info in it. I also see the vdisk.img files in my VM directories for my windows installs. I have done a few searches on this forum as well as the internet and can't seem to find a method for restoring my windows VM. please can someone point me in the right direction for a step by step guide on how to do this or at least let me know it can't be done.

Thanks for the advice, how would one go about checking to see if the libvert.img file is corrupted?

Hello all, the other day I rebooted my server and didn't realize that the motherboard battery was dead. After the reboot I tried to start my windows VM and it errored out. The error said something about configuration being wrong which I thought was funny as I was just running my VM prior to rebooting the server. I rebooted the server again and this time when it came up the VM was not even listed in my VM's tab. I later found out that the motherboard reverted to default which turned off the virtual machine settings in the bios. I installed a new battery and booted again but no lock the VM is still not listed. I am hoping someone can point me in the right direction to help me not only get my VM back if possible but to also find the information to learn more about where all the files are kept and what those files are that manage a VM. Signed please help!!!

I get this message from time to time from my server. it seems to build up 70 80 90% then I get a message saying its normal again. the only docker running on my server is Plex. Docker high image disk utilization: 08-12-2020 20:59 Warning [MEDIANAS] - Docker image disk utilization of 71% Docker utilization of image file /mnt/user/system/docker/docker.img is it possible that my tv tuner recordings are temp dumping into the wrong directly or into a directory that is limited on space before they are moved off to my main storage?

anyone

The temperature reads 90f/220f does this mean that the system maxes at 220f or is there two temp sensors on my card and it is about to burn down my computer?

installed a new power supply and all seems to be ok now. thanks for all the support