Unfortunately I can't see this error on my system. I boot from ext partition on my hard drive (sda1 usually). Can you give some more details about your setup like ext, vfat, ntfs partition. I will try to reproduce the same situation and test with 4Gb save file (I never use more than 1GB).Tm_mT wrote: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.saintless wrote:Do you see this fsck save file message on boot (before modules loading 01-filesystem.squashfs message).
I think the 2Gb limit is for Fat16 and Fat32 partitions (but then it should be impossible to create bigger save file on vfat partition and I see no reason for 2Gb limit in the utility). I didn't know it is limited this way for porteus-boot mk-save utility. Maybe there is a reason and Fred will give more information about this later.Tm_mT wrote: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 changes.dat
Still tried to copy the data to a 2 Gb file with the tool (seemed to work)
The script is combined for all boot methods and the only easy way to make bigger encrypted save file is to boot with live-boot-2x or live-boot-3x and create save file then. Just give it name changes.dat. Too much typing from command line otherwise.
I guess this is because you had more than 2Gb data in source save. I tested few times (with much smaller save file) by installing and removing programs and adding keyboard layout. After the copy in encrypted save file with move-in-crypt no problem to boot the encrypted save and all changes are there. I will test it with 4Gb files to see if there is any difference.After rebooting I needed to add the password, but then my keyboard entry wasn't accepted (it even hang completely..)
To be sure it wasn't something else, I used another keyboard, rebooted and the same result.
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 at the moment but I will try to test it somehow.
Edit2: OK, checked with 4Gb encrypted save and kernel 3.14 (vmlinuz6 and initrd63.xz). Using move-in-crypt to copy 2Gb non-encrypted in 4Gb encrypted save and boot with encrypted save file. I can't start X with 3.14 kernel because of my old hardware but the save file is checked for errors and changes are there (checked the new installed and removed programs from command line). Still can't reproduce the problem you have. It is working well for me.
Is the error message you get about save file: /dev/mapper/crypt was not clearly unmounted ... forced check...? If so this is only when using encrypted save file and seems /dev/mapper/crypt is not unmounted before reboot. I don't know if Fred can do something about this but I doubt it will create some kind of a problem. Save file is always checked on boot.
Toni