LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Linux Mint
User Name
Password
Linux Mint This forum is for the discussion of Linux Mint.

Notices


Reply
  Search this Thread
Old 07-13-2018, 06:12 PM   #1
Ulrog
LQ Newbie
 
Registered: Jul 2016
Location: North Carolina, USA
Distribution: Mint 19
Posts: 14

Rep: Reputation: Disabled
Can't Open Files


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.
 
Old 07-13-2018, 08:04 PM   #2
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,272
Blog Entries: 28

Rep: Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123
More information is required. For starts:

Is this an internal hard drive or a USB drive?

If it's a removable USB drive, the first thing to do is test it an another computer.

In any event, what is the output of the command fdisk -l issued as root?
 
Old 07-13-2018, 08:23 PM   #3
Ulrog
LQ Newbie
 
Registered: Jul 2016
Location: North Carolina, USA
Distribution: Mint 19
Posts: 14

Original Poster
Rep: Reputation: Disabled
It's a secondary internal HDD.

sudo fdisk -l

Quote:
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xc5523248

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 1953521663 1953519616 931.5G 83 Linux


Disk /dev/sdb: 223.6 GiB, 240057409536 bytes, 468862128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x2fb5adfc
 
Old 07-13-2018, 08:51 PM   #4
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,272
Blog Entries: 28

Rep: Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123
First, I suggest not doing anything until someone more knowledgeable of partitioning than I has a chance to chime in on this thread.

Is sdb the problem device?

The fdisk command is not showing any partitions on sdb. Note that sda shows a partition, sda1.

You might want to take a look at it with something like gparted. Be very careful, though, not to change anything.

Another course of action might be to boot to a live CD of something and seeing whether you can inspect the device.
 
Old 07-13-2018, 09:37 PM   #5
Ulrog
LQ Newbie
 
Registered: Jul 2016
Location: North Carolina, USA
Distribution: Mint 19
Posts: 14

Original Poster
Rep: Reputation: Disabled
The sda is the drive I was trying to get access to. I'm getting a unknown file type message telling me it has no known programs associated with it.

I can now click on Computer, Home & Trash successfully after uninstalling Rhythmbox program.



After a restart following the uninstall of Rhythmbox I am able to access the 1TB secondary HDD but unsure I will be able to next time I boot computer.

sudo fdisk -l
Quote:
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xc5523248

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 1953521663 1953519616 931.5G 83 Linux


Disk /dev/sdb: 223.6 GiB, 240057409536 bytes, 468862128 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x2fb5adfc

Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 468860927 468858880 223.6G 83 Linux

Last edited by Ulrog; 07-13-2018 at 09:58 PM.
 
Old 07-13-2018, 10:25 PM   #6
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,272
Blog Entries: 28

Rep: Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123
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.
 
Old 07-13-2018, 10:40 PM   #7
Ulrog
LQ Newbie
 
Registered: Jul 2016
Location: North Carolina, USA
Distribution: Mint 19
Posts: 14

Original Poster
Rep: Reputation: Disabled
No problem. I have some 12 hour shifts to work Sat & Sun so I'll pick this back up Monday if you want to help.
 
Old 07-16-2018, 01:17 PM   #8
Ulrog
LQ Newbie
 
Registered: Jul 2016
Location: North Carolina, USA
Distribution: Mint 19
Posts: 14

Original Poster
Rep: Reputation: Disabled
Quote:
# /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

Quote:
cat /etc/mtab
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=8157084k,nr_inodes=2039271,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=1637624k,mode=755 0 0
/dev/sdb1 / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/unified cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/rdma cgroup rw,nosuid,nodev,noexec,relatime,rdma 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=24,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16096 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime,pagesize=2M 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=1637620k,mode=700,uid=1000,gid=1000 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 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.
 
Old 07-16-2018, 08:45 PM   #9
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,272
Blog Entries: 28

Rep: Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123Reputation: 6123
Thanks for the response.

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.
 
Old 07-17-2018, 12:05 PM   #10
Ulrog
LQ Newbie
 
Registered: Jul 2016
Location: North Carolina, USA
Distribution: Mint 19
Posts: 14

Original Poster
Rep: Reputation: Disabled
sudo blkid

Quote:
/dev/sda1: UUID="6a240be3-6a5c-4125-8874-dc456a5cb513" TYPE="ext4" PARTUUID="c5523248-01"
/dev/sdb1: UUID="41a8c23e-ea4b-4fd6-bea2-bae065c18c06" TYPE="ext4" PARTUUID="2fb5adfc-01"
Is this what you wanted?
 
Old 07-17-2018, 04:44 PM   #11
soveda
Member
 
Registered: Feb 2018
Distribution: Mint 19; Ubuntu Studio; Kali
Posts: 37

Rep: Reputation: Disabled
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.
 
Old 07-17-2018, 04:54 PM   #12
soveda
Member
 
Registered: Feb 2018
Distribution: Mint 19; Ubuntu Studio; Kali
Posts: 37

Rep: Reputation: Disabled
Quote:
Originally Posted by Ulrog View Post
sudo blkid



Is this what you wanted?
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)
 
Old 07-17-2018, 09:31 PM   #13
Ulrog
LQ Newbie
 
Registered: Jul 2016
Location: North Carolina, USA
Distribution: Mint 19
Posts: 14

Original Poster
Rep: Reputation: Disabled
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

Last edited by Ulrog; 07-17-2018 at 09:40 PM.
 
Old 07-18-2018, 03:39 AM   #14
soveda
Member
 
Registered: Feb 2018
Distribution: Mint 19; Ubuntu Studio; Kali
Posts: 37

Rep: Reputation: Disabled
duplicate post

Last edited by soveda; 07-18-2018 at 03:43 AM.
 
Old 07-18-2018, 03:39 AM   #15
soveda
Member
 
Registered: Feb 2018
Distribution: Mint 19; Ubuntu Studio; Kali
Posts: 37

Rep: Reputation: Disabled
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
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] How do I get xdg-open (and Chromium) to open FLV files in mpv? dugan Slackware 2 08-15-2015 04:51 PM
mmap cache can't open foo.php - Too many open files guarriman Linux - Software 3 12-16-2013 01:03 PM
Cant open .dat files (video) by double clicking though I can open it by openwith.. ravi_npatty Linux - Newbie 17 07-31-2007 08:19 PM
how to open files from a network server from open office or any apps reycapoy Linux - Software 4 01-26-2006 07:00 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Linux Mint

All times are GMT -5. The time now is 03:08 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration