uSD/eMMC not mounting when booting from eMMC/uSD

I just grabbed the 2015-12-07 image and flasher image and placed them on separate uSD cards. I used the flasher image to flash the eMMC. Board boots fine.

I then inserted the uSD card with the normal image. Apparently, it doesn’t automagically mount anymore. I see in ``dmesg that the system sees the new device:

[ 598.137586] mmc0: new high speed SDHC card at address aaaa
[ 598.150733] mmcblk1: mmc0:aaaa SE32G 29.7 GiB
[ 598.161203] mmcblk1: p1

lsblk can see the uSD card:

debian@beaglebone:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0boot0 179:8 0 2M 1 disk
mmcblk0boot1 179:16 0 2M 1 disk
mmcblk0 179:0 0 3.6G 0 disk
└─mmcblk0p1 179:1 0 3.6G 0 part /
mmcblk1 179:24 0 29.7G 0 disk
└─mmcblk1p1 179:25 0 29.7G 0 part

But, no mountie…

debian@beaglebone:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 0 10M 0% /dev
tmpfs 98M 8.4M 90M 9% /run
/dev/mmcblk0p1 3.5G 2.8G 595M 83% /
tmpfs 245M 4.0K 245M 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 245M 0 245M 0% /sys/fs/cgroup
tmpfs 49M 0 49M 0% /run/user/1000

Note that I can mount the uSD by hand thusly:

debian@beaglebone:~$ sudo mount /dev/mmcblk1p1 temp
debian@beaglebone:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 0 10M 0% /dev
tmpfs 98M 8.4M 90M 9% /run
/dev/mmcblk0p1 3.5G 2.8G 595M 83% /
tmpfs 245M 4.0K 245M 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 245M 0 245M 0% /sys/fs/cgroup
tmpfs 49M 0 49M 0% /run/user/1000
/dev/mmcblk1p1 30G 2.7G 25G 10% /home/debian/temp
debian@beaglebone:~$ ls temp
bbb-uEnv.txt dev ID.txt media opt run sys var
bin etc lib mnt proc sbin tmp
boot home lost+found nfs-uEnv.txt root srv usr
debian@beaglebone:~$

I can repeat this same sequence by rebooting from the uSD card and the same happens w.r.t. eMMC.

On another system, (BeagleBoard.org Debian Image 2015-11-01, 4.1.13-ti-r35), I am apparently getting the same behavior.

I seem to remember that automagical mounting of the uSD/eMMC used to happen. Maybe this was explicitly removed to avoid confusion? Or is this something that bit-rotted?

ba

With lxqt, i have this disabled by default:

https://github.com/rcn-ee/repos/blob/master/pcmanfm-qt/suite/jessie/debian/patches/desktop-defaults.patch#L20

Look at these values;

[Volume]
AutoRun=true
CloseOnUnmount=false
MountOnStartup=false
MountRemovable=false

/home/${USER}/.config/pcmanfm-qt/lxqt/settings.conf

Regards,

With lxqt, i have this disabled by default:

https://github.com/rcn-ee/repos/blob/master/pcmanfm-qt/suite/jessie/debian/patches/desktop-defaults.patch#L20

Look at these values;

[Volume]
AutoRun=true
CloseOnUnmount=false
MountOnStartup=false
MountRemovable=false

/home/${USER}/.config/pcmanfm-qt/lxqt/settings.conf

Got it. Thanks.

FWIW, it threw me a bit when the volume label of the eMMC (as flashed by the flasher image) showed as “BOOT”. I first thought that this was the old boot partition, but it’s really rootfs. The normal image (on the uSD) shows as “rootfs”.

debian@beaglebone:~$ sudo blkid
/dev/mmcblk0p1: LABEL=“rootfs” UUID=“cf6fe36e-7116-41eb-849f-d6c5e41cc387” TYPE=“ext4”
/dev/mmcblk1p1: LABEL=“BOOT” UUID=“d3ea6827-343b-48e2-ac60-b925be97d3b9” TYPE=“ext4”
/dev/mmcblk0: PTTYPE=“dos”
/dev/mmcblk1: PTTYPE=“dos”
debian@beaglebone:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk1boot0 179:16 0 2M 1 disk
mmcblk1boot1 179:24 0 2M 1 disk
mmcblk0 179:0 0 29.7G 0 disk
-mmcblk0p1 179:1 0 29.7G 0 part / mmcblk1 179:8 0 3.6G 0 disk -mmcblk1p1 179:9 0 3.6G 0 part /media/debian/BOOT

Yeah, i need fix the default naming... Side affect of the "fat/boot"
bb.org doc's rip out and convert to deb package conversion. :wink:

Regards,