On Thu, Feb 26, 2015 at 06:41:24PM +0100, Csányi Pál wrote:

I tried these steps by using Gparted too, but at this step Gparted can't read partitions from the during read on

/dev/mmcblk0

Gparted gives the error message: I/O error during read on /dev/mmcblk0

What can I do to solve this problem?

Your hardware has issues, and I don't think any software will fix it. My guess is that the issue is in one of three places: 1: Your SD card is damaged / broken. To test this, try it in a known-working reader. Note that Windows will not understand Linux / RPi partitions (but should be able to at least see the boot partition). 2. If you're using a microSD to SD adapter, I've seen plenty of those be flaky and crappy. Try a different adapter, or get a reader that supports uSD directly. 3. The reader is broken. Since it's the built-in one on the laptop, the only way to test this is to try a different card / try on a different OS (live boot USB drives are useful for this). In any case, seeing IO errors in dmesg means that there are hardware problems. Udisk will not in any way solve those, and is not needed for imaging SD cards for the Pi. If your edit to the polkit config broke your login, undo it. --Sean

Op 26 feb. 2015 19:58 schreef "Csányi Pál" :

2015-02-26 19:25 GMT+01:00 Sean Greenslade :

...

On Thu, Feb 26, 2015 at 06:41:24PM +0100, Csányi Pál wrote:

...

I tried these steps by using Gparted too, but at this step Gparted can't read partitions from the during read on

/dev/mmcblk0

Gparted gives the error message: I/O error during read on /dev/mmcblk0

What can I do to solve this problem?

Your hardware has issues, and I don't think any software will fix it. My guess is that the issue is in one of three places:

1: Your SD card is damaged / broken. To test this, try it in a known-working reader. Note that Windows will not understand Linux / RPi partitions (but should be able to at least see the boot partition).

I can mount it's first partition, that with FAT32 type filesystem. I can't only format it's second partition, with ex4 type filesystem.

Still does it mean that the uSD card is damaged?

...

2. If you're using a microSD to SD adapter, I've seen plenty of those be flaky and crappy. Try a different adapter, or get a reader that supports uSD directly.

Yes, I'm using a microSD card to SD adapter. I shall try another brand of SD adapter, that I have.

...

3. The reader is broken. Since it's the built-in one on the laptop, the only way to test this is to try a different card / try on a different OS (live boot USB drives are useful for this).

I shall try that too.

One thing I ran into was the difference between sd versions; sdhc cards wont work in an (standard) sd reader. I don't know how to check the reader from Linux, but it's probably in the hardware specs. Mvg, Guus

Hello everyone, 2015-02-27 1:41 GMT+01:00 Sean Greenslade :

On Thu, Feb 26, 2015 at 07:58:13PM +0100, Csányi Pál wrote:

...

...

1: Your SD card is damaged / broken. To test this, try it in a known-working reader. Note that Windows will not understand Linux / RPi partitions (but should be able to at least see the boot partition).

I can mount it's first partition, that with FAT32 type filesystem. I can't only format it's second partition, with ex4 type filesystem.

Still does it mean that the uSD card is damaged?

If when you attempt to do an operation on it, you get IO errors in dmesg, yes, that means your card OR card reader OR card adapter is broken. If it is partition-specific, I would assume that it is the card that is broken.

I bought an USB microSD card reader and with it I can use the microSD card. I completed partitioning and formatting microSD card. I have now installed on it Arch linux. I can boot with it the RaspberryPi. Thank you all for helping me out. -- Regards from Pal

2015-02-25 23:58 GMT+01:00 Aaron Caffrey :

Install udisks, udisks2. Create /etc/polkit-1/rules.d/10-enable-mount.rules

polkit.addRule(function(action, subject) { if (action.id == "org.freedesktop.udisks2.filesystem-mount-system" && subject.isInGroup("storage")) { return polkit.Result.YES; } });

After I created this file and try to reboot with microSD card left inserted in the card reader, I can't even login into my system. Why? -- Regards from Pal

On 26/02/15 at 07:31pm, Jens Adam wrote:

Wed, 25 Feb 2015 11:36:59 +0100 Csányi Pál :

...

mmcblk0: error -84 transferring data, sector 7, nr 1, cmd response 0x900, card status 0x0 Buffer I/O error on dev mmcblk0, logical block 0, async page read

This clearly indicates a hardware/kernel problem, so I don't know why people are suggesting to paste random config snippets that won't solve anything.

Simple googling will produce dozens of similar problems, most without solution.

My guess: Your card reader (which one? lspci/lsusb/dmesg? laptop type and age?) or its firmware is simply too old to recognize the card. See https://en.wikipedia.org/wiki/Secure_Digital#Compatibility

--byte

Because I had exactly the same issue with different kernels, one kernel will read my micro sd card and others wont. The solution which I posted has helped me long time ago, that is why I shared it. What is the purpose of this mailing list if we can't help each other ?