Can't figure out where MicroSD space is
#1
In trying to troubleshoot an unusable PPB I've just received, I bought a 64G MicroSD card to boot the Fedora 32 Xfce image.  I'm partial to Fedora, and wanted something different from the Manjaro or KDE that is pre-installed for testing purposes.   With dd the install was easy and Fedora booted like a charm.  I've added only apps I needed, like Firefox and Geany to keep it simple.  But even so, the operating system seems to think I have no space left on the MicroSD.

We have lsblk showing the MicroSD disk, mmcblk2, essentially full:

Code:
$ lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mmcblk2      179:0    0  58.2G  0 disk
├─mmcblk2p1  179:1    0 213.6M  0 part
└─mmcblk2p2  179:2    0    58G  0 part
mmcblk2boot0 179:32   0     4M  1 disk
mmcblk2boot1 179:64   0     4M  1 disk
mmcblk1      179:96   0  59.5G  0 disk
├─mmcblk1p1  179:97   0 213.6M  0 part /boot
└─mmcblk1p2  179:98   0  10.7G  0 part
With df we get a similar story:
Code:
df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        1.9G     0  1.9G   0% /dev
tmpfs           1.9G   99M  1.8G   6% /dev/shm
tmpfs           1.9G  9.5M  1.9G   1% /run
/dev/mmcblk1p2   11G  9.8G  201M  99% /
tmpfs           1.9G   48K  1.9G   1% /tmp
/dev/mmcblk1p1  214M  134M   81M  63% /boot
tmpfs           380M   24K  380M   1% /run/user/1000
But in fact, du gives:
Code:
$ sudo du -sh *
0    bin
134M    boot
0    dev
28M    etc
2.6G    home
0    lib
0    lib64
4.0K    lost+found
4.0K    media
4.0K    mnt
4.0K    opt
du: cannot access 'proc/4494': No such file or directory
du: cannot access 'proc/4497/task/4497/fd/3': No such file or directory
du: cannot access 'proc/4497/task/4497/fdinfo/3': No such file or directory
du: cannot access 'proc/4497/fd/3': No such file or directory
du: cannot access 'proc/4497/fdinfo/3': No such file or directory
0    proc
3.3G    root
9.5M    run
0    sbin
4.0K    srv
0    sys
40K    tmp
3.5G    usr
442M    var

Your counting may be better than mine, but that doesn't look like much more than 10G.  At the moment, the OS complains of lack of space, which limits my ability to do much.  What am I missing here?
Any ideas much appreciated.
Kendew
#2
>What am I missing here?
This distro did not expand the file system for you, notice size blk1p2
so, sudo cfdisk /dev/mmcblk1, move highlight to p2, expand, write, type "yes"
Then sudo resize2fs /dev/mmcblk1p2, it may ask for a fsck first
#3
If mmcblk2 is the SD, then mmcblk1 is the eMMC. According to df, only mmcblk1's two partitions are mounted, and you're running from those.

sudo mount /dev/mmcblk2p2 /mnt

and then see what df says.

lsblk isn't showing that it's full, it's showing that all the blocks are assigned to partitions.

Before attempting to edit the partition table of either disk or resize its filesystems, make sure you're booted & running from the other disk.

Also, how sure are you that mmcblk2 is the SD? When I boot Manjaro from SD, it ends up as mmcblk1 and the eMMC ends up as mmcblk2. Device name assignments for block devices aren't necessarily the same across reboots depending on things like kernel & where you booted from, which is why it's preferred to use UUIDs to specify what gets mounted where in /etc/fstab.
#4
from post #1
seems to think I have no space left on the MicroSD.
/dev/mmcblk1p2 11G 9.8G 201M 99% /

I am assuming this is a boot from SD
If so, sd is blk1 and emmc blk2
Yes, it gets quite confusing when both sd and emmc are 64G
Mounting is irrelevant for changing mbr
from the manpage for resize2fs

If the filesystem is mounted, it can be used to expand the size of the mounted filesystem, assuming the kernel and the file system supports on-line resizing.

But, if it wants a fsck (about 1/2 the time), yes that should be done on an unmounted fs
For that matter, a fsck is good practice, never hurts
And, another point,,, I have never seen boot0 or boot1 on a SD card, only on emmc
I think this is an android remenent (there is little info about this),,, and not used by linux
--edit--
If you have more than a few uSD cards, it can be annoying, what is on this card?
No room for a (physical) label
I have 15,, yes you can 'root through' /etc and find out, and then forget tomorrow
cd / (of SD) ; sudo touch This-is-$(DISTRO-VERSION)-SD
quick and easy,, if you say, "no good" and burn another distro, directory entry is gone, do a new one
#5
(09-23-2020, 04:25 PM)kendew Wrote: In trying to troubleshoot an unusable PPB I've just received, I bought a 64G MicroSD card to boot the Fedora 32 Xfce image.  I'm partial to Fedora, and wanted something different from the Manjaro or KDE that is pre-installed for testing purposes.   With dd the install was easy and Fedora booted like a charm.  I've added only apps I needed, like Firefox and Geany to keep it simple.  But even so, the operating system seems to think I have no space left on the MicroSD.

We have lsblk showing the MicroSD disk, mmcblk2, essentially full:

Code:
$ lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
mmcblk2      179:0    0  58.2G  0 disk
├─mmcblk2p1  179:1    0 213.6M  0 part
└─mmcblk2p2  179:2    0    58G  0 part
mmcblk2boot0 179:32   0     4M  1 disk
mmcblk2boot1 179:64   0     4M  1 disk
mmcblk1      179:96   0  59.5G  0 disk
├─mmcblk1p1  179:97   0 213.6M  0 part /boot
└─mmcblk1p2  179:98   0  10.7G  0 part
With df we get a similar story:
Code:
df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        1.9G     0  1.9G   0% /dev
tmpfs           1.9G   99M  1.8G   6% /dev/shm
tmpfs           1.9G  9.5M  1.9G   1% /run
/dev/mmcblk1p2   11G  9.8G  201M  99% /
tmpfs           1.9G   48K  1.9G   1% /tmp
/dev/mmcblk1p1  214M  134M   81M  63% /boot
tmpfs           380M   24K  380M   1% /run/user/1000
But in fact, du gives:
Code:
$ sudo du -sh *
0    bin
134M    boot
0    dev
28M    etc
2.6G    home
0    lib
0    lib64
4.0K    lost+found
4.0K    media
4.0K    mnt
4.0K    opt
du: cannot access 'proc/4494': No such file or directory
du: cannot access 'proc/4497/task/4497/fd/3': No such file or directory
du: cannot access 'proc/4497/task/4497/fdinfo/3': No such file or directory
du: cannot access 'proc/4497/fd/3': No such file or directory
du: cannot access 'proc/4497/fdinfo/3': No such file or directory
0    proc
3.3G    root
9.5M    run
0    sbin
4.0K    srv
0    sys
40K    tmp
3.5G    usr
442M    var

Your counting may be better than mine, but that doesn't look like much more than 10G.  At the moment, the OS complains of lack of space, which limits my ability to do much.  What am I missing here?
Any ideas much appreciated.
Kendew

You need to expand the filesystem [SD Card] so that the OS can see all of its available space.
I'd google 'expanding SD card file system linux' and you'll find the info you need - I don't know the commands, but know this is normal behaviour. Simply have to expand the filesystem on your SD card.
-----
 pAULIE42o
.  .  .  .   .  . .
/s


Possibly Related Threads…
Thread Author Replies Views Last Post
Question Disassembling PineBook Pro Docking Deck (due to disappeared microSD card) gritibaenz 4 1,196 04-02-2021, 06:45 PM
Last Post: tkudog
Shocked Is there a RIght and Wrong MicroSD? SpaceLord 4 693 03-15-2021, 09:17 PM
Last Post: dsimic
  microSD card stuck charlesnorris 7 2,225 11-19-2020, 05:11 AM
Last Post: KC9UDX
  Emmc to MicroSD adapter won't fit in recessed slot of pbp sunjam 3 1,591 03-04-2020, 01:20 PM
Last Post: zaius

Forum Jump:


Users browsing this thread: 1 Guest(s)