Seeing some error messages, but will continue. root@debian:/opt/bin/special/patch-live-initrd# /opt/bin/special/patch-live-initrd/patch-initrd Extract initrd? (y/n) y Apply patches automatically? (y/n) y cp: cannot create regular file `extracted/scripts/': No such file or directory cp: cannot create...
BTW. Not sure if it is worth mentioning, but I think I noticed twice that after creating an encrypted save file (the default method) it is not possible anymore to shutdown my PC. Maybe it is totally unrelated, but if it is worth checking out further let me know and I can check if I can consistently ...
A copy of the original initrd to patch should exist in this directory. Detected initrd files: initrd.img-3.14-0.bpo.1-686-pae Please enter the name of the initrd to extract: initrd.img File not found root@debian:/boot# cd /opt/bin/special/patch-live-initrd/ root@debian:/opt/bin/special/patch-live-i...
BTW. No rush, I will not be able to do more this evening and will check again tomorrow or the weekend (have a lot more time then) Thanks ! Thanks for your courage to test things but as a reminder.. my post from here: http://murga-linux.com/puppy/viewtopic.php?p=794575#794575 . Sometimes things just...
If you did this: Copy /boot/initrd.img-3.14-0.bpo.1-686-pae in /opt/bin/special/patch-live-initrd/ and rename it to initrd.img you should not have initrd.img-3.14-0.bpo.1-686-pae anymore. no I didn't I renamed it and then moved it from another directory so that is why both were still present. Maybe...
Type in terminal: /opt/bin/special/patch-live-initrd/patch-initrd Choose initrd.img as name to patch and confirm the patch questions. root@debian:/boot# /opt/bin/special/patch-live-initrd/patch-initrd Extract initrd? (y/n) y A copy of the original initrd to patch should exist in this directory. Det...
Testing is basically the only thing I can help with, so no problem to spend some time on that (usually the end user is causing his own problems anyway )
Will check all comments after diner and share the testing results.
The only line for non-encrypted unmount error message that can be useful is this one in /var/log/porteus-livedbg which I'm sure is the same (except UUID part) for you: /mnt/sda2//changes.dat: LABEL="persistence" UUID="a306672d-86ae-4263-88e6-f538cd584e5d" TYPE="ext4" L...
And does it boot and run normally after, no problems? And what happens when you enter password for encrypted save, no error message, nothing? Fred Hi Fred, sorry for not answering before. just noticed you also asked a question. Debian dog hangs, so no entering of a password at all. To illustrate th...
sure, no worries. The encryption is not necessary, it is only a nice to have so no rush.
If I can help with additional tests or uploading log files (isn't there anything in /var/log that can help you?) let me know.
Give me some more details to try to make the same setup as you. Jwm or OpenBox version (I guess it is still Jwm). Jvm indeed. Where is installed DebianDog - usb, hdd, what file system (ntfs, ext2,3,4, vfat)? sda2 hdd - ext4 How big is the save file and what file system (ext2, 3, 4)? non encrypted 4...
One thing I can't test and may be is important is Copy to Ram. I'm not sure Fred made such test with encrypted save also. Please, before posting answers to my questions remove copy2ram from your boot code to check if the same persistence unmounted error appears and if encrypted save works without c...
Do you see this fsck save file message on boot (before modules loading 01-filesystem.squashfs message). See attachment 2014-08-11 21.58.59.jpg, sorry for the bad quality Edit: Are you using vmlinuz6 and initrd63.xz? Is encrypted save file work at all for you? I can't start X with 3.14 kernel module...
Make sure it is the same size or bigger from the non-encrypted source save file. Just gave it a shot, unfortunately my save file is bigger than what was accepted by the make save file script. I think my previous savefile was created in live-boot 2 and there was no limit then. I created a 4 Gb chang...
saintless wrote:Do you see this fsck save file message on boot (before modules loading 01-filesystem.squashfs message).
The message comes after the message it is checking the dat file for errors. Then it reports persistence was not correctly unmounted and the check starts.