Boot bug

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
odys03
White ninja
White ninja
Posts: 14
Joined: 15 Sep 2014, 05:12
Distribution: Porteus 32bit lxde
Location: Greece

Boot bug

Post#1 by odys03 » 15 Sep 2014, 16:51

After four days of smooth and enjoyable usage, today I have the first real annoying bug or i do something wrong.
I always started the system with the first option in the boot screen. As i had configured the save.dat file everything was ok. My bookmarks, my wifi connection password, my firewall settings, were saved and the system was started updated.
But today i starded with the second option (clean boot) as i tried the usb stick in another laptop.
After this, even i start from the first option always the system starts clean, (as the first boot) all my bookmarks and settings are reseted every time i start.

I do something wrong or I have to fix something?

Thanks

User avatar
francois
Contributor
Contributor
Posts: 5124
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus artix
Location: C'est l'hiver: la neige soudainement est là à Montréal.

Re: Boot bug

Post#2 by francois » 15 Sep 2014, 17:34

If you system is set to save the changes all the time and you saved the clean environment, you have just overwrited all the changes that you had done precedently.

What is the content of your /boot/syslinux/porteus.cfg? Just show us the instructions in that file that you modified to have you save.dat file to retain changes.
Carpe diem.

odys03
White ninja
White ninja
Posts: 14
Joined: 15 Sep 2014, 05:12
Distribution: Porteus 32bit lxde
Location: Greece

Re: Boot bug

Post#3 by odys03 » 15 Sep 2014, 18:43

As after many tries i formatted the usb key I can't post the settings of the config file.

As I understand after i chose the second option of boot (clean install) the save.dat file corrupted with a .bat proccedure and always start the proteus with clean install. Very annoying! Sometimes we need clean boot to repair harddisks in other systems etc, but then we loose our proteus settings for normal use with bookmarks, firewall settings, internet wifi passwords....

I think this issue needs a solve with 2 diferent start config files one reffering to the normal use of proteus, and one for the clean boot mode, or when we use the clean mode the system must not save the session to the save.dat

Thanks I liked very much proteus and I wait forward to be better and more safe and stable.

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

Re: Boot bug

Post#4 by brokenman » 15 Sep 2014, 18:54

Booting Porteus into 'Always fresh mode' simply doesn't load your changes.dat file. The next time you boot into the first option all your changes should be back. I think Francois assumed that you booted into 'Fresh mode' and then saved the session and overwrote the original changes.

Something is wrong. Can you please boot into the first option and then run the Porteus Settings Centre and then run the information dump. Upload it to pastebin and post the link here.
How do i become super user?
Wear your underpants on the outside and put on a cape.

tome
Contributor
Contributor
Posts: 577
Joined: 26 Jun 2013, 14:03
Distribution: x64 Openbox
Location: Poland
Contact:

Re: Boot bug

Post#5 by tome » 15 Sep 2014, 19:29

Maybe your save.dat container was on first laptop HD drive. :Search:

odys03
White ninja
White ninja
Posts: 14
Joined: 15 Sep 2014, 05:12
Distribution: Porteus 32bit lxde
Location: Greece

Re: Boot bug

Post#6 by odys03 » 15 Sep 2014, 22:02

As i have formatted the usb stick and i made a new istallation I can't run the information dump. I just try to understand what i done wrong in the other laptops, as i run there the porteus with the second option of the boot (clear boot).
Thanks anyway the truth is i tried the usb stick in 4 different laptops and obviously i done something wrong.

User avatar
francois
Contributor
Contributor
Posts: 5124
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus artix
Location: C'est l'hiver: la neige soudainement est là à Montréal.

Re: Boot bug

Post#7 by francois » 16 Sep 2014, 00:53

Are you now able to save changes to desktop or not?

Do you keep them from laptop to laptop?
Carpe diem.

odys03
White ninja
White ninja
Posts: 14
Joined: 15 Sep 2014, 05:12
Distribution: Porteus 32bit lxde
Location: Greece

Re: Boot bug

Post#8 by odys03 » 16 Sep 2014, 11:24

As i have the same boot issue with the new installation let me write what i done.
I formatted the usbstick with the Porteus, then i created the save.dat file and i fixed the path for this. For 5 restarts in the same laptop all the changes were saved good (bookmarks, firewall settings etc).
I then run the porteus in another laptop and everything was good.
Again in the first laptop and everything was good.
After this I used windows to transefered a .mp4 file (a video) in the usb stick. (I copied it in the root directory of the usb) I used the stick to transfer the video in a desktop pc with windows.
After this i returned home to my laptop, And now Porteus started with clear boot by itself. All my bookmarks and settings lost again.

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

Re: Boot bug

Post#9 by Ed_P » 16 Sep 2014, 13:13

It sounds like a Windows machine's security software, AV, deleted it. And the software was probably configured to delete new, suspicious files automatically without user intervention.

Once you have the save.dat file configured the way you want at home, reboot and make a copy of the file on the home machine's hard drive. If possible, on the machines where the file disappears, see if you can access the AV's security logs. When you find the culprit notify the vendor of the software that it is catching a false positive.
Ed

tome
Contributor
Contributor
Posts: 577
Joined: 26 Jun 2013, 14:03
Distribution: x64 Openbox
Location: Poland
Contact:

Re: Boot bug

Post#10 by tome » 16 Sep 2014, 14:33

even worse antivirus than usual virus :)

odys03
White ninja
White ninja
Posts: 14
Joined: 15 Sep 2014, 05:12
Distribution: Porteus 32bit lxde
Location: Greece

Re: Boot bug

Post#11 by odys03 » 16 Sep 2014, 15:00

I can see that the porteussave.dat exists in the root folder of the usbstick. It isn't deleted from the windows.

Here is how i changed the path to find the system the .dat file

APPEND initrd=initrd.xz changes=/mnt/sdb/porteussave.dat

Is it possible to be corrupted this file, by my windows? Ι check the file now and it say it is has permissions for anyone to change but the logs from the dump file are these:

[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] e820: last_pfn = 0xb6000 max_arch_pfn = 0x100000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-D3FFF write-protect
[ 0.000000] D4000-DBFFF uncachable
[ 0.000000] DC000-DFFFF write-back
[ 0.000000] E0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0FFE00000 mask FFFE00000 write-protect
[ 0.000000] 1 base 000000000 mask F80000000 write-back
[ 0.000000] 2 base 080000000 mask FC0000000 write-back
[ 0.000000] 3 base 100000000 mask FC0000000 write-back
[ 0.000000] 4 base 0B8000000 mask FF8000000 uncachable
[ 0.000000] 5 base 0B7E00000 mask FFFE00000 uncachable
[ 0.000000] 6 disabled
[ 0.000000] found SMP MP-table at [mem 0x000f74c0-0x000f74cf] mapped at [c00f74c0]
[ 0.000000] initial memory mapped: [mem 0x00000000-0x01bfffff]

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

Re: Boot bug

Post#12 by Ed_P » 16 Sep 2014, 15:27

odys03 wrote:I can see that the porteussave.dat exists in the root folder of the usbstick. It isn't deleted from the windows.
That's good to hear.
Here is how i changed the path to find the system the .dat file

APPEND initrd=initrd.xz changes=/mnt/sdb/porteussave.dat
You're missing the partition number.
changes=/mnt/sdb_/porteussave.dat
Most likey a "1", as in
changes=/mnt/sdb1/porteussave.dat
You could also try simply
changes=/porteussave.dat
Ed

odys03
White ninja
White ninja
Posts: 14
Joined: 15 Sep 2014, 05:12
Distribution: Porteus 32bit lxde
Location: Greece

Re: Boot bug

Post#13 by odys03 » 16 Sep 2014, 16:04

I tested separately both the config lines they don't work
changes=/porteussave.dat
changes=/mnt/sdb1/porteussave.dat

I deleted then porteussave.dat I created a fresh one
I use now the line
changes=/mnt/sdb/porteussave.dat

and the system works. but it is the same line before that the old porteussave.dat wasn't working...
most of all i don't understand why happens this.
I will use the usbstick with Porteus, as with the gparted tool I repair other laptops and pc.
But sometimes I want my boomkarks my own settings....

tome
Contributor
Contributor
Posts: 577
Joined: 26 Jun 2013, 14:03
Distribution: x64 Openbox
Location: Poland
Contact:

Re: Boot bug

Post#14 by tome » 16 Sep 2014, 18:28

I conclude that your OS is infected. You can try changes-ro cheatcode and then check md5 sum of save.dat before and after connecting pendrive to Windows.

odys03
White ninja
White ninja
Posts: 14
Joined: 15 Sep 2014, 05:12
Distribution: Porteus 32bit lxde
Location: Greece

Re: Boot bug

Post#15 by odys03 » 17 Sep 2014, 04:44

You mean that my Windows 7 are infected? And everytime i login in Windows,and I use the usbstick my windows infect the save.dat file or the structure of the root directory with entries?

Post Reply