I had a problem with the fat32 partition on my images. I just had to reimage it... use HDD Raw Copy. It doesn't ALWAYS work, but it does most of the time. Also, make sure your flash drive or hard drive is bigger than 16gb. I ran into a problem with mine where the drive was just a hair shy of the required size for the image and that caused partition file table problems that made the first part unreadable.
You could also use gparted to try to repair the partition which works sometimes. Or use TestDisk if you're savvy with partition file table manipulation at all.
http://www.cgsecurity.org/wiki/TestDisk_DownloadIt isn't important at all as you do image what software and in what operating system. At the first loading everything is read perfectly!
Important the fact that after incorrect completion of nvOC (for example the system is too overclocked) data on FAT32 /dev/sda1 are damaged and you are stimulated every time to repair this partition and to do mount, remount. look above how many restarts of nvOC at me happen in days. Every time is a potential problem of damage of FAT32. IMHO needs to refuse this partition, to transfer oneBash to other directory and to modify it, using gnome (local) or ssh, sftp (remote).
Of course I will try to find the stable and balanced configuration of my system. I plunge into Linux more and more and I look for analysis techniques of system dumps.
All of good luck!
[/quote]
I don't disagree with you that oneBash on a fat32 part instead of exFat isn't ideal for a linux o/s to read. I've run into problems today where my oneBash file was just empty entirely and so nvOC wouldn't boot.
Copying oneBash to /home/m1/ on boot might be a more elegant solution to avoid these partition issues, or just avoid that partition entirely by downloading pastebin text directly to /home/m1.
Even windows doesn't like fat32 partitions that small... it forces you to format it in fat instead, so its no surprise that linux doesn't play nice with it I guess.