Systemback

How to restore a 'dead' system using another OS or a terminal cmd line

Asked by RonCam

I need to do a system repair. Putting Mint to 'Sleep' was working, and now I notice it's 'hanging' with a black screen that only responds to pushing the hard reset button.

I am at the Systemback 'System repair' window and see the directions that the user is to select his installations 'system partitions' (I assume, this means the partitions on one's system that correspond to /boot - /root - /home) from the left-hand drop-down menu, then identify them as to what each one is, and then press 'Mount'.

=>> I am having a problem with the drop-down menu, as _it only shows partitions up to /dev/sda8,_ and on my system /root and /home are _/dev/sda9 and /dev/sda10. _ <<==

So, I don't see how I could mount them, or proceed to repair them.

To explain why I'm have no choice but to have such high partition numbers, I have a triple-boot (Windows 2000 Pro, Windows 7 Pro, and Linux Mint Quiana). The triple boot is working fine, but I had to create quite a few partitions to do it.

What should I do? I'd very much like to see if Systemback can get my 'Sleep' function working again. Help, please!!
____________________________________
Linux Mint Quiana / KDE
Systemback v_1.1.1.200_10.23.2014_Qt5.2.1_i386

Question information

Language:
English Edit question
Status:
Solved
For:
Systemback Edit question
Assignee:
No assignee Edit question
Solved by:
Kendek
Solved:
Last query:
Last reply:
Revision history for this message
Kendek (nemh) said : 		#1

The mounted partitions aren't listed. Please click the "System copy" menu, and unmount the partitions. If done, click "System repair", and click refresh button (backward circular arrow). Mount system partitions, and perform a system repair.

Revision history for this message
RonCam (rac2) said : 		#2

Ah! It never occurred to me that you could unmount /root and /home, while the operating system was running. But if you say this can be done, and should be done, then I shall follow your directions.

I am now in the window, titled System Copy, Partition Settings and have selected (by moving the blue bar) first, to /dev/sda9 (/root) and then, to /dev/sda10 (/home).

You said I should now Unmount each of these, by clicking the Unmount button, when each partition was selected? _ But, in each case, Unmount is 'grayed-out' and therefore, does not respond. _ You didn't say to do this step now, but just in case -- I clicked 'Refresh' to see what would happen, but of course there was no change. The Unmount button remains inaccessible.

Please advise.

Revision history for this message
Kendek (nemh) said : 		#3

If the system is running, but the GUI does not start, just push Ctrl+Alt+F1 buttons, and login in. Execute 'sudo systemback' command (systemback-cli package), and perform a system restoration.
If system is not running at all (even the recovery mode either), just boot a compatible Live system (or other seperated system), mount the partitions and perform a system repair.

Revision history for this message
Kendek (nemh) said : 		#4

Sorry, execute 'sudo systemback-cli' command. This is a command line interface.

Revision history for this message
RonCam (rac2) said : 		#5

Hi Kendek, your support for Systemback is great and I appreciate your answering even basic questions about the operation of your utility.

I want to make sure you know exactly what's happening on my end, to make your task easier. For that reason, let me clarify on one small point, which may or may not be important:

I wrote:
"I am now in the window, titled System Copy, Partition Settings and have selected ... [the partitions to be mounted].

You wrote, in reply:
"If the system is running, _but the GUI does not start_ ... "

By "in the window" I meant to say, "in the 'window' of the Systemback GUI, the one with a title of System Copy displayed at the top ..."

Sorry if I gave the impression that the Systemback GUI had failed to start -- that was not the case. Please let me know if this changes your advice.

Revision history for this message
RonCam (rac2) said : 		#6

Sorry, pushed the wrong button.
IShould have been 'Still Need an Answer'.
You could just say 'makes no difference' if the 'Added Comment' makes no changes in what you already said I should do.
Thanks!

Revision history for this message
Best Kendek (nemh) said : 		#7

No, you misunderstood. If system GUI (X) isn't starting (after sleep and hard reset) because many possible reasons (get black screen), but if possible, change the tty (Ctrl+Alt+F1) and login in, use 'systemback-cli' command and system restoration method instead of system repair. System repair method is difficult, but system restoration is very easy.

Revision history for this message
RonCam (rac2) said : 		#8

Thanks again, for the clarification. I have no more questions. Your answer will be a good resource not only for me but for other Systemback users!

Revision history for this message
RonCam (rac2) said : 		#9

Thanks Kendek, that solved my question.