hansolo77

Members
  • Content Count

    96
  • Joined

  • Last visited

Community Reputation

4 Neutral

1 Follower

About hansolo77

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Just updating. I did have a bit of a nuclear meltdown with my server. Read all about it here: https://forums.unraid.net/topic/107529-recent-troubles-shutting-downrebooting/ Turns out that 100% drive usage I reported a few posts ago was evil. I had my split-level set wrong for one of my shares. Unraid was stuck and being forced to write new files to that drive when it couldn't. Once I figured it out, I tried using Unbalance to move data off the drive and onto others. I thought I understood what was going on but it really started to screw up my Parity. I FIXED the split l
  2. I installed an application called "CA Auto Turbo Write Mode". Is this something I should uninstall? It was a recommended addon from SpaceInvaderOne. Not knowing much about how the file transfer stuff works I just blindly installed it. Could this have created parity corruption as well? I'm grasping at straws here trying to figure out what happened, and have literally disabled EVERYTHING at this point.
  3. Ahhh... so a non-safe shutdown should be ON, but just scheduled checks should be OFF to prevent corruption. Got it! Thanks!
  4. Why would you want it to non-correct? I've seen this a few times.. Wouldn't fixing errors it finds be better than just reporting there are errors?
  5. Cool. I typically have my scheduled checks on the first of the month. Should I maybe do a scheduled check in a week from now to be safe?
  6. I've got about 2.5 hours left on this correcting parity check. 0 errors so far. Should I do another check after this to make sure it's still good, or would you think I'm good as it is (having done a non-correcting check then this correcting check) ?
  7. Yeah go figure. They called me in to work today so I’m not able to directly watch the check but I’ve been looking at it through My Servers off and on. So far so good. About 4.5 hours in and no errors yet (knock on wood).
  8. After passing all the RAM tests, I've ran another non-correcting parity check. It passed as well. Starting a regular check now.
  9. I'm back home now.. it says it's been running for about 3 hours. It's still in pass #2. So probably won't finish 4 passes for another few hours at least. So far, no issues though.
  10. Wow, it took about 20 minutes to get Memtest v9 to be fully up and ready to test. About 3 minutes of black screen, then like 2-3 minutes each line of it's pre-testing detection stuff. But I've got it up and running now. I left everything at default, which is 4 passes with the CPU using all cores in parallel. I'm going to go out to lunch. When I get back, if it's already completed I'll go back into the settings and set the pass to 99 or something so it will continue to run overnight. In a matter of like 2 minutes, it was already reporting like 48% of the first pass was completed lol. So
  11. It should be, I only have 3 PCIe 3.0 slots, one is used by the P2200 video card and the other is the HBA. Prior to all this, I also had that 10 gig nic installed on a slot too. Removing it should have helped the bandwith.
  12. I actually thought that was a little slow, considering the controller is supposed to do 6 GB/s. I dunno, it might be a limitation of the backplane used in the case, or the drives themsevles.
  13. Ok sounds good. I'm off work today so I can spend time working on this. Next days off are Sunday and Monday, then a long stretch of working. Whatever I need to do I'm on it.
  14. Total bandwith is averaging 3.2 GB/s. Each disk is hitting around 155.5 MB/s. When you say use 2 spare disks.. you mean a parity and a data right? If it comes to that, I would actually have to BUY some drives. I've been upgrading my drives to 12tb and have been giving my lower capacity drives to my brother, so I have no spares.
  15. Should I stop my current non-correcting scan then? It's still found 0 errors and I'm pretty confident it's passed the mark where the first error occured yesterday.