February 10, 201115 yr Hi , I'm very new to all this , I've build 3 2TB hard drives box with unraid beta 5 free version First install took 11 hours of making the parity / disk1 / disk2 work. I've manually installed sabnzbd and downloaded 2gb movie to disk1. When I reboot the server , It once again want to do data-rebuild and claims it will take around 560 minutes. Why does it take so long ? How my files are protected with data-rebuild , or unprotected if I'll cancel it ? How will adding cache drive (and upgrading to plus license) will makes life better ? While data rebuild , is there a problem to share NFS movies / keep downloading with sabnzbd ? Thank you all for your replies and patience for newbi .
February 10, 201115 yr Hi , I'm very new to all this , I've build 3 2TB hard drives box with unraid beta 5 free version First install took 11 hours of making the parity / disk1 / disk2 work. I've manually installed sabnzbd and downloaded 2gb movie to disk1. When I reboot the server , It once again want to do data-rebuild and claims it will take around 560 minutes. Why does it take so long ? How my files are protected with data-rebuild , or unprotected if I'll cancel it ? How will adding cache drive (and upgrading to plus license) will makes life better ? While data rebuild , is there a problem to share NFS movies / keep downloading with sabnzbd ? Thank you all for your replies and patience for newbi . Step 1. attach a system log to your next post. It is critical to giving you the correct advice. For the array to want to re-build a disk it must somehow think the disk has changed since you shut down last. Did you change the disk in any way? Did you un-plug the USB drive so it would not be able to see the old configuration? What does the web management console show as indicators for the disks? Tell us the actions you performed when shutting down and rebooting so we do not have to guess. Your use of the 5.0beta is probably not the best for a newbie, but which exact "beta" are you using? There are known issues with them... You really should be using 4.7 until the beta version of 5.0 get a bit further along. If the software is asking to perform a data-rebuild it indicates you are currently simulating a failed disk. You are currently being "protected" by parity but would not be if another disk were to fail. Let the re-construction continue if it has started. And post the system log. Instructions (I think) are in the sticky at the top of this forum.
February 10, 201115 yr Author Hi , I'm very new to all this , I've build 3 2TB hard drives box with unraid beta 5 free version First install took 11 hours of making the parity / disk1 / disk2 work. I've manually installed sabnzbd and downloaded 2gb movie to disk1. When I reboot the server , It once again want to do data-rebuild and claims it will take around 560 minutes. Why does it take so long ? How my files are protected with data-rebuild , or unprotected if I'll cancel it ? How will adding cache drive (and upgrading to plus license) will makes life better ? While data rebuild , is there a problem to share NFS movies / keep downloading with sabnzbd ? Thank you all for your replies and patience for newbi . Step 1. attach a system log to your next post. It is critical to giving you the correct advice. For the array to want to re-build a disk it must somehow think the disk has changed since you shut down last. Did you change the disk in any way? Did you un-plug the USB drive so it would not be able to see the old configuration? What does the web management console show as indicators for the disks? Tell us the actions you performed when shutting down and rebooting so we do not have to guess. Your use of the 5.0beta is probably not the best for a newbie, but which exact "beta" are you using? There are known issues with them... You really should be using 4.7 until the beta version of 5.0 get a bit further along. If the software is asking to perform a data-rebuild it indicates you are currently simulating a failed disk. You are currently being "protected" by parity but would not be if another disk were to fail. Let the re-construction continue if it has started. And post the system log. Instructions (I think) are in the sticky at the top of this forum. Attached syslog. What I tried to do after the first installation is to install sabnzbd and sickbeard using the instructions here : http://www.lockstockmods.net/2010/06/03/unraid-with-sabnzbd-and-sickbeard/ then i tried to edit my go script (but i dont have cache drive , so changed everything to disk1 instead of cache) I didn't succeed to make things work with the go script , but only when I manually ran the installpkg and python command. I reboot the server and took out the flash drive to update the go script on my pc (so I could copy paste into the file , midnight commander through telnet doesn't let me copy paste) and then I saw the parity error , only when i deleted my changed to the go script , all was ok (but disk1 needs data-rebuild now). Will the disks need data rebuild every time I'll download something new ?! syslog.txt
February 10, 201115 yr All is not OK if disk1 needed to rebuild. That should not happen. It sounds like you are having trouble with unRAID recognizing and properly assigning the disks each time you boot. Others using the 5.0beta series users/testers could possibly comment on fixes. I would recommend you stick to using 4.7 which is a solid release and not a beta test release. Peter
February 11, 201115 yr Author All is not OK if disk1 needed to rebuild. That should not happen. It sounds like you are having trouble with unRAID recognizing and properly assigning the disks each time you boot. Others using the 5.0beta series users/testers could possibly comment on fixes. I would recommend you stick to using 4.7 which is a solid release and not a beta test release. Peter Hi , I've dl'ed 4.7 , backed up up 5 beta on the flash drive and copied all 4.7 files to it. Booted the server , unRAID os came up with no drives set so I manually chose which drive was parity , disk1 , disk2 and now it does parity sync which again will take 600 minutes. Did I do it right ? (downgrading to 4.7)
February 11, 201115 yr There was a way to avoid rebuilding parity, but it is too late. Just let it build.
February 11, 201115 yr Author There was a way to avoid rebuilding parity, but it is too late. Just let it build. Thats what I'm doing . Patience is a virtue. While it builds , I can keep downloading files and install addons on the unRAID ,right ?!
February 11, 201115 yr Downloading is fine, but some of the addons take some effort to get working 100%. You won't be able to reboot while the parity build is running without restarting the parity build. Personally I'd let the build finish before installing addons.
February 11, 201115 yr Downloading is fine, but some of the addons take some effort to get working 100%. You won't be able to reboot while the parity build is running without restarting the parity build. Personally I'd let the build finish before installing addons. I'd let the parity build complete, then run a parity Check to make sure the data written is readable. Only then are you protected. Until you perform the "Check" you are only guessing the data was written to the parity drive correctly. (there have been drives that failed when written to, but give no external indication of the error until later read)
February 11, 201115 yr Author Downloading is fine, but some of the addons take some effort to get working 100%. You won't be able to reboot while the parity build is running without restarting the parity build. Personally I'd let the build finish before installing addons. I'd let the parity build complete, then run a parity Check to make sure the data written is readable. Only then are you protected. Until you perform the "Check" you are only guessing the data was written to the parity drive correctly. (there have been drives that failed when written to, but give no external indication of the error until later read) Will do.
February 11, 201115 yr Just to note, when you say you reboot, make sure you do so by using the web management to stop the array and then use the reboot or shutdown buttons that appear. Hitting the power or typing "reboot" on the command line will cause another parity check. Peter
February 11, 201115 yr Author Hitting the power or typing "reboot" on the command line will cause another parity check. Peter That what I was doing... foolish me.
Archived
This topic is now archived and is closed to further replies.