I installed ARM64 CHR 7.15rc3 on Hetzner CAX servers with 40GB disk using this guide: https://community.hetzner.com/tutorials/mikrotik-chr-basic-setup
but after rebooting the server in winbox/Resources it shows only 9GiB of Total HDD Size!
no issue with x86 CHR on CPX servers (in winbox/Resources shows 37.9GiB Total HDD Size).
i want to know if there is a bug in CHR arm64 image or i am doing something wrong?
thanks.
stmx38
June 20, 2024, 9:03am
2
Bug on CHR ARM was confirmed and will be fixed in the next version - http://forum.mikrotik.com/t/v7-16beta-testing-is-released/176494/1
Re-installation will be required
stmx38
June 20, 2024, 2:51pm
4
Can we use at Hetzner a workaround mentioned by nescafe2002 ?
It works on 7.16beta2
you can expand the filesystem manually in Hetzner rescue console:
root@rescue ~ # e2fsck -f /dev/sda2
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda2: 45/2391200 files (2.2% non-contiguous), 620354/9991168 blocks
root@rescue ~ # resize2fs /dev/sda2
resize2fs 1.47.0 (5-Feb-2023)
Resizing the filesystem on /dev/sda2 to 39964672 (1k) blocks.
The filesystem on /dev/sda2 is now 39964672 (1k) blocks long.
root@rescue ~ # reboot
You may run into problems in future due to different disk block sizes.
Reinstall would be more safe solution (when version is released).
Fixed in 7.16beta3 (2024-Jun-27 08:33):
*) chr - fixed incorrect disk size for ARM64;
[admin@MikroTik] > system/resource/print
uptime: 36s
version: 7.16beta3 (testing)
build-time: 2024-06-27 05:33:05
free-memory: 3633.8MiB
total-memory: 4000.0MiB
cpu: ARM64
cpu-count: 2
cpu-load: 0%
free-hdd-space: 36.4GiB
total-hdd-space: 36.4GiB
write-sect-since-reboot: 3442553
write-sect-total: 3442553
architecture-name: arm64
board-name: CHR Hetzner vServer
platform: MikroTik