Help determining why DTivo reboots

[captainjrl]

Where on my HDVR2 can I look to figure out why it reboots itself every so often? Seems like it goes anywhere from a couple of days to a couple of weeks fine and then reboots. One time after a reboot it gave me a GSOD, but it self repaired and is back working fine, minus the reboots. Is there some sort of log file I can look at to see what may be causing it?

TIA

[cheer]

The kernel log would be the place to look -- should tell you why it's rebooting.

[captainjrl]

Forgive my ignorance but where do I locate it and how do I read it. Is it something accessable via Tivowebplus?

[cheer]

Right off the main menu in TWP -- Logs, then kernel.

[captainjrl]

What would I be looking for in there?

[cheer]

Something that looks like an error message would be a good start. Just post the log in an attachment here.

[captainjrl]

Its pretty huge, so I only put the last part of it.

[cheer]

Couldn't swear to it, but it looks like this is your problem:
Dec 29 23:40:19 (none) kernel: Filesystem assert: strcmp( pPrev->GetName(), pEntry->GetName() ) < 0 at nmactive.C line 655 in int NmActive::Audit(int, bool, bool, bool, int)
Dec 29 23:40:20 (none) kernel: Filesystem flagged as inconsistent!
Dec 29 23:40:22 (none) kernel: Tmk Assertion Failure: strcmp( pPrev->GetName(), pEntry->GetName() ) < 0
Dec 29 23:40:22 (none) kernel: int NmActive::Audit(int, bool, bool, bool, int), line 655 (nmactive.C)
Dec 29 23:40:22 (none) kernel: Tmk Fatal Error: Thread ApgWriter <154> died due to signal -2
I'm guessing a hard drive problem.

[captainjrl]

OK, I'll try a new one. Hmm, now I need to see if I have one around.

Thanks cheer.

[Narf54321]

These things jeep popping up, too:

Dec 28 03:55:08 (none) kernel: Filesystem is inconsistent - cannot mount!
Dec 28 03:55:44 (none) kernel: fsfix: mounted MFS volume, starting consistency checks.
Dec 28 03:55:44 (none) kernel: I-Nodes:
Dec 28 03:55:44 (none) kernel: I-Node table size is 131072 entries for 100000 active nodes max.
Dec 28 03:55:44 (none) kernel: FsId high-water mark is 0xf64e2
Dec 28 03:55:44 (none) kernel: Pass 1 - scan and analyze
Dec 28 03:55:44 (none) kernel: reconstructing zone buddymaps
Dec 28 03:55:44 (none) kernel: synchronizing...
Dec 28 03:55:44 (none) kernel: volume marked as needing database cleanup
Dec 28 03:55:44 (none) kernel: scanned 71050 files, covering 22010 extents
Dec 28 03:55:44 (none) kernel: 217840 application pages in use
Dec 28 03:55:44 (none) kernel: 152397824 media pages in use
Dec 28 03:55:44 (none) kernel: Inode table collision details
Dec 28 03:55:44 (none) kernel: 37492 hash collisions in node table.
Dec 28 03:55:44 (none) kernel: 40 hash collisions in longest run.
Dec 28 03:55:44 (none) kernel: 21 hash collisions in longest busy run.
Dec 28 03:55:44 (none) kernel: 14626 files aren't in their primary hash locations.


Sounds like something either got corrupted, or like cheer suggested the HDD is starting to go bad or lose sectors.

At minimum, you can try to load clean slices to your alternate partition and re-hack before rebooting.