Sounds like a filesystem issue to me. I never run linux on fat. I do use fat pendrives for backup/restore but that is all. And if, you are unpacking Linux onto fat, surely permission issues will occur. Recently, an extension was submitted and the perms of all files were atypical. I would suggest to correct the partition table and format to native Linux. That is why I provide the pendrive installation scripts within DSLThanks for all the help so far Roberts. You have been awesome. I will try and reinstall the key with ext2 since I no longer need it to be accessible by winblows. Will post the results either way incase anyone else has this problem.Well, after 3 hours of trying, I can't get it to give me even the most basic bootloader (grub or otherwise) when the key is formated to ext2. If we aren't suposed to use FAT16 as the base file system on the key, why does the how-to say to do it that way? Or am I not understanding something?
Quote
I would suggest to correct the partition table and format to native Linux. That is why I provide the pendrive installation scripts within DSL
Your pendrive script doesn't format ext the pendrive.
legalize cannabis, etc.Yeah, I can't remember everything.
But the script does change the geometry and therefore avoids the tweaked, broken, bad partition table. A table that may be fine for Windows but appears with many error when viewed with fdisk -l in Linux.
I just tested a 512MB with a single partition using usbhdd script which is vfat (FAT!6) and am able to mount on cloop63
Perhaps the issue is/was the bad partition table.Next Page...
original here.