(Probably not) Random Reboots

[SolidTechie]

Hi folks,

Got a bit of a problem. My main TiVo sadly, didn't survive the recent house move, and my spare, is still in transit.

I have replaced my twin 120's with a shiny new 400GB drive, and a kind forum member (you know who you are -thanks again) saved my bacon, with an image file, as I wasn't able to recover one from the failed disk pair.

So, having used a Large disk image, and restored/expanded as per Steve Conrads instructions, plugged in, booted up and off we jolly well go.

Started to change "channels I receive", and it rebooted - probably around the time it would have finished indexing guide data - so I wasn't alarmed. That was late last night so, I left it.

This morning, I installed TiVoWeb, and went off to work. Came back, started to set up some SPs -and it was very, very unresponsive. I would press a button, and would here the "bong" - but would then have to wait 3-5 seconds, before the TiVo "reacted" to the command.

I figured that there was summat wrong.

It's rebooted twice this evening, and much as I can get at the logs, I confess, I don't really know what I'm looking for.

the only thing I found was this, from the tverr log:

Jun 20 16:45:31 (none) Recorder[140]: CheckSchedule took 11838 milliseconds
Jun 20 17:17:17 (none) TvRecorder[140]: Tmk Fatal Error: Thread TvRecorder <140> died due to signal 11
Jun 20 17:17:18 (none) TvRecorder[140]: NIP 0x1a53e98 link 0x1a53ddc ctr 27645832
Jun 20 17:17:18 (none) TvRecorder[140]: R00 0x00003001 R01 0x7fffeb40 R02 0x00000100 R03 0x00006cb0
Jun 20 17:17:18 (none) TvRecorder[140]: R04 0x01da0000 R05 0x00000018 R06 0x00000072 R07 0x00000006
Jun 20 17:17:18 (none) TvRecorder[140]: R08 0x00000001 R09 0x01db6000 R10 0x00000000 R11 0x00003000
Jun 20 17:17:18 (none) TvRecorder[140]: R12 0x22200092 R13 0x01da9208 R14 0x00000000 R15 0x00000000
Jun 20 17:17:18 (none) TvRecorder[140]: R16 0x018bdd4c R17 0x00000000 R18 0xffffffff R19 0xffffffff
Jun 20 17:17:18 (none) TvRecorder[140]: R20 0x01840000 R21 0x018d24ec R22 0x00000000 R23 0x00000001
Jun 20 17:17:18 (none) TvRecorder[140]: R24 0x00000000 R25 0x00000000 R26 0x01b3e4f8 R27 0x7fb59538
Jun 20 17:17:18 (none) TvRecorder[140]: R28 0x0000001e R29 0x00003cb0 R30 0x01d9be54 R31 0x01db2350
Jun 20 17:17:18 (none) TvRecorder[140]: Tmk Thread Backtrace: 1a344fc 7fffea58 1a53ddc 1a53958 1a412a4 1b409f0 1b3f70c 1b404b0 1b3c10c 1b3c054 1b3bf2c 1b3d6a0 1b3e694 1b19be0 1b19b1c 1b1b0ac 1b43594 1b42c64 1b03520 1b03294 1b02dd0 1b98f88 1b98e24 1b03f80 1b04e88 1b91bb4 1c24a0c 1c249b8 1c23c84 1c23db0 1c27364 1c28374 1c28420 1c27504 1c23eb4 1c248fc 1c06ecc 1bf7094 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 ipe
Jun 20 17:17:18 (none) TvRecorder[140]: Tmk Fatal Error: Thread died due to signal 11
Jun 20 17:17:18 (none) TvRecorder[140]: Invoking rule 834: rebooting system
Jun 20 19:38:21 (none) EventLog event handler[132]: Tmk Fatal Error: Thread EventLog event handler <132> died due to signal 11
Jun 20 19:38:22 (none) EventLog event handler[132]: NIP 0x1a53e98 link 0x1a53ddc ctr 27645832
Jun 20 19:38:22 (none) EventLog event handler[132]: R00 0x00002f31 R01 0x7fffee50 R02 0x00000100 R03 0x00006be0
Jun 20 19:38:22 (none) EventLog event handler[132]: R04 0x01da0000 R05 0x00000018 R06 0x00000072 R07 0x00000006
Jun 20 19:38:22 (none) EventLog event handler[132]: R08 0x0000001c R09 0x01db60d0 R10 0x00000000 R11 0x00002f30
Jun 20 19:38:22 (none) EventLog event handler[132]: R12 0x22200032 R13 0x01da9208 R14 0x00000000 R15 0x00000000
Jun 20 19:38:22 (none) EventLog event handler[132]: R16 0x018bdd4c R17 0x00000000 R18 0xffffffff R19 0xffffffff
Jun 20 19:38:22 (none) EventLog event handler[132]: R20 0x01840000 R21 0x018d24ec R22 0x00000000 R23 0x00000001
Jun 20 19:38:22 (none) EventLog event handler[132]: R24 0x7ffff188 R25 0x00000000 R26 0x01b3e4f8 R27 0x7fb5ac74
Jun 20 19:38:22 (none) EventLog event handler[132]: R28 0x0000001e R29 0x00003cb0 R30 0x01d9be54 R31 0x01db2420
Jun 20 19:38:22 (none) EventLog event handler[132]: Tmk Thread Backtrace: 1a344fc 7fffed68 1a53ddc 1a53958 1a412a4 1b409f0 1b3f70c 1b404b0 1b3c10c 1b3c054 1b3bf2c 1b3d6a0 1b3e694 1b31cc0 1b1c020 1b1bf74 1ac0908 1ac1118 1ac0704 1b90c28 1b90c98 1b90b10 1b91bb4 1c24a0c 1c249b8 1c23c84 1c23db0 1c27364 1c28374 1c28420 1c27504 1c23eb4 1c248fc 1c0145c 1bf6f94 1c239b0 1c2764c 1c28374 1c28420 1c27748 1c2379c 1c24388 1c2400c 1bf6b00 1c28af4 1800134 ipe
Jun 20 19:38:22 (none) EventLog event handler[132]: Tmk Fatal Error: Thread died due to signal 11
Jun 20 19:38:22 (none) EventLog event handler[132]: Invoking rule 834: rebooting system

Anyone care to hazzard a guess - or point me in the right direction of where to look?

[ColinYounger]

My hazarded guess is swapfile - what did you set up with the new drive?

[SolidTechie]

Hi Colin,

restore -x -r 4 -s 300 -zpi /mnt/dos/tivo.bak /dev/hdc

I think that means 300MB for the swap file?

[RichardJH]

I assume you ran copykern to enable Tivo to access all the disc

[blindlemon]

Have you tried triggering a GSOD with mfsassert -please ?

That should clear up any MFS corruption from the image that might be causing problems...

[SolidTechie]

Richard - no, it was a large disk image - I assumed it would work without needing to do the copykern

blindlemon

Nope, but you can rest assured, I'm just about to! :)

[SolidTechie]

Have you tried triggering a GSOD with mfsassert -please ?



Erm... how long would you expect this to take? it's been going for over 6 hours now..

[bigwold]

Richard - no, it was a large disk image - I assumed it would work without needing to do the copykern


unless you run copykern (or otherwise initialise your swap ) you will not have a swap file

[SolidTechie]

(or otherwise initialise your swap )

Forgive my ignorance - is this not what the :

-s 300 is in the restore command?

restore -x -r 4 -s 300 -zpi /mnt/dos/tivo.bak /dev/hdc

And if it's not, then how do I do it now? (can it be done via telnet?)

[RichardJH]

Don't think you can do it any other way than by putting the drive in a PC and booting from LBA48 CD.

If you followed Steve Conrads upgrade http://www.steveconrad.co.uk/tivo/upgrade3.html
did you follow:- Part 5 : Patching the Tivo Operating System.

[SolidTechie]

No,

I skipped that part, because I was restoring an image from a Large Disk -

" tivolba48.bak which already has the large disk support "

I'm assuming that this image was (a backup) taken from a TiVo which had already been upgraded. I assumed therefore, that I wouldn't need to run the copykern command.

Please fell free to tell me if I'm stupid, and if I have to pull the disk and re-run it I will!

[ColinYounger]

Ian - see stage five of Steve Conrad's guide (http://www.steveconrad.co.uk/tivo/upgrade3.html), which says:Currently, although the drive is ready for use and is using the whole 250G of the drive, the Tivo system will not know how to access the area of this drive beyond 137G. If you were to place the new drive into Tivo at this point, it would only register 137G as the size of the new drive - a large waste of drive space!

So we need to tweak the Tivo system with a patch to the Tivo Kernel (it's main program).He then goes on to describe usign copykern.

I'd like Blindlemon to confirm, but in my opinion, it's pull-the-drive time. What I don't know is if you can run copykern at any point.

[ColinYounger]

Doh! Sorry for repeating Richard's advice. I went away for a cuppa mid-reply. :(

[RichardJH]

I am sure that one of our more knowledgable memmbers will be along soon to confirm my suspicions.

No you are not stupid it is just part of the learning process ;) ;) . I know I have been there.

You will only have to do the copykern bit not the whole backup. It wouldn't hurt to do it.

[RichardJH]

I'd like Blindlemon to confirm, but in my opinion, it's pull-the-drive time. What I don't know is if you can run copykern at any point.

Doh! Sorry for repeating Colins's advice. I went away for a cuppa mid-reply. :D :D

[bigwold]

You specified 300MB of swap but the TiVo software can only initialise up to 127MB. If you specify a greater size it will need to be initialised by you otherwise you will have none, not even 127MB . Copykern includes an initialisation script and there is also a stand alone one which I can't remember the name of. Running copykern won't cause any harm.

[SolidTechie]

Thanks everyone for your replies and assistance

I am not trying to be argumentative, and I hope I'm not coming across that way - I really want to understand what has gone wrong.

I know that after I had done the restore, I was reasonably confident - it reported 400+ hours IIRC, which was why I figured it didn't need the CopyKern.

Anyway -sadly, one of my colleagues has left today, and I'm afraid I'm duty bound to accompany him this evening to make sure he is capable of getting home safely! I shan't of course, have a drop myself! :)

Hopefully by the time I get home, the GSOD rebuild will have completed, and we can take it from there.

[SolidTechie]

Just an update -

After forcing the GSOD, it went back into perpetual rebooting. I pulled the drive, and ran copykern, put it back in the TiVo, and it seems to be running OK now -thanks all.

I'm a little confused by this though.

If I was to pull my now large drive, and do a backup, then restore to a new similarly sized or larger drive, would I still need to run copykern on the new drive?

[bigwold]

If I was to pull my now large drive, and do a backup, then restore to a new similarly sized or larger drive, would I still need to run copykern on the new drive?

I would expect you to have the LBA48 kernel but your swap would not be initialised and hence unusable as you have found. Running copykern will initialise your swap for you (as well as copying the kernel).

[SolidTechie]

Ok, I think I've got it now.

Thanks again for all your assistance.