Op zondag 2 februari 2014 16:28:21 schreef jdd:
Le 02/02/2014 15:15, Freek de Kruijf a écrit :
I got:
│ ├─/var/run/media/freek/BOOT /dev/sde1 vfat ro,nosuid,nodev,relatime,uid=1000,gid=100,fmask=0022,dmask=0077,codepage=4 37,iocharset=i │ └─/var/run/media/freek/root /dev/sde3 ext2 ro,nosuid,nodev,relatime
good. How did you mount them, with command line or with dolphin? (the mount point is unusual)
I used Dolphin, which means it is mounted like above.
can you mount any on /mnt, if necessary as --bind, to see if the permission probem can be excluded?
I can and when I do I get: # mount /dev/sde3 /mnt mount: /dev/sde3 is write-protected, mounting read-only The fact that the device is write-protected, is the problem. The SD card is not write protected. So how can I make the device /dev/sde3 not write- protected or rather /dev sde when I use dd to write an image to the device.
problems mounting windows partition is often due to a bad umounting (from windows). The only fix I know is to mount them again *in windows* and umount them cleanly, it needs sometime *minutes* to have the file system umo_unted really and be able to remove the card from the computer
It has never been used on a Windows machine. The SD card is used to boot from by a Raspberry Pi.
there should not be any problem with ext2, beside an eventual fsck
I forgot to ask what the dd copy is. did you already did it or do you want to do it now (like it seems through the subject)?
See above.
I beg if you want to dd *to* the card, it's content is not important, so can you modify it in any way (fdisk, mkfs, rm)?
did you try imagewriter(from opensuse)? not that this should change anything :-)
No. The problem is that somehow the device is defined as read-only. Maybe something in udev that does that. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org