maemo.org - Talk - "Unable to perform operation. Internal error" msg keeps popping up a lot of times after start up

maemo.org - Talk (https://talk.maemo.org/index.php)

- Maemo 5 / Fremantle (https://talk.maemo.org/forumdisplay.php?f=40)

Re: "Unable to perform operation. Internal error" msg keeps popping up a lot of times after start up

I don't mind loosing the data. I have everything backed up!
I only worry i might do any additional damage to the phone, as i am not so experienced. Before i mess with my N900 i always go through cureful reading of the threads and the wisdom that is share here..
If i reflash it, does anyone know if it will get back to normal?

Re: "Unable to perform operation. Internal error" msg keeps popping up a lot of times after start up

Quote:

Originally Posted by koznj (Post 1344354)

you will have to flash both rootfs and emmc.
Yes it will go back to normal but you will lose all data and files on your n900.
I tried checking the mmcblk0p2 using backupmenu and force fsck but it doesn't fixes the issue.

Re: "Unable to perform operation. Internal error" msg keeps popping up a lot of times after start up

@raaj13 Thnk u for your time mate. Really appreciate it!
And the irony is, that i bought this (second) N900 from a friend, because i have a broken usb port in mine. The one with the broken port, works fine.. haha
Anyway, i have to go through a lot of reading again, because i have never reflashed my device since 2009 and i have no idea.. This will be funny (o:

I tried also sfdisk -l and this is what i get

HTML Code:

# sfdisk -l 



Disk /dev/mmcblk1: 124368 cylinders, 4 heads, 16 sectors/track

Warning: The partition table looks like it was made

for C/H/S=*/7/6 (instead of 124368/4/16).

For this listing I'll assume that geometry.

Units = cylinders of 21504 bytes, blocks of 1024 bytes, counting from 0



Device Boot Start End #cyls #blocks Id System

/dev/mmcblk1p1 195+ 189513- 189319- 3975680 b W95 FAT32

start: (c,h,s) expected (195,0,3) found (1,2,3)

end: (c,h,s) expected (1023,6,6) found (987,6,6)

/dev/mmcblk1p2 0 - 0 0 0 Empty

/dev/mmcblk1p3 0 - 0 0 0 Empty

/dev/mmcblk1p4 0 - 0 0 0 Empty



Disk /dev/mmcblk0: 977024 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 1 884864 884864 28315648 c W95 FAT32 (LBA)

/dev/mmcblk0p2 884865 950400 65536 2097152 83 Linux

/dev/mmcblk0p3 950401 974976 24576 786432 82 Linux swap / Solaris

/dev/mmcblk0p4 0 - 0 0 0 Empty

Any ideas?

Re: "Unable to perform operation. Internal error" msg keeps popping up a lot of times after start up

You could try to disable the optfs partition, reboot to check the partition, then enable the partition and reboot to check the outcome.

This is the detailed procedure:

Code:

sudo gainroot

sfdisk -c /dev/mmcblk0 2 0

Reboot

Code:

sudo gainroot

fsck -af /dev/mmcblk0p2

fsck -af /dev/mmcblk0p2

Yes, do it twice!
If still errors in the file system check try the -r option for a repair like this: fsck -r /dev/mmcblk0p2
If no errors occur any more, enable the partition

Code:

sfdisk -c /dev/mmcblk0 2 83

Reboot to look for success of the proceedings!
Hope it helps!

Re: "Unable to perform operation. Internal error" msg keeps popping up a lot of times after start up

Quote:

Originally Posted by michaaa62 (Post 1344552)

You could try to disable the optfs partition, reboot to check the partition, then enable the partition and reboot to check the outcome.

This is the detailed procedure:

Code:

sudo gainroot

sfdisk -c /dev/mmcblk0 2 0

Reboot

Code:

sudo gainroot

fsck -af /dev/mmcblk0p2

fsck -af /dev/mmcblk0p2

Yes, do it twice!
If still errors in the file system check try the -r option for a repair like this: fsck -r /dev/mmcblk0p2
If no errors occur any more, enable the partition

Code:

sfdisk -c /dev/mmcblk0 2 83

Reboot to look for success of the proceedings!
Hope it helps!

And after an hour of endless pressing of the y and repairing lots of stuff, it gets to a point that it stops..

Error deallocating inode 66809: Illegal doubly indirect block found
e2fsck: aborted
And if i run again fsck -r /dev/mmcblk0p2 it seems like, it is repairing the same things over and ovr

HTML Code:

Connect to /lost+found<y>? yes



Inode 65963 ref count is 2, should be 1.  Fix<y>? yes



Inode 65972 (...) has invalid mode (00).

Clear<y>? yes



Inode 65979 (...) has invalid mode (00).

Clear<y>? yes



Inode 65980 (...) has invalid mode (00).

Clear<y>? yes



Inode 65981 (...) has invalid mode (00).

Clear<y>? yes



Inode 65982 (...) has invalid mode (00).

Clear<y>? yes



Inode 65983 (...) has invalid mode (00).

Clear<y>? yes



Inode 65984 (...) has invalid mode (00).

Clear<y>? yes



Inode 65985 (...) has invalid mode (00).

Clear<y>? yes



Unattached inode 66207

Connect to /lost+found<y>? yes



Inode 66207 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66297

Connect to /lost+found<y>? yes



Inode 66297 ref count is 2, should be 1.  Fix<y>? yes



Inode 66307 (...) has invalid mode (00).

Clear<y>? yes



WARNING: PROGRAMMING BUG IN E2FSCK!

        OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.

inode_link_info[66317] is 5, inode.i_links_count is 0.  They should be the same!

Inode 66317 ref count is 0, should be 4.  Fix<y>? yes



WARNING: PROGRAMMING BUG IN E2FSCK!

        OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.

inode_link_info[66318] is 3, inode.i_links_count is 0.  They should be the same!

Inode 66318 ref count is 0, should be 2.  Fix<y>? yes



WARNING: PROGRAMMING BUG IN E2FSCK!

        OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.

inode_link_info[66319] is 4, inode.i_links_count is 0.  They should be the same!

Inode 66319 ref count is 0, should be 3.  Fix<y>? yes



Inode 66320 (...) has invalid mode (00).

Clear<y>? yes



Inode 66321 (...) has invalid mode (00).

Clear<y>? yes



Inode 66322 (...) has invalid mode (00).

Clear<y>? yes



Inode 66323 (...) has invalid mode (00).

Clear<y>? yes



Inode 66324 (...) has invalid mode (00).

Clear<y>? yes



WARNING: PROGRAMMING BUG IN E2FSCK!

        OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.

inode_link_info[66325] is 3, inode.i_links_count is 0.  They should be the same!

Inode 66325 ref count is 0, should be 2.  Fix<y>? yes



Inode 66328 (...) has invalid mode (00).

Clear<y>? yes



Inode 66330 (...) has invalid mode (00).

Clear<y>? yes



Inode 66331 (...) has invalid mode (00).

Clear<y>? yes



Inode 66332 (...) has invalid mode (00).

Clear<y>? yes



Inode 66333 (...) has invalid mode (00).

Clear<y>? yes



Inode 66334 (...) has invalid mode (00).

Clear<y>? yes



Inode 66335 (...) has invalid mode (00).

Clear<y>? yes



Inode 66336 (...) has invalid mode (00).

Clear<y>? yes



Inode 66337 (...) has invalid mode (00).

Clear<y>? yes



Inode 66338 (...) has invalid mode (00).

Clear<y>? yes



Inode 66339 (...) has invalid mode (00).

Clear<y>? yes



Inode 66340 (...) has invalid mode (00).

Clear<y>? yes



Inode 66419 ref count is 6, should be 3.  Fix<y>? yes



Unattached inode 66427

Connect to /lost+found<y>? yes



Inode 66427 ref count is 2, should be 1.  Fix<y>? yes



Inode 66561 ref count is 6, should be 5.  Fix<y>? yes



Unattached inode 66617

Connect to /lost+found<y>? yes



Inode 66617 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66693

Connect to /lost+found<y>? yes



Inode 66693 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66794

Connect to /lost+found<y>? yes



Inode 66794 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66795

Connect to /lost+found<y>? yes



Inode 66795 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66797

Connect to /lost+found<y>? yes



Inode 66797 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66799

Connect to /lost+found<y>? yes



Inode 66799 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66800

Connect to /lost+found<y>? yes



Inode 66800 ref count is 2, should be 1.  Fix<y>? yes



Inode 66802 (...) has invalid mode (0160276).

Clear<y>? yes



Inode 66803 (...) has invalid mode (0160425).

Clear<y>? yes



i_faddr for inode 66806 (...) is 90226, should be zero.

Clear<y>? yes



i_blocks_hi for inode 66806 (...) is 16, should be zero.

Clear<y>? yes



Extended attribute block for inode 66806 (...) is invalid (842021155).

Clear<y>? yes



Unattached inode 66806

Connect to /lost+found<y>? yes



WARNING: PROGRAMMING BUG IN E2FSCK!

        OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.

inode_link_info[66806] is 2, inode.i_links_count is 12593.  They should be the same!

Inode 66806 ref count is 12593, should be 1.  Fix<y>? yes



Inode 66808 (...) is an illegal block device.

Clear<y>? yes



Symlink ... (inode #66809) is invalid.

Clear<y>? yes



Error deallocating inode 66809: Illegal doubly indirect block found

e2fsck: aborted

/home/user #

Now what? (o:
Thank you for your time..

Re: "Unable to perform operation. Internal error" msg keeps popping up a lot of times after start up

@michaaa62 - TBH I think his FS is FUBAR, a flash is imminent :)

Re: "Unable to perform operation. Internal error" msg keeps popping up a lot of times after start up

Quote:

Originally Posted by koznj (Post 1344601)

HTML Code:

Connect to /lost+found<y>? yes



Inode 65963 ref count is 2, should be 1.  Fix<y>? yes



Inode 65972 (...) has invalid mode (00).

Clear<y>? yes



Inode 65979 (...) has invalid mode (00).

Clear<y>? yes



Inode 65980 (...) has invalid mode (00).

Clear<y>? yes



Inode 65981 (...) has invalid mode (00).

Clear<y>? yes



Inode 65982 (...) has invalid mode (00).

Clear<y>? yes



Inode 65983 (...) has invalid mode (00).

Clear<y>? yes



Inode 65984 (...) has invalid mode (00).

Clear<y>? yes



Inode 65985 (...) has invalid mode (00).

Clear<y>? yes



Unattached inode 66207

Connect to /lost+found<y>? yes



Inode 66207 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66297

Connect to /lost+found<y>? yes



Inode 66297 ref count is 2, should be 1.  Fix<y>? yes



Inode 66307 (...) has invalid mode (00).

Clear<y>? yes



WARNING: PROGRAMMING BUG IN E2FSCK!

        OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.

inode_link_info[66317] is 5, inode.i_links_count is 0.  They should be the same!

Inode 66317 ref count is 0, should be 4.  Fix<y>? yes



WARNING: PROGRAMMING BUG IN E2FSCK!

        OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.

inode_link_info[66318] is 3, inode.i_links_count is 0.  They should be the same!

Inode 66318 ref count is 0, should be 2.  Fix<y>? yes



WARNING: PROGRAMMING BUG IN E2FSCK!

        OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.

inode_link_info[66319] is 4, inode.i_links_count is 0.  They should be the same!

Inode 66319 ref count is 0, should be 3.  Fix<y>? yes



Inode 66320 (...) has invalid mode (00).

Clear<y>? yes



Inode 66321 (...) has invalid mode (00).

Clear<y>? yes



Inode 66322 (...) has invalid mode (00).

Clear<y>? yes



Inode 66323 (...) has invalid mode (00).

Clear<y>? yes



Inode 66324 (...) has invalid mode (00).

Clear<y>? yes



WARNING: PROGRAMMING BUG IN E2FSCK!

        OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.

inode_link_info[66325] is 3, inode.i_links_count is 0.  They should be the same!

Inode 66325 ref count is 0, should be 2.  Fix<y>? yes



Inode 66328 (...) has invalid mode (00).

Clear<y>? yes



Inode 66330 (...) has invalid mode (00).

Clear<y>? yes



Inode 66331 (...) has invalid mode (00).

Clear<y>? yes



Inode 66332 (...) has invalid mode (00).

Clear<y>? yes



Inode 66333 (...) has invalid mode (00).

Clear<y>? yes



Inode 66334 (...) has invalid mode (00).

Clear<y>? yes



Inode 66335 (...) has invalid mode (00).

Clear<y>? yes



Inode 66336 (...) has invalid mode (00).

Clear<y>? yes



Inode 66337 (...) has invalid mode (00).

Clear<y>? yes



Inode 66338 (...) has invalid mode (00).

Clear<y>? yes



Inode 66339 (...) has invalid mode (00).

Clear<y>? yes



Inode 66340 (...) has invalid mode (00).

Clear<y>? yes



Inode 66419 ref count is 6, should be 3.  Fix<y>? yes



Unattached inode 66427

Connect to /lost+found<y>? yes



Inode 66427 ref count is 2, should be 1.  Fix<y>? yes



Inode 66561 ref count is 6, should be 5.  Fix<y>? yes



Unattached inode 66617

Connect to /lost+found<y>? yes



Inode 66617 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66693

Connect to /lost+found<y>? yes



Inode 66693 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66794

Connect to /lost+found<y>? yes



Inode 66794 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66795

Connect to /lost+found<y>? yes



Inode 66795 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66797

Connect to /lost+found<y>? yes



Inode 66797 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66799

Connect to /lost+found<y>? yes



Inode 66799 ref count is 2, should be 1.  Fix<y>? yes



Unattached inode 66800

Connect to /lost+found<y>? yes



Inode 66800 ref count is 2, should be 1.  Fix<y>? yes



Inode 66802 (...) has invalid mode (0160276).

Clear<y>? yes



Inode 66803 (...) has invalid mode (0160425).

Clear<y>? yes



i_faddr for inode 66806 (...) is 90226, should be zero.

Clear<y>? yes



i_blocks_hi for inode 66806 (...) is 16, should be zero.

Clear<y>? yes



Extended attribute block for inode 66806 (...) is invalid (842021155).

Clear<y>? yes



Unattached inode 66806

Connect to /lost+found<y>? yes



WARNING: PROGRAMMING BUG IN E2FSCK!

        OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.

inode_link_info[66806] is 2, inode.i_links_count is 12593.  They should be the same!

Inode 66806 ref count is 12593, should be 1.  Fix<y>? yes



Inode 66808 (...) is an illegal block device.

Clear<y>? yes



Symlink ... (inode #66809) is invalid.

Clear<y>? yes



Error deallocating inode 66809: Illegal doubly indirect block found

e2fsck: aborted

/home/user #

Now what? (o:
Thank you for your time..

you need to reflash your n900.
I already mentioned that i tried fsck on mcblk0p2 but it never fixes anything .

Re: "Unable to perform operation. Internal error" msg keeps popping up a lot of times after start up

Quote:

Originally Posted by raaj13 (Post 1344630)

you need to reflash your n900.
I already mentioned that i tried fsck on mcblk0p2 but it never fixes anything .

I didn't quite got that on your last post..
It is the first time that my n900 needs a doctor.
Now i see what you mean buddy.
One last question and i will stop bothering you people..
If i follow the instructions on that video http://www.youtube.com/watch?v=E1zvRjL-2cM, is it okay or there are any changes that i don't know? Because it is dated back in Feb. 2011.
Thnks (again)(o:

Re: "Unable to perform operation. Internal error" msg keeps popping up a lot of times after start up

I was having exactly the same issue a few days back. /home somehow became read-only. So what I did was using this to get into mass storage mode and check the file system with GParted in Ubuntu. And it worked fine.

I don't know if things can still be fixed like this in your case, as it looks so f*cked up. But since you already backed things up, I think reflashing might be better for system stability.

Flashing guide http://wiki.maemo.org/Updating_the_firmware
Nokia took down the repository for images and flasher, so these are mirrors:
Images http://skeiron.org/tablets-dev/nokia_N900/
Flasher http://skeiron.org/tablets-dev/maemo_dev_env_downloads/

Flashing procedure is the same, just need to pay attention to the filename of the image.

I think you only need to flash rootfs, so don't flash the eMMC and MyDocs will be intact.

Re: "Unable to perform operation. Internal error" msg keeps popping up a lot of times after start up

Looks bad :(
How sophisticated are your linux skills?

You could try to check the file system from an external linux PC, be that running installed linux or a Live-CD, IF you have backupmenu installed on the N900. A modern linux has a far advanced fsck application compared to the aging maemo system. This would be my No.1 option.

You could copy all the files from the partition to another linux file system to keep the file permissions, create the file system of the partition fresh and copy the backup to the new file system, but that might also copy the corrupted files.

Well there are some cases also in this forum, where the internal memory simply deteriorates. That would make both possibilities worthless...

For both of these methods you would need to make the partition active

Code:

sudo gainroot

sfdisk -c /dev/mmcblk0 2 83