Linux MintThis forum is for the discussion of Linux Mint.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I moved from mint 17.3 to 19. I have a secondary internal HDD with files I wanted to use but after attempting to mount I can no longer double click on Computer or Home to access. I can't access files with the UI or the 1TB HDD.
I must admit that I am baffled and it is late here and, as I said to someone the other day, I am not beating on all syllables! I'll have to ponder on this more tomorrow.
In the meantime, what is the output of cat /etc/fstab and cat /etc/mtab? Be sure to surround the output of any terminal commands with code tags, which become available when you click the "Go Advanced" button beneath the "compose post" windows.
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb1 during installation
UUID=41a8c23e-ea4b-4fd6-bea2-bae065c18c06 / ext4 errors=remount-ro 0 1
/swapfile none swap sw 0 0
I am able to access it right now. When clicking on "Properties" & "Permissions" it says "The permissions of "6a240be3-6a5c-4125-8874-dc456a5cb513" could not be determined.
I don't have any answers yet, but I have another question: What is the output of the command blkid issued as root? Since UUID numbers are used in fstab, that will help me understand the fstab contents, since it will return the UUID numbers of the various partitions.
Your /etc/fstab shows the same pattern as mine (on Mint 19)
Code:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda5 during installation
UUID=77d1d696-a91e-4b34-b39b-05711eaaddf6 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda1 during installation
UUID=c3e899ae-c7fd-4b22-97ec-1d33dccb4f5d none swap sw 0 0
I wonder if the symbolic links from your home folder have been broken by updating Mint.
it's clear from this shat sdb1 is the partition that is in fstab.
The sda1 is not set to automatically mount. Are you mounting through Disks or some other way?
When you moved to Mint 19 did you upgrade or did you do a full new install?
If you are getting "permissions could not me determined" this might be due to a different set of user permissions compared to those of the user that created the partition. (not sure i'm expressing that too well)
I did a fresh install of Mint 19 on the smaller SSD (sdb1).
It's hit & miss. Sometimes I can click on the drive & access it. Sometimes I get this message.
Unknown file type
The file "6a240be3-6a5c-4125-8874-dc456a5cb513" has no known programs associated with it. If you trust the source of this file, and have sufficient permissions, you can mark it executable and launch it. Or, you can use the Open With dialog to pick a program to associate it with.
If I select Mark executable & run it says ...
The permissions could not be changed.
Sorry, could not change the permissions of "6a24 (ect.)": Error setting permissions: Permissions denied
Don't mark as executable, it isn't an executable file.
For some reason your install thinks that the 1Gb disk is a "file" rather than a disk/directory type "file".
Does the disk mount on your system?
Last edited by soveda; 07-18-2018 at 03:44 AM.
Reason: precision
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.