Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About nickro8303

  • Rank
    Advanced Member


  • Gender
  • Location

Recent Profile Visitors

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

  1. This is the one I got. https://www.amazon.com/gp/product/B073SBQMCX/ref=ppx_yo_dt_b_asin_title_o09_s00?ie=UTF8&psc=1 So far it's working flawlessly
  2. You can try more sata cables but I can tell you you're wasting your time. I tried several brands and none of them stopped the errors. I replaced the Samsung SSD with WD and the errors stopped. So now I have a 1tb SSD I paid over $100 for working as coaster on my desk. I feel your pain.
  3. Looks like Samsung brand SSD was the issue, replaced it with a WD SSD and I'm not getting any more CRC errors. Thanks for the help guys.
  4. Thanks for the help. I'm at my wit's end with these CRC errors. I've spent months trying to stop them. I'm ordering a WD SSD to see if that will resolve the issue. Sent from my SM-G950U using Tapatalk
  5. I found a work around. I renamed that share, created a new back up share and used krusader to move the data to the new share. Seems to be no issues writing to that share as of now.
  6. I have not tried another brand yet. As far as I can tell though there is no issue with the SSD. When I replaced it the CRC error count picked up where it left off with the old one and continued. I've not seen any failures to read/write from the SSD. Any ideas as to the error I just posted about?
  7. Well I changed the cables out and swapped ports with another drive and as no surprise to me I'm still getting CRC errors on the cache drive. I'm telling you there is no getting rid of these errors. I've literally replaced everything. Any way I connected a spare drive and transferred the Backup data off the cache drive and then back to the array but now I'm getting an error when trying to write to the Backup share. The only way it will let me write to that share is if I enable cache on it. Any ideas? tower-diagnostics-20190606-0002.zip
  8. Any SATA cables you'd recommend or should I should just find the most expensive one Amazon?
  9. I'm not kidding when I say I've literally replaced almost every part on this server over the last few months trying to stop those CRC errors. The only parts that I haven't replaced are the CPU and the RAM modules. I am using those flat red cables (my cable management isn't perfect either) I'll pick up some better cables and try replacing them again but I'm still not sure that this is causing the mover to error out on those files.
  10. I believe it is, but the SSD is not plugged in to the controller. Would it still causing these errors even though it's not on those ports?
  11. The mover works fine with other shares, this is the only one that it is giving errors for.
  12. I've replaced the cables several times. I replaced the motherboard, the power supply, the controller and even the SSD. Those CRC errors won't go away. The cache disk isn't plugged in to the controller it's plugged in to the motherboard.
  13. Thanks for the reply, I've already checked the settings on that share several times to make sure it was set to use the cache. I ran the fix common problems plugin but it didn't find anything.
  14. Trying to free up space on my cache and the mover isn't moving some files off. I turned on logging and it shows "error: Invalid argument" on multiple files. Somethings I've tried to resolve this issue: 1. Stop all dockers and run mover. 2. Set new docker safe permissions and run mover 3. Installed the Open Files plugin and checked it for the files the syslog listed but it doesn't show any in use. Not sure what is causing this error I thought it might be from the backups running but it continues to error even though I stopped the back ups. Any ideas as to what is causing this? tower-diagnostics-20190603-1602.zip
  15. Well I got impatient and rebooted and it seems to have resolved the issue. I found another forum post regarding this issue and the guy said it was his power supply not sure if that could be it or not. tower-diagnostics-20190525-2159.zip