Hi suicidaleggroll,

Once i extract the liveiso file to the usb ,Can i access my system from the liveusb?

Possible if you actually copy it off the disk elsewhere, isn't it? And you continue to make absolutely no sense....you say it's 'hard' to back up 500 GB....yet seem to have NO problems with the snapshot of the same system?? Wouldn't they be the SAME SIZE???
...which means you'll lose everything in /home, right???
...which takes us back to "use the command-line, back up your data, and do a fresh install". What part of these things aren't you understanding???
You don't extract an ISO; you follow the very well documented steps to create a bootable USB stick. Which is STILL POINTLESS, since you can boot your system NOW...you don't need a LiveUSB stick. Boot your system, back up your data, and start fresh. A liveUSB stick WILL STILL NOT GET YOU ANYTHING.

Yes, but you can already access your system by simply booting it, so what is it you're trying to accomplish?

The OP is wanting to (somehow) boot the system from a live USB stick, so they can get a GUI, to run timeshift. Because (apparently), backing up their data is too hard, because it's 500 GB (unlikely)...but (somehow) the timeshift image of the same system is VERY easy to manage. (??)

He's stuck on this because he tried to "upgrade" python2, apparently. And now he's uber stuck since he apparently has never tested his backup medium or processes.

One mistake is forgivable, the other is not.

thank you for the replies friends,

I am really worrying about the mistake that i have done.At the time i didnt know the upgradation will make harm to my system.
Even at this time also I dont know why this was happened by the upgrade of my system .

If there is any awareness to do something ,that'll be helpfull.


Here the problems are raising only .There is no solution for that problem...I hate this type problems.

thank you guys..

I am going to take a backup from my system using rsync.

If u know the another best way please tell me.

onemore second thank you friends

Python is still in a state of active development, and backwards compatibility is, in my experience, terrible. When a new version comes out, the developers might make a change to the calling sequence of some routine, breaking the old syntax in the process. So now any programs that call that routine need to be modified to conform to the new syntax or it will throw an error and crash.

This means that in order to update python, you also need to update every other program that depends on python. The only way to do this properly is to use the standard package manager, yum. Going outside of yum and updating python manually will very likely kill every program that uses python, which on CentOS/RHEL is a LOT.

You MIGHT be able to get the system back to a usable state by manually downloading the EXACT version of python that SHOULD be on the system and installing it, but this is still no guarantee everything will work correctly again.

You keep asking for a solution, and we keep telling you what it is. Wipe the system, reinstall the OS, restore from your backup. THIS IS THE SOLUTION. The sooner you come to terms with that, the sooner your system will be back up and running. It should only take a couple of hours, FAR LESS time than you've already spent here arguing about whether or not it's necessary.

I'd backup (using rsync is wise) all data from the user(s)' /home directory and optionally everything under /etc.
logs are important for Security reasons, so I'd advise not collecting those at this time, since we know how this happened.

rsync should be done as root or equivalent permissions.
If /home is a separate partition (it should now be apparent why it should be) then all you really need is /etc at this time.
If /home is NOT a separate partition, then I encourage you to consider implementing one.
I have a separate /home partition and I still back that up often.
My separate /home... I can re-install in 15 min and be back at the the grind in 16.

See also Simple, Secure Backups for Linux with rsync

Good Luck.