Porteus

When making a save.dat, it gets up to 1023mb and then the following:

"Building save.dat (1023 Mb)
XXX
XXX
Building save.dat (1.0 Mb)
XXX
/opt/porteus-scripts/make-changes.sh: line 91: [: 1.0: integer expression expected"

I've reinstalled Porteus but have had no luck. I am running the 32bit version on a 16GB FAT32 USB drive.

Please let me know if there's any more information I should supply, and thanks in advance


EDIT: I tried making another save.dat file but now with 1000MB, but I got a 'losetup: /dev/loop10: device is busy' error once it reached 1000MB.

Hi Ekot,

This is a known bug, with a fix.

If you are using 32-bit Porteus, please go to this link:

http://ponce.cc/porteus/i486/testing/1.0-fixes/

If you're using 64-bit, please go to this link:

http://ponce.cc/porteus/x86_64/testing/1.0-fixes/


Download the save.dat_manager-1.0-fix.xzm file, and copy it to your /mnt/sdXY/porteus/modules/ folder (where sdXY is the device on which Porteus is installed). Then, reboot, and try again. This should resolve the issue. If not, please let us know.

Other fixes are in the same folder on the server, if you're interested in installing them as well (they all go in /porteus/modules/, except the linuxrc fix, which needs to be extracted -- it contains a replacement initrd.xz that goes in /boot/).

Thanks!

Thanks for your quick reply! The fix worked and I now have my save.dat file. However, on boot it says the file at /mnt/sdb1 cannot be found, even after I have confirmed its location.

Any ideas? :S

what is the name and location of your save.dat on disk (e.g. /mnt/sda1/porteus/yoursave.dat), and how is the location specified in /boot/porteus.cfg (e.g. changes=/dev/sda1/porteus/yoursave.dat) ?

The file is definitely named changes.dat and in /media/sdb1/

In porteus.cfg it is specified as changes=/mnt/sdb1/changes.dat

I have also tried changing this to changes=/media/sdb1/changes.dat, but this won't work either.

Thank you.

hi Ekot,

pls try "changes=UUID:" as described in /boot/docs/cheatcodes.txt. this is most reliable method of finding files, folders, devices, etc...

please also run the command 'psinfo' in a console. This will generate a text file and put it on your desktop. Please post the contents to pastebin and post a link to them here.

On my way in to work this morning I created a save.dat and tested using it in the root of my device, with changes=/mnt/sdb2/saved.dat, and it seemed to work fine. I know changes=/dev/sdb2/ worked for me in the past, and now I use the UUID method as fanthom suggests...I'd like to see more info on your system to see if that will help us sort this out.

thanks!

Here's the pastebin from psinfo.txt. http://pastebin.com/vuDD1Tgi while I attempt Fanthoms suggestion.

Posted after 5 hours 37 minutes 53 seconds:
I've changed it to changes=UUID:mnt/sdb1/changes.dat but I must be doing something wrong.

Any help is appreciated.

Hi Ekot,

To use the UUID, you need to have the UUID, which is a unique string of characters that is associated with your particular device/partition. To get the UUID, you need to issue the command 'blkid' in a terminal. That will print all of your mounted drive partitions and their UUID's, for example:

/dev/sdb1: UUID="d52de253-ae12-424a-9d99-1a62d26bbb6a" TYPE="vfat"

So, in this case, your UUID would be 'd52de253-ae12-424a-9d99-1a62d26bbb6a '

and your porteus.cfg entry should read:
of course, replacing the d5.... string of characters with the one that actually shows up for /dev/sdb1 when you issue the blkid command.

Please also provide the output of the following command:
EDIT:

if that returns nothing, then please provide the output of:

The UUID Method hasn't seemed to have worked.

The output from the first command '-rwxrwxrwx 1 root root 4193255424 Jul 11 23:38 changes.dat*'

The output from the second command ' find /mnt/sdb1 -name "*.dat"'

Well, I must say, you have me stumped. With changes.dat sitting in /mnt/sdb1/, you should be able to use any of the following:

changes=/changes.dat
changes=/mnt/sdb1/changes.dat
changes=/dev/sdb1/changes.dat
changes=UUID:StRiNG-of-CHaRs/changes.dat
And more.

The only thing I can think of is a corrupt .dat container or a very 'lazy' device that isn't getting picked up early in the boot process or something like that.

Maybe try creating another container (smaller this time, maybe 200mb, so it doesn't take so long), with a different name, set it up in /mnt/sdb1/newsave.dat, and point your porteus.cfg to changes=/dev/sdb1/newsave.dat. If that works, we can deal with the 4gb one.

Sorry to keep sending you back to the drawing board. It's hard to debug remotely sometimes

EDIT: Trying the delay= cheatcode, e.g. 'delay=9' might be worth a shot as well.