Jump to content

willdouglas

Members
  • Content Count

    25
  • Joined

  • Last visited

Everything posted by willdouglas

  1. Had some life events get in the way of my troubleshooting. Memtest wouldn't boot for me from the unraid install, so I pulled the newest version and ran that. It took a few days but came out perfect, four passes and no errors. I've moved on to full rebuild mode in the interest of having a working system in place during coronavirus lockdown. New bootable USB drive with a fresh image of 6.8.3. Currently pre-clearing all my disks because I was seeing errors on one of the new drives already.
  2. Ran the file system check and let it correct the errors, the outcome wasn't pretty. I did upgrade RAM in this host a few weeks before the first failure. Leaving memtest running overnight and tracking down some spare DIMMs. I also checked the drives that have been pulled in a different machine, they're definitely a mixture of dead/dying/busted. One refuses to spin up at all and the other two throw tons of errors but will allow me to view the directory structure before refusing to function beyond that.
  3. If there's a low effort way to get the shares back to normal I'll give it a shot, but I think I can pull from the individual drives via SCP and get a decent transfer rate. I'll sort it out on the other side.
  4. Rebuild completed, disk check/repair run, user shares available but several show empty when navigated over the network. I can browse the filesystem, for instance my TV directory, from the webgui but actually attempting to access over the network displays an empty directory. cadance-diagnostics-20200308-0943.zip
  5. Will wait for rebuild completion, run file system checks, and report back. Thanks!
  6. Had some drives fail, luckily within warranty. First drive was replaced with a "hot spare" drive I leave in the server but don't allocate. During rebuild another drive failed but rebuild completed. First drive was removed and replaced, and I tried to begin the next rebuild but I observed some funny behavior that persisted through reboots. The array had difficulty starting and stopping, missing VMs, missing docker apps. Issues cleared when I pulled the second failed disk out. I also moved all drives to the SATA ports since all the failures were on the same SAS breakout. The rebuild completed, but another drive reported as bad during the juggling. I'm pretty sure I went beyond my failure limit at some point during the rebuilds and all the swapping around, my disk space utilization has dropped about 5TB from start to finish. My array is currently reporting good drive health but it's also reporting no user shares and when I try to start VMs I'm getting an error. I thought I might be able to add the shares back, but when I try nothing happens and "starting services..." is added to the status at the bottom of the GUI. I'm not looking to get back to where I was, more just wondering how to make the media I can recover available so it can be pulled off. Ideally I'd like to recover what I can and re-provision the whole setup from scratch. There have been some hardware and configuration changes to the machine through it's life and I'm sure I've got a nice pile of mistakes stacked precariously on top of other mistakes. I don't want to make things worse for myself during the recovery process. There is nothing I care about on this array, but there is a lot of stuff so I'd like to save time/bandwidth/admin work if possible. cadance-diagnostics-20200307-1231.zip
  7. Ten days of uptime. I'm comfortable leaving well enough alone. End thread.
  8. Figured I should follow up with this. I never figured out what the issue was or managed to pull usable info out of a crash. I replaced the USB drive with a newer drive, and with a fresh install only installed the official plex docker. All other apps are running in an unraid VM until I feel like investing time in this again.
  9. Alright, cutting down docker apps to sonarr, nzbget, and plex I've somehow extended average up-time to three or four days, and have a new symptom to add. If I catch the lockup after network access drops, but before hangcheck value past margin messages start appearing there is limited access to the box at console. I wasn't able to log in, but I was able to get it to respond to key presses at what felt like a fifteen to twenty second delay. I ended up rebooting rather than fight with it because there was a request for Plex access from family but I'll re-enable logging and see if I can catch it quickly enough. I do have an impi controller onboard, so I'll see if I can get into the box next time to poke around and maybe dump logs to another box for easy viewing.
  10. I'm going to, possibly unfairly, blame the binhex-radarr plugin. They did warn me, it said it was under active development but I've been using radarr for a while, how bad could it be?! I'm at just over 48 hours of uptime and going to put the box back in the crawlspace where it lives and continue without radarr for now, maybe run it on another host for the time being.
  11. Fail! Made it somewhere around nineteen hours I think. Going to leave Radarr disabled and see how long of an up time counter I can accrue. EDIT, forgot to mention I upgraded to 6.5.0 before starting radarr so I was on a fresh reboot and upgrade, possibly hosing my troubleshooting by changing a variable. It seemed so innocent, so safe! Uptime was great! FCPsyslog_tail.txt cadence-diagnostics-20180314-0542.zip
  12. 72 hours uptime. Enabled deluge, nzbget and sonarr all at the same time yesterday and triggered a couple searches to see if they were playing nicely together. No lockups in the last 24 hours. At this point I only have radarr and plexpy to re-enable and I'm kinda tempted to just not enable them, but I will forge ahead and enable radarr.
  13. I've broken 48 hours of uptime. Feel safe ruling out plex at this point. Time for the next app!
  14. I'm breaking records over here with twenty hours of uptime without a lockup. Once I hit 24 hours I'll start the first app, probably plex, then 24 hours later start another, and so on. I thought I had them all installed and running before the lockups started but might not have. I did update library shares before the crashes start so maybe it'll be tied to plex usage as people started adding load.
  15. I'm not seeing anything pop up using stress or memory testers. I also updated my post with the correct SAS controller, it's an LSI 9211-8i. I also verified it has the most recent IT firmware flashed - 20.00.07.00-IT, nothing newer on their site anyway. Going to start trying permutations of apps I guess. I feel like hardware is good, only new purchases for this were drives and controller, server previously did duty as a virtualization server for training so if it was going to flake I hope I'd have seen it previously impacting VMs.
  16. Have you observed any output at console when the system locks up? I'm seeing a similar issue and am also elbow deep in hardware tests that seem to pass with flying colors.
  17. Logs from second lockup. cadence-diagnostics-20180310-0257.zip FCPsyslog_tail.txt
  18. Daily lockup achieved, logs captured and attached. cadence-diagnostics-20180309-1217.zip FCPsyslog_tail.txt
  19. I will do that now. 24 hours of memory tests haven't revealed any issues so it's time for the next thing.
  20. Too impatient to let this thing freak out while I'm away repeatedly. Feels like flirting with disaster. Redid PSU calcs to make sure I'm not under powering and I have quite a bit of leeway. Removed tuner card since it wasn't being used anyway, flashed BIOS(probably same revision, forgot to check), currently running Memtest to verify RAM and looking for some good burn in software.
  21. Locked up without parity drive. Re-adding it to the array. After parity finishes I'll shutdown clean and start removing things. TBC.
  22. Hi All, OS Version: 6.4.1 Hardware: Supermicro X9-DRL-iF 2 x Xeon E5-2670 8 x 8GB DDR3 6 x 8TB HGST, 5 data, 1 parity. 2 x 240GB Kingston SSD, using as Cache pool. 1 x Kingston Data Traveler 8GB for boot. 1 x HAUPPAUGE WinTV-quadHD(haven't tried to use it yet) 1 x LSI 9211-8i (works great!) 1x Mellanox 10G Network Card(works great!) Installed Apps: Binhex Plex Binhex Deluge Binhex nzbget Binhex Sonarr Binhex Radarr Linuxserver plexpy CA Fix common problems - reports the unclean shutdowns afterward but other than that just wants me to install trim plugin and docker update check. System locking up solid roughly once per day over the last two days, both times at some point mid day when the server should be seeing little to no utilization. The system has only been up for eight days, and I didn't see any lockups until mid day seven, then again mid day eight. Pulled the tower from it's home in the crawlspace after first lockup and moved it to a table with a monitor so I could observe but haven't seen anything out of the ordinary. It's not overheating, and as far as I can remember the only change I made was specifying the parity drive and allowing it to build after the rsync copy from my old server completed. There were single smart warnings I don't recall specifically on two of the 8tb drives when I first installed them but I acknowledged them and haven't seen anything since that point. Rolled back to no parity to see if it will lock up tomorrow. Could attach some logs if anything interesting happens without a lockup, but no errors present besides the quoted output dumped to console and present when I get to the locked up box.
  23. Any repeat or remediation on this behavior? I just got my machine set up and have seen this happen twice in the past two days. I'm running similar gear, same procs, same memory total, and a slightly different board(X9DRL-IF).