January 28, 201313 yr My array runs perfectly fine as long as there is no cache operations. After every unRAID system update I try it again and I just have to start totally over. I moved about 100GB of data last night and then manually initialized the mover. This morning when I got up the entire system was locked up. I couldn't access it via telnet, unmenu, or directly through the console. Not a good way to start my morning. I had no choice but to hard boot. After doing a parity check, everything written is gone. It's not on the array and it's not on the cache drive. Just gone. I've removed the cache drive and will never try to use it again. It's just never a viable option for me. To my question, when I do a monthly write to my array, what is the fastest way to write? My goal is to not clog up my network and my machine for hours on end, I want it on the array as fast as possible and let the array to it's job. If I were to disable the parity drive for the fastest write speed and then re-enable and do a parity check; would that be my best option?
January 28, 201313 yr My array runs perfectly fine as long as there is no cache operations. After every unRAID system update I try it again and I just have to start totally over. I moved about 100GB of data last night and then manually initialized the mover. This morning when I got up the entire system was locked up. I couldn't access it via telnet, unmenu, or directly through the console. Not a good way to start my morning. I had no choice but to hard boot. After doing a parity check, everything written is gone. It's not on the array and it's not on the cache drive. Just gone. If it is "gone" then it sounds like you were writing to RAM and not to the cache drive. That would easily use up all your ram and cause the server to crash. The other possibility is you are filling the syslog with error messages, and running out of ram that way. Regardless of why, you need to perform some tests to determine what is happening. You might have some marginal hardware. Have you looked in the syslog? (you elected to not post one for analysis, so perhaps you don't want help there) You would want to look at in the middle of one of your transfers, and as the "mover" starts its process. I've removed the cache drive and will never try to use it again. It's just never a viable option for me. Your choice, I've never needed one. To my question, when I do a monthly write to my array, what is the fastest way to write? My goal is to not clog up my network and my machine for hours on end, I want it on the array as fast as possible and let the array to it's job. If I were to disable the parity drive for the fastest write speed and then re-enable and do a parity check; would that be my best option? There is no "fast" way. unRAID is a poor solution for you if all you are looking for is speed. Your best bet, get some modern high speed (7200 RPM) 3TB disks, leave parity enabled. People report write speeds of 25MB/s and some much higher. 100GB of data will take a while to move on any network. at 25MB/s it will take 4 seconds per 100MB, 40 seconds per 1GB. 40,000 seconds for 100GB. (11 hours) Joe L.
January 28, 201313 yr 100GB of data will take a while to move on any network. at 25MB/s it will take 4 seconds per 100MB, 40 seconds per 1GB. 40,000 seconds for 100GB. (11 hours) Joe L. Nope. (100 GB) / (25 (MB / s)) = 1.13777778 hours
January 28, 201313 yr 100GB of data will take a while to move on any network. at 25MB/s it will take 4 seconds per 100MB, 40 seconds per 1GB. 40,000 seconds for 100GB. (11 hours) Joe L. Nope. (100 GB) / (25 (MB / s)) = 1.13777778 hours OOps... at 25MB/s it will take 4 seconds per 100MB, 40 seconds per 1GB. 4,000 seconds for 100GB. (1.1 hours) It helps if I post AFTER my first cup of coffee and have engaged my brain. 40 x 100 = 4,000, not 40,000. 100GB = 102400 MB 102400 MB / 25 = 68.2666666667 68.2666666667 / 60 minutes-per-hour = 1.13777778 hours See... . plenty fast enough... 8) even with a parity drive.
January 28, 201313 yr It seems odd you're having so many issues yet for most everyone else with a cache drive it works just fine. Files going missing like you describe is very odd considering the mover apparently uses rsync which verifies each files get moved properly. I'd start investigating your methods of using the server first and then your hardware second to try and figure out what is happening.
Archived
This topic is now archived and is closed to further replies.