SOLVED - save.dat issues

[Englischdude]

Hi,

i am having some issues with saving to my save.dat. Everytime I go through the process there are a number of error messages which appear. my system is in german hence one of the messages being in german.

Here is the procedure I use:

- under system - system settings open the save manager
- select save to existing file and I navigate to the save.dat
- now when I click save session I get various error messages before at the end getting a window telling me that the session was successfully saved, however a reboot results in the loss of the changes.

Here the error messages:

1st message: Einhängen von Datenträger 537mb nicht möglich, Device /dev/loop12 is already mounted at `/mnt/loopsave'.

2nd message: Error mounting /dev/loop12 at /run/media/root/98ad0b3c-4ab2-4f75-a62e-3a8be233047e: Command-line `mount -t "xfs" -o "uhelper=udisks2,nodev,nosuid" "/dev/loop12" "/run/media/root/98ad0b3c-4ab2-4f75-a62e-3a8be233047e"' exited with non-zero exit status 32: mount: block device /dev/loop12 is write-protected, mounting read-only
mount: /dev/loop12: can't read superblock

3rd message: confirming my session has been saved to /mnt/mmcblk0p1/porteus/save.dat



any help would be appreciated.

[Englischdude]

and here some more info to help with the diagnosis:

root@porteus:~# cat /var/log/porteus-livedbg /proc/cmdline
# Recognized devices:
/dev/sda1: LABEL="System-reserviert" UUID="F08C806B8C802E62" TYPE="ntfs"
/dev/sda2: UUID="86E283AAE2839CD5" TYPE="ntfs"
/dev/mmcblk0p1: LABEL="USB-Stick" UUID="27af9fc6-7150-4128-bd87-88ff55ff2632" TYPE="ext4"

# Booting device:
/mnt/mmcblk0p1

# Porteus data found in:
/mnt/mmcblk0p1/porteus

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/mmcblk0p1/porteus/base/000-kernel.xzm
/mnt/mmcblk0p1/porteus/base/001-core.xzm
/mnt/mmcblk0p1/porteus/base/001-core_alldesktops-150124.xzm
/mnt/mmcblk0p1/porteus/base/002-xorg.xzm
/mnt/mmcblk0p1/porteus/base/002-xorg_alldesktops-150126.xzm
/mnt/mmcblk0p1/porteus/base/003-mate.xzm
/mnt/mmcblk0p1/porteus/base/004-mate_fixes-150124.xzm
/mnt/mmcblk0p1/porteus/base/0099-settings.xzm
/mnt/mmcblk0p1/porteus/base/04-firefox.xzm
/mnt/mmcblk0p1/porteus/base/06-abiword.xzm
/mnt/mmcblk0p1/porteus/base/08-skype.xzm
/mnt/mmcblk0p1/porteus/modules/locales-de_DE.utf8-i486-1prt.xzm
quiet initrd=initrd.xz changes=/porteus timezone=Europe/Zurich kmap=de,us login=root BOOT_IMAGE=vmlinuz

[W8nGGh0sT]

Sorry, but i did not recognized your point.
Are u trying to make a partition NFTS for a new installation ?
I've donne something like that to install Porteus to hard drive, and i used a Porteus tool that runs in "Always Fresh" mode.
I remember that Porteus has asked me to try do a save.dat before install
In any case there is http://www.porteus.org/info/tips-and-tricks.html#2

C yah

[fanthom]

this is wrong:

Code: Select all

changes=/porteus

you should point it to your save.dat (if it was created properly).

[Englischdude]

oh je, now I have even bigger fish to fry. Cant even boot from the SD Card even though I have changed nothing. Now when I boot I just get a black Screen prompt stating something like no Default or UI directive found or something. Will do a fresh install when I get home from my travels tomorrow on a new sd Card and see if that solves the Problem.

[stuck on stupid]

What mode did you boot into standard desktop or always fresh/ram? It looks like the you usb is in ready only mode.

[Englischdude]

So, seems like the sd card i was using has used up its service life. I just installed the iso on a new card using rufus and all is fine. I still have some elementary newbie questions concerning saving.

1. What is the difference between saving to a file and saving to a module?
2. I have setup my save.dat file using the manager and changed porteus.cfg accordingly. Are all changes saved automatically? At the moment if i make any changes i always go to save session and save to my save.dat file before shutting down and clicking on remove previous changes. Is that the right procedure?
3. When saving the session as detailed in point 2 i get a message saying that the available space in root filesystem is limited.
4. My save.dat file is growing. I originally set it up as 512mb but now is more than 600. should all changes not be contained within the 512mb limit originally set up?

I would appreciate some clarification as to the use of the save function.
Many thanks.

[brokenman]

Glad you got it sorted.

1. What is the difference between saving to a file and saving to a module?
Saving to a file creates a .dat file which supports encryption. Saving to a module does not.

2. I have setup my save.dat file using the manager and changed porteus.cfg accordingly. Are all changes saved automatically? At the moment if i make any changes i always go to save session and save to my save.dat file before shutting down and clicking on remove previous changes. Is that the right procedure?
Changes are saved automatically.

3. When saving the session as detailed in point 2 i get a message saying that the available space in root filesystem is limited.
The root file system is a live file system and is limited by your RAM. If you are booting with the changes= and saving to disk this is not the case. It should be noted that a 'save file' is only required when saving on a FAT32/NTFS file system. Whenever possible you should ormat your install media with a linux file system and instead of using a .dat file just save to a folder on the device.

4. My save.dat file is growing. I originally set it up as 512mb but now is more than 600. should all changes not be contained within the 512mb limit originally set up?
Your save file can be stripped of many things but it is hard for another person to know what to strip.

[Englischdude]

solved.

managed to get a fresh install working with a ext3 file system. The reason I was using fat was I was having problems getting a linux install to work.

All saving is done automatically, all working as expected.

[francois]

Very good decision. Porteus is Linux, and ext3 is Linux filesystem, the match is as best as it could be. 8)