Stanley,
Hope you get a good nights sleep. You will need the rest to prepare you for the bad news. This glitch is an ongoing problem and the method of shut down you were using really has nothing to do with it. In this case I don't think it was generating your problem, although it is always wise to follow the most recommended procedure.
I have personally been battling this scenario since day one when I received my first AZBox. It has not changed (much) with the firmware upgrades or my model upgrade from the Premium to the Premium Plus.
We are not doing anything incorrectly as far as I can determine. It is a resident "quirk" or "glitch" in the programming itself. Opensat needs to address this issue on their programming end. We can do a few things to reduce the frequency of occurrence of the problem, but we cannot completely eliminate it.
Best rule I have found is to make a clean slate of your entire list to work from. This means deleting all the European and Asian satellites from the list and creating your own list with all the western hemisphere satellites ONLY.
I recommend that you add ALL the western hemisphere satellites that you can possibly achieve from horizon to horizon, even if you don't think you can get them. As long as you start with a list containing them ALL, then you won't be tempted to go back and enter something else later and risk the possibility of your list becoming fouled.
Look into the thread regarding how to North Americanize your sat list and follow those instructions and advice.
I made up a list entirely of all the Ku band sats and added one TP to each sat only (generically - I added TP 11700 Horizontal with a SR of 1000 and set the FEC to AUTO). Then, after I uploaded the list, I performed a BLIND SCAN of each satellite for the FTA ONLY channels, one sat at a time, and saved the found channels.
You can make up a list of Ku only, C band only or a combination, that does not seem to mess anything up. But if you mix USALS with DiSEqC 1.2 it appears to generate problems. I think this has something to do with how the address pointers are used in the firmware program. If you don't enter the DiSEqC position properly, it wants to move another sat out of position and alter its orbital location.
It is extremely beneficial if you can use USALS motor control for each and every satellite in the list. Therefore, I would set each sat in your created list to utilize USALS only first. Then upload that list to your box. Once uploaded, if you must revert to DiSEqC 1.2 motor positioning, start at your furthest east satellite and fine tune it with DiSEqC 1.2 and save the position using the AUTO STORE feature. Then, work your way west, one satellite at a time.
That is NOT a guarantee that you still won't experience a foul up in your satellite listing, but it may reduce the frequency of the errors.
If you detect one of these foul ups, don't waste your time trying to fix it. Just delete the satellites that are fouled and re-enter them, doing so manually would be preferred.
The sorry part of this whole ordeal is, when you think you finally figured it out, it fouls up again. But, once you get all the satellites in the list and accurate, then as long as you don't try to get fancy or add something new, they will remain there in their proper positions with their proper names. You may scan all you wish and it will be fine. Just avoid adding a new sat to the list or changing the position of an existing sat. This is why I suggest creating a full blown list of ALL the satellites right off the bat.
Even though a sat has no history of being active for your area, you just never know when they might turn it on. Then, you will be tempted to play with it and if it isn't already in the list, you will have to add it. That is when you start having troubles again. So go ahead and put every orbital position in the list right from the start. Once in there, you don't have to use it. But, if you want to experiment with it, you won't foul anything up since all you have to do is scan what is already there.
Well, that is just my personal reccommendations to help REDUCE the troubles.
Good luck and welcome to the AZBox club of bald guys with nervous twitches and tourettes syndrome. LOL!
RADAR