Haiku uses the BFS file system which currently can’t be resized. (there are old patches around that implemented this function but they were never merged for some reason).
So you have to create a new disk, add it to the machine and format it with BFS (with the DriveSetup app). Then you can use the installer from your existing installation to install Haiku on the new disk. As far as I remember the installer should transfer any setting changes that you made to the system.
If you can boot from the second drive, you can delete the old one.
Alternatively, you can reformat it and then use it to house the virtual memory, browser caches, user settings directory and so on. symlinks are your friends!
Yes of course. Just make sure you can boot from the newly created installation on the new drive. I would just remove the 2G from the VM first. If the new installation boots you can delete the old drive.
The reason is that the work was not complete, and it would leave you with a corrupt, half-resized disk. It seems better to finish it before merging it, otherwise people would (rightfully) complain that they tried to use it and it ate all their data.
I fully agree, I just couldn’t remember what the exact reason was. Thanks for the explanation.
Btw, where can I find these patches? Not that I’ll be of much help, my knowledge of file system internals is very rudimentary.
Checksum errors are often caused by the server (outdated packages in the CDN cache).
Can you please share the terminal output you got when running pkgman?