Jump to content

Wayne66

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Wayne66

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I had the same issue, but reverting back to 1.17.0.1841 resolved the issue. No loss of functionality. Just have to see notifications that there is an update, which of course you don't want to do.
  2. OK, Thanks! I changed the cron job to weekly, so hopefully that solved that issue. Guess I can disregard the error. Thanks for your help.
  3. Fix common problems is reporting a HW error and I have no idea what might be wrong. Please review my diagnostics file. Thanks in advance. tower-diagnostics-20190811-1624.zip
  4. I just bought 2 - 10tb enterprise drives to replace my existing dual parity. I was thinking that the 7200rpm drives would improve parity checks and ultimately write speed, probably more so as the data drives which are 5400 now get replaced with faster drives. So I posted about this on another forum and the general consensus is that I wouldn't see any real performance improvements and that I should just leave the 5400 drives in as parity and add as data drives. It's obviously time consuming to change the parity drives. Is it worth it?
  5. Thanks for the reply. Sorry I'm a complete noob when it comes to linux. I'm guessing it is a command to issue on terminal. How do I initiate a memtest? Thanks!
  6. This morning I noticed that Fix Common Problems is reporting a hardware error. I don't notice any issue, but it recommended that I install mcelog and post my diagnostics to the forum. I'm hoping someone can shed light on what it found because I have no clue what is going wrong. tower-diagnostics-20190406-1031.zip
  7. First off, thanks for creating this. The data it provides is fantastic. So now here's my issue. I installed an LSI 9211 SAS controller flashed to IT mode. I have one drive connected to it right now and the drive is not assigned to the array yet. When I run the "Benchmark drives" (or the individual drive) it finished the scan, but then reports the speed gap is too large and retries. I've let it go up to 100 retries before aborting. I have tried checking the box to "disable speed gap detection" but it seems to have no affect. I'm using Google Chrome. I read that the speed gap is supposed to increase by 5 MB each try, but mine stays the same (45 MB). Am I doing something wrong? SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]: Scanning sdf at 8 TB (100%) - Speed Gap of 79.95 MB (max allowed is 45 MB), retrying (22)
  8. I have the 9/29/2018 version running and then did the 2018.10.06c update. Not the vnstat is no longer running. I did go to the plugin settings and tried to click "Start". No luck.