Radxa rock 5b instalation problem

it’s not some advanced error (I’ve already dealt with it) so I’ll skip all the required information, after a fresh installation the first run script returned an error, I managed to find out that the error was related to the fact that there was insufficient space on the partition, 100MB was required and 81MB was available, I used dietpi-drive_manager and after resize the error disappeared.

the error has been solved as I wrote above

Could you share the log oft the script which should have done the expansion?

cat /var/tmp/dietpi/logs/fs_partition_resize.log

this is the output of this log

[ INFO ] Detected root drive /dev/mmcblk0 with root partition 1
GPT PMBR size mismatch (2285600 != 488554495) will be corrected by write.
The backup GPT table is not on the end of the device.
[ INFO ] Detected trailing DietPi setup partition /dev/mmcblk0p2
mount: /dev/mmcblk0p2 mounted on /tmp/tmp.LuM8mrtldc.
umount: /tmp/tmp.LuM8mrtldc (/dev/mmcblk0p2) unmounted
rmdir: removing directory, '/tmp/tmp.LuM8mrtldc'
GPT PMBR size mismatch (2285600 != 488554495) will be corrected by write.
The backup GPT table is not on the end of the device. This problem will be corrected by write.

The partition table has been altered.
Removed "/etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service".
[ INFO ] Detected root drive /dev/mmcblk0 with root partition 1
[ INFO ] No DietPi setup partition found, last partition is: "ext4 "
NAME             LABEL  SIZE TYPE FSTYPE MOUNTPOINT
/dev/mmcblk0            233G disk
└─/dev/mmcblk0p1        1.1G part ext4   /
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
Disk /dev/mmcblk0: 232.96 GiB, 250139901952 bytes, 488554496 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: DF944772-9EA6-4A59-A25C-8C9F79E53477

Old situation:

Device         Start     End Sectors  Size Type
/dev/mmcblk0p1 32768 2283519 2250752  1.1G Linux filesystem

/dev/mmcblk0p1:
New situation:
Disklabel type: gpt
Disk identifier: DF944772-9EA6-4A59-A25C-8C9F79E53477

Device         Start       End   Sectors   Size Type
/dev/mmcblk0p1 32768 488554462 488521695 232.9G Linux filesystem

The partition table has been altered.
resize2fs 1.47.0 (5-Feb-2023)
Filesystem at /dev/mmcblk0p1 is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 30
The filesystem on /dev/mmcblk0p1 is now 61065211 (4k) blocks long.```

Hmm it shows very well partition and filesystem expansion to 232 GiB :thinking:. … ah the drive manager enables just this very same service/script. It’s two runs indeed with a gap at an unexpected position, somewhere after the config partition was removed.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.