It depends where the error is.
The system 'lives' in a compressed file system (squashfilesystem). It is unpacked and used 'on the fly'...or as it is needed. It's like having a life raft packed in a valise; but you can still access the 'medical kit' when you need it. When you no longer need it, it's packed in the valise with everything in place as if it had never been touched. It is ingenious.
It is 'read only' and should always be the same. Should be the same... Data change (or corruption) here is not a good thing.
Since it always remains the same, or should, there is no persistence...information cannot be added or updated (changed) that will carry over from one boot to the next. There are persistence files to allow this to happen.
If the data in these files is corrupted, or you just want to start over with a 'fresh' copy, these files can be rebuilt.
Within one second (and a second is a long time if you know it's coming)...within one second of the Blue splash screen appearing hit <esc> repeatedly until the screen turns black and stay black. In the upper left corner will appear
boot:
type in fix with <enter>. The compressed filesystem will rebuild the persistence files.
Data located in Desktop, Charts, Documents, Downloads, Music, Picture, and Video will remain, but the supporting configuration will be reset to the original.
This is his best shot at recovering from the error...if the error is not in the squashedfilessystem.
It's for this reason they added a checksum to the boot menu in 0.5. You just select the "just tell me if system on the stick is whole or screwed up in some fashion" ....the first step to solve most any problem. Well, so I'm told...if my information is correct.
|