Can't write to micro SD card
by jesusangel from LinuxQuestions.org on (#4WZBN)
Hello,
I have a micro SD card which I was using in a Raspberry PI 3. I can read from and write to it, but after remounting the filesystems, the new files disappear.
The card has two partitions, one with a FAT32 filesystem and other one with an ext4 filesystem.
Code:Disk /dev/sda: 14,9 GiB, 16021192704 bytes, 31291392 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8f1eafaf
Device Boot Start End Sectors Size Id Type
/dev/sda1 8192 131071 122880 60M c W95 FAT32 (LBA)
/dev/sda2 131072 31291391 31160320 14,9G 83 LinuxThe card is not write protected:
Code:# hdparm -r /dev/sda
/dev/sda:
readonly = 0 (off)I can mount the filesystems RW and a write operation in the card doesn't return any error:
Code:/dev/sda1 on /mnt/slot1 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
/dev/sda2 on /mnt/loop type ext4 (rw,relatime,data=ordered)
# file loop/rnd.bin
loop/rnd.bin: data
# umount /mnt/loop
# mount /dev/sda2 /mnt/loop
# ls -l /mnt/loop/rnd.bin
Can't access to /mnt/loop/rnd.bin. No such file or directoryI have checked both filesystems:
Code:# dosfsck -w -r -l -a -v -t /dev/sda1
fsck.fat 4.1 (2017-01-24)
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "mkfs.fat"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
8192 bytes per cluster
1 reserved sector
First FAT starts at byte 512 (sector 1)
2 FATs, 16 bit entries
16384 bytes per FAT (= 32 sectors)
Root directory starts at byte 33280 (sector 65)
512 root directory entries
Data area starts at byte 49664 (sector 97)
7673 data clusters (62857216 bytes)
63 sectors/track, 255 heads
0 hidden sectors
122880 sectors total
Checking file /boot
../..
Checking file /overlays/imx219.dtbo (IMX219~1.DTB)
Checking for bad clusters.
Reclaiming unconnected clusters.
/dev/sda1: 215 files, 3020/7673 clusters
# fsck.ext4 -fv /dev/sda2
e2fsck 1.43.4 (31-Jan-2017)
Paso 1: Verificando nodos-i, bloques y tamanos
Paso 2: Verificando la estructura de directorios
Paso 3: Revisando la conectividad de directorios
Paso 4: Revisando las cuentas de referencia
Paso 5: Revisando el resumen de informacion de grupos
208423 nodos-i utilizados (21.68%, el 961520)
654 ficheros no contiguos (0.3%)
399 directorios no contiguos (0.2%)
nimero de nodos-i con bloques ind/dind/tind: 0/0/0
Histograma de las profundidades de extents: 188727/231
2177729 bloques usados (55.91%, el 3895040)
0 bloques danados
1 fichero grande
165610 ficheros regulares
23075 directorios
55 dispositivos de caracteres
25 dispositivos de bloque
0 fifos
64 vinculos
19649 enlaces simbolicos (19377 vinculos simbolicos ripidos)
0 zocalos
------------
208478 ficherosI tried also to delete the partitions but I couldn't. I couldn't either create new filesystem. The mkfs.ext4 ran without errors, but after mounting the new filesystem, the old files are still there.
What's happening?
Maybe the card is broken?
Kind regards,
I have a micro SD card which I was using in a Raspberry PI 3. I can read from and write to it, but after remounting the filesystems, the new files disappear.
The card has two partitions, one with a FAT32 filesystem and other one with an ext4 filesystem.
Code:Disk /dev/sda: 14,9 GiB, 16021192704 bytes, 31291392 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x8f1eafaf
Device Boot Start End Sectors Size Id Type
/dev/sda1 8192 131071 122880 60M c W95 FAT32 (LBA)
/dev/sda2 131072 31291391 31160320 14,9G 83 LinuxThe card is not write protected:
Code:# hdparm -r /dev/sda
/dev/sda:
readonly = 0 (off)I can mount the filesystems RW and a write operation in the card doesn't return any error:
Code:/dev/sda1 on /mnt/slot1 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
/dev/sda2 on /mnt/loop type ext4 (rw,relatime,data=ordered)
# file loop/rnd.bin
loop/rnd.bin: data
# umount /mnt/loop
# mount /dev/sda2 /mnt/loop
# ls -l /mnt/loop/rnd.bin
Can't access to /mnt/loop/rnd.bin. No such file or directoryI have checked both filesystems:
Code:# dosfsck -w -r -l -a -v -t /dev/sda1
fsck.fat 4.1 (2017-01-24)
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "mkfs.fat"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
8192 bytes per cluster
1 reserved sector
First FAT starts at byte 512 (sector 1)
2 FATs, 16 bit entries
16384 bytes per FAT (= 32 sectors)
Root directory starts at byte 33280 (sector 65)
512 root directory entries
Data area starts at byte 49664 (sector 97)
7673 data clusters (62857216 bytes)
63 sectors/track, 255 heads
0 hidden sectors
122880 sectors total
Checking file /boot
../..
Checking file /overlays/imx219.dtbo (IMX219~1.DTB)
Checking for bad clusters.
Reclaiming unconnected clusters.
/dev/sda1: 215 files, 3020/7673 clusters
# fsck.ext4 -fv /dev/sda2
e2fsck 1.43.4 (31-Jan-2017)
Paso 1: Verificando nodos-i, bloques y tamanos
Paso 2: Verificando la estructura de directorios
Paso 3: Revisando la conectividad de directorios
Paso 4: Revisando las cuentas de referencia
Paso 5: Revisando el resumen de informacion de grupos
208423 nodos-i utilizados (21.68%, el 961520)
654 ficheros no contiguos (0.3%)
399 directorios no contiguos (0.2%)
nimero de nodos-i con bloques ind/dind/tind: 0/0/0
Histograma de las profundidades de extents: 188727/231
2177729 bloques usados (55.91%, el 3895040)
0 bloques danados
1 fichero grande
165610 ficheros regulares
23075 directorios
55 dispositivos de caracteres
25 dispositivos de bloque
0 fifos
64 vinculos
19649 enlaces simbolicos (19377 vinculos simbolicos ripidos)
0 zocalos
------------
208478 ficherosI tried also to delete the partitions but I couldn't. I couldn't either create new filesystem. The mkfs.ext4 ran without errors, but after mounting the new filesystem, the old files are still there.
What's happening?
Maybe the card is broken?
Kind regards,