[SOLVED] After Cinnamon lock-up can’t access one particular program

hydrurga · 05-16-2018, 08:52 AM

Thanks. Click on the three dots along from "Folder" and select a folder on your external hard drive (create a new one for your system images if necessary). This is where the system image will be saved. In the "Backup filename" box, give the file a reasonable name (I use e.g. Mint-2018-05-16). Then click on Finish.

Just a point of information. Normally you shouldn't make a partition image while that partition is actually active (normally meaning that its filesystem is mounted). It is for that reason that I, who don't have a dual boot setup, have created a boot media with Macrium Reflect on it - I boot up my computer with that media when I want to make system images of my Linux partitions. In your case, however, because you have booted up into Windows and you want to make an image of your inactive Linux partition, it should be fine.

paxolin · 05-16-2018, 09:04 AM

Quote:

Originally Posted by hydrurga

Thanks. Click on the three dots along from "Folder" and select a folder on your external hard drive (create a new one for your system images if necessary). This is where the system image will be saved. In the "Backup filename" box, give the file a reasonable name (I use e.g. Mint-2018-05-16). Then click on Finish.

Just a point of information. Normally you shouldn't make a partition image while that partition is actually active (normally meaning that its filesystem is mounted). It is for that reason that I, who don't have a dual boot setup, have created a boot media with Macrium Reflect on it - I boot up my computer with that media when I want to make system images of my Linux partitions. In your case, however, because you have booted up into Windows and you want to make an image of your inactive Linux partition, it should be fine.

Ahh, when I came out of Mint, I opted for "Freeze/Suspend", or whatever it's called, the second from the left option when you shut the system down.
Do I need to go back into Mint first and close it completely before I do the backup, or doesn't it matter?

edit: I just noticed that you said click on Finish, although I see "Next" is highlighted?

hydrurga · 05-16-2018, 09:15 AM

Quote:

Originally Posted by paxolin

Ahh, when I came out of Mint, I opted for "Freeze/Suspend", or whatever it's called, the second from the left option when you shut the system down.
Do I need to go back into Mint first and close it completely before I do the backup, or doesn't it matter?

edit: I just noticed that you said click on Finish, although I see "Next" is highlighted?

I'm not quite sure, to be honest, but perhaps you should indeed properly shut down Mint before making a system image. It will keep things cleaner. You can start Macrium Reflect again when you boot back up into Windows.

"Next" just summarises what will happen before you carry on with the procedure, but from what you've done so far, it looks good to go, and I didn't want to complicate things by having you look through the summary. However, you can indeed click "Next", check that it will do what you expect it to, and then click the relevant button, perhaps "Finish", on that window, to continue with the actual procedure itself.

paxolin · 05-16-2018, 09:50 AM

I went back to Mint and closed it down completely.
Now I'm in Windows again, I clicked "Finish" and have been asked the following. Do I leave the checked boxes as they are? Do I need to change backup definition?

hydrurga · 05-16-2018, 09:57 AM

Quote:

Originally Posted by paxolin

I went back to Mint and closed it down completely.
Now I'm in Windows again, I clicked "Finish" and have been asked the following. Do I leave the checked boxes as they are? Do I need to change backup definition?

Personally I wouldn't check the second box (I've never seen that window before - it may be Windows-specific). The process of making a system image is quite simple anyway and I think it's good to go through the steps each time to keep the mind thinking and aware. Also, using an xml file makes things more complicated and I prefer simplicity.

paxolin · 05-16-2018, 10:06 AM

Quote:

Originally Posted by hydrurga

Personally I wouldn't check the second box (I've never seen that window before - it may be Windows-specific). The process of making a system image is quite simple anyway and I think it's good to go through the steps each time to keep the mind thinking and aware. Also, using an xml file makes things more complicated and I prefer simplicity.

OK, I unticked the second box. It's now running. I thought it might be a couple of minutes, it says an hour! I hope we don't have a power failure in the meantime, we get one or two a month here in Thailand.
I'll wait and see, hope it completes OK, will confirm the result. Thanks for your help so far hydrurga.

hydrurga · 05-16-2018, 10:18 AM

Quote:

Originally Posted by paxolin

OK, I unticked the second box. It's now running. I thought it might be a couple of minutes, it says an hour! I hope we don't have a power failure in the meantime, we get one or two a month here in Thailand.
I'll wait and see, hope it completes OK, will confirm the result. Thanks for your help so far hydrurga.

That's longer than I would expect it to take. Perhaps a slow processor or your external hard drive is only USB 2.0-capable or plugged in to a USB 2.0 socket? In the future, it might also well be faster if you boot up off a boot media containing Macrium Reflect as you won't have all the other Windows processes working away in the background as they do in your Windows system.

If you do get power failures then you should really think about buying yourself an uninterruptible power supply for your computer. They don't cost that much and could save you a lot of bother.

paxolin · 05-16-2018, 10:26 AM

Quote:

Originally Posted by hydrurga

That's longer than I would expect it to take. Perhaps a slow processor or your external hard drive is only USB 2.0-capable or plugged in to a USB 2.0 socket? In the future, it might also well be faster if you boot up off a boot media containing Macrium Reflect as you won't have all the other Windows processes working away in the background as they do in your Windows system.

If you do get power failures then you should really think about buying yourself an uninterruptible power supply for your computer. They don't cost that much and could save you a lot of bother.

Ha ha! I have a UPS - it's away being repaired under (Thai) warranty. It originally lasted for twenty minutes, then it went down to one minute!
The backup is about 30% done so far. I'm off to bed, I will report back tomorrow.

paxolin · 05-16-2018, 07:16 PM

Had a dreaded power failure during the night, so I don't know what happened with the image.

I thought it would be better to start again, so I deleted the file on my Seagate backup. I also had a look in the Log tab, saw there was an entry in there and deleted that too.
The reason I did that was because when I started Macrium Reflect, the backup drive is now showing in red (see the attached image)
After deleting it, I restarted Macrium Reflect, but it's still red. I'm guessing the red is perhaps because it's showing as nearly full?
The only other reason it's now showing as nearly full might be because the Seagate backup software has always been set in Windows to constantly backup. As I hardly ever go into Windows, it hasn't been backing up for months.

Does it being red mean there's now not enough space to now save the image, would you know? In a previous image I posted it said "total selected 28.13GB"
Looking at the figures below the red line, it appears to me I have 1.82TB - 1.7TB = 1.22GB?

If delete all the Windows backups it has done incrementally over time, then backup it up again, I "think" it will use less space, but the backup will take about 6 - 8 hours.
Awaiting your comments.
Btw, the Seagate drive is USB3 and it is plugged into the one USB3 port I have (the rest are USB2).

hydrurga · 05-16-2018, 07:32 PM

1.82 TB - 1.7 TB = 0.12 TB = 120 GB

That will be enough for the system image, but in the long run you should think about making space on that external drive. Remember, when you do that, that you should always have at least 2 copies of all your data (including the original data), preferably on different drives in different locations.

So, go ahead and make that system image with Macrium Reflect.

Now it's my turn to go to my kip. I won't be around until later tomorrow.

paxolin · 05-16-2018, 09:08 PM

At last!
You can see the second time the process completed a lot quicker. It was a 19GB file.
Perhaps it was the Seagate data backup that was ongoing at the same time.

What do I need to do next?

paxolin · 05-16-2018, 09:54 PM

hydrurga · 05-16-2018, 11:50 PM

Great. Now that you've made that system image, you can now boot back up into Mint and bring it up to date.

First:

Code:

apt update

apt upgrade

No need to paste the output if there are no warnings/errors.

paxolin · 05-17-2018, 12:19 AM

Quote:

Originally Posted by hydrurga

Great. Now that you've made that system image, you can now boot back up into Mint and bring it up to date.

First:

Code:

apt update

apt upgrade

No need to paste the output if there are no warnings/errors.

Most of that went pretty smoothly, apart from a few warnings:
"No support for locale: en_GB.utf8" As well as the block of code below, that same warning appeared maybe half-a-dozen times separately, at a few other places during the upgrade.

Code:

Setting up linux-firmware (1.157.18) ...
update-initramfs: Generating /boot/initrd.img-4.4.0-124-generic
Warning: No support for locale: en_GB.utf8
update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic
Warning: No support for locale: en_GB.utf8
update-initramfs: Generating /boot/initrd.img-4.4.0-121-generic
Warning: No support for locale: en_GB.utf8
update-initramfs: Generating /boot/initrd.img-4.4.0-119-generic
Warning: No support for locale: en_GB.utf8
update-initramfs: Generating /boot/initrd.img-4.4.0-116-generic
Warning: No support for locale: en_GB.utf8
update-initramfs: Generating /boot/initrd.img-4.4.0-112-generic
Warning: No support for locale: en_GB.utf8
update-initramfs: Generating /boot/initrd.img-4.4.0-109-generic
Warning: No support for locale: en_GB.utf8
update-initramfs: Generating /boot/initrd.img-4.4.0-104-generic
Warning: No support for locale: en_GB.utf8
update-initramfs: Generating /boot/initrd.img-4.4.0-103-generic
Warning: No support for locale: en_GB.utf8
update-initramfs: Generating /boot/initrd.img-4.4.0-101-generic
Warning: No support for locale: en_GB.utf8
update-initramfs: Generating /boot/initrd.img-4.4.0-57-generic
Warning: No support for locale: en_GB.utf8
update-initramfs: Generating /boot/initrd.img-4.4.0-21-generic
Warning: No support for locale: en_GB.utf8

Why do I have/need "en_GB.utf8", is it because I want to use a UK English keyboard, but my locale(?) is Thailand?

hydrurga · 05-17-2018, 01:11 AM

Don't worry about the en_GB.utf8 warnings - I get those as well and I'm in the UK.

However, you do have more kernels than you need (I usually only keep three of those at at time, the active one and two previous ones).

Please open the Update Manager, choose View->Linux kernels, and tell me which kernel is marked as "Active".