/boot partition is too small...

ghost commented 7 years ago

I think everyone knows this... but...

/boot contains the boot loader / config /berryboot contains the OS images and data (supposedly)

On initial install, /boot is WAY too small... I was easily able to install as many OS as I wanted, because it was the partition with like 99% of the disk space... But when I booted RecalBox (it woulda happened with Raspbian too) and tried installing all my games, the disk filled up...

So I figured out that its the boot partition and am now using GParted to resize it... I resized the berryboot partition to have a few gigs free space in case I want to install more OS's, and then resized the boot partition to fill the free space - now I can install all the games I want again.

Could we please make it possible to resize the partitions within the boot menu? Maybe make a menu that asks how big the /boot and /berryboot partitions should be, then it resizes them?

That would make BerryBoot the best!!! I mean it already IS the best, because NOOBS will reinstall and wipe your OS's every time you install a new one - BerryBoot doesn't! Also it is how you would program your own bootloader, with the data for all OS on one partition.

Thanks BerryBoot & developers very much!

<3 you!

maxnet commented 7 years ago

/boot contains the boot config as well as the data for the OS's that are installed

It should NOT contain any data. The OS you are using should not touch it...

ghost commented 7 years ago

So why does RecalBox claim there is no disk space? Why do I find the games that I was able to upload to it inside the /boot partition? Why did I have to try to resize the /boot partition (it wont go larger than 3 or 4 GB)?

The fact is, there is data on that partition that has nothing to do with booting... The RecalBox game roms are stored on that partition by default...

It doesn't matter anymore, I was able to insert a seperate USB card, then tell RecalBox to use the external USB. Now my games store on my USB instead of /boot

This really does need to be fixed though, because the only data that should be in /boot is the boot loader files...

maxnet commented 7 years ago

None of the operating system images we provide touch /boot Cannot comment about third party ones, we didn't create.

substring commented 6 years ago

Hi,

I'm part of the Recalbox dev team. Recalbox just adds a couple of tiny files to /boot. If roms are stored on /boot, then somehthing erronously mounted the data partition on /boot, butit's not part of Recalbox.

@MyS5Droid Your best chance would probable to use external storage for Recalbox, leaving your SD untouched.

I'll have a look at adding Berryboot support once Recalbox squashfs is done.

maxnet / berryboot

/boot partition is too small... #412