cowgill

Members
  • Posts

    16
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

cowgill's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Okay...ready to mark this solved. ... The reset button on my case was shorting out. When I disconnected it from the motherboard case header my issues were resolved. 🥴 Other minor item: The IO CREST SI-PEX40156 if installed would not allow the Gigabyte GA-X58A-UD3R to get far enough booting to even get to the BIOS. The card boots fine installed in a modern (LGA 1200) motherboard. No idea what was going on there. Wanted to put that data point out there in case others have issues in the future as I have learned finding unresolved issue threads is beyond frustrating.
  2. I had no VM's running and that service was disabled. I tried disabling Docker on your advice, that did not make a difference for me. I have since tried replacing my flash boot drive, that did not help either. Since the start of the thread I've ditched all the new hardware and gone back to my old stuff (first gen i7 w/ Gigabyte GA-X58A-UD3R). As far as I know the only things I have left to try are reseating/new SATA cables and a new SATA expansion card. I currently have the SAS9211-8I. My motherboard has 10x onboard SATA and I could get away with a 4xSATA expansion card, so I ordered an ASMedia ASM1064 (IO CREST SI-PEX40156). I figure even if that isn't the issue that card is flexible for use under other circumstances being 1x slot friendly. Also I guess I'll order a bunch of SATA cables to swap out just in case. If that doesnt work I'm out of ideas.
  3. I found a bad stick of memory and made it through 24hrs of MEMTEST w/ no errors, but that doesn't solve the issue of the server rebooting itself while in Unraid. Using two completely seperate sets of PSU/MB/CPU/RAM and I have the same issue. Both sets of hardware make it through MEMTEST fine now that I eliminated the bad stick of RAM. Unraid safe mode is not safe, still reboots randomly there as well. Potential problems (things I haven't tried): SATA cables, LSI SAS card, Hard drives, USB boot drive. Any ideas on how best to troubleshoot? The USB drive checked out fine in my Windows machine, is it worth just trying a new one? I don't have enough SATA slots without the SAS card or I would pull that. I also don't have enough spare cables to try all that as well. Is there anything else that I'm missing?
  4. I have a UPS but disconnected it when I first started having issues. Your reply inspired me to check the PSU cables...the 2x2 motherboard power cable was not connected. 😭 Apparently that is optional unless you need extra juice though? Anyway I connected it.
  5. Appreciate the feedback! No overclocking. I did not have XMP enabled and lowered the RAM speed manually to 2666 from whatever it defaulted at. I did not mess with any timings. I had not run MEMTEST as you may have suspected due to my faulty logic above. I started MEMTEST, and about 5.5 hours later I get an email from my server that it has started a parity check. I guess MEMTEST crashed and the system rebooted? When MEMTEST fails in this fashion (at least I think that means it failed) does that typically imply memory issues? I am not too familiar with digging into RAM issues. I checked into the RAM / MB settings and it was at 1.20v when Crucial recommends 1.35v. I changed that as well as changing all the timings to Crucial's recommended settings and am running MEMTEST again now. Is that a reasonable course of action or should I retard some of the timings while keeping the voltage at recommended in order to gain more stability? Will report back on MEMTEST results.
  6. So, a few weeks ago my server started crashing/rebooting every few minutes to few hours, never lasting more than 6 hours or so at a time. I do not expect it is a hardware issue related to CPU/MB/RAM/Power Supply, as I've taken troubleshooting this as an opportunity to perform some upgrades and these are now new, yet the . If anyone sees any clues as to what may be going on or what to try it would be greatly appreciated. tower-diagnostics-20210131-0726.zip Unraid Version 6.8.3 CPU: Intel Core i7-9700K Coffee Lake 3.6GHz Eight-Core MB: Gigabyte Z390 Aorus Pro WiFi Intel LGA 1151 ATX RAM: Crucial Ballistix Gaming 32GB (2 x 16GB) DDR4-3600 PC4-28800 (not running it anywhere near that speed...2666 I believe right now) PSU: SEASONIC FOCUS+ 750W 80+G FM ATX Hardware items which were not upgraded: LSI Logic SAS9211-8I 8PORT Int 6GB Sata+SAS Pcie 2.0 (appears to have latest firmware installed, v20.00.07.00) Old (fanless) ASUS Video Card for booting prior to setting up iGPU as default, but still installed (2) 1TB SSD cache drives (1) 8TB parity drive (9) data drives (various sizes)
  7. I'm interested in having a similar setup. What hardware are you planning on using in order to route HDMI/USB to the separate rooms?
  8. Yes. This is what I switched to and it has been working well so far. My Unraid box's processor is apparently too old for a Libreelec VM but the pi seems like an acceptable alternative. The advantage of a pi or VM over the headless variant (as was mentioned earlier in the thread) is the ability to easily adjust your scrapers, settings for those scrapers, etc. That is probably possible with the headless version as well but I wouldn't call it easy.
  9. Does the bug exist in the Krypton beta build as well?
  10. Update: Gary I think you were spot on asking about plugins. I went into my config directory on the flash and renamed some old plugin files that i wasn't using anymore from ".plg" to ".plg2". Now the array started right up and went into a parity check. I also now see the format button for the new disk which I will do after the parity check is complete. I haven't quite completed the addition of the drive to my array yet, but I'm going to knock on wood and mark this topic solved. Thanks Gary and Joe for the help.
  11. unRAID Server Pro version: 5.0-rc12a I am running the Subsonic 4.8 plugin on the cache drive. I may have remnants of old addons I don't use anymore. What is the best way to check what is still running? How do I get rid of all plugins/addons? Hmm, I am not seeing a format button anywhere and I cannot start the array, when I try to start the array is when it will "lock up". I tried restarting the server and trying it again, and that's where I am now. Here are some screenshots of where my webgui is now:
  12. I am finishing up a mass upgrade of my server where I've upgraded to the latest RC of 5.0, replaced the 2TB parity drive with a 3TB, added a cache disk, and now I'm trying to add a 3TB data disk to the array. Everything has gone smoothly up to now. I ran preclear on the 3TB data drive and added it to the array while stopped via the webgui, then told it to start the array. Nothing seems to happen and I cannot refresh the webgui. The flash drive is still mounted on the network and I can telnet into the box just fine, but the webgui and array are both down. Syslog is too large to be attached (ask if you need more and I'll find a way), but these lines seem to be relevant: May 19 15:39:28 Tower emhttp: shcmd (53): mkdir /mnt/disk5 May 19 15:39:28 Tower emhttp: shcmd (54): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md5 /mnt/disk5 |& logger May 19 15:39:28 Tower kernel: REISERFS warning (device md5): sh-2021 reiserfs_fill_super: can not find reiserfs on md5 May 19 15:39:28 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md5, May 19 15:39:28 Tower logger: missing codepage or helper program, or other error May 19 15:39:28 Tower logger: In some cases useful info is found in syslog - try May 19 15:39:28 Tower logger: dmesg | tail or so May 19 15:39:28 Tower logger: May 19 15:39:28 Tower emhttp: _shcmd: shcmd (54): exit status: 32 May 19 15:39:28 Tower emhttp: disk5 mount error: 32 Any ideas? I've tried searching for mount error 32 and bad superblock but am coming up with nothing.
  13. I'm in the same boat as you. I tried replacing all the double quotes in kapperz' scripts with ` but that just changes the errors I get.
  14. Thanks for the suggestion, Joe. I'll mess around with it more this weekend.