RobWill Posted January 1, 2018 Share Posted January 1, 2018 (edited) I have run into two problems I cannot find a fix for here in the forums. I've been using UNRAID for about nine months, and recently decided to buy an all new computer system. My system specs: UNRAID 6.3.5 (latest you can download from Lime Tech) Thermaltake V3 Black Edition ATX Mid Tower Computer Case Intel® Core™ i5-7600K CPU @ 3.80GHz G.Skill 16GB 2 x 8GB DDR4-2400 CL16 Dual Channel Desktop Memory Kit G.Skill 16GB 2 x 8GB DDR4-2400 CL16 Dual Channel Desktop Memory Kit Solid Gear Neutron Series 750 Watt PS2 ATX Power Supply ASRock H270 Pro4 LGA 1151 ATX Intel Motherboard ASUS GeForce® GT 1030 2GB GDDR5 CSM HDDs: Toshiba 2TB (Parity), Samsung 2TB, Western 2TB, Western 1 TB Cache: Crucial MX300 275GB M.2 Type 2280SS Internal SSD With this setup, I had created multiple Windows VMs (have since removed them all and turned off VMs to rule them out). Typical usage has been as an everyday VM machine, with regular Plex video streaming. I now have data on my disks that I would prefer to keep; so if there are things we can do without having to start all over, I’d prefer to take that approach. I have two core issues, which I suspect may be related. First, at random periods of time (anywhere from an hour to full week after successful boot up and all drives mounted) my machine will "lock up". Specifically, the video output on my local machine will be black, I cannot telnet in, Plex will not be found active, and my VMs not able to be accessed. Through a whole lot of testing, I have replaced my video card, upgraded by PSU from 500W to 750W, moved my SSD M.2 to another slot, and have replaced my entire USB disk / even started with a vanilla install (several times). Lockups happen in every circumstance I have tried so far; they happen in shorter periods of time when a VM is in use. My second problem has been this kernel panic. I have been able to isolate this error to be the only one I see on boot and could use your guidance to help me further troubleshoot (and frankly, understand) what is going on. Sometimes when I boot after memtest, everything works fine; at other random times, I get the panic. This kernel panic happens under all the same tests I already outlined. Can someone explain what this kernel error is telling me? “kernel panic-not syncing: VFS: unable to mount root fs on unknown block(0,0)” I suspect a clue may be found from my attached screenshot [kernalpanic.jpg]. How do I appended sda or sda1 with 'root' for the system to load? In my bios, it is worth noting that I see a USB and UEFI USB option that can be selected [bootoptions.jpg]. When I pick the UEFI option, it never loads (just puts me back into my bios settings menu). The only way I can load UNRAID, is when the non UEFI USB is selected. This happens regardless of: 1) USB disk (all diff models tried have been 2.0, including brand new fresh install and tests with copies including my config); 2) different placement of the USB on MB with different connecting cables (e.g. tried multiple USB 2 header AND 2.0 case ports, as well as USB3 ports- which caused other errors, so I now avoid); and 3) if I have both USB options loaded as boot priority #1 and #2 in any order. I have read many other threads related to both of these errors, and have found that my system will most reliably load when the USB is plugged into 2.0 port and after a memtest of at least 5 min. Once the system is live, I get the problem above with the lock up as described. The other night I fired my system up and was doing some movie streaming for about an hour to see if I could capture information on a crash while with common issues in troubleshooting mode. I am uploading that log here [FCPsyslog_tail.txt & tower-diagnostics-20171231-0704.zip]. Thank you all in advance and cheers to 2018! FCPsyslog_tail.txt tower-diagnostics-20171231-0704.zip FCPsyslog_tail.txt tower-diagnostics-20171231-0704.zip Edited January 17, 2018 by RobWill Quote Link to comment
RobWill Posted January 17, 2018 Author Share Posted January 17, 2018 Lots of lessons learned on this one. The solution: one bad stick of RAM was causing all of this mess. I found this not by running long memtests (in fact they often reported no errors!), but by trying each stick in the first slot one at a time until the kernel fault occurred. After reviewing a lot of related posts, and even my own logs, my issue was not the USB stick, as reported frequently for others. Am really happy my RAM is from G.Skill, as they guarantee their RAM products and am in the process of returning it for a replacement. My hope is that this post might help someone else. Quote Link to comment
Solution RobWill Posted February 26, 2018 Author Solution Share Posted February 26, 2018 One more post to confirm that my replacement stick of RAM from G.Skill resolved this issue. Also worth noting that they kept good to their brand promise and provided me with a replacement without hassle. Quote Link to comment
MarkRMonaco Posted July 30, 2019 Share Posted July 30, 2019 +1 for bad RAM. Just attempted to install some additional RAM modules in my system and ran into this issue. - Pulled the RAM, but had to redo my flash drive. Thankfully, I had a copy of the config folder. 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.