TinyCore(Pure64) 10.1 massive issue: non-deterministic FS->RAM mappings

[SeventhSin]

Hello,

I first noticed this in VMWare Workstation VMs, and thought it is related to Hypervisor weirdness however, the numbers stay... consistently inconsistent on hardware as well.

The data presented below has been pulled form post-boot df output on hardware.

System    : TinyCorePure64 10.1
Hardware : 10 GB RAM PC

Behold:

Boot 01: nogui boot, waitusb=0 => ROOTFS= 8.8G, TMPFS= 4.9G
Boot 02: nogui boot, waitusb=0 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 03: nogui boot, waitusb=0 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 04: nogui boot, waitusb=0 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 05: nogui boot, waitusb=0 => ROOTFS= 4.8G, TMPFS= 4.9G

Boot 06: nogui boot, waitusb=5 => ROOTFS= 8.8G, TMPFS= 4.9G
Boot 07: nogui boot, waitusb=5 => ROOTFS= 8.8G, TMPFS= 4.9G
Boot 08: nogui boot, waitusb=5 => ROOTFS= 8.8G, TMPFS= 4.9G
Boot 09: nogui boot, waitusb=5 => ROOTFS= 8.8G, TMPFS= 4.9G
Boot 10: nogui boot, waitusb=5 => ROOTFS= 8.8G, TMPFS= 4.9G

Boot 11: nogui boot, waitusb=10 => ROOTFS= 8.8G, TMPFS= 4.9G
Boot 12: nogui boot, waitusb=10 => ROOTFS= 8.8G, TMPFS= 4.9G
Boot 13: nogui boot, waitusb=10 => ROOTFS= 8.8G, TMPFS= 4.9G
Boot 14: nogui boot, waitusb=10 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 15: nogui boot, waitusb=10 => ROOTFS= 4.8G, TMPFS= 4.9G

Boot 16: GUI boot, waitusb=0 => ROOTFS= 8.8G, TMPFS= 4.9G
Boot 17: GUI boot, waitusb=0 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 18: GUI boot, waitusb=0 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 19: GUI boot, waitusb=0 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 20: GUI boot, waitusb=0 => ROOTFS= 8.8G, TMPFS= 4.9G

Boot 21: GUI boot, waitusb=5 => ROOTFS= 8.8G, TMPFS= 4.9G
Boot 22: GUI boot, waitusb=5 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 23: GUI boot, waitusb=5 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 24: GUI boot, waitusb=5 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 25: GUI boot, waitusb=5 => ROOTFS= 4.8G, TMPFS= 4.9G

Boot 26: GUI boot, waitusb=10 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 27: GUI boot, waitusb=10 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 28: GUI boot, waitusb=10 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 29: GUI boot, waitusb=10 => ROOTFS= 4.8G, TMPFS= 4.9G
Boot 30: GUI boot, waitusb=10 => ROOTFS= 8.8G, TMPFS= 4.9G

Conclusions:

1. FS->RAM mapping is semi-deterministic at best (deterministic=good, non-deterministic=bad, semi-deterministic=worse)
2. waitusb seems to help somewhat on hardware, however it is not a solution, non-determinism still manifest