July 22, 201114 yr Just set up a cache drive tonight and it doesn't seem to be working. I am running unRAID 4.7 I pre-cleared the cache drive and added it as the cache drive. It's formatted and ready to roll. I can access it just fine from command line. I have all shares set to use the cache drive and I have even rebooted after setting it up. When I copy anything to the server it goes right into the share and nothing appears on the cache. What am I missing? Thanks!
July 22, 201114 yr When you add stuff it should appear in "the share" - that is what is intended. The question is, where are you looking? If you look at the shares that you have set up then you will not see any difference. It is only if you look at the disks that you will see where the files are actually located. Newly added files should be on the cache drive and will get moved later by the mover script, typically in the small hours of the morning unless you've set things up differently.
July 22, 201114 yr Author As I'm moving stuff I am looking is two spots. In the unRAID web admin, I can see writes are being done to the share drive and not the cache drive. I also am logged in the console and go into the share drive itself and can see that nothing is there. I've read the wiki and I have each share set to use the cache drive. Wasn't sure if I was missing something.
July 23, 201114 yr Author Anyone have any ideas why the cache drive is not functioning correctly? Attached are two screenshots. One is how I have the share set up to use the cache and the other is a shot of what it looks like when I am transferring to the "BluRay" share. You can see that it shows that it's writing directly to the share and not the cache drive.
July 23, 201114 yr Author Ok I DID catch something in SYSLOG. I had scoured it before but never noticed this. Jul 23 12:00:12 BIGHOSS kernel: attempt to access beyond end of device Jul 23 12:00:12 BIGHOSS kernel: sdc1: rw=0, want=976773104, limit=976541632 (Drive related) Jul 23 12:00:12 BIGHOSS kernel: reiserfs_resize: can't read last block SDC is the cache drive. I have precleared this drive and it passed. Any idea why unRAID would be attempting (on an empty drive for no less) to access part of a drive that doesn't exist?!
July 25, 201114 yr Author The problem was I did not have a "minimum" value set on the shares. They were all set at zero. Set each of the shares at a minimum of 20 GIG (20000000) and restarted array. Cache drive working correctly.
July 26, 201114 yr Sorry I did not respond earlier - I was away for a couple of days. Glad it's now working OK for you.
July 26, 201114 yr Ok I DID catch something in SYSLOG. I had scoured it before but never noticed this. Jul 23 12:00:12 BIGHOSS kernel: attempt to access beyond end of device Jul 23 12:00:12 BIGHOSS kernel: sdc1: rw=0, want=976773104, limit=976541632 (Drive related) Jul 23 12:00:12 BIGHOSS kernel: reiserfs_resize: can't read last block SDC is the cache drive. I have precleared this drive and it passed. Any idea why unRAID would be attempting (on an empty drive for no less) to access part of a drive that doesn't exist?! This is an entirely different issue. If it occurred during the pre-clearing, it is one issue... But it appears as if it was when the disk was being formatted with a reiser file-system. It is almost as if it is attempting to determine the file system size? I'd do a file system check on /dev/sdc1 Joe L.
July 26, 201114 yr FYI, the minimum free space not being set won't mean the cache drive is not used. However, without it set you could get a no free space error due to the cache drive being full. Something else was the real issue but apparently it's cleared up now. It could easily have been due to that issue in your syslog. Peter
Archived
This topic is now archived and is closed to further replies.