Citazione Originariamente Scritto da bovirus Visualizza Messaggio
@ciamardo


Prove effettuate su Ubuntu 16.04

Se insersico la SD viene riconsociuta (ho provato con un lettroe singolo che i lettori multiformato)

root@ubuntu:~# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1994092k,nr_inodes=498523 ,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode =000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=402876k,mode=755)
/dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_age nt=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=34,pgrp=1,timeout=0,minproto=5,max proto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
vmware-vmblock on /run/vmblock-fuse type fuse.vmware-vmblock (rw,relatime,user_id=0,group_id=0,default_permissi ons,allow_other)
vmhgfs-fuse on /mnt/hgfs type fuse.vmhgfs-fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,all ow_other)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=402876k,mode=700,ui d=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=10 00)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)
/dev/sdb1 on /media/ubuntu/DEF7-9AEC type vfat (ro,nosuid,nodev,relatime,uid=1000,gid=1000,fmask= 0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remou nt-ro,uhelper=udisks2)

In grasetto il mount della SD

root@ubuntu:~# ls /sys/block/
loop0 loop1 loop2 loop3 loop4 loop5 loop6 loop7 sda sdb sr0

Come si vede non c'è mmcblk0

se faccio

root@ubuntu:~# ls -l /media/ubuntu/DEF7-9AEC
total 128
drwxr-xr-x 5 ubuntu ubuntu 32768 feb 28 18:49 cryptnav
drwxr-xr-x 3 ubuntu ubuntu 32768 feb 28 18:49 myUPOIs
-rw-r--r-- 1 ubuntu ubuntu 100 gen 16 2017 prod_info.txt
drwxr-xr-x 2 ubuntu ubuntu 32768 lug 5 13:49 System Volume Information

si vede il contenuto della SD.

questa è la scritta che ti interessa a te :
/dev/sdb1
questo significa che il tuo pc non è in grado di riscrivere il cid di una sd
se invece avevi la scritta
/dev/mmcblk1
allora il tuo pc era in grado di riscrivere il cid di una sd !

come detto 2 sono le componenti fondamentali x riscrivere il cid di una sd :
1) un pc in grado di riscrivere il cid di una sd
2) una samsung evo o evo + col cid modificabile