JohnnyT

Members
  • Posts

    53
  • Joined

Converted

  • Gender
    Undisclosed

JohnnyT's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. I ended up just blowing away the cache and starting over. My array seems to be all good, Thanks for the help
  2. Thanks, I have been planning on redoing it anyways so now it's likely a good time.
  3. Here are the current diagnostics. diagnostics-20190209-0925.zip
  4. After some more digging it looks like the cache pool is set to read only. I am looking how to fix that. It is a raid 10 setup.
  5. I got the cables swapped and it is going much faster now 95 MB/sec but I am having another issue. My docker service won't start "Docker Service failed to start." This is what I am seeing in the log "root: truncate: cannot open '/mnt/cache/system/docker/docker.img' for writing: Read-only file system" Any ideas?
  6. I will order it and then go from there. Thanks
  7. I was looking to get this "LSI 9201-16e External SAS HBA" and put most of my drives on that. Would that be a lot better than what I have now? I know there is a firmware update to do what I need.
  8. I will try that when I get home. I had tried moving the new drive to the board itself instead of a card with a new sata cable and that did not change anything. Thanks
  9. I had a drive go bad "disk 5" and swapped it with a new one. The drive I swapped was working fine in a windows box before I put it in and all the drives show passed for smart test. The issue is that when I do a parity rebuild it is very very slow 162.8 KB/sec. I unplugged all the cables and plugged them back in. I also did a reboot. I am not sure what the issue is. Any help would be awesome. diagnostics-20190207-2223.zip
  10. Instead of waiting until I got home since I had to hard boot it anyways I issued the command below at the cmd prompt and it forced an unclean reboot. The machine is back up and doing a parity check. echo b > /proc/sysrq-trigger http://www.linuxjournal.com/content/rebooting-magic-way
  11. Ok, I will hard boot when I get home. :'( I will keep you posted.
  12. How did it get to OOM hmm..... I just logged in, said yeah update, then it downloaded the update so I started array shutdown and BOOM broken. Is this going to require a parity rebuild?
  13. Still just hanging out. I tried a reboot command and nothing.
  14. It should not be doing any heavy IO. I don't have anything special running. No preclears file moves etc. My cache is btrfs raid 10 with 4 drives, not sure it that matters. I issued the restart command and it just ignored it.
  15. I issued powerdown -r and am waiting to see what it does. Hoping I do not have to do another parity check, it takes 36 hours with 8tb drives :-( root@davidFlix:~# powerdown -r Broadcast message from root@davidFlix (pts/1) (Thu Feb 9 10:29:59 2017): The system is going down for reboot NOW!