ISO - save changes

Post here if you are a new Porteus member and you're looking for some help.
User avatar
Ed_P
Contributor
Contributor
Posts: 3154
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: ISO - save changes

Post#16 by Ed_P » 23 Feb 2013, 00:21

Yes, the old files were not copied to the new one.

To be a complete "resize" the old changes need to be copied to the new save file, the old save file renamed or deleted and the new save file renamed to the old name, otherewise the cheatcode needs to be changed to point to the new name.
Ed

User avatar
fanthom
Site Admin
Site Admin
Posts: 4566
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: ISO - save changes

Post#17 by fanthom » 23 Feb 2013, 09:59

On the FAT16 flash drive the save file is 64MB and on the root of the drive but Porteus is displaying a unsupported fs msg on about the 4th line when booting and the save drive is not being used.
just to be sure:
you are booting Porteus from FAT16 formatted partition (so this fs is supported by the kernel) and getting 'unsupported fs' message when linuxrc is trying to use it as savefile container, right?

please do a simple test for me:
run 'mloop /path_to/64MB.dat' container and then show me output of 'losetup -a' and 'cat /proc/mounts' commands.

also - (if possible), could you boot porteus with 'debug' cheatcode and take a photo of your screen when get 'usnupported fs' message, please.

thanks
Please add [Solved] to your thread title if the solution was found.

User avatar
Ed_P
Contributor
Contributor
Posts: 3154
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: ISO - save changes

Post#18 by Ed_P » 23 Feb 2013, 16:12

you are booting Porteus from FAT16 formatted partition
Yes and it is the only partition on the flash drive.
and getting 'unsupported fs' message when linuxrc is trying to use it as savefile container, right?
I'm not sure what is prompting the error msg. But it is about the 3rd or 4th line produced when booting and the boot process is quick, very quick. How about a cheatcode that freezes the booting after x lines? freeze=10 would be perfect. :D
also - (if possible), could you boot porteus with 'debug' cheatcode and take a photo of your screen when get 'usnupported fs' message, please.
I will do my best to get a picture. Did I mention that this process is quick. :D
please do a simple test for me:
run 'mloop /path_to/64MB.dat' container and then show me output of 'losetup -a' and 'cat /proc/mounts' commands.
I would if I had a clue how to do either of those things. My background is DOS and Windows. At this point I don't know how to get to a Linux Command Prompt window or how to save the output shown in such a window. In Windows, no problem.

hmmmm Booting Porteus via QEMU in Windows is slow, very slow,.....
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3154
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: ISO - save changes

Post#19 by Ed_P » 23 Feb 2013, 17:34

A picture of the error.
http://img441.imageshack.us/img441/1047 ... serror.png

Your commands.

Code: Select all

root@porteus:~# mloop porteussave.dat
using /dev/loop9

Please wait while i gather some info ....


Sorry, that file was not found
root@porteus:~# mloop /porteussave.dat
using /dev/loop9

Please wait while i gather some info ....


Sorry, that file was not found
root@porteus:~# mloop /sdb1/porteussave.dat
using /dev/loop9

Please wait while i gather some info ....


Sorry, that file was not found
root@porteus:~# mloop /mnt/sdb1/porteussave.dat
using /dev/loop9

Please wait while i gather some info ....

NTFS signature is missing.
Failed to mount '/dev/loop9': Invalid argument
The device '/dev/loop9' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?


#################################
Your data file has been mounted at:
/mnt/loop

You can unmount it by typing uloop

Here is a list of the files:

root@porteus:~# 

root@porteus:~# losetup -a
/dev/loop0: [2065]:4 (/mnt/sdb1/ISOs/Porteus-v2.0-i486.iso)
/dev/loop1: [1792]:2438 (/mnt/live/opt/isoloop/porteus/base/000-kernel.xzm)
/dev/loop2: [1792]:2443 (/mnt/live/opt/isoloop/porteus/base/001-core.xzm)
/dev/loop3: [1792]:2447 (/mnt/live/opt/isoloop/porteus/base/002-xorg.xzm)
/dev/loop4: [1792]:2452 (/mnt/live/opt/isoloop/porteus/base/004-razor.xzm)
/dev/loop5: [1792]:2456 (/mnt/live/opt/isoloop/porteus/base/005-apps.xzm)
/dev/loop6: [1792]:2460 (/mnt/live/opt/isoloop/porteus/base/006-abiword.xzm)
/dev/loop7: [1792]:2465 (/mnt/live/opt/isoloop/porteus/base/007-devel.xzm)
/dev/loop8: [1792]:2469 (/mnt/live/opt/isoloop/porteus/base/008-firefox.xzm)
root@porteus:~# cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /mnt/live tmpfs rw,relatime,mode=755 0 0
proc /mnt/live/proc proc rw,relatime 0 0
sysfs /mnt/live/sys sysfs rw,relatime 0 0
none /mnt/live/dev devtmpfs rw,relatime,size=895772k,nr_inodes=221764,mode=755 0 0
/dev/sda1 /mnt/sda1 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/sda2 /mnt/sda2 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/sda3 /mnt/sda3 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/sda5 /mnt/sda5 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/sda6 /mnt/sda6 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/sdb1 /mnt/sdb1 vfat rw,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,check=s,utf8,errors=remount-ro 0 0
/dev/loop0 /mnt/live/opt/isoloop iso9660 ro,relatime 0 0
tmpfs /mnt/live/memory/changes tmpfs rw,relatime,size=1075584k 0 0
aufs / aufs rw,relatime,si=79e70084,nowarn_perm 0 0
/dev/loop1 /mnt/live/memory/images/000-kernel.xzm squashfs ro,relatime 0 0
/dev/loop2 /mnt/live/memory/images/001-core.xzm squashfs ro,relatime 0 0
/dev/loop3 /mnt/live/memory/images/002-xorg.xzm squashfs ro,relatime 0 0
/dev/loop4 /mnt/live/memory/images/004-razor.xzm squashfs ro,relatime 0 0
/dev/loop5 /mnt/live/memory/images/005-apps.xzm squashfs ro,relatime 0 0
/dev/loop6 /mnt/live/memory/images/006-abiword.xzm squashfs ro,relatime 0 0
/dev/loop7 /mnt/live/memory/images/007-devel.xzm squashfs ro,relatime 0 0
/dev/loop8 /mnt/live/memory/images/008-firefox.xzm squashfs ro,relatime 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
devtmpfs /dev devtmpfs rw,relatime,size=895772k,nr_inodes=221764,mode=755 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,relatime,mode=755 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
root@porteus:~# 
-UPDATE-

The problem is the Space File Manager's Resize function. I deleted the 64MB save file that it created, recreated a new 64MB one, rebooted, same FAT16 flash drive, NO problem. The save file appears to be working. I'll find out next reboot.


Confirmed. Changes were saved. :good:
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5456
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: ISO - save changes

Post#20 by brokenman » 24 Feb 2013, 00:18

The problem is the Space File Manager's Resize function.
I think you mean Porteus Settings Centre resize.

I just checked the savefile resize function and it works fine. Old files are copied over correctly. Would you prefer that the old save-file were deleted and replaced with the new one? I guess this makes more sense but i was too scared of deleting someones changes file in case something went wrong with the new file. If it is preferred that the new 'resized' save file replaces the old one then i can certainly code that in and push an update.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3154
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: ISO - save changes

Post#21 by Ed_P » 24 Feb 2013, 04:08

brokenman wrote:The problem is the Space File Manager's Resize function.
I think you mean Porteus Settings Centre resize.
Well there's no question you know more about Porteus than I do. This is a screen shot of the app I used to resize the save file. My results have previously been described.

http://imageshack.us/photo/my-images/713/screenswr.png/
brokenman wrote:Would you prefer that the old save-file were deleted and replaced with the new one?
No. Is that what happens when you resize a window? Resize to me at least means the current contents remain. Deleteing and reallocating to me means Replace not Resize. IMHO
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5456
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: ISO - save changes

Post#22 by brokenman » 24 Feb 2013, 13:22

Ok, but a window is not like a file container. Think of it as a box. If you want to resize a box, you need to take everything out, dismount it and rebuild it, then put everything back in. Or you can make a bigger box and transfer the contents. Perhaps a i will just replace the old container with the new one. Thanks for your thoughts.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3154
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: ISO - save changes

Post#23 by Ed_P » 24 Feb 2013, 14:27

Ok, your box example is better than my window example, and deleting the old and adding a new is an interesting option, but if you use that approach it should be labeled Replace rather than Resize.

I like the idea of resizing an existing space file, ie not loosing what has been saved and keeping the same file name, which is why I used it. But for some reason it didn't work for me. The FAT16 format of my flash drive may have played a part. I wasn't using the EXIT: option at that point.

Is there a way to know how much of the space file is used or available? Or what's in it?
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5456
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: ISO - save changes

Post#24 by brokenman » 24 Feb 2013, 14:36

You can mount the porteussave.dat on a read only loop.

Code: Select all

mloop /mnt/sda6/dump/porteussave.dat
du -sh /mnt/loop  # Show the amount used
df -h /mnt/loop # show how much is left
uloop # unmount the loop
The above commands are porteus specific and won't work on other distros.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3154
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: ISO - save changes

Post#25 by Ed_P » 24 Feb 2013, 15:08

Thanks brokenman. :good:

This is what I see:

Code: Select all

root@porteus:~# mloop /mnt/sdb1/porteussave.dat
using /dev/loop10

Please wait while i gather some info ....

mount: wrong fs type, bad option, bad superblock on /dev/loop10,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so



#################################
Your data file has been mounted at:
/mnt/loop

You can unmount it by typing uloop

Here is a list of the files:

root@porteus:~# du -sh /mnt/loop
0	/mnt/loop
root@porteus:~# df -h /mnt/loop
Filesystem      Size  Used Avail Use% Mounted on
aufs            1.1G  3.9M  1.1G   1% /
root@porteus:~# uloop

nothing is mounted in /mnt/loop

root@porteus:~# 

and of course I don't understand it. I have a save file, it is 64MB not 1.1G and I know it has my changes in it since I just booted and they are here. :%)
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5456
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: ISO - save changes

Post#26 by brokenman » 24 Feb 2013, 15:23

Definitely an issue with the save file. Perhaps corruption. To test it please create a new savedat file through the Settings Centre with the default xfs file system.

This time mount it as writable:

Code: Select all

mkdir /tmp/dat
mount -t auto /path/to/porteussave.dat /tmp/dat
cp /usr/share/applications/* /tmp/dat  # Copy a bunch of files to it.
umount /tmp/dat
The above commands are NOT porteus specific and should work on any distro.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3154
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: ISO - save changes

Post#27 by Ed_P » 24 Feb 2013, 15:46

:oops: When I enter the commands in Terminal mode the error msg flashes by and I don't see it but in my posting it's hard to miss!! What the heck??

The thing is the file is working!! Let me reboot without the EXIT: option and see if that makes a difference.
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3154
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: ISO - save changes

Post#28 by Ed_P » 24 Feb 2013, 15:59

Ok, I removed EXIT: from my changes= cheatcode, rebooted, most of my changes are still here but the FF bookmarks I've added are now gone. And the results of your terminal commands is now:

Code: Select all

root@porteus:~# # mloop /mnt/sdb1/porteussave.dat
root@porteus:~# du -sh /mnt/loop
du: cannot access ‘/mnt/loop’: No such file or directory
root@porteus:~# uloop
/usr/bin/uloop: line 12: [: : integer expression expected

nothing is mounted in /mnt/loop

root@porteus:~# 

I've had enough. :beer:
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3154
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: ISO - save changes

Post#29 by Ed_P » 24 Feb 2013, 20:12

OK, will try this again, with no comment character at the begining of the line this time.

Same FAT16 partition, same save file, no EXIT: option.

Code: Select all

root@porteus:~# mloop /mnt/sdb1/porteussave.dat
using /dev/loop10

Please wait while i gather some info ....

mount: wrong fs type, bad option, bad superblock on /dev/loop10,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so



#################################
Your data file has been mounted at:
/mnt/loop

You can unmount it by typing uloop

Here is a list of the files:

root@porteus:~# dmesg
[    0.000000] Linux version 3.7.8-porteus (root@porteus) (gcc version 4.7.1 (GCC) ) #1 SMP PREEMPT Fri Feb 15 12:03:14 UTC 2013

:
:
:


[   13.129140] [drm] Internal thermal controller without fan control
[   13.129281] [drm] radeon: power management initialized
[   13.482120] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input13
[   13.509110] mousedev: PS/2 mouse device common for all mice
[   13.553041] [drm] fb mappable at 0x80142000
[   13.553051] [drm] vram apper at 0x80000000
[   13.553056] [drm] size 4325376
[   13.553061] [drm] fb depth is 24
[   13.553065] [drm]    pitch is 5632
[   13.553211] fbcon: radeondrmfb (fb0) is primary device
[   14.100498] Console: switching to colour frame buffer device 170x48
[   14.117906] fb0: radeondrmfb frame buffer device
[   14.117911] drm: registered panic notifier
[   14.118362] [drm] Initialized radeon 2.24.0 20080528 for 0000:00:01.0 on minor 0
[   17.764947] NET: Registered protocol family 10
[   17.820244] atl1c 0000:06:00.0: irq 42 for MSI/MSI-X
[   17.844100] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   34.674443] ata1.00: configured for UDMA/100
[   34.674457] ata1: EH complete
[   38.895886] qxkb[2479]: segfault at 94 ip b695ef16 sp bfa883a0 error 4 in libX11.so.6.3.0[b68d5000+132000]
[  204.810642] XFS (loop10): Filesystem has duplicate UUID 108ea2ba-dfd6-404b-90c3-91bce62c8035 - can't mount
Well I did the dmesg but its beyond me to figure out.

As for this:
brokenman wrote:To test it please create a new savedat file through the Settings Centre with the default xfs file system.
Is the Settings Centre the same as the Razor Configuration Center cause I'm not finding a Settings Centre?


Oh! System Settings>Porteus Settings Centre Found it. Will see what to do.


I tried a Porteus Settings Centre Savefile Manager Recover option and got a Porteus msg to view this log.
savefile-recovery.log wrote:Phase 1 - find and verify superblock...
Cannot get host filesystem geometry.
Repair may fail if there is a sector size mismatch between
the image and the host filesystem.
Phase 2 - using internal log
- zero log...
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed. Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair. If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3154
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: ISO - save changes

Post#30 by Ed_P » 24 Feb 2013, 22:55

Ok, I think I'm done here.

I deleted the porteussave.dat file on the USB flash drive.
I rebooted to Windows and ran CHKDSK on the flash drive. CHKDSK found no errors.
I readded the EXIT: option to my changes= boot parameter.
I rebooted Porteus and use the attached image app to recreate the Porteus Save Changes file. porteussave.dat 64MB
Image
(Uploaded with ImageShack.us)
I ran a mloop on the new porteussave.dat file. This is what it showed.

Code: Select all

root@porteus:~# mloop /mnt/sdb1/porteussave.dat
using /dev/loop9

Please wait while i gather some info ....



#################################
Your data file has been mounted at:
/mnt/loop

You can unmount it by typing uloop

Here is a list of the files:

root@porteus:~#
I rebooted Porteus.
I ran another mloop on the new porteussave.dat file. This is what it showed.

Code: Select all

root@porteus:~# mloop /mnt/sdb1/porteussave.dat
using /dev/loop10

Please wait while i gather some info ....

mount: wrong fs type, bad option, bad superblock on /dev/loop10,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so



#################################
Your data file has been mounted at:
/mnt/loop

You can unmount it by typing uloop

Here is a list of the files:

root@porteus:~# dmesg | tail
[   14.702463] fb0: radeondrmfb frame buffer device
[   14.702464] drm: registered panic notifier
[   14.703449] [drm] Initialized radeon 2.24.0 20080528 for 0000:00:01.0 on minor 0
[   18.009302] NET: Registered protocol family 10
[   18.240912] atl1c 0000:06:00.0: irq 42 for MSI/MSI-X
[   18.254729] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   35.017177] ata1.00: configured for UDMA/100
[   35.017197] ata1: EH complete
[   39.723021] qxkb[2966]: segfault at 94 ip b6959f16 sp bfd88e20 error 4 in libX11.so.6.3.0[b68d0000+132000]
[   79.043234] XFS (loop10): Filesystem has duplicate UUID 86bf39ee-fa3f-4de5-a068-a17da83834a6 - can't mount
root@porteus:~# 

I did nothing other than what I have posted here.


Porteus appears to have a problem with my FAT16 flash drive.

PS Same situation with my FAT32 flash drive and it's 128MB porteussave.dat file.

Code: Select all

root@porteus:~# dmesg | tail
[   19.955909] fb0: radeondrmfb frame buffer device
[   19.955914] drm: registered panic notifier
[   19.956360] [drm] Initialized radeon 2.24.0 20080528 for 0000:00:01.0 on minor 0
[   23.117080] atl1c 0000:06:00.0: irq 42 for MSI/MSI-X
[   23.145348] NET: Registered protocol family 10
[   23.156935] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   41.751653] ata1.00: configured for UDMA/100
[   41.751673] ata1: EH complete
[   45.765604] qxkb[2488]: segfault at 94 ip b69f1f16 sp bf97f430 error 4 in libX11.so.6.3.0[b6968000+132000]
[  107.784764] XFS (loop10): Filesystem has duplicate UUID 53633a40-a5a9-4d30-9c17-760b0f6b2b2c - can't mount
root@porteus:~# 
And both files show as being "filesystem is posix compatible" when booting.
Ed

Post Reply