maemo.org - Talk - Bad microSD

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

- Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)

- - Bad microSD (https://talk.maemo.org/showthread.php?t=70974)

AndrewX192

2011-03-13 09:12

Bad microSD

Hey folks,

Does anyone want to confirm that the errors I am getting (see http://pastebin.com/QTKKFBbj) indicate a problem with the microSD card, or is it possible that the phone itself has an issue?

I am using a 32GB class 10 microSD card.

raaj13

2011-03-13 10:58

Re: Bad microSD

Quote:

Originally Posted by AndrewX192 (Post 966715)

is the card new or old one?

michaaa62

2011-03-13 12:05

Re: Bad microSD

There is not much evidence that the phone itself is affected. The dmesg output just shows errors for one partition. This might further indicate to the external card, may be just this one partition being corrupted. Try to fsck the partition, possibly with repair options.

Code:

sudo gainroot

umount /dev/mmcblk1p6

fsck -af /dev/mmcblk1p6

fsck -r /dev/mmcblk1p6

Remount the partition to check for errors in kernel messages again.

AndrewX192

2011-03-13 15:38

Re: Bad microSD

Quote:

Originally Posted by raaj13 (Post 966754)

is the card new or old one?

This is a new card. (See http://www.newegg.com/Product/Produc...82E16820220547)

AndrewX192

2011-03-13 15:39

Re: Bad microSD

Quote:

Originally Posted by michaaa62 (Post 966787)

Code:

sudo gainroot

umount /dev/mmcblk1p6

fsck -af /dev/mmcblk1p6

fsck -r /dev/mmcblk1p6

Remount the partition to check for errors in kernel messages again.

The partition has corrupted multiple times, and fsck was not able to help, the only solution was to re-create the fs, which would work for a while, until I actually tried to use it (eg: apt-get upgrade in easy debian) and then it would corrupt.

raaj13

2011-03-13 16:23

Re: Bad microSD

Well did You tried formatting the whole card?
If fsck didn't help recreating fs didn't help then you can try replacing it It's under warranty I assume.

michaaa62

2011-03-13 19:19

Re: Bad microSD

Well you did not mention Easy Debian before....
Did you try to fsck the EasyDebian-Image itself? Which version of the image do you use?
Hope someone knowledgable people about Easy Debian chip in, because i just know nothing about it.

AndrewX192

2011-03-14 05:33

Re: Bad microSD

Quote:

Originally Posted by raaj13 (Post 966906)

Well did You tried formatting the whole card?
If fsck didn't help recreating fs didn't help then you can try replacing it It's under warranty I assume.

No I have not done that yet, that will be my next step.

Quote:

Originally Posted by michaaa62 (Post 966982)

I copied image in the standard way I have done for my other microSD card (mounting both microSD cards and copying the files over - preserving permissions)

AndrewX192

2011-03-16 05:48

Re: Bad microSD

This is starting to look more like an issue with the Nokia N900, as I am having problems reproducing this error on my netbook.
Has anyone been able to get a 32GB microSD to work propery in the Nokia N900?
UPDATE - 03/16/2011 13:50PST: Patriot Memory suggested switching out the microSD for a class 6 microSD, incase this is compatibility issue.

AndrewX192

2011-03-17 07:33

Re: Bad microSD

From further research, I can only reproduce the issue when I am using Maemo5 to access the microSD card, when I use "Mass Storage Mode" and copy files onto the microSD card from my computer, the issue goes away.

So, this leads me to ask a few questions:

1) Is there a incompatibility in the Linux Kernel (2.6.28.10power46) on the Nokia N900 with 32GB class 10 microSD cards?

2) Has anyone tried a 32GB microSD card with Maemo5? - and did it work properly?

3) Has anyone tried a class 10 microSD with Maemo5? - and did it work properly?

4) Is there any way to upgrade the kernel beyond 2.6.28 on the Nokia N900?

chemist

2011-03-17 08:32

Re: Bad microSD

1 not afaik
2 yes there was a "does work" some time ago, you may google
3 yes
4 yes

EDIT: some cards - some vendors just do a mess, like sandisk never worked for me

abill_uk

2011-03-17 09:09

Re: Bad microSD

Quote:

Originally Posted by AndrewX192 (Post 969456)

The problem your having sounds like the sd card is not making contact with the sprung pins, take out the card and make sure the little plate it is slotted into has a dent facing towards the card so that it pushes as much as possible making a tight fit when you push the 2 lips under the retainers either side.

More often than not problems happen because the sd card is not making proper contact on the sprung loaded tiny contacts it sits on top of.

This is in my opinion another hardware design fault as it keeps coming up on this forum in many weird forms of problems.

I have used both 16 and 32gb versions with no problems whatsoever but i have made sure the sd card is pushed as hard as possible against the contacts.

Problems related are as follows,
Device not seeing the sd card,
See's the sd card now and then,
Only part of the sd card is recognised,
Gives weird messages like sd card not formatted or data is corrupted.

retsaw

2011-03-17 09:44

Re: Bad microSD

There is a simple Windows utility (it runs using Wine on Linux as well) called h2testw which was designed to detect fake USB drives (ones which lie about their true capacity), it does this by writing large files then verifying it can read them back properly. It may be worth trying this to check your MicroSD card is working properly, but it will take quite a while to check a 32GB card.

AndrewX192

2011-03-17 15:04

Re: Bad microSD

Quote:

Originally Posted by abill_uk (Post 969500)

This does not explain why the card works when it is used via "Mass Storage Mode". If it was the pins, then mass storage mode should not work either.

geneven

2011-03-17 15:09

Re: Bad microSD

Quote:

Originally Posted by AndrewX192 (Post 968710)

I have had no problems with my 32GB microSD and the Nokia N900. I think mine is a class 10 -- It cost enough!

abill_uk

2011-03-17 15:16

Re: Bad microSD

Quote:

Originally Posted by AndrewX192 (Post 969690)

This does not explain why the card works when it is used via "Mass Storage Mode". If it was the pins, then mass storage mode should not work either.

I hear what you are saying and yes on the surface it does sound a software issue but before you can be certain of this you must make sure there is no hardware issue.

To check that the sd card is sitting properly and is tightly pinned down onto the contacts will cost you no more than a few minutes of your time, if that is ok then you have to check the sd card itself either by the method explained by Retsaw or a similar routine, failing this not being the issue and your sd card checks out ok then what is there left?... your device itself and to put that right, if it was me instead of running around in circles taking up much time and effort i would simply relash both images and start again.

If you have done a backup this does not take long at all in comparison to the amount of time you will spend running routines with no real answers.

All your answers are within this post if you look and get rid of possible causes one by one, you will eventually find your answer.

Good luck it is worth the effort i tell you.

shadowjk

2011-03-17 19:09

Re: Bad microSD

In mass-storage mode the kernel is providing access to the microsd card through the usb port. So, that means that the kernel is perfectly able to talk to the card.

N770-Freak

2011-03-18 18:06

Re: Bad microSD

I also bought a Patriot 32GB microsdhc class 10 card today.

So far I had not any issues (at least I didn't notice any). But looking into dmesg shows also a few lines with I/O errors:

Code:

[41945.280578] mmcblk1: error 1 sending read/write command, response 0x0, card status 0x900

[41945.280609] mmcblk1: error 1 transferring data, sector 59950448, nr 8, card status 0x900

[41945.280670] end_request: I/O error, dev mmcblk1, sector 59950448

[41945.280700] Buffer I/O error on device mmcblk1p2, logical block 414886

[41945.280731] lost page write due to I/O error on mmcblk1p2

AndrewX192

2011-03-18 18:35

Re: Bad microSD

Quote:

Originally Posted by N770-Freak (Post 970491)

I also bought a Patriot 32GB microsdhc class 10 card today.

So far I had not any issues (at least I didn't notice any). But looking into dmesg shows also a few lines with I/O errors:

Code:

[41945.280578] mmcblk1: error 1 sending read/write command, response 0x0, card status 0x900

[41945.280609] mmcblk1: error 1 transferring data, sector 59950448, nr 8, card status 0x900

[41945.280670] end_request: I/O error, dev mmcblk1, sector 59950448

[41945.280700] Buffer I/O error on device mmcblk1p2, logical block 414886

[41945.280731] lost page write due to I/O error on mmcblk1p2

That looks like the issue I am having.

jurop88

2011-03-18 20:48

Re: Bad microSD

I read some other thread here speaking about fs corruptions while unpacking easydebian, sometimes leading to N900 to crash. I think it's something related to heavy input/ouput and swap activity kicking in, simply N900 hardware not coping, and not dependent on SD dimension or class. Don't know if it's a similar problem but try to look for that.

AndrewX192

2011-03-20 01:53

Re: Bad microSD

Quote:

Originally Posted by N770-Freak (Post 970491)

I also bought a Patriot 32GB microsdhc class 10 card today.

So far I had not any issues (at least I didn't notice any). But looking into dmesg shows also a few lines with I/O errors:

Code:

[41945.280578] mmcblk1: error 1 sending read/write command, response 0x0, card status 0x900

[41945.280609] mmcblk1: error 1 transferring data, sector 59950448, nr 8, card status 0x900

[41945.280670] end_request: I/O error, dev mmcblk1, sector 59950448

[41945.280700] Buffer I/O error on device mmcblk1p2, logical block 414886

[41945.280731] lost page write due to I/O error on mmcblk1p2

Have you had any luck resolving your issue? I am going to have to downgrade to a class 6 or 4 if no fix can be found.

N770-Freak

2011-03-20 07:14

Re: Bad microSD

Quote:

Originally Posted by AndrewX192 (Post 971337)

Have you had any luck resolving your issue? I am going to have to downgrade to a class 6 or 4 if no fix can be found.

Actually these 4 error lines were the only ones until now. And I didn't notice any problems because of this error. The card is working since two days now.

I've downloaded a 700MB distro image over wlan to the sdhc and md5sum was ok. No errors occured. Reading from the card is also ok. No filesystem corruption.

If you have any specific usecase I should reproduce to force a filesystem corruption, I'll test it for you.

Maybe your card is faulty and you should replace it with another class 10 card.

AndrewX192

2011-03-20 07:20

Re: Bad microSD

Quote:

Originally Posted by N770-Freak (Post 971452)

Can you try setting up an easydebian image on it, and do basic APT operations?
Also, I was able to get fs corruption when deleting files.

N770-Freak

2011-03-20 07:34

Re: Bad microSD

Quote:

Originally Posted by AndrewX192 (Post 971454)

Can you try setting up an easydebian image on it, and do basic APT operations?
Also, I was able to get fs corruption when deleting files.

Do you have some step by step instructions for setting up the easy debian image?

AndrewX192

2011-03-20 07:38

Re: Bad microSD

Quote:

Originally Posted by N770-Freak (Post 971460)

Do you have some step by step instructions for setting up the easy debian image?

The instructions on http://talk.maemo.org/showpost.php?p...4&postcount=29 should be sufficient.

If that looks like too much for you, just installing easydebian and placing the image on /media/mmc1, and running "apt-get update; apt-get install geany" inside the debian chroot should be enough to get I/O errors, and cause issues.''

I am currently testing copying an ubuntu livecd image to the microSD card over wifi, which seems to be going fine so far.

EDIT: Nitdroid is another thing which did not work for me on the microSD, you could try that if you want.

N770-Freak

2011-03-20 10:37

Re: Bad microSD

Ok, I formated my 32GB class 10 card with ext2 (I did this on my PC). After putting the card into my N900, I started to copy (tar) the debian files to the card. But this process aborted quite soon (I/O error).

Doing the same steps with my 16GB class 6 card is no problem.

AndrewX192, the questions now really would be if this can be fixed with a kernel patch, or if this really is a hardware compatibility problem.

N770-Freak

2011-03-20 11:05

Re: Bad microSD

Quote:

Originally Posted by geneven (Post 971553)

I have Easy Debian installed on my Class 10 Sandisk 32 GB card. It works fine.

Where did you get this card? I can buy only a Sandisk 32GB Class 2 card! The Patriot card was the only card which was available as Class 10.

AndrewX192

2011-03-20 18:50

Re: Bad microSD

Quote:

Originally Posted by N770-Freak (Post 971534)

Same issue then, I will likely downgrade as I do not have time to mess with this issue.

AndrewX192

2011-03-20 18:51

Re: Bad microSD

Quote:

Originally Posted by N770-Freak (Post 971568)

Where did you get this card? I can buy only a Sandisk 32GB Class 2 card! The Patriot card was the only card which was available as Class 10.

This is what I saw as well.

AndrewX192

2011-03-22 07:33

Re: Bad microSD

I am going to downgrade my card to a class 6 or 4 now.

AndrewX192

2011-03-26 17:54

Re: Bad microSD

I am still waiting for Patriot Memory to get back to me about my RMA, but unfortunately, it seems like I will be stuck with this useless microSD.
Has anyone had any luck getting it to work?

stlpaul

2011-03-29 15:21

Re: Bad microSD

I have exactly the same problem with Transcend 8GB Class 6 card and Adata 16GB class 10 card. They work and test just fine on multiple PCs in multiple card readers, but in N900 they are bad news.

So far the only one that works reliably for me is Sandisk 16GB class 2, but it is extremely slow (as the class 2 rating would indicate).

It's really disappointing and I've spent a lot of money on SD cards.

I suspect maybe the N900 isn't providing enough voltage to the SD card and some cards are less tolerant of low-voltage situations than others. Does anyone know if it's possible to tell what voltage or change the voltage of the SD card in N900?

stlpaul

2011-03-29 15:25

Re: Bad microSD

Here's an example of formatting with badblocks check on a ~2GB partition on my Adata card:

Code:

N900 ~ # mkfs.ext3 -m0 -Ldebian -cc -v /dev/mmcblk1p4

mke2fs 1.41.3.maemo0 (12-Oct-2008)

fs_types for mke2fs.conf resolution: 'ext3', 'default'

Filesystem label=debian

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

159680 inodes, 637696 blocks

0 blocks (0.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=654311424

20 block groups

32768 blocks per group, 32768 fragments per group

7984 inodes per group

Superblock backups stored on blocks:

        32768, 98304, 163840, 229376, 294912



Running command: badblocks -b 4096 -X -s -w /dev/mmcblk1p4 637695

badblocks: Input/output error during ext2fs_sync_device

Testing with pattern 0xaa: done

badblocks: Input/output error during ext2fs_sync_device

Reading and comparing: done

Testing with pattern 0x55: done

Reading and comparing: done

Testing with pattern 0xff: done

Reading and comparing: done

Testing with pattern 0x00: done

Reading and comparing: done

Writing inode tables: done

Creating journal (16384 blocks): done

Writing superblocks and filesystem accounting information: done



This filesystem will be automatically checked every 36 mounts or

180 days, whichever comes first.  Use tune2fs -c or -i to override.

Code:

[34309.382904] mmcblk1: error -110 sending read/write command, response 0x900, card status 0xe00

[34309.382934] mmcblk1: error -110 transferring data, sector 27271168, nr 8, card status 0xc00

[34309.450683] end_request: I/O error, dev mmcblk1, sector 27271169

[34309.450714] __ratelimit: 3 callbacks suppressed

[34309.450714] Buffer I/O error on device mmcblk1p4, logical block 0

[34309.450744] lost page write due to I/O error on mmcblk1p4

[35821.749053] mmcblk1: error -110 transferring data, sector 30941184, nr 16, card status 0xc00

[35821.749420] end_request: I/O error, dev mmcblk1, sector 30941185

[35821.749450] Buffer I/O error on device mmcblk1p4, logical block 458752

[35821.749450] lost page write due to I/O error on mmcblk1p4

[35821.749511] end_request: I/O error, dev mmcblk1, sector 30941192

[35821.749542] Buffer I/O error on device mmcblk1p4, logical block 458753

[35821.749542] lost page write due to I/O error on mmcblk1p4

[35822.362915] mmcblk1: error -110 transferring data, sector 31203328, nr 16, card status 0xc00

[35822.363189] end_request: I/O error, dev mmcblk1, sector 31203329

[35822.363220] Buffer I/O error on device mmcblk1p4, logical block 491520

[35822.363250] lost page write due to I/O error on mmcblk1p4

[35822.363281] end_request: I/O error, dev mmcblk1, sector 31203336

[35822.363311] Buffer I/O error on device mmcblk1p4, logical block 491521

[35822.363311] lost page write due to I/O error on mmcblk1p4

[35823.062774] mmcblk1: error -110 sending read/write command, response 0x900, card status 0xe00

[35823.062805] mmcblk1: error -110 transferring data, sector 31465472, nr 16, card status 0xc00

[35823.123229] end_request: I/O error, dev mmcblk1, sector 31465473

[35823.123260] Buffer I/O error on device mmcblk1p4, logical block 524288

[35823.123291] lost page write due to I/O error on mmcblk1p4

[35823.123352] end_request: I/O error, dev mmcblk1, sector 31465480

[35823.123352] Buffer I/O error on device mmcblk1p4, logical block 524289

[35823.123382] lost page write due to I/O error on mmcblk1p4

[35823.822967] mmcblk1: error -110 sending read/write command, response 0x900, card status 0xe00

[35823.822998] mmcblk1: error -110 transferring data, sector 31727616, nr 16, card status 0xc00

[35823.883148] end_request: I/O error, dev mmcblk1, sector 31727617

[35823.883178] Buffer I/O error on device mmcblk1p4, logical block 557056

[35823.883209] lost page write due to I/O error on mmcblk1p4

[35823.883239] end_request: I/O error, dev mmcblk1, sector 31727624

[35823.883270] Buffer I/O error on device mmcblk1p4, logical block 557057

[35823.883300] lost page write due to I/O error on mmcblk1p4

[35824.582946] mmcblk1: error -110 sending read/write command, response 0x900, card status 0xe00

[35824.582977] mmcblk1: error -110 transferring data, sector 31989760, nr 16, card status 0xc00

[35824.642639] end_request: I/O error, dev mmcblk1, sector 31989761

[35824.642669] Buffer I/O error on device mmcblk1p4, logical block 589824

[35824.642700] lost page write due to I/O error on mmcblk1p4

[35824.642761] end_request: I/O error, dev mmcblk1, sector 31989768

[35825.342315] mmcblk1: error -110 sending read/write command, response 0x900, card status 0xe00

[35825.342346] mmcblk1: error -110 transferring data, sector 32251904, nr 16, card status 0xc00

[35825.402618] end_request: I/O error, dev mmcblk1, sector 32251905

[35825.402679] end_request: I/O error, dev mmcblk1, sector 32251912

pataphysician

2011-03-31 23:43

Re: Bad microSD

It's not really a class 10 problem, as much as it's a Patriot Transcend Adata problem. I consider these to be very poor companies to buy from, and will only usually do so if a specific card has stunning reviews and also has a good price, otherwise it's usually not worth it. In the case of Transcend and Patriot 32GB class 10, the reviews on Newegg and Amazon are very awefull, I didn't even look at Adata as I have had way to much bad luck with them. Many of the reviews have bad problems getting them to work with Android devices.

I have a 32GB, class 10, Lexar, which I just made an ext2 partition and transfered the Easy Debian Image to the file system, and used it without any errors whatsoever. The performance of this card is really good.

Sandisk is usually very conservative with their class ratings, and most of my Sandisk class 2 cards perform easily within class 4 specs or even higher. The one exception is the 32GB class 2 Sandisk, while it does performs within the class 2 spec, strangely it's read speed is very very poor compared to other Sandisks, which are usually quite high. It's write speeds are actually very good, but strangely average read speed are actually lower than average write speeds, which is pretty bizarre, but max read speeds are higher than max write speeds, but not by much. It's OK performance, but some people have complained about stuttering when playing back video on it on Android devices, I haven't had this problem on the n900.

There was briefly a Sandisk 32GB class 4 microsd, on the market, but I couldn't find it anymore, this one might perform really well.

AndrewX192

2011-05-05 05:46

Re: Bad microSD

New kernel patches seem to alleviate this issue.
Please see http://talk.maemo.org/showthread.php?p=1000405 for details.

All times are GMT. The time now is 17:40.

vBulletin® Version 3.8.8