Our native mobile app has a new name: Fora Communities. Learn more.

Unexpected Quick Setup Recovery

3233 Views 7 Replies 5 Participants Last post by rm -rf *.*, Oct 19, 2004

l8er

Discussion Starter · Oct 19, 2004

Following a reboot this afternoon, one of my ReplayTVs entered Quick Setup. This had me worried, since there were a couple of dozen shows recorded, including some of my wife's favorites.

So I did a search here and came up with a Jeff D thread that outlined how to recover and save the shows:
http://www.avsforum.com/avs-vb/showt...74#post4170574 .

It still required Ethernet/Modem info and ReplayTV Name info but everything else was still there, including the Replay Guide and all recorded shows. Thanks, Jeff!

Save

Status: Not open for further replies.

1 - 8 of 8 Posts

drubixcube

· #2 · Oct 19, 2004

What good timing of your post. A buddy of mine, just gave me his replay today with this problem. I was going to load a fresh image on the drive thinking it got corrupt.

One good thing, about this happening to him today. I convinced him that he needed to upgrade that 40GB to a 250GB drive. But now we can preserve his shows.

Thanks

Drew

Save

rm -rf .

· #3 · Oct 19, 2004

This being said without knowing any more details than what you posted here:

What concerns me about that situation - What the heck happened to the RTV that would unexpectedly send it into QuckSetup?

The way I interpert the following is that the QuickSetup hit you totally without warning:

"Unexpected Quick Setup Recovery

Following a reboot this afternoon, one of my ReplayTVs entered Quick Setup."

See less See more

Save

rm -rf .

· #4 · Oct 19, 2004

Quote:

Originally posted by drubixcube
What good timing of your post. A buddy of mine, just gave me his replay today with this problem. I was going to load a fresh image on the drive thinking it got corrupt.

One good thing, about this happening to him today. I convinced him that he needed to upgrade that 40GB to a 250GB drive. But now we can preserve his shows.

Thanks

Drew

Word of advice:

Offload the shows to DVArchive - coping the MPEG partition is deadfully slow (I tried it once w/ 40Gb drives and it took something like 10+ hours)

See less See more

Save

sfhub

· #5 · Oct 19, 2004

I think QuickSetup will come up on reboot if one of the files gets corrupted.

Probably the Registry. The time it happened to me maybe 8 months ago,

I just went through the quick setup as normal and when it was done my

shows were still there. I didn't need to do any special procedure and it

never asked me to repartition the drive.

Save

Jeff D

· #6 · Oct 19, 2004

Glad someone got help from that "feature" find.

As to the cause... I suspect it's a check of the configuration files, I'm not sure much more beyond that. The data seems to be there as it's still available when you go into setup after circumventing the QuickSetup process. I can only guess that the backups may be used after the initial check that caused the quick setup trigger.

The one time it happened to me has been the only time and the replay has worked fine since. So... I don't suspect in my case it was a drive related issue, everyone else may have different findings.

SFHub, I hope that's the case, but my findings don't match. The reason I stumbled across this fix was because I was sick of losing my recordings. Every time I've had to do the QS after running I've always been required to reconfigure the photo partition (which destroys the mpeg partition records).

Maybe this changed on some newer software to eliminate the partition step if there is a partition? I don't know, maybe someone will be the sacrificial lamb and test out what happens if you finish the QS. =)

See less See more

Save

l8er

Discussion Starter · #7 · Oct 19, 2004

Quote:

Originally posted by sfhub
I think QuickSetup will come up on reboot if one of the files gets corrupted. Probably the Registry.

That's probably what happened in my case, as I was trying to make a change in the registry via WiRNS and getshellcmds.

Save

rm -rf .

· #8 · Oct 19, 2004

Quote:

Originally posted by l8er
That's probably what happened in my case, as I was trying to make a change in the registry via WiRNS and getshellcmds.

Oh s--t...

I'm sorry Gary - I know it was late night typo on my part, but I still feel kinna bad about putting you through the extra work.

...hopefully all the bright orage warning signs I tossed out there yesterday when you pointed out the problem won't get ignored (by too many dubasses)...

Save

1 - 8 of 8 Posts

Status: Not open for further replies.

Top Contributors this Month