HD300 won't boot with Phoenix

[Joebob]

Hi All,

Please Help! I installed Phoenix, restarted my server, and then selected the Phoenix stv. Since then, the 1 HD300 that I installed the stv on won't boot up. I gets to the below screen and then hangs. Any suggestions?

[robogeek]

There might be a better solution or more specific set of properties that can be deleted that cause this, but you can delete the .properties files for that extender to fix that problem. That's what worked for me.

Check the back or bottom of the extender unit to get its ethernet MAC address, then look in the SageTV\clients directory on your SageTV server, and delete the <MAC address>.properties and <MAC address>.properties.autobackup files. You should stop SageTV on the server before deleting the files. If you've made significant configuration changes to the stock interface (or to the Diamond interface if you were using that), you may want to just move those files instead of deleting them so you can revert back if you decide not to continue with Phoenix. One other note, if you move or delete those .properties files, you will have to go through the initial configuration wizard for that extender again.

[graywolf]

Originally Posted by robogeek

There might be a better solution or more specific set of properties that can be deleted that cause this, but you can delete the .properties files for that extender to fix that problem. That's what worked for me.

OR instead of deleting the entire .properties file, you can look for STV= and change the line to:

STV=C\:\\SageTV\\SageTV\\STVs\\SageTV7\\SageTV7.xml

(my path is c:\SageTV so change it to whatever yours is)
then reboot

[robogeek]

That's partially correct, graywolf. Changing that property will revert the extender back to the SageTV 7 UI, but that didn't fix the problem with Phoenix not loading correctly after changing back to the Phoenix STV. Reverting the STV back to default manually and re-selecting the Phoenix STV resulted in the same problem. For the sake of providing more detailed information, it's not that the extender fails to boot when loading the Phoenix STV, it's just that Phoenix doesn't render properly and leaves the extender boot screen visible as the background. It seems there is some conflict between some setting(s) in the .properties file that causes Phoenix to not be able to render correctly, and deleting the .properties file and re-selecting the Phoenix STV fixed that.

[graywolf]

ok. Different situation than what I thought. Had 1 time where I choose the wrong .xml as STV and couldn't get out of it for the HD300.

Didn't feel like going thru the entire setup so did some experimenting.

Changing the STV= got me in where I could "undo" the lockup I had done and didn't have to redo everything.

Guess I should have looked at the picture/attachment

[mguebert]

I had the same thing happen on my HD300, the cure for me was to reboot the server and unplug the power on the HD300. When I plugged the HD300 back in it booted up fine.

[Joebob]

Originally Posted by mguebert

I had the same thing happen on my HD300, the cure for me was to reboot the server and unplug the power on the HD300. When I plugged the HD300 back in it booted up fine.

Already tried the reboot thing and no joy.

Just replaced the STV line in the properties file and that allowed the system to boot back up into the Diamond theme.

Completely deleted the properties file and tried to re-enable the Phoenix UI and get the exact same problem.

[PiX64]

I had a problem with Phoenix and diamond co-existing a few builds ago. Try removing diamond completely, rebooting, then insstalking Phoenix. Also make sure you are running the most recent Phoenix API.

[jorton]

I have the latest Phoenix and Diamond coexisting on my Server, Clients and an HD300 no problems. Not sure why Diamond would cause any issues as it is only running on top of the default STV and when Phoenix is active it should be disabled along with the default STV as well as any other plugins. It shouldn't be interacting with Phoenix STV in any way.

http://forums.sagetv.com/forums/show...60&postcount=5

J

[Joebob]

I have the latest Phoenix and Diamond too. I am also using SageMyMovies and Playon. Maybe one of these is making Phoenix mad?

[robogeek]

Originally Posted by Joebob

Already tried the reboot thing and no joy.

Just replaced the STV line in the properties file and that allowed the system to boot back up into the Diamond theme.

Completely deleted the properties file and tried to re-enable the Phoenix UI and get the exact same problem.

When you deleted the properties file, did the extender go through the configuration wizard on the next startup? If not, you didn't properly delete the extender properties files or you deleted the wrong files (I forgot to mention earlier that if you use a USB wireless adapter on the extender, then you should use the MAC address of the wireless adapter to identify the .properties files and not the one printed on the extender). If it did go through the wizard and you still had the problem after reselecting the Phoenix STV, then I'm stumped and you can ignore the rest of this post

The proper steps to reset the extender properties: turn off extender, stop all SageTV apps on SageTV server PC (double check with Task Manager to be sure no SageTV.exe or SageTVService.exe processes are running), delete both the .properties file and the .properties.autobackup files of the affected extender from the SageTV\clients directory, then start SageTV back up, turn on the extender, go through the configuration wizard, and finally, reselect the Phoenix STV in Detailed Setup. Here are a couple of reasons why these steps have to be performed in that particular order... If you leave SageTV running, delete the .properties files, and restart the extender, SageTV recreates the .properties file with settings it has cached in memory for that extender instead of starting a new .properties file. If you leave SageTV running, delete the files, and then restart the SageTV Service, it will rewrite the files with settings it has cached in memory before it restarts so you won't really restart with a new .properties file. If you delete just the .properties file but not the .autobackup file, then the next restart of the extender should cause SageTV to regenerate the .properties file using the settings from the .autobackup instead of starting with a new .properties file.

[stuckless]

Originally Posted by Joebob

I have the latest Phoenix and Diamond too. I am also using SageMyMovies and Playon. Maybe one of these is making Phoenix mad?

If you have the bmt web ui installed, then try restarting the sagetv server, and once it's restarted, then try Phoenix on the extender, again, and then use the "Create Support Request" link in the Help section from the bmt web ui. That will create a zip of all the log files on your server (related to sagetv). Email that to metadatatools at gmail dot com and I can take a look at what is happening on the phoenix side of things to see if Phoenix is doing something odd.

[Joebob]

Originally Posted by robogeek

When you deleted the properties file, did the extender go through the configuration wizard on the next startup?

Yes

[PiX64]

Originally Posted by Joebob

I have the latest Phoenix and Diamond too. I am also using SageMyMovies and Playon. Maybe one of these is making Phoenix mad?

That Setup is exactly what I had runnig when I had my issues with it. Since the. I have reinstalled diamond and no longer have issues..

[ColumbusGEEK]

I removed the properties files and rebooted and Phoneix worked.