sd card permmision

liorglaz · August 13, 2017 at 10:35 AM

hi

i put sd card on my streamer with libreelec os , and i get error " no premmison" whey i try to write on sd card in my network .

why ??

thnx

**chewitt** · August 14, 2017 at 8:33 AM Official Post

How is the SD card formatted?

liorglaz · August 14, 2017 at 9:21 AM

ntfs

liorglaz · August 15, 2017 at 12:43 PM

????

**Klojum** · August 15, 2017 at 1:07 PM Official Post

Is the write tab on the SD card in the readonly position?

**chewitt** · August 15, 2017 at 2:02 PM Official Post

could be a problem with the NTFS filesystem, e.g. unclean mount, although in those situations the normal behaviour is Linux refuses to mount the drive completely..

liorglaz · August 16, 2017 at 11:16 AM

in windows its work fine , in fat32 its the same problem , I think its something in Linux , but i dont know what to do to fix that

any ideas ??

thnx

**chewitt** · August 16, 2017 at 10:38 PM Official Post

share the URL from "dmesg | paste" so we can see if there are errors in the kernel log

liorglaz · August 17, 2017 at 10:13 PM

fQNh

**chewitt** · August 18, 2017 at 6:18 AM Official Post

Share after a clean boot so we can see the early boot messages. That logs shows nothing.

liorglaz · August 19, 2017 at 7:17 PM

LZJh

**kszaq** · August 19, 2017 at 7:32 PM

liorglaz Are you using "full size" SD card? Make sure that "lock" switch is in correct position.

liorglaz · August 21, 2017 at 4:29 PM

hi

In windows i have no probkem

**chewitt** · August 22, 2017 at 6:03 AM Official Post

Code

[    3.491608@1] mmcblk0: sd:1388 NCard 14.8 GiB (ro)
[    3.514280@1]  mmcblk0: p1
[    3.919301@0] mmcblk1: emmc:0001 NCard  7.21 GiB 
[    3.919434@0] mmcblk1boot0: emmc:0001 NCard  partition 1 4.00 MiB
[    3.919562@0] mmcblk1boot1: emmc:0001 NCard  partition 2 4.00 MiB
[    3.920731@0]  mmcblk1: p1
[    3.922404@1] [mmcblk1p01]           bootloader  offset 0x000000000000, size 0x000000400000 
[    3.922604@1] [mmcblk1p02]             reserved  offset 0x000002400000, size 0x000004000000 
[    3.922789@1] [mmcblk1p03]                cache  offset 0x000006c00000, size 0x000020000000 
[    3.922977@1] [mmcblk1p04]                  env  offset 0x000027400000, size 0x000000800000 
[    3.923164@1] [mmcblk1p05]                 logo  offset 0x000028400000, size 0x000002000000 
[    3.923338@1] [mmcblk1p06]             recovery  offset 0x00002ac00000, size 0x000002000000 
[    3.923506@1] [mmcblk1p07]                 misc  offset 0x00002d400000, size 0x000002000000 
[    3.923720@1] [mmcblk1p08]                 boot  offset 0x00002fc00000, size 0x000002000000 
[    3.923903@1] [mmcblk1p09]               system  offset 0x000032400000, size 0x000060000000 
[    3.924074@1] [mmcblk1p10]                 data  offset 0x000092c00000, size 0x00013b500000 
[    3.925427@1]  mmcblk1boot1: p1
[    3.925450@1] mmcblk1boot1: p1 start 16065 is beyond EOD, truncated
[    3.926875@1]  mmcblk1boot0: p1
[    3.926892@1] mmcblk1boot0: p1 start 16065 is beyond EOD, truncated
[    6.115749@1] EXT3-fs (mmcblk1p9): error: couldn't mount because of unsupported optional features (40)
[    6.116116@1] EXT2-fs (mmcblk1p9): error: couldn't mount because of unsupported optional features (40)
[    6.123021@1] EXT4-fs (mmcblk1p9): mounted filesystem with ordered data mode. Opts: (null)
[    6.272221@1] EXT3-fs (mmcblk1p10): error: couldn't mount because of unsupported optional features (40)
[    6.272595@1] EXT2-fs (mmcblk1p10): error: couldn't mount because of unsupported optional features (40)
[    6.280626@2] EXT4-fs (mmcblk1p10): mounted filesystem with ordered data mode. Opts: (null)

Display More

"It works in Windows" because Windows blindly trusts whatever disk/partition geometry data is presented to the OS before it goes ahead and mounts the partitions on the storage device. In comparison; Linux validates the geometry data presented to prevent data loss issues. In this case the partition data is invalid so Linux correctly refuses to mount the damaged partitions. Id guess the SD card is going bad, or there are traces of previous partition schemes on the storage that cause conflict.

Use our USB/SD creator app to restore bootsector.img to the SD card then reformat the media in Windows (any format scheme you like) and try again.

liorglaz · August 23, 2017 at 7:30 PM

ok

How i restore in app ?

Thnx

**chewitt** · August 24, 2017 at 5:01 AM Official Post

LibreELEC USB-SD Creator - LibreELEC

liorglaz · September 9, 2017 at 8:05 PM

hi

I change sd card the same problem

Cannot write on sd card, maybe premmision in libreelec ?