Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About bonustreats

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So I found out why my cache drive failed! Looks like a cheap molex to SATA connector melted and caught on fire! If any other folks see this, please learn from my mistake and use better connectors - crimped connectors or the SATA power cables are better. I posted on Reddit and a couple people gave some really great information, including a youtube review of another situation eerily similar to mine.
  2. Thanks a lot - I appreciate all the help! I'll mark this one as solved.
  3. Wow - thanks so much for the quick reply! Just out of curiosity, were you able to tell that from the server diagnostics or from the SMART report? If from the SMART report, was it because all the attribute VALUES were 100? OR was it because there were P's in the prefailure warning column? From this post it indicates that V-NAND or 3D TLC are the preferred types of SSD - is that correct? I was also looking and couldn't find a size recommendation for the cache - would 500GB be enough for...pretty much only Plex? This drive looked okay, if that's the case. Thanks so much for all the help and sorry for the billion questions!
  4. Hi Everyone, Yesterday, I noticed Plex was down and went to investigate. I tried rebooting the server, but I saw that the cache drive was unmountable. I found a couple forum posts about how to erase/rebuild the cache drive, but I'm not sure if the drive itself is bad. I ran a SMART report, but I'm not sure if the drive is dead or if it's just behaving weird because it doesn't have a proper file system associated with it. If the drive is okay and I just need to rebuild it, just wanted to confirm that this link would work for this situation. Thanks very much for your time! radagast-diagnostics-20190911-1534.zip radagast-smart-20190911-1130.zip
  5. I've had some issues before with call traces However, I got some new hardware and I'm getting them again. I looked through the log file and didn't see anything that I recognized; at least from previous posts. Are these call trace errors something to be concerned about or is it possible to ignore them? Thanks for your time! radagast-diagnostics-20171013-1713.zip
  6. Yeah, I think I'd be leery about trying a preclear again regardless - seems like you're just begging for trouble. New one should be here tomorrow. Thanks very much for your time and responses! I'll mark this thread as "solved."
  7. Gotcha. Do read failures always equal disk replacement? Is it safe to assume that any time there are errors in that column on the main screen that the drive is bad? Thanks very much!
  8. Here it is, sorry for the delay! Edit: sorry, uploaded the wrong one. radagast-smart-20170817-1237.zip
  9. I don't think I have them enabled; is this the correct way to enable them?: https://wiki.lime-technology.com/Configuration_Tutorial#Install_UnMENU_for_Screen_and_Email_Notifications Extended SMART test is currently running, but I think it said to allow 2 hours per TB. I can just download the results and paste them here, correct? Thanks for responding!
  10. Gotcha, I was guessing/hoping it's something along those lines. Write activity is suspended. Thanks!
  11. Hi Everyone, Setup: 1x4TB WD Red (parity), 2x2TB WD Green, 2x2TB WD Red, 64 GB SSD Cache, 2GB Flash. On the Main tab, under the "Array Devices," unRAID is saying that there are 239,435 errors for the parity disk. However, under the Parity History, the last check completed with 0 errors (run on 14AUG) - please see attached image. Is this something to worry about? I tried searching the forums, but could only really find info about actual parity errors that come up during a check. Diagnostics are also attached. Thanks in advance! radagast-diagnostics-20170816-1803.zip
  12. Meowlrighty, here they are - thanks for the quick reply! radagast-diagnostics-20170301-1835.zip
  13. I got an update to FCP, and ran a rescan - it's now showing the irq 16: nobody cared in the GUI, and it's telling me to post my diagnostics. Will posting the diagnostics now provide any new information compared to the one from Saturday? If so, I'll gladly post them. I haven't seen any particular issues of note; maybe some transfer speed reduction in some cases, but that might be related to the hard drive that's being used for that copy.
  14. I guess it hasn't, because it is now back again; same "irqpoll nobody cared" error. The question now is: is this a serious problem or just some kind of background process that's not going to hurt anything? radagast-diagnostics-20170225-1151.zip
  15. It looks like other people are running into the same issue that I was (call trace errors, at least), and unfortunately, I am again. I got a new (to me) MB, processor, and RAM from a friend of mine early last week. Swapped everything over, and it booted right up, I couldn't quite believe how easy everything was. I went through and updated all my plug-ins, as well as went from 6.2.4 to 6.3.1. I ran into a bit of a snag trying to upgrade to 6.3.2, but figured it wasn't a big deal and would upgrade later. Parity check ran; everything seemed great again. Unfortunately, the same call trace error popped up in Fix Common Problems again. I ran the diagnostics to post this yesterday, but it seemed like the forum was down or something, so they're here now. I didn't do a windiff or anything, but it looks like the exact same error that came up before. I was able to upgrade to 6.3.2 and (so far) the issue hasn't resurfaced, so I'm not sure how useful the diagnostics are. However, that makes me wonder how the heck the same error could crop up with completely different hardware. Could it possibly be my flash drive? radagast-diagnostics-20170220-1301.zip