Biloxi_1 Posted December 23, 2017 Share Posted December 23, 2017 Hello, I am new to unraid and have a new build that is continuously crashing. When the crash occurs I am unable to log on remotely or locally. I can't even get the keyboard to power on when plugging it in to log in locally. I originally started off with build 6.3.5, but after several crashes, I downloaded the fix common problems add on, and it advised me to upgrade to 6.4 for Ryzen CPU's. I then upgraded to version 6.4.0rc17b, but I am still having the same issue. My build is as follows: Ryzen 5 1600 Gigabyte AB350M-D3H motherboard (with F10 Bios) 16 gigs of ddr4 Samsung Evo NVME 3x WD Red 4 Tb drives 1x Seagate 1 Tb drive (not in the array at this time) I have uploaded a pic of the screen after a freeze, and some logs from the fix common problems "troubleshooting mode" Any help would be greatly appreciated. FCPsyslog_tail.txt disk.cfg docker.cfg domain.cfg go ident.cfg network.cfg super.dat docker.txt libvirt.txt syslog.txt no qemu log files a-----a.cfg D-------s.cfg d-----s.cfg D--a.cfg i--s.cfg M---a.cfg s----m.cfg Samsung_SSD_960_EVO_250GB_S3ESNX0JB19084W-20171222-0701 cache (nvme0).txt SanDisk_Cruzer_Glide_4C530001221031105432-0-0-20171222-0701 flash (sda).txt ST31000528AS_5VP3RZ7F-20171222-0701 (sde).txt WDC_WD40EFRX-68N32N0_WD-WCC7K5LCE0FE-20171222-0701 parity (sdb).txt WDC_WD40EFRX-68N32N0_WD-WCC7K5LCETHH-20171222-0701 disk2 (sdd).txt WDC_WD40EFRX-68N32N0_WD-WCC7K7XF3EVD-20171222-0701 disk1 (sdc).txt btrfs-usage.txt cmdline.txt df.txt ethtool.txt folders.txt ifconfig.txt iommu_groups.txt lscpu.txt lsmod.txt lsof.txt lspci.txt lsscsi.txt lsusb.txt memory.txt ps.txt top.txt vars.txt unRAID-6.4.0_rc17b.txt Link to comment
Biloxi_1 Posted December 25, 2017 Author Share Posted December 25, 2017 So after doing some research on my own I was able to find this thread that has fixed my issue =) The tower has been up with out crashing for 33 hours now, so fingers crossed. Link to comment
BRiT Posted December 25, 2017 Share Posted December 25, 2017 FYI: For future times when troubleshooting just upload the Diagnostics zip file as is and not each individual file. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.