"Please wait" failure modes other than HD?

[mgraban]

My Replay 5504 starting doing the "please wait" lockup. Based on everything I read here, it sounded like a HD problem.

I put the HD in my PC and was able to read/extract shows using Extract_RTV.

Then, I believe I properly set up a new 80 gig western digital HD using RTV Patch and the downloaded RTV image. Again, using Extract_RTV (in DOS mode), I could see that the disk had the 3 partitions -- system, mpeg, and photo. The system partition had a ton of the files, mpeg and photo were blank basically, as expected.

I put the new drive in my Replay and I'm still getting the "please wait" after a few hard and soft reboots.

What else could the problem be?

It's out of warranty. If it's dead, though, would DNNA let me buy a replacement and transfer the subscription?

[SeeSpotRun]

This happened to a 5504 that I had too. A replacement drive didn't fix the problem. Even though the system was till under warranty, I was fortunate to pick up a 5040 instead during the last fire sale and manage to have DNNA transfer service back while they were still doing transfers.

At this point, seems like you are going to have to have them repair it unless you can get them to transfer service.

So, how much does a repair cost?

SeeSpotRun

[rm -rf *.*]

Check for:

-Improperly set jumper (5k's use Cable Select, but try Master also. WD's have two Master settings, try 'em both.)

-Poorly/improperly seated ATA cable

-Electron pipe not properly connected

[mgraban]

Originally posted by rm -rf *.*
Check for:

-Improperly set jumper (5k's use Cable Select, but try Master also. WD's have two Master settings, try 'em both.)

-Poorly/improperly seated ATA cable

-Electron pipe not properly connected

I'll try changing the jumper. I had the jumper off completely, as I thought that was one "master" setting.

I've check the cable, both connections, but will check again.

What is the "electron pipe"??

[mgraban]

Originally posted by mgraban


What is the "electron pipe"?? [/B]

Duh, you must have mean the power cable.

[dstoffa]

Originally posted by mgraban
My Replay 5504 starting doing the "please wait" lockup. Based on everything I read here, it sounded like a HD problem.

What else could the problem be?



There are two "Please Wait" screens. Which one you get stuck on may shed a better light on the project.

The first splash Screen is generated by hardware, and will be displayed only if you are NOT using the RF output. It will say "ReplayTV. Please Wait" Normally, this is displayed for about 10-15 seconds. The splash will be centered in the screen, and the

THe second splash screen is software generated, and It will Read "Welcome to ReplayTV. One Moment Please." Other things in the splash will depend on the Rev of OS you are booting. (It may state SONIC BLUE). This one will have a more colorful display.

If you are stuck at the hardware splash, your software isn't even booting. Check the drive jumper, IDE Ribbon, re-set all connectors, etc.

If you are stuck at the software splash, then you have an OS problem. Try a new image / or use a diffrent make / model hard disk.

If that doesn't work, then there is a problem on the MOBO. In today's disposable world, that may mean you can throw the unit away. The cost of a replacement baord is likely cheaper than the cost for you to ship two-ways and pay for parts / labor.

-Doug

[mgraban]

It's the hardware splash. I'm starting to think the MOBO is bad, since the original HD didn't seem corrupted at all when I put it on the PC.

So, I guess I'll call DNNA, try to buy a 5504 replacement and maybe put this new 80 gig HD in it (after verifying it works with the new orig HD).

Will DNNA transfer the lifetime on it? They better.

[Crunchy Doodle]

I know this sounds religious, but I don't believe in Cable Select, and used jumpered master or slave on five ReplayTV upgrades.

If you're still having trouble, maybe a low-level format or full zero-fill will help. A ReplayTV has no tolerance for bad spots on the hard drive. A low-level format or zero-fill will allow the drive to map out any bad spots.

Oh, and don't forget the hysteresis dust. :)

Bye. :cool:

Originally posted by rm -rf *.*
Check for:

-Improperly set jumper (5k's use Cable Select, but try Master also. WD's have two Master settings, try 'em both.)

-Poorly/improperly seated ATA cable

-Electron pipe not properly connected

[JohnnyArcade]

First - my ATA cable hosed recently for absolutely no reason. Try a new one and see if it helps.

Second - This is completely unscientific, but it helped me when I had this same problem with a 4500. I disconnected the Hard Drive ATA and power cable, and then plugged the replay in. After a few minutes at the "Please Wait" screen, I unplugged it again. I reconnected the hard drive, and plugged it back in, and it booted up just fine.

[archdog99]

I had the same problem and it turned out to be the network cable was crimped and was causing a short.

-a

[Jazzsax]

My problem a while back was booting with the Ethernet cable plugged in. No idea why, and replugging it in after it finished rebooting worked fine to connect to my other unit. And, it doesn't happen anymore. Go figure.

[mgraban]

Originally posted by JohnnyArcade
First - my ATA cable hosed recently for absolutely no reason. Try a new one and see if it helps.

Second - This is completely unscientific, but it helped me when I had this same problem with a 4500. I disconnected the Hard Drive ATA and power cable, and then plugged the replay in. After a few minutes at the "Please Wait" screen, I unplugged it again. I reconnected the hard drive, and plugged it back in, and it booted up just fine.

Thanks, I'll try the cable that came with the new drive I bought. I have an RMA number just in case -- hopefully they won't notice that I took the thing apart (had taken the sticker off carefully).

[jimwa]

Originally posted by Jazzsax
My problem a while back was booting with the Ethernet cable plugged in. No idea why, and replugging it in after it finished rebooting worked fine to connect to my other unit. And, it doesn't happen anymore. Go figure.

Thank Heaven for this post. I had a REALLY strange thing happen with three of my four Replays today. Both of my 4500s and my 5000 (each in different rooms) ALL THREE got stuck on the "Please Wait" hardware screen (only my 4000 didn't, or at least hasn't yet, so failed TODAY), and none of them would boot.

The ONLY two things I was pretty sure of was that each failure happened after each unit's respective daily update, and, given the law of probabilities and MTBFs, I just don't believe in that much coincidence as to that many simultaneous hard drive failures.

If not for Jazzsax's post, I probably wouldn't have thought of the possibility that their network connection could have been the problem (now, given the commonality and proximity of the events, I suspected a problem with the actual daily update download, but NOT the fact that just being plugged into the network would stop the boot sequence). But, even after spending about 12 hours seeing if unplugging each unit from the AC, waiting a while, and then reconnecting power (and as the 2nd and then the 3rd Replay failed), I hadn't thought about the network connections being the problem, as my network was working for everything else (including web and mail access).

Nevertheless, after finding this post, I disconnected each Replay's network connection, cycled the power again via the AC cord, and all three came back up.

Does anybody have a good explanation for why, without my network going down at all, three of my four Replays could get stuck on the hardware screen, and each only coming up after cycling them without the ethernet cable attached? I have had Replays since the 2000 series days, and I have never run into anything like this before. Even if the DHCP server had scrambled their IP addresses, why would mere physical attachment to the home network prevent booting? It can't be checking for a valid IP address before it boots, or you would never be able to set or change your network setup.

Thanks,

[lrfisher]

please help.... i've seen reference to someone to whom i can send my broken showstopper to.... we blew a fuse in our apartment and I think our hard drive is frozen. I have one of the original showstoppers so I'm due for a new machine but really want to try and save what's on the machine - some is irreplaceable!! can someone help????

[toys4boys]

I ran into a similar problem after relocating a 5504. The machine had been acting up beforehand, so I starting gearing up for a hard drive replacement (needed more space anyway).

I happened to check my other Replays and noticed the last net connect was 2 days prior (strange). Forced a net connect and managed to hang another machine.

After further analysis, I found the problem. WiRNS had locked up and was preventing all Replays from updating. A quick reboot and a few net connects later and all was well (including my problematic 5504).

[Markinsac]

Hook the hard drive back up to your system, and use the appropriate hard drive diagnostic (like Maxtor's PowerMax). When my system was stuck, I found that running this utility, and allowing to repair when it found some errors, resurrected the hard drive, and I have it back in my 4508.

Good Luck!

Mark