Our VIP2250 DVR has seizures.

IIRC, they weren't AF drives, but there was failing if it wasn't a 7200rpm. The AF drives seem to have a conflict with MediaRoom, how much of that is a function of the Windows CE base is anyone's guess. And, yes, they were SATA (pretty much anything 2008 or so and forward usually is).

There has been, for years, a full diagnostics on the CABLE side of the converter realm, and from the same suspects (Motorola and Cisco/Scientific Atlanta) that Uverse and others using the IPTV MediaRoom buy from. Why they don't have something similar attached to their build that interfaces with Win CE/MediaRoom is yet another of those anyone's guesses.

As to it running hot, get a set of checkers from the dollar store, and make 4-checker stacks, and wrap them with some black electrical tape. The DVR feet fit perfectly into them, and the additional elevation will allow more air circulation. Anything to prevent some sort of malfunction would be wise. (I re-treaded mine from my Comcast Motorola DVR days, and have had no problems with my Uverse VIP 1225.)

Odd behavior... Yeah, since Windows CE 5 is still supported, it should have an updated driver that would handle AF transactions, so in theory Mediaroom shouldn't have to be bothered with low level data alignment.

The VIP1225 has only 64MB, after a fresh boot seventy three percent is consumed and after a short span of time gets to ninety percent - not much of space left for live diagnostic display or even in flash ROM.

VIP2250 probably has no excuse, because it has twice the ram and I think a larger ROM. Noting the present issues, it might create even more tech support calls. The built in SoC controller meet industry standards, so unless S.M.A.R.T is disabled on the drive it work. My guess is they don't believe it's necessary, and maybe legal issues.

I like that, a house on stilts. 🙂  It's cold here, and it's in a nice empty space with optional fan. VIP1225's are vented all around and spacious inside - makes a difference.

Are you still having the issue where the DVR resets between 10:20 and 10:30AM?  I instantly wondered if something on the same circuit was "kicking on" (or maynbe off) at the same time and causing interference / noise on the line?  Some folks have had issues with motors in treadmills, transformers in printers, thermostats, furnance motors or igniters and so on.  Just curious.

No.

I did question if it also was a matter of bad power. We don't knowingly have any heavy duty appliances on the circuit.

This was at a time of year when the Texas PUC or Oncor would be practicing the art of punitive load balancing. (I'll just leave my opinion out of this post.)

The tech's a solution to the problem was to stop using VIP2250 HDMI and move the DVR to another room - currently I'm using a VIP1200 with the HDTV. There are the intermittent rendering problems but that's not a showstopper.

I haven't even tried to reconnect the VIP2250 to the TV. When AT&T updates the DVR again, then I'll reconnect.

I continue to re-boot my 2250 a couple of times per day, often losing a recording in progress.  I'm tired of having AT&T Techs come out because they can't do anything but tell m e they can't find a problem.  I've been trying to determine if I have the latest TV Client Version, but can't find that information anywhere.   I have 2.6.31312.24

SAD

Unplug your gateway. Unplug your dvr. Plug your gateway back in and let it reboot fully. Green lights. Plug in your dvr. Let it reboot. See if your problems stop after that. Check that all connections at the gateway and tv are tightly/fully connected. Try a different Ethernet cable from the gateway to the tv. 

If if you can, move the dvr to another tv and see if you still get problems. 

This "fix" works for a while, until the next failure.

Actually, I have the most LUCK using the 2250 Support Process to Reboot the Router, following which, reboot the DVR.  However, the problem is with the DVR (ARRIS 2250), most likely with the TV Client, which is supported (and I use that term loosely) by AT&T, not ARRIS.  You can tell this as the DVR responds slowly, if at all, to any command from the remote.

Sometimes, I think that what is needed is a DEFRAG, but the problem may be deeper than that.  Unfortunately, I'm not sure AT&T has any remaining interest in the 2250 as they want to push customers to Direct TV.