PDA

View Full Version : Manually Forcing mfsassert -please



Soapm
12-31-2011, 01:29 AM
How can I flag my file system where I can force my tivo to do a mfsassert -please.

Since I was down to about 300 gigs free space I decided I was over my 20 minute reboot hurdle so I began cleaning up the drive since I had everything flagged "keep until I delete". So I set most of the season passes to keep 5 and deleted a bunch of movies that recorded. I was then in TWP when I noticed under UI there was this deleted feature. It has all the shows that were in the recently deleted folder with a button that said purge. So guess what I did???

Yep, I selected all and hit purge thinking it was like emptying the recycle bin...

It did its thing for about 15 minutes then the Tivo rebooted. Every since it will boot back up for about 2 or 3 minutes then reboot again. I pulled the drive and found this in the tvlog logs...


Dec 30 07:02:05 (none) Recorder[347]: Recording 107429 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107428 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107425 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107424 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107423 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107422 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107421 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107420 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107419 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107418 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107417 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107416 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107415 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107414 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107413 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107412 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107411 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 107410 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 156178 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 112411 does not have forced delete
Dec 30 07:02:05 (none) Recorder[347]: Recording 112410 does not have forced delete
Dec 30 07:02:06 (none) Recorder[347]: Recording 121563 does not have forced delete
Dec 30 07:02:06 (none) Recorder[347]: Recording 106622 does not have forced delete
Dec 30 07:02:06 (none) Recorder[347]: Recording 106621 does not have forced delete


The problem is it doesn't stay booted long enough for the telnet to become active and I don't have a change to run the command to clean the file system. I can do kickstart 57 which completes in like 5 minutes then reboots to the same. I try kickstart 58 but instead of the GSOD I get the screen saying it's installing a software update. I hate to wipe the drive again because you all know how hard I worked to get passed that 20 minute reboots. I was hoping I can try to repair the MFS partitions instead of starting from scratch.

I found this section in \etc\rc.d\StageA_PreKickstart\rc.Sequence_700.CheckForPanic.sh


export EMERGENCY_REINSTALL=0
do_upgrade=0
do_mfs_assert=0
do_mfs_cleanup=0
do_factory_reset=0
do_aft_test=0
do_hdd_test=0
do_stageB_kickstart=0
do_repeat_guided_setup=0
do_forensic=0


it looked like I could set assert and cleanup to 1 and get it to check MFS but no luck. I guess I have to get it to panic mode before these switches come into play. Anyone know how to manually get it to panic mode?

Soapm
12-31-2011, 01:31 AM
Here is one round of the kernel logs in case someone sees something...

philhu
02-20-2013, 02:36 PM
I know this is late, but did you see this in the log?

Dec 30 06:58:44 (none) kernel: AACK! 4 seconds for 10 MB, write bandwidth is low, hard drive may be failing
Dec 30 06:58:44 (none) kernel: Performing basic S.M.A.R.T. checks
Dec 30 06:58:44 (none) kernel: This can cause DriveStatusError messages in some cases... don't worry.
Dec 30 06:58:44 (none) kernel: Checking /dev/hda
Dec 30 06:58:44 (none) kernel: S.M.A.R.T. pass on /dev/hda
Dec 30 06:58:44 (none) kernel: No forensic selected
Dec 30 06:58:46 (none) kernel: Obliterating PlanetX datum (it obstructs my view of Venus)...
Dec 30 06:58:46 (none) kernel: Where's the KABOOM? There's supposed to be an Earth-shattering KABOOM!

Soapm
02-21-2013, 10:05 PM
Yes, what is that? By the way, I reformatted and been using the same drive so I don't think it was a drive failure. I think I corrupted the database to the point it couldn't fix itself.

Dave20042004
02-22-2013, 03:07 PM
Maybe this is common...and few even notice? At least I know of four people now that are seeing "hard drive may be failing". According to lrhorer, he has run this way trouble free for 6 years and gives some insight here (http://www.dealdatabase.com/forum/showthread.php?p=316345#post316345).