Not sure if it is relevant either but I figured I would include it as I didn’t have many other things to go off of that I did wrong in my eyes but I thought that could have been one of them. considering downsizing the vms storage before I realized there are risks associated with that, risks I am not willing to take…
It never maxed out entirely but around 1% was left at one point, and I determined this because in the top right a triangular yellow exclamation icon appeared telling me the percentage utilized and the percentage left of my total disk usage.
I apologize, I shutdown the machine in the normal manner via clicking the top right most icon/user icon and pressed it then pressed shutdown on the drop down menu and let the machine power down healthfully.
Not sure at what point the storage would have been corrupted or how I could tell but this may possibly be what happened, it took lots of CPU resources to try and start the cube seemingly idling however. I even took what one user said and increased the timeout time to 300 seconds/5 minutes with no avail as the results were the same. I also compared logs with a healthy boot from another VM on my machine and I did not have the same “A start job is running for initial…” which makes me think something else was bugged that caused this to hang/loop without ever finishing.
This assumption however I wish were true is mistaken lol, this is also why I was so concerned, and what I did ended up being this however since I didn’t have a backup I had to do something else to recover the files from the vm without booting it. I detail that solution in my other post here “How to recover files from a non functional (won't start) Qubes VM” So my files have been successfully recovered at this point however I do appreciate your trying to help me.