Reply
Thread Tools
hoggerz's Avatar
Posts: 56 | Thanked: 35 times | Joined on Oct 2009
#1
Hi,
I noticed my N9 seems a little laggy recently, so I looked in dmesg noticed lots of the following:
onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x88
onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0

These occur frequently throughout. I also noticed :

EXT4-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended

Has anyone else noticed these errors? And is there any easy way to fix them without having to return the device under warranty?
Thanks for any help

Hoggerz
 
misterc's Avatar
Posts: 1,625 | Thanked: 998 times | Joined on Aug 2010
#2
Originally Posted by hoggerz View Post
Hi,
I noticed my N9 seems a little laggy recently, so I looked in dmesg noticed lots of the following:
onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x88
onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0

These occur frequently throughout. I also noticed :

EXT4-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended

Has anyone else noticed these errors? And is there any easy way to fix them without having to return the device under warranty?
Thanks for any help

Hoggerz
what is the output of
Code:
 fdisk -l /dev/mmcblk0
?
__________________
information is a necessary though no sufficient condition to rationality...
 
hoggerz's Avatar
Posts: 56 | Thanked: 35 times | Joined on Oct 2009
#3
Hi,
thanks for reply, I get:

Disk /dev/mmcblk0: 1957120 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 16 1760511 1760496 56335872 c W95 FAT32 (LBA)
/dev/mmcblk0p2 1760512 1891583 131072 4194304 0 Empty
/dev/mmcblk0p3 1891584 1957119 65536 2097152 83 Linux
/dev/mmcblk0p4 0 - 0 0 0 Empty

hoggerz
 
misterc's Avatar
Posts: 1,625 | Thanked: 998 times | Joined on Aug 2010
#4
Originally Posted by hoggerz View Post
Hi,
thanks for reply, I get:

Disk /dev/mmcblk0: 1957120 cylinders, 4 heads, 16 sectors/track
Units = cylinders of 32768 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End #cyls #blocks Id System
/dev/mmcblk0p1 16 1760511 1760496 56335872 c W95 FAT32 (LBA)
/dev/mmcblk0p2 1760512 1891583 131072 4194304 0 Empty
/dev/mmcblk0p3 1891584 1957119 65536 2097152 83 Linux
/dev/mmcblk0p4 0 - 0 0 0 Empty


hoggerz
refer to this post to become root and try
Code:
 tune2fs -i 0 /dev/mmcblk0p2
might want to do it for /dev/mmcblk0p4 as well while at it...

mind yourself, enabling devel-su will show a warning; live with it just for this once & disable it again once done...
__________________
information is a necessary though no sufficient condition to rationality...
 

The Following User Says Thank You to misterc For This Useful Post:
hoggerz's Avatar
Posts: 56 | Thanked: 35 times | Joined on Oct 2009
#5
Heres what I get from those two:


~ # /sbin/tune2fs -i 0 /dev/mmcblk0p2
tune2fs 1.41.12maemo1 (17-May-2010)
Setting interval between checks to 0 seconds
~ # /sbin/tune2fs -i 0 /dev/mmcblk0p4
tune2fs 1.41.12maemo1 (17-May-2010)
/sbin/tune2fs: No such file or directory while trying to open /dev/mmcblk0p4
Couldn't find valid filesystem superblock.

Any idea what the problem is/was?

thanks

hoggerz
 
misterc's Avatar
Posts: 1,625 | Thanked: 998 times | Joined on Aug 2010
#6
Originally Posted by hoggerz View Post
[...]

Any idea what the problem is/was?

thanks

hoggerz
my mistake
p4 looks indeed completely messed up
Device Boot Start End #cyls #blocks Id System
[...]
/dev/mmcblk0p4 0 - 0 0 0 Empty
can't help wondering who came up with that partitioning
__________________
information is a necessary though no sufficient condition to rationality...
 
hoggerz's Avatar
Posts: 56 | Thanked: 35 times | Joined on Oct 2009
#7
Hi,
I rebooted and checked dmesg again but i still get the same errors, do i have to do that command each time I restart, or is my n9 probably dying?

Thanks

hoggerz
 
Posts: 19 | Thanked: 20 times | Joined on Sep 2011
#8
hi, i have th same EEC corectable errors, i idea how can we fix them? Do you find more info for correct them?
sorry my english.
if you need to test something tell me.
 
Posts: 477 | Thanked: 1,277 times | Joined on Jan 2012 @ Enschede, The Netherlands
#9
It has been discussed before, so I refer to my earlier post. Moreover, under some conditions "stuck" bits can get "unstuck", effictively repairing itself. Unless you have serious issues or the log is full with these messages, I wouldn't mind an occasional ECC message too much.
 
Posts: 1,225 | Thanked: 1,905 times | Joined on Feb 2011 @ Quezon City, Philippines
#10
Originally Posted by hoggerz View Post
Hi,
I noticed my N9 seems a little laggy recently, so I looked in dmesg noticed lots of the following:
onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x88
onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0


These occur frequently throughout. I also noticed :

EXT4-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
These two (emphasis mine) are completely coincidental.
The OneNAND is on a separate chip from the eMMC.

The OneNAND sits on top of the OMAP and is largely unused (~240 MB free, if you want to use it for some bizarre purpose like install an emergency rootfs on there), save for the CAL, bootloader and kernel.
The eMMC, which stores the rootfs and user data is a separate chip on the board.

"Maximum mount count reached" just means that the partition has been mounted >~30 times. Nothing to worry about, but if you want to shut it up, load up the Rescue Initrd and run "tune2fs -c 0 -i 0 /dev/mmcblk0p3".
__________________
N9 PR 1.3 Open Mode + kernel-plus for Harmattan
@kenweknot, working on Glacier for Nemo.

Last edited by Hurrian; 2012-10-06 at 15:20.
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 01:12.