You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I selected all directories but /data to be moved to sd card, rebooted and it worked perfectly for months...
Yesterday I chose to move also application data, rebooted the phone and it did not start in couple of minutes so I rebooted it again. This time it started but there was nothing shown on the screen. The only button that worked was the power button.
I rebooted to CWM recovery, backed up whole FS to the sd card and then opened it on my laptop. I found that the /data location was present in both data.ext4.tar and also in the sd-ext.ext4.tar files. Then I found s2e logs in which there was a statement saying that it had not found it's config:
This lead to the situation that the s2e config was not moved but deleted from phone's internal memory which made the system bootable but useless since all apps and data (the already moved part) was on sd card but s2e did not mount it (because there was no config...).
I found that other commands may also fail (like moving data from sd-card back to internal memory) when they are interrupted. My suggestion is to use && for chaining the commands and always use "cp && rm" pair instead of mv. This way if the command is interrupted then You still have the data...
Furthermore the config file should be always backed up in some location other than /data so that it's always available...
I managed to fix my problem by manually moving app data back to phone's internal memory and creating an xml file parsable by the s2e script with proper settings that reflected current situation. The phone started, some settings were lost but it was a great relief to have it working...
The text was updated successfully, but these errors were encountered:
I selected all directories but /data to be moved to sd card, rebooted and it worked perfectly for months...
Yesterday I chose to move also application data, rebooted the phone and it did not start in couple of minutes so I rebooted it again. This time it started but there was nothing shown on the screen. The only button that worked was the power button.
I rebooted to CWM recovery, backed up whole FS to the sd card and then opened it on my laptop. I found that the /data location was present in both data.ext4.tar and also in the sd-ext.ext4.tar files. Then I found s2e logs in which there was a statement saying that it had not found it's config:
Initialization...
Ext partition found: /dev/block/mmcblk0p2
Use built-in tune2fs
Use built-in e2fsck
Setup read_ahead value
/dev/block/mmcblk0p2 successfully mounted!
Config not found... Exit!
The problem is that when You select to move application data to sd card then there's not just an movement but also delete!
This lead to the situation that the s2e config was not moved but deleted from phone's internal memory which made the system bootable but useless since all apps and data (the already moved part) was on sd card but s2e did not mount it (because there was no config...).
I found that other commands may also fail (like moving data from sd-card back to internal memory) when they are interrupted. My suggestion is to use && for chaining the commands and always use "cp && rm" pair instead of mv. This way if the command is interrupted then You still have the data...
Furthermore the config file should be always backed up in some location other than /data so that it's always available...
I managed to fix my problem by manually moving app data back to phone's internal memory and creating an xml file parsable by the s2e script with proper settings that reflected current situation. The phone started, some settings were lost but it was a great relief to have it working...
The text was updated successfully, but these errors were encountered: