From the docs:
[i]You can boot only from OS images that are loaded from within the first 1024 cylinders of the disk. This means that while you may be able to initially install and boot from a partition which extends past the 1024th cylinder, it will someday fail when you go to update the boot image because the location of some of its blocks may change. When this happens you will have a system which is no longer bootable.
Avoid this problem by creating a separate partition to boot from that lies entirely within the first 1024 cylinders of the hard drive, and use a second partition to access the additional space on the drive. (The boot partition may be quite small – just a few megabytes will suffice.)[/i]
This came to me some time ago… Maybe you will want to reinstall a new hard disk with the new boot image, following the mentioned recommendations and transfer old data to the new disk…
We usually create a first small boot partition for system’s files (let’s say 8 GB), and others partitions for large data storage (databases, etc)
If those partitions will have more than 40 GB you MUST have updated Fsys, and Fsys.eide to the latest version (this is update your whole system) and when you build your boot image, it’s very important that you add “-Hdisk<disk_capacity_in_GB>” to Fsys in order to set the a bigger heap-size than the default (which was enough some years ago, but no nowadays…)
For example: Fsys … -Hdisk120
You can read more in:
qnx.com/developers/docs/qnx_ … #Heap_size
I hope you’ll find this useful.