iwens

I upgraded to this version from beta 11. I can confirm that the short freeze in video playback when spinning up other drives is solved in this version. I checked the spin-up groups and it seems every drive on my rig is on his own host. So my problem before was not related to the spinning up of multiple harddisks on the same controller. Anyway's great job, as this was the last problem i had with unraid. Everything seems to work flawless now.

What you are experiencing is not an unRAID problem, but a CLIENT SIDE OS problem. I've seen this exist even when playing media files from a WinOS server to a WinOS client. I do not believe this is a client side os problem, as i also see it on my popcorn hour. The thing is i use 4 gig in my unraid server so let's say i use 1 gig as cache this will mean even after all drives are for some reason in accessible there will be enough data in cache to feed my popcorn hour for at least 15 min on a standard sd stream. I know this is only theoretically but the fact remains that when unraid spins up a drive the complete unraid server is unresponsive, on a spin up of a drive my media player or any other source cannot receive any data from the server. Now the popcorn hour has a very limited cache build in, so it may survive maybe a 1 sec freeze but it seems a 2 sec data break will confuse the player enough to get a stutter in the playout. So i am interested why the unraid server seems to freeze completely when a drive is spun up, to be clear it could be a hardware/os limit and maybe this can not be avoided. That will be a disappointment as then i will need to avoid any write actions to the server when i am watching on my popcorn hour. Or spin-up all drives when i read data from my video share which will mean increased spin-up and down actions on drive's.

Well let me clarify, my doughter watched a dvd this is a 8mbit stream and at the same time i took out my laptop and wanted to clean up some stuff on my server. With every copy action i did to different disks there was a short stutter, but after activating 3 shares by copying things to different shares the c200 gave up and frooze completely. On my normal windows nas i never experienced these problems i did let windows put the non used drives to sleep, and i never ever experienced a drop or stutter in a sd stream or hd stream when a drive got spun up ,especialy since sd is only 8mbit/s. So apperently as the machine has 4gig of memory the whole unraid server must be shortly unresponsive as a disk is spun up, in my case all the spin up drives where on the same controller. Also as i experienced the stutter 4 times it seems to happen after every single spin up. i do not know what httpc setup u have for your own, but if it's a windows based one u indeed probably will not see a stutter as the huge cache these machine's use will need a huge break in a data stream before u will notice it. In my case when a drive will spin up the server will be unresponsive for about 2-3 seconds in that time i can do nothing to the server in windows or on my popcorn and 2-3 seconds is to much for the small cache my popcorn hour c200 has or for that matter any hardware based media player. Maybe it's already explained but why does the unraid server become completely unresponisve after every drive spin-up ?

I can confirm that spinning up drives will interupt read, even when i watch a simple dvd bit rate max 12 Mbit/s the dvd get's interupted on my popcorn hour c200. I have 4 gig mem in the unraid computer so i was rather suprised. Hope this can be solved as this makes the server rather unusable.

I am using unmenu with the latest beta 4.5b8 and 3 times it happened now that it stopped working with th efollowing error: Nov 12 09:39:41 Tower emhttp: shcmd (242): /etc/rc.d/rc.nfsd restart | logger Nov 12 09:50:46 Tower unmenu[1441]: gawk: ./08-unmenu-array_mgmt.awk:115: warning: escape sequence `\'' treated as plain `'' Nov 12 10:09:20 Tower unmenu[1441]: awk: ./unmenu.awk:579: fatal: print to "/inet/tcp/8080/0/0" failed (Connection reset by peer) I do not now how to restart it after this, but the page at port 8080 cannot be loaded anymore after this error. Is there a way to restart unmenu ? Telnet acces and the main unraid web interface keeps working fine