Active Topics
-
Porting apps to Leste (40)
to Maemo 7 / Leste by Maemish - 1 day, 21 hrs ago -
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 6 days, 1 hr ago - more...
|
2010-04-21
, 17:57
|
|
Posts: 12 |
Thanked: 1 time |
Joined on Nov 2009
|
#2
|
I'm experiencing almost the same problems.
My N900 is complaining about errors on mmcblk0, any ideas?
The errors are:
Any ideas?
Last edited by Snow_King; 2010-04-21 at 18:02.
My N900 is complaining about errors on mmcblk0, any ideas?
The errors are:
[81613.395782] mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
[81613.395812] mmcblk0: error -110 transferring data, sector 56696903, nr 1, card status 0x0
[81613.395812] end_request: I/O error, dev mmcblk0, sector 56696903
[81613.395843] Buffer I/O error on device mmcblk0p2, logical block 8192
[81613.395965] mmcblk0: retrying using single block read
[81613.396057] mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
[81613.396087] mmcblk0: error -110 transferring data, sector 56696896, nr 8, card status 0x0
[81613.396118] end_request: I/O error, dev mmcblk0, sector 56696896
[81613.396179] mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
[81613.396209] mmcblk0: error -110 transferring data, sector 56696897, nr 7, card status 0x0
[81613.396240] end_request: I/O error, dev mmcblk0, sector 56696897
[81613.396331] mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
[81613.396362] mmcblk0: error -110 transferring data, sector 56696898, nr 6, card status 0x0
[81613.396362] end_request: I/O error, dev mmcblk0, sector 56696898
[81613.396453] mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
[81613.396484] mmcblk0: error -110 transferring data, sector 56696899, nr 5, card status 0x0
[81613.396514] end_request: I/O error, dev mmcblk0, sector 56696899
[81613.396575] mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
[81613.396606] mmcblk0: error -110 transferring data, sector 56696900, nr 4, card status 0x0
[81613.396636] end_request: I/O error, dev mmcblk0, sector 56696900
[81613.396697] mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
[81613.396728] mmcblk0: error -110 transferring data, sector 56696901, nr 3, card status 0x0
[81613.396759] end_request: I/O error, dev mmcblk0, sector 56696901
[81613.396850] mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/write command, response 0x0, card status 0x0
[81613.396881] mmcblk0: error -110 transferring data, sector 56696902, nr 2, card status 0x0
[81613.396881] end_request: I/O error, dev mmcblk0, sector 56696902
Last edited by Snow_King; 2010-04-21 at 18:02.
|
|
2010-04-28
, 09:01
|
|
Posts: 12 |
Thanked: 1 time |
Joined on Nov 2009
|
#3
|
I've just returned my N900 to a Nokia service point here in the Netherlands.
Attached you will find a letter i sent with my N900. Seems to me the internal memory is broken
EDIT: Attachment is to large, a download link: http://zooi.widodh.nl/forums/maemo-t...nokia_n900.pdf
Last edited by Snow_King; 2010-04-28 at 09:09.
Attached you will find a letter i sent with my N900. Seems to me the internal memory is broken
EDIT: Attachment is to large, a download link: http://zooi.widodh.nl/forums/maemo-t...nokia_n900.pdf
Last edited by Snow_King; 2010-04-28 at 09:09.
|
|
2010-05-25
, 09:46
|
|
Posts: 12 |
Thanked: 1 time |
Joined on Nov 2009
|
#4
|
Well, i got my phone back from the Noka Service Center for the second time and it's still broken, see my blog: http://blog.widodh.nl/2010/05/nokia-shame-on-you/
Shame on you Nokia.
Shame on you Nokia.
|
|
2010-05-28
, 07:45
|
|
Posts: 3 |
Thanked: 0 times |
Joined on Dec 2009
|
#5
|
Yesterday I got back N900 from service. It's a new device and it seems everything works ok. With device came a new 24 month warranty starting on May 26th. I'm happy about that.
But on the other side I find it strange that it took almost one month to resolve my issue - I handed over my device with 3 page description of a problem on April 27th. And that was a second time, first time device was "serviced" for a week in the first half of April and returned without any fix.
In the mean time I become a happy user of a different smartphone and will probably not switch back to N900. The main reason - servicing took to long so I had enough time to get used with new device, to move all my data, to customize my new device, ...
But on the other side I find it strange that it took almost one month to resolve my issue - I handed over my device with 3 page description of a problem on April 27th. And that was a second time, first time device was "serviced" for a week in the first half of April and returned without any fix.
In the mean time I become a happy user of a different smartphone and will probably not switch back to N900. The main reason - servicing took to long so I had enough time to get used with new device, to move all my data, to customize my new device, ...
|
|
2010-09-06
, 15:07
|
|
Posts: 15 |
Thanked: 12 times |
Joined on Jan 2010
|
#6
|
Same to me.
I'm so unhappy with the nokia care support. After 2 times of giving my device they did nothing. Third time they said that there was a file corrupted in the system (false suspicion), and that this kind of reparation isn't covered by warranty, So I had to pay 100 € to repair n900. I was not agree paying that, but they said that if I don't want to pay they'll send back the phone as I have sent. After paying THE DEVICE IS IN THE SAME STATE. I'm so sorry nokia. You re about to loose not only a customer, also a developer (I have developed support for icecast in n900, and Qice app).
Good OS but a customer service is a shame...
Also is a shame that you cannot contact the global office of nokia support. Only the local ones. And here in spain they are not doing the job...
Does anybody knows where I have to write to explain it to global nokia?
I'm so unhappy with the nokia care support. After 2 times of giving my device they did nothing. Third time they said that there was a file corrupted in the system (false suspicion), and that this kind of reparation isn't covered by warranty, So I had to pay 100 € to repair n900. I was not agree paying that, but they said that if I don't want to pay they'll send back the phone as I have sent. After paying THE DEVICE IS IN THE SAME STATE. I'm so sorry nokia. You re about to loose not only a customer, also a developer (I have developed support for icecast in n900, and Qice app).
Good OS but a customer service is a shame...
Also is a shame that you cannot contact the global office of nokia support. Only the local ones. And here in spain they are not doing the job...
Does anybody knows where I have to write to explain it to global nokia?
|
|
2010-10-29
, 21:25
|
|
Posts: 18 |
Thanked: 5 times |
Joined on Apr 2010
|
#7
|
I ran into the same problem. My mmcblk0p2 partition started to fall apart with a lot of badblocks and read errors.
I reflashed successfully with the RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin image.
then I tried to reflash the emmc and it failed.
After a lot of reflashing of the os image i finally got into the situation where i got the os installed and the mmcblk0p2 patition unmounted due to filesystem failure.
Then i put the n900 in r&d mode.
Ran
badblocks -w /dev/mmcblk0p2
several times.
I seems like the pattern writing by the badblocks application did the same job as a flash formatter and i got into a situation where there where o badblock left.
Then I ran
mkfs.ext3 /dev/mmcblk0p2
and
fsck.ext3 /dev/mmcblk0p2
Finally a last reflash of the os image
And to my surprise the phone was ok again!
I reflashed successfully with the RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin image.
then I tried to reflash the emmc and it failed.
After a lot of reflashing of the os image i finally got into the situation where i got the os installed and the mmcblk0p2 patition unmounted due to filesystem failure.
Then i put the n900 in r&d mode.
Ran
badblocks -w /dev/mmcblk0p2
several times.
I seems like the pattern writing by the badblocks application did the same job as a flash formatter and i got into a situation where there where o badblock left.
Then I ran
mkfs.ext3 /dev/mmcblk0p2
and
fsck.ext3 /dev/mmcblk0p2
Finally a last reflash of the os image
And to my surprise the phone was ok again!
| The Following User Says Thank You to bitwit For This Useful Post: | ||
|
|
2010-10-29
, 21:28
|
|
Posts: 18 |
Thanked: 5 times |
Joined on Apr 2010
|
#8
|
And I forgot, I had to recreate the folder /home/opt before the final os reflash so that the mounting worked.
 |
|
2012-04-30
, 12:04
|
|
Posts: 128 |
Thanked: 41 times |
Joined on Nov 2010
@ BONDY, FRANCE
|
#9
|
Try this: http://talk.maemo.org/showthread.php...37#post1199437
That's working for me.
That's working for me.
__________________
Mulder FOX
Nokia N900 PR1.3@1GHz
Mulder FOXNokia N900 PR1.3@1GHz
I managed to start X-Terminal and found out that /dev/mmcblk0p2 was not mounted on /home. Graphical elements were probably missing because I moved them to /home/opt according to instructions found here: http://wiki.maemo.org/Free_up_rootfs_space
I could not fix partition with e2fsck, reformat file system with mkfs.ext3 or flash the eMMC content. But managed to flash latest firmware according to instructions found here: http://wiki.maemo.org/Updating_the_firmware
I sent my N900 to official Nokia repair center, but it came back without being fixed - "nothing wrong with device" according to them.
Output from 'mount':
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,bulk_read,no_chk_data_crc)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /tmp type tmpfs (rw,noatime,size=1024k)
tmpfs on /var/run type tmpfs (rw,nosuid,noatime,size=256k,mode=755)
none on /dev type tmpfs (rw,noatime,size=10240k,mode=755)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noatime,size=65536k)
nodev on /sys/kernel/debug type debugfs (0)
/dev/mmcblk0p1 on /home/user/MyDocs type vfat (rw,noauto,nodev,noexec,nosuid,noatime,nodiratime, utf8,uid=29999,shortname=mixed,dmask=000,fmask=013 3,rodir)
Output from 'df -h':
Filesystem Size Used Available Use% Mounted on
rootfs 227.9M 162.8M 60.9M 73% /
ubi0:rootfs 227.9M 162.8M 60.9M 73% /
tmpfs 1.0M 60.0k 964.0k 6% /tmp
tmpfs 256.0k 68.0k 188.0k 27% /var/run
none 10.0M 72.0k 9.9M 1% /dev
tmpfs 64.0M 4.0k 64.0M 0% /dev/shm
/dev/mmcblk0p1 27.0G 648.5M 26.4G 2% /home/user/MyDocs
After trying to do 'mkfs.ext3 /dev/mmcblk0p2' I find such lines in output from 'dmesg':
[ 892.505706] mmcblk0: error -110 transferring data, sector 58743105, nr 7, card status 0x200900
[ 892.505737] end_request: I/O error, dev mmcblk0, sector 58743105
[ 892.516876] mmcblk0: error -110 transferring data, sector 58743106, nr 6, card status 0x200900
[ 892.516906] end_request: I/O error, dev mmcblk0, sector 58743106
[ 892.528045] mmcblk0: error -110 transferring data, sector 58743107, nr 5, card status 0x200900
[ 892.528076] end_request: I/O error, dev mmcblk0, sector 58743107
[ 892.539215] mmcblk0: error -110 transferring data, sector 58743108, nr 4, card status 0x200900
[ 892.539245] end_request: I/O error, dev mmcblk0, sector 58743108
[ 892.550384] mmcblk0: error -110 transferring data, sector 58743109, nr 3, card status 0x200900
[ 892.550415] end_request: I/O error, dev mmcblk0, sector 58743109
[ 892.551727] Buffer I/O error on device mmcblk0p2, logical block 263968
For me it looks like there is some hardware problem with internal flash memory (eMMC), some kind of bad sectors?
Did I miss something? Should I try something else? How to explain Nokia repair center that device is not fully functional?
I could probably repartition the flash (according to instructions found here: http://wiki.maemo.org/Repartitioning_the_flash)
to avoid problematic part of flash, but I want to have device without any such hardware problems (if it's hw problem).