Would you happen to know how I should get around this? Perhaps installing syslinux and unpacking all the dist-isos in their own directories? Using isohybrid (if that would help) on the iso images? On sysrescue and the Ubuntus, I don’t get the choice to specify where the isos are, that I know of, so it’s even trickier. I chose ‘sdc4’ but TRK still would not continue.) In TRK, it did not help to pull out the stick and plug it back in (it said that the stick was then recognized as sdc, with partitions sdc1 and sdc4. Like the iso-file wasn’t loopback mounted or similar. I’ve added all the Linux images in the ‘grub4dos compatible’ field for iso filenames, but when I boot, none of them sees their root filesystem. On the same stick, I have Windows 7, Windows 10 (who both installs just fine), then trinity-rescue-kit, systemrescuekit, Ubuntu 16.04 i386, and Ubuntu 18.04 圆4. Hello! I’ve got a bit of a hassle with starting Linux dists from the USB stick. If successful, I’d like to give you the steps I took for it, as well as to suggest that the default persistence label be changed to “casper-rw”. Right now testing with an 8 GB persistence file (wowzers) with UEFI:NTFS built usb using winsetupfromusb to put linux on there. Right now I’m testing a theory from “” and I might be interested in writing you up a tutorial on how to have UEFI:NTFS (from Rufus) combined with WSFUSB. It didn’t show it as a persistent drive, but /cow (the cow-file system that is used by ubuntu to make persistent live files) showed the right size, and changes were being written to the partition when I re-mounted it. I’m not sure if it’s because of the capital letters in the label or not, but it seems to have worked when I set the label SPECIFICALLY to “casper-rw” all lower-case. Tested with some changed files in /etc and /home - they work. Turns out that when I had casper-rw (all-lower-case) in my label, I WAS getting persistence! Linux just never mounted the disk directly – but when I checked the /cow directory it persisted. There’s a Linux tool called Multisystem which seems to be, according to most forum threads, able to get around this, and I don’t know how they’re doing it but it might be worth a shot looking at that? Maybe it will help improve the process for WSFUSB. And we can’t assume editing the files pretty much. May have the answer – in that it requires editing the files in an installed live USB – however, we’re not really doing LIVE USBs now are we? We’re doing emulated Live CDs off of USB. However, the idea of lower-casing the partition name sounded promising – in post #7 on that thread they say that using Multisystem they can get persistence to work with a casper-rw partition… I’ve rebuilt my linux mint with a 300 mb persistence file with lowercase partition name, but still no luck.Īpparently the newest Ubuntu, however, has the same problem – I tested it the other night with a friend’s stick and he had the same problem – no persistence with ubuntu 16.x using WSFUSB. Since partition #4 is used to create the booting file system, partition #3 being casper-rw is being ignored. Post #3 mentions that Ubuntu mangled casper such that it won’t recognize a casper-rw on the SAME DEVICE AS ONE IS BOOTING TO (emphasis mine). It seems the last post mentions that persistent partitions stopped working.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |