Jump to content

rxnelson

Members
  • Content Count

    147
  • Joined

  • Last visited

Community Reputation

1 Neutral

About rxnelson

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. Looks like it made it a week and a half or so. I put the card in another slot and rigged a fan to blow on it. Time for a new card? towertest-diagnostics-20190923-0332 (1).zip
  2. Funny enough just before the issues started. I removed a secondary video card and did some housecleaning in the case. I thought maybe reseating everything would work because maybe I bumped something. Too many variables to really know. I guess I just have to eliminate one by one.
  3. It’s in an intel 4U tower style case similar to this one. http:// https://rover.ebay.com/rover/0/0/0?mpre=https%3A%2F%2Fwww.ebay.com%2Fulk%2Fitm%2F193042042853 I thought that bottom fan would provide airflow and haven’t had issues since I put it together in what looks like 2016 according to purchase history. I guess that is why I’m still not sure if heat or bad card or maybe heat finally killed the card. I’ll see if I can rig something up closer to the card. For a dual PSU system it has a very small amount of molex and sata power. I’m assuming the card doesn’t have any “live” reading of temps once in Unraid or you guys would have already mentioned it.
  4. Ok. Thanks. I was just wondering if you’d come back and say the dell cards are known to overheat or something like that. Anyway, I put the card in a different slot and the parity drive is resynching now. I’ll let that finish and wait a few more days to see if the card acts up again I guess. Thanks again
  5. I didn’t try another PCIe slot but I did reseat the card. I can try that after rebuild. If you don’t care to say what are you using and what firmware version? I believe I have the Dell cards that I flashed. Thanks
  6. It rebuilt disk 1 and survived for about a day then it looks like it the card stopped responding again and disabled the disk. Logs attached. Card going bad? The machine has been stable for a couple years prior to this. Next steps? towertest-diagnostics-20190908-0412.zip
  7. So if I am reading this correctly I can install CA User scripts and follow the directions to put this in? #!/bin/bash mkdir /tmp/PlexRamScratch mount -t tmpfs -o size=4g tmpfs /tmp/PlexRamScratch This will run at boot before the docker starts or do I have to do something else? I saw some old posts about setting permissions for the ramdisk as well. It isn't necessary in this case? I have 128 gigs of memory and am dabbling in with the live TV stuff in Plex. Any recommendations on how much to allocate?
  8. Thanks for all the help. I got busy the last few days but I did as you said and disk 1 is rebuilding.
  9. New diagnostic. Should I remove the disks one at a time and try to rebuild them? towertest-diagnostics-20190904-0240.zip
  10. Also maybe a stupid question but should I just disable the drives and readd them like I did before?
  11. No. I’ve left it sit. I didn’t want to do anything before I was told.
  12. I get what you are saying but I can click on the disks and see the contents (except disk 1 it says 0 objects). It doesn't say anything is emulated. That diagnostics file was the latest I had.
  13. Is there a way to tell that from a command or do I need to physically trace back the connections? Also, could that be old log info? It looks like they are connected in the gui right now. Maybe you are saying that is what happened in the past?
  14. It looks like diagnostics has a good log file in it. towertest-diagnostics-20190903-2336.zip
  15. I had an instance about 2 weeks ago where I thought that Plex filled up my cache drive and freaked the system out creating a bunch of errors on disk 1 and parity 1. I disabled both drives one at a time and let them rebuild. Unraid seemed happy and the drives passed a long smart test. Fast forward to the weekend and I'm not sure what happened as the system really wasn't in use but I have a full log, tons of errors during the monthly parity check, and those two drives are disabled again. I tried to pull the log from the tools menu in the gui but it looks blank. Anything I can do to assist the diagnosis before I reboot? Thanks.