June 10, 201313 yr Same problem here. Stopped the array and then the whole system hangs. Could not even ping the machine anymore. Had to turn off the machine manually (holding down the power button)
June 11, 201313 yr Looks like this "crash/hang" issue is closely related to the "sync/reiserfs" issue in the other thread. So, limetech says, a new -RC is coming that will fix that. http://lime-technology.com/forum/index.php?topic=27783.msg246595#msg246595 Thanks for updating this thread. I haven't been looking at the other 5.x Issue List threads; just this one and the Announcement forum. Do I understand correctly it might be better to run a 4GB memory limit? I guess 13 continues to be an unlucky number.
June 12, 201313 yr Regardles of the 4GB limit, -rc13 is prone to serious crashes. So stay away from -rc13. Go back to -rc10 or something, and wait for the release of -rc14, which should be very soon. Since I'm running rc13 as we speak, is there a "safe" procedure to get the array stopped and power the system down? In all my testing I've always used the stock web gui not unMenu or /root/powerdown@ (script). Thanks!!
June 12, 201313 yr Thought is was worth confirming that on my system with RC14 this problem has disappeared whereas it happened every time with RC13.
June 12, 201313 yr I had the stop issue almost every time on rc13 - no sign of it in rc14 to mark it up as [sOLVED] for me.
June 12, 201313 yr Author I had the stop issue almost every time on rc13 - no sign of it in rc14 to mark it up as [sOLVED] for me. Thank you for the feedback, much appreciated!
June 12, 201313 yr I am upgrading to Rc14 now. I stopped the array for upgrading and now it hangs again... I have no choice then to turn it off manually. Do i need to worry that something is damaged?
June 12, 201313 yr I am upgrading to Rc14 now. I stopped the array for upgrading and now it hangs again... I have no choice then to turn it off manually. Do i need to worry that something is damaged? http://lime-technology.com/forum/index.php?topic=27785.msg246064#msg246064
June 12, 201313 yr Author I am upgrading to Rc14 now. I stopped the array for upgrading and now it hangs again... I have no choice then to turn it off manually. Do i need to worry that something is damaged? The 'crash' happens during un-mount of the data disks. By this time all data has been 'sync'ed to disk. The worst that can happen is that upon restart the s/w will think there's been an 'unclean' shutdown and start a parity-check. But it's ok to cancel this check because all the data is safe.
June 12, 201313 yr I am upgrading to Rc14 now. I stopped the array for upgrading and now it hangs again... I have no choice then to turn it off manually. Do i need to worry that something is damaged? The 'crash' happens during un-mount of the data disks. By this time all data has been 'sync'ed to disk. The worst that can happen is that upon restart the s/w will think there's been an 'unclean' shutdown and start a parity-check. But it's ok to cancel this check because all the data is safe. Thanks for your reply! The array started on RC14 and is checking parity now. Still a happy Unraid user
June 12, 201313 yr Author I am upgrading to Rc14 now. I stopped the array for upgrading and now it hangs again... I have no choice then to turn it off manually. Do i need to worry that something is damaged? The 'crash' happens during un-mount of the data disks. By this time all data has been 'sync'ed to disk. The worst that can happen is that upon restart the s/w will think there's been an 'unclean' shutdown and start a parity-check. But it's ok to cancel this check because all the data is safe. Thanks for your reply! The array started on RC14 and is checking parity now. Still a happy Unraid user It should be safe to Cancel the parity check, but it's ok to let it run too.
Archived
This topic is now archived and is closed to further replies.