weezzer008

Members
  • Posts

    16
  • Joined

  • Last visited

Recent Profile Visitors

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

weezzer008's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Doing that now.... Thank you for all your help! it is truly appreciated!
  2. Ok, so I found the bad stick of RAM and now am running with the remaining good 3 sticks (12GB). However now I still have the problem of my cache pool being either read-only or full. It is not reporting as full and I'm unsure of how to get it out of this state. Balances fail due to being read-only and the docker service "failed to start" even after deleting the docker.img and rebooting. Any ideas where to go from here? htpc-diagnostics-20220302-0855.zip
  3. Ok so already encountered some errors. Is there a way to determine which stick out of 4 this error is on? and is as simple as removing the bad ram and rebooting?
  4. Running Memtest now. Will run for the rest of the day and report back. Thank you for your quick response JorgeB.
  5. A couple days ago I started having issues with my Docker containers not working properly. I saw on the dashboard that Memory “Log” was at 100%. I rebooted and it resolved the issues for a while but it quickly returned. I looked online and found some people who have had luck deleting the docker image file and recreating. I tried that too but it didn’t help. I saw other posts stating to “re-balance” the cache pool but when I try to, it says my cache is “read-only” or full. I also saw that error. My cache seems to be reporting that it is not full but perhaps this is not the case? I have two SSD’s in a cache pool, 1.) Samsung 250GB and 2.) OCZ 128GB. I think my issue is somewhere in the cache but I’m not sure. Is anyone able to help? Diagnostic attached. htpc-diagnostics-20220228-1201.zip
  6. Ah...Not sure How I missed that. Awesome! Thank you! Now just hopefully this doesn't happen again.... not sure what happened to begin with.
  7. Hi Johnnie, I appreciate all of your help. In the link you sent it states: "RAID0: requires 2 device, best performance, no redundancy, if used with different size devices only 2 x capacity of smallest device will be available, even if reported space is larger." This is the only option I can see available to me with my two different sized SSD's. I would not be able to use full capacity at 384GB with this would I?
  8. Now the problem is I completely forgot how to set that up. Everything I read online states If I put these two different sized drives into the pool as raid0, it will be double the size of the smallest drive...Which would be 256GB....Meaning I would loose 128GB.
  9. Am I correct in my belief that using these two drives in raid 0 was only coming out to 256GB? which would mean I was wasting almost 128GB of SSD space?
  10. Ok, That still didn't work. So This is what I'm doing now: - use "New Config" to reset cache assignments - Using only my 256GB SDD in cache - Using the 128GB SSD as an unassigned device (Wasn't getting more cache space from putting these in raid 0 correct?) Parity is rebuilding but other than that everything seems to be working well.
  11. So I went through it again, and it seems to be working now. the blkdiscard command on the second SSD finishes instantly making me think it is not working. The cache pool has the total space available as the correct SUM of the two drives, even though More drive space is being used than should be. Are you able to confirm that both SSD's are correctly integrated into the pool? htpc-diagnostics-20200131-0828.zip
  12. So I went through this process and deleted my "docker.img" from the docker settings. Now when I try to re-create my dockers I get the same type of error that the file system is read only. Error: open /var/lib/docker/tmp/GetImageBlob648374300: read-only file system Any ideas? htpc-diagnostics-20200130-1527.zip
  13. Ok thank you for your reply. What is the best way to formatt the cache pool?
  14. Here you go. Thanks! htpc-diagnostics-20200130-1309.zip
  15. I awoke this morning to my dockers failing to load and it seems that the primary drive of my cache pool has been forced into "Read-Only" mode. I wouldn't be surprised if this drive is finally dying, (older OCZ SSD 128GB) but I'm at a loss for what to do. the health checks on the drive all fail to run as well as the "Scrub" option. I'm of the belief I will need to purchase another SSD, however I'm not sure the proper process to install it without loosing my docker's and VM's. I've attached the log file associated with the drive in question. Is anyone able to help? Unraid_cacheDrive.txt