Confirmed the problem, MythTV was trying to access the NAS storage because it has the largest free space, which I had it set as (Read only), I tried to use "Storage group" from Backend setup, no luckI tried to edit "/usr/pluto/bin/mythtv_setup.pl", no luck I couldn't find a way in MythWeb.

Does anyone know how to force MythTV to use specific hard drive for Live TV and Storage???

Mathieu,I'm using #23165 snapshot, I have 4 MDs, 2 of them were OK and 2 did not have the "Media Scenario" even deleting the MD and recreating them today did not work, so I looked into the "My Scenarios" from WebAdmin and found 2 rooms had duplicates so I went to the 2 MDs that didn't have "Media Scenario" and changed them to a new room and reload/Regenrate All, then I've got all MDs with all Scenarios.

From my experience you can not add squeezbox to a room that already has core/MD, you need to select a room that is not in use example "Garage" then you can go to the floorplan and place the squeezebox Icon.

After doing more tests, I found out that playing and transfering Audio and DVD between Mds/Core or playing them at the same time there is no issues.BUT if you transfer "WMV or MPEG" videos between MDs/Core then it fails you get no audio and black screen.

MythTV is not playing LiveTV, the reason I believe is the way I have setup my storage, I have 2 HD on the Core and a NAS, I blocked first HD and the NAS from automatic access by LinuxMCE, I want only the second drive to be use by LinuxMCE, so now mythTV is not playing Live TV because I believe is trying to access the first drive, can someone show me how to setup MythTV to use the second drive only (sdb1), I looked at this post but I could not find anything on how to set up the storage by MythWeb per Merkur2k reply http://forum.linuxmce.org/index.php?topic=8498.msg66816#msg66816I attached my Mythweb storage setup.

I just found out, when installing a zwave motion sensor "ZIR000" in snapshot #23165, using Sarah, two "Generic Sensors" get created one under (Zwave=>Zwave embedded security interf) which is OK, and a second one under (Core) which is not OK, and causing after reload to get "Orbiter cannot register with the router. Please try again later", I attached a snapshot that depict what I just mentioned.

Solution:Delete the sensor under the Core and regenerate the oribiter and reload the router, everything is ok at this point.

P.S> I installed this zWave setup many times in the past no issues found, this is the first time I see this.

FYI, when installing zwave sensor and selecting sensor type, Sarah ask you if want to change the name "Generic Sensor" and hit "Next"==> in this screen there is no "Next Button", in order to continue you need to select "Done Button"I'm using snapshot #23165

P.S. I noticed this in 710 and 810, did not have a chance to record it & I'm not sure if someone else recoded this either.

It happened to me yesterday, I tried almost everything (Regenerating, rebuilding..), the only thing that worked for me is to delete the MD from the WebAdmin, and start from scratch, and it worked the second time.FYI I'm using "snapshot#23165" , the first 3 MDs I created didn't have a problem.