December 10, 201015 yr I've been using my unRAID Basic for about a month and during that time everything was working great. But recently I've bought Plus license and added two drives: 1TB WD EARS for data and 2,5" 160GB Samsung for cache. I've precleared both of them. I had some errors with EARS (it's 4 months old and used to be part of my other PC) but have been added to the array without any problem. ============================================================================ Dec 10 08:33:40 Tower preclear_disk-diff[16372]: S.M.A.R.T. error count differences detected after pre-clear Dec 10 08:33:40 Tower preclear_disk-diff[16372]: note, some 'raw' values may change, but not be an indication of a problem Dec 10 08:33:40 Tower preclear_disk-diff[16372]: 58c58 Dec 10 08:33:40 Tower preclear_disk-diff[16372]: < 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Dec 10 08:33:40 Tower preclear_disk-diff[16372]: --- Dec 10 08:33:40 Tower preclear_disk-diff[16372]: > 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 Dec 10 08:33:40 Tower preclear_disk-diff[16372]: ============================================================================ But the second drive is troubling me. It used to have 3 or 4 partitions (one swap and rest ext2) and I thought preclear will handle this but it left me with two /dev/sdd and /dev/sdd1. I've stopped my array and in "Devices" tab on //tower picked /dev/sdd because that was the only thing I could choose. But after the array restart nothing really happened. Default unRAID control planel shows that there is a cache drive, but whenever I try to copy something unRAID uses parity and data drive. Now look at those screenshots – in default control panel everything is OK but in unmenu… So what should I do with this /dev/sdd1 ? It's clearly messing up my cache drive. HELP!!!! P.S. – sorry for my english, it's not my native language :-( syslog-2010-12-10.txt
December 10, 201015 yr The /dev/sdd1 is the name of the first partition of your cache drive. It is perfectly normal. It is expected. If it was not there the disk would not have been partitioned. The /dev/sdd name represents the entire cache drive including its first 63 sectors unused by unRAID. It was the correct name to use in the unRAID setup screen. About the only thing you've not done is to enable the use of the cache drive on your individual user-shares. That is done of the shares page in the user-interface. Everything else looks perfectly normal. Until you tell it to use the cache drive for a specific user-share, it will be unused. The cache drive is only used on user-shares. It is not used when copying files to the "disk" shares. One more thing, be sure to set a min free space value on the cache drive configuration. It is in kilobytes. (the field is not labeled) Make it a bit bigger than the largest single file you'll write.
December 10, 201015 yr I do not see any problem with the cache drive on those sreenshots, 1. Green blinking = sleeping 2. sdd = Depends which port you have it hooked to on the MB 3. drive partitions not in protected array = This simply means that your cache drive is not protected by the parity drive which it is not. All looks well with your cache drive from this screen. If your are still concerned you can attach a syslog and someone will look at it and give you guidance.
December 10, 201015 yr Author About the only thing you've not done is to enable the use of the cache drive on your individual user-shares. That is done of the shares page in the user-interface. Everything else looks perfectly normal. Until you tell it to use the cache drive for a specific user-share, it will be unused. I'm stupid, stupid, stupid. Sorry for bothering you and making all the noise :-/ I must've missed this part when digging through the wiki. But you must agree with me that this is not the most intuitive part of the unRAID. Cron syntax for setting up a mover schedule? C'mon... Anyway, thanks for your help!!!
Archived
This topic is now archived and is closed to further replies.