I had a Motorola 7216 DVR box that had an external ESata drive. The box had three issues: froze 2-3 times a day for maybe 30 seconds, sound "clipping" during loud sections of shows/movies, and I could never get the Android app or web app to connect to the DVR. So, I received a new 7232 DVR today. Prior to disconnecting the old, I did the proper method of ejecting of the ESata Drive.
I hooked up the new DVR, and (possibly mistakenly) hooked up the ESata drive as well before booting it up the first time. Did the initialization, all went well. Went through the routine of adding ESata, rebooted, didn't recognize the drive. Realize I maybe shouldn't have plugged it in, so unplugged ESata cord, rebooted, did Set-Top Box Auto Correct, then went through the proper routine to add external storage. However, when rebooting, the box blinks one light for 30 seconds, then the entire display lights up, then it reboots, repeating this routine ad infinitum (nothing ever displays on the TV).
So, thinking I got a bad box, I hook up the old DVR, get it working, and then run the add ESata routine. It now is in the same infinite loop as the old box (for 30 minutes now as I type).
Removing the ESata, and rebooting, back to normal operation, though without ESata and all of the recorded shows.
Any ideas? Do you think my "mistake" in hooking up the ESata drive to the new box right off the bat might have messed up the drive? I'm ordering an ESata to Sata cable so I can hook up the drive to my PC and see if it's accessable. Maybe I can reformat it, knowing we'll lose all our programs (actually, my wife's programs......no big deal to me
)
Or does it take a long time to initialize an existing ESata drive with lots of programs on it?