[SOLVED] Expand partition after flashing.

Help and Support Guides
1

Hello everyone,
I just flashed my 1.55 volumio and of course like any raspbian distro i wish extend the partition to fill all the space in the SD card.
I should see 3 partition like here:

chrisnewland.com/resize-ras … rry-pi-245

but i see only 2 partition, i deleted the #2 and create a new one.
It does not works :imp: :imp:
It seems like there is an hidden partition, why?

2

I found it the solution.

I need to run only:

sudo resize2fs /dev/mmcblk0p1

Seems to work

3

For whomever it may concern: in here you can find the complete step-by-step manual on how to increase/expand the partition size of Volumio:

faq-and-the-answers-for-t1545.html “Increase the partition size”

4

Hey,
I went exactly trought the instructions (FAQ) (twice) and i couldnt log on afterwards both times (ssh).
I get the error “Bad file number”. Any clues? Is sudo resize2fs /dev/root only from “onBoard” possible?! I havent got an HDMI device :confused:
Raspi B+, 16Gb Class 10 SDCard, wired connection, Volumio2

Thanks, regards
d

5

I can see that the 3rd partion is there, but it isnt mounted (that I can tell…pardon my self taught linux skills). How are we supposed to put music on it?

/dev/mmcblk0p2  2.0G  529M  1.4G  28% /imgpart
/dev/loop0      263M  263M     0 100% /static
overlay          13G  844M   11G   8% /
devtmpfs        233M     0  233M   0% /dev
tmpfs           242M     0  242M   0% /dev/shm
tmpfs           242M  4.8M  237M   2% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           242M     0  242M   0% /sys/fs/cgroup
tmpfs           242M   16K  242M   1% /tmp
tmpfs           242M     0  242M   0% /var/spool/cups
tmpfs           242M  360K  241M   1% /var/cache/apt/archives
tmpfs           242M   60K  242M   1% /var/log
tmpfs           242M     0  242M   0% /var/spool/cups/tmp
/dev/mmcblk0p1   61M   29M   33M  47% /boot
tmpfs            49M     0   49M   0% /run/user/1000
Device         Boot   Start      End  Sectors  Size Id Type
/dev/mmcblk0p1 *          1   125000   125000   61M  c W95 FAT32 (LBA)
/dev/mmcblk0p2       125001  4492187  4367187  2.1G 83 Linux
/dev/mmcblk0p3      4492188 31116287 26624100 12.7G 83 Linux
6

In Volumio2 it looks like the media is put on the 3rd partition, that is automatically sized to be full remainder of the partition. you wont see it when you do a df -h (no idea why).

The 2nd partition, is about 4gb, and only seems partially used, but on a 16gb card, I should be fine filling the 3rd partition.

7

The second partition stores the core system images (factory, current image, and backup image), basically those are snapshots of the system that get loaded on RAM on boot. The third partition is the data partition, where we store changes to the system and user data. It is automatically resized on first boot to fit the entire sd card…

8

Hi there.
I try to extend my " /dev/mmcblk0p1" / “boot”. Init it is just ~92 MB which is to small for maybe “sudo rpi-update”.

volumio@volumio:/$ sudo rpi-update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** Performing self-update
*** Relaunching after update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
Partition size 91M may not be sufficient for new Pi4 files
This could result in a system that will not boot.
256M FAT partition is recommended. Ensure you have a backup if continuing.
Would you like to proceed? (y/N)

How can I resize /boot to … let`s say 300 MB?

9

Apart from you replying to an ancient post, the answer is simple, you should never do an rpi-update with Volumio. Volumio is a dedicated, customized OS, based on Debian but not equal to Rasbian.
Why the urge to use rpi-update?