Mint 18.3 Cinnamon Dual Boot Issues with Win7



wizardfromoz

Super Moderator
Staff member
Gold Supporter
Credits
4,725
Reboot the computer, then open GParted and take me a snap of the T5 from there.

Thanks :)

Chris

BTW we can do this tomorrow if your are tired. I have to take Elaine for a B12 shot at 9:40am our Thursday morning (tomorrow) but other than that, I am mostly clear.
 

whazzupdoc

Active Member
Credits
56
Wow...now I can't shut down in a normal way w/o this message.

And you can see gparted also attached.
Doc




Screenshot from 2019-02-13 09-09-45.png



Screenshot from 2019-02-13 09-14-12.png
 
Last edited by a moderator:

whazzupdoc

Active Member
Credits
56
O.K., the shutdown/reboot unclogged some things and the left side panel now shows MyTimeShift...inside is the regular timeshift folder. I also see another lost+found folder that doesn't permit access. I don't understand why this folder is here and what it does.
Doc


Screenshot from 2019-02-13 09-46-12.png
 
Last edited by a moderator:

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Credits
4,725
OK looks like you are as good as gold now, I modified those last couple of threads to make the pix easily viewable :)

Check with Timeshift that you had reset the Daily option in Settings - Schedule.

Then leave it until the weekend for it to take a couple of snaps and we'll check that the procedure is working as it should, we can confirm that through File Manager Nemo or Timeshift itself.

Might do both, for better understanding.

Lost + Found

is a common occurrence for drives both removable and internal, whether they be external drives such as the T5 or even USB sticks.

This thread elsewhere

https://unix.stackexchange.com/questions/18154/what-is-the-purpose-of-the-lostfound-folder-in-linux-and-unix

... gives as good an answer as any, whereby it says, in part

If you run fsck, the filesystem check and repair command, it might find data fragments that are not referenced anywhere in the filesystem. In particular, fsck might find data that looks like a complete file but doesn't have a name on the system — an inode with no corresponding file name. This data is still using up space, but it isn't accessible by any normal means.

If you tell fsck to repair the filesystem, it will turn these almost-deleted files back into files. The thing is, the file had a name and location once, but that information is no longer available. So fsck deposits the file in a specific directory, called lost+found (after lost and found property).

Files that appear in lost+found are typically files that were already unlinked (i.e. their name had been erased) but still opened by some process (so the data wasn't erased yet) when the system halted suddenly (kernel panic or power failure). If that's all that happened, these files were slated for deletion anyway, you don't need to care about them.

Files can also appear in lost+found because the filesystem was in an inconsistent state due to a software or hardware bug. If that's the case, it's a way for you to find files that were lost but that the system repair managed to salvage. The files may or may not contain useful data, and even if they do they may be incomplete or out of date; it all depends how bad the filesystem damage was.

On many filesystems, the lost+found directory is a bit special because it preallocates a bit of space for fsck to deposit files there. (The space isn't for the file data, which fsck leaves in place; it's for the directory entries which fsck has to make up.) If you accidentally delete lost+found, don't re-create it with mkdir, use mklost+found if available.
For the benefit of the Windows Users who get under the hood with MS-DOS

Code:
fsck
... is very similar to

chkdsk /F

Now, Dick will not have actively run the fsck command himself, but it is a part of the GParted processes that run, and somehow with the procedures he has followed, and with that strange but thankfully brief change of ownership of his Timeshift partition from /media/dick to /media/root ... something got corrupted, hence the creation of Lost+Found.

No further action at this point, but we will review.

Cheers all

Wizard
 

Condobloke

Well-Known Member
Credits
3,670
""No further action at this point, but we will review.""....later

leave it alone.
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Credits
4,725
What HE said, :)

(his bark is worse than his bite)

Wiz
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Credits
4,725
Dick, you had posted

Can I delete the lost+found? How best to get to it ...to do so?
Brian's (@Condobloke 's) was to quote what I had said

hence the creation of Lost+Found.

No further action at this point, but we will review.
And to add to that to leave it alone, that is, it is better left well alone.

Unless ... it is found to cause problems later, and then we will act on it.

Your Timeshift partition is fine for the moment, snapshots should go according to schedule if you have checked Daily again (have you?), and we can take a look in a day or two to see that all is good in the land of Linux.

Cheers

Chris
 

whazzupdoc

Active Member
Credits
56
Screenshot from 2019-02-15 09-13-26.png
I'm sorry Chris...I misunderstood Brian. My apologies, Brian! Somehow all the other parts to the post confused me.

Now TimeShift...I checked and learned the last backup was 2/12 and I think even that one was OD (on demand)...so something isn't functioning. The 'Daily' option is checked but 'Boot' isn't. Take a look.
Doc
 
Last edited by a moderator:

whazzupdoc

Active Member
Credits
56
I may be all wet, Wiz. I just tried again to check-in on TimeShift and I'm told a backup is in progress...get back to you.
 

whazzupdoc

Active Member
Credits
56
O.K., after 2 attempts to unfreeze TimeShift by shutting down, it is back up. The last Daily was 2/11 and one On-Demand on 2/12. It appears the Daily is not kicking in. I'll check it again with the Toshiba and report back.
Doc
 

whazzupdoc

Active Member
Credits
56
The OD worked fine...I don't know how to get TimeShift to trigger those Daily backups though. Also as you can see I'm still being told a scheduled snapshot is in progress.
Doc


Screenshot from 2019-02-15 10-02-32.png
Screenshot from 2019-02-15 10-27-09.png



Screenshot from 2019-02-15 10-33-31.png
 
Last edited by a moderator:

whazzupdoc

Active Member
Credits
56
Hi Chris. Here's an update for Sat afternoon.

TimeShift Log is recording data and the On Demand works but the Daily is not working. ???

Doc



Screenshot from 2019-02-16 16-05-17.png




Screenshot from 2019-02-16 16-05-42.png
 
Last edited by a moderator:

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Credits
4,725
Not necessarily a drama.

1. Open Timeshift
2. Go to Settings - Users and take a screenshot
3. Go to Settings - Filters and take a screenshot
4. Post the screenshots here

If Timeshift is set to a Schedule, and you are a person who switches off their computer overnight, then when you start a new computer session (boot up the computer), it will wait perhaps 10 minutes and then launch and take its Boot, Daily, Weekly, whatever, snapshot.

If you then try to launch Timeshift manually while that process is going on, that would account for the error you receive

"Scheduled Snapshot in Progress ... another instance ...".

The initial steps Timeshift takes before creating a snapshot involve it comparing the current state of your system with its previously taken log files, to see if anything has changed since its last snapshot.

If there have been no changes (no files created or modified by you or the system), then it may not take a snapshot. That does not mean it is not working.

Wizard
 

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Credits
4,725
Did you see them?
Yep.

Here's what you've asked for.
Ta (thanks), that is as it should be.

What is the significance of having 'Boot' selected, or not? Mine is not.
If you were writing the next best-selling novel, or doing any number of other activities where the same document, or spreadsheet was constantly being replaced by a newer, saved, version, then you might want Boot option set.

If you were constantly putting on (installing) new software each day to try it out, and that software required you to reboot the computer to take effect, then you might want to have Boot option set.

But if you are not, then you don't need it checked.

Cheers

Chris
 

whazzupdoc

Active Member
Credits
56
Terrific! Where do we go from here, Chris?...with regard to the best use of this SSD space?

I've a thought. What would be wrong with swapping the HDD sdb1 (Toshiba MQ01ABFO ATA 320 GB) which is currently the drive of the Linux OS with sdc1 (Samsung SSD 860 ATA)?

In doing so I gain a faster hard drive and likely as much storage space as this old man will ever need. And put into 2nd place the HDD which I can then replace with the new SSD 1TB T5 when it comes. That new SSD would in effect act like the current Portable SSD T5 Samsung sda1 we've been reworking.

I still am wondering what my options are that would make sense with the current HDD once this all is done?

Doc
 


Members online


Latest posts

Top