Every thread I've seen on this topic has two downsides to that: we have to partition anything bigger into 2TB chunks, and even then the resulting kluge is reportedly highly unwieldy and very unreliable in Hopper-land. People complain of losing part or all of their archived content immediately or within a few weeks.
Yes, self powered hard drives are becoming rare. And the USB ports on a H3 can't supply enough power for most drives (a design flaw in my option). So that leads to the issue you are seeing.
I've had a 6TB Seagate with USB hub for many years working fine with about the same amount full. I had a whilte OTA adapter plugged into the Seagate hub also working fine even when the disk itself was not visible. Then all of a sudden the disk isn't recognized.
So far my Seagate has been fine, I haven't seen any indications that there's a problem. I'd be curious to see if Gibson Research Corp's SpinRite would find something on your hard drive that it could find and repair.
Sigh...
Wrong. Where the heck are you getting this information?
A 3.0 would work just fine. I only recommend a 3.1 because that's the most common, high speed hub types these days. There's a cheap 4 port two charging ports 3.0 one I found on Amazon (about $15). Link below.
Dozens of posts in many threads in several forums, plus multiple Dish techs right up to yesterday, over dozens of hours. I'm an engineer and have used computers ever since I coded my first program in 1961, but as my screen name suggests, I am just not interested in the level of detail in this topic many of you guys have mastered. Heck, just switching from Spectrum to Dish took me hundreds of hours over 6 months and counting, because neither of them know what the hell they're talking about, both just make stuff up, and every Dish tech in my home (12-15 and counting) has scratched his head and said he's never seen a setup like my fully integrated, operationally independent 2-Hopper/7-Joey/9-TV system spread over two buildings. Several of my questions and bugs have stumped every one of them.
1. That's where I was leaning at this point.
I like a system like that. They're few and far between. But taking on that install and making it work is something I wish I could have done more often.
Your success fits within the wide range of experiences I've seen on this topic. However, far too many other people have had serious problems with it, and Dish in other publications has insisted that we must use external power. I'm going to play it safe (?) and go with a self-powered hub and top-rated (probably WD) EHD. When and if my backup approach fails and I lose everything, I'll want to know I had done the best I could. A hundred bucks means nothing if -- IF -- it avoids the hassles and losses others have experienced.
Fortunately, they make cute paperweights.
Having been through this kind of process many times myself, I recommend that you test drive a couple of less important programs first just to make sure everything works; something you can afford to lose if something goes wrong. When transferring, do only a dozen or so shows at a time. This does make for more tedious babysitting the process, but it means you're less likely to lose a lot of shows if something in any one transfer process goes wrong.
I've been using a WD Elements 2TB for my iMac Time Machine drive for years without failure.Your success fits within the wide range of experiences I've seen on this topic. However, far too many other people have had serious problems with it, and Dish in other publications has insisted that we must use external power. I'm going to play it safe (?) and go with a self-powered hub and top-rated (probably WD) EHD. When and if my backup approach fails and I lose everything, I'll want to know I had done the best I could. A hundred bucks means nothing if -- IF -- it avoids the hassles and losses others have experienced.
On that note, Apple, Sandisk, WD, and I have given up trying to get three different Sandisk and WD SSDs to get Apple's Time Machine to back up my Mac properly.
Words of wisdom. Even the Dish tech who installed my system a year or two ago suspected this Hopper was buggy, but subsequent experiments by techs and me lead us to suspect my WiFi, now mesh, system(s) to be my biggest source of bugs. It's mostly odd behaviors rather than lost segments, and my next experiment will be adding another couple of nodes to my Google Nest Pro 6E mesh system. I intend to pursue that approach in time to return them to the sellers for full refund if it doesn't out-perform my TPLink WiFi router-and-one-extender system.
Limited time offer
