Freezing on restore

[birdman]

Given that mtd knows where the partitions are, why are they given as parameters to ofgwrite, rather than just let it use what it finds?

And if they are there for a sanity check, then the failure should be reported to the user. This is what ofgwrite reports when given the wrong device info:

Found /proc/mtd entries:
Device:   Size:     Erasesize:  Name:                   Image:
mtd0:     1ff00000  00020000    "complete"        
mtd1:     00600000  00020000    "kernel"            <-  Error: Selected by user is not a rootfs mtd!!
mtd2:     1f900000  00020000    "rootfs"            <-  Error: Selected by user is not a kernel mtd!!
mtd3:     00080000  00010000    "cfe"             
mtd4:     00200000  00010000    "splash"          
mtd5:     00080000  00010000    "macadr"          
mtd6:     00080000  00010000    "nvram"           
mtd7:     00040000  00010000    "bootconfig"      
mtd8:     00040000  00010000    "facconfig"       
Using kernel mtd device: /dev/mtd2
Using rootfs mtd device: /dev/mtd1
Error: User selected mtd device cannot be used!

I'd expect that last line at least to end up being shown to the user. Perhaps it is, but then ofgwrite immediately exits so the user gets taken straight back to the imagemanager screen and loses the error message. Perhaps ofgwrite needs to add a wait after all of its error reports....currently there are none.

 

[abu baniaz]

In a nutshell, would you say that installing the football plugin causes the issue? Maybe filling flash memory?

If so ,we can let author know and he can improve it.

 

[birdman]

and a screenshot - note that the problem with the device message is only because I removed the pen drive to get the log files

Better to shut the box down before removing the USB stick. Or just FTP the log file off the box.

 

[insertusername]

Better to shut the box down before removing the USB stick. Or just FTP the log file off the box.

will do that next time

 

[insertusername]

In a nutshell, would you say that installing the football plugin causes the issue? Maybe filling flash memory?

If so ,we can let author know and he can improve it.

It definitely was one of the scenarios which triggered a crash. After installing the plugin, the box upon reboot locked with the fast spinner. This does not happen with openatv.

However, the boot also crashed with a settings restore with absolutely no plugins installed - only the initial first time boot screens completed and then straight to backup settings. settings backed up, but regardless of whether I started with a fresh image or simply did a restore factory settings if I tried to restore the settings backup (containing no more than 28.2e, internet, HDMI) that also crashed with a fast spinner - Irrespective of the live football or any otherplugin.

 

[Piranha]

@insertusername - just a thought - as you have restored factory settings at least once, have you then flashed the latest bootloader for your box before flashing the latest image? Also, the symptoms you describe make me think that something is writing to flash memory and filling it - maybe EPG? I would also check the mounts settings of your storage devices.

Good luck!