-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug /dev/loop0 Partition don't follow the config to resize #199
Comments
Hey, what image are you building? Could you provide a build log so I can determine if there some edge case where it detects what filesystem its resizing? That code does stuff to resize BTRFS systems, but its likely you are using EXT4 |
The image I am trying to building is mainsailos. I think it's the if statement in The code below is the screenshot of The code below is skipped code in this if statement. (The code EXT4 filesystem need) e2fsck -fy $LODEV
resize2fs -p $LODEV Then I swap the function It seems this issue can be solved by adding a fallback. Like add Also, what dependence I need? The dependence I install "aria2, coreutils, jq. p7zip-full, qemu-user-static, zip". Or? Do this is somethings only in GitHub Action? -Neko.vecter |
Ok, pushed an echo that should print the filesystem line result if it can't determine, could you build and paste that result? That way we can figure why its failing. |
I know why! I am missing dependence I think we need add docs. list what dependence need? Also, add a script to install the dependence that CustomPiOS need. -Neko.vecter |
Since problem solved... I think we can close this issue? Conclusion: -Neko.vecter |
After commit
d8c63803c17a3bcab6eb61c14280c5a9a4c16711
. Cannot create a larger partition for img and and system /dev/loop0 always the size of original img. In my case I use raspbian (64bit). So, the root partition around 1.7G.The
df -h
look like below/dev/loop0 1.7G mount on
workspace/mount
/dev/loop1 256M mount on
workspace/mount/root
in config file I set
BASE_IMAGE_RESIZEROOT=4500
This issue starting at
06d9bdbb7077a792c7a5057e9a44cc384dfc87c3
it is not possible to use the configuration to create a larger disk partition.I think it might be related to the modification of
common.sh
. Based on the commit logs, support for Btfs was added in06d9bdbb7077a792c7a5057e9a44cc384dfc87c3
version.System info.
Update 2023/08/01
Things I try.
d8c63803c17a3bcab6eb61c14280c5a9a4c16711
(it works) (last version currently know is working)function enlarge_ext()
in last version that worked (it works)What change in
06d9bdbb7077a792c7a5057e9a44cc384dfc87c3
function enlarge_ext()
incommon.sh
-Neko.vecter
The text was updated successfully, but these errors were encountered: