It all depends on one information: Which file system the hard drive uses.
Depending on the file system type, our approach will be different.
Press Ctrl + Alt + T to open a terminal emulator.
Type the commands presented on the paragraph bellow (for every new line,
press Enter), except the comments between the # characters (be careful, if
you find a #, be sure to not type anything until you find its pair).
# This starts the guide. #
# Run as system administrator. This command shows which file systems are
mounted, along with its type and some other information. The file system in
question should be shown here, otherwise, stop following this guide and tell
us about it. #
sudo blkid
# Example of the output from blkid: #
# /dev/sda2: LABEL="Toutatis" UUID="5a2afc93-af3f-4453-9298-83b3e96a3805"
TYPE="ext4"
#
# /dev/sda5: UUID="f2d5cc14-d1d6-41b8-864d-da060f84e16f" TYPE="swap"
#
# /dev/sdb1: LABEL="BACKUP" UUID="E478-8E5E" TYPE="vfat" #
# For most users, I suggest to look for the label (LABEL attribute) of the
problematic file system, which is, in most cases, a friendly name set by the
user. If you can't find the label of the problematic file system, stop
following this guide and tell us about it. #
# After finding the problematic file system, see if its type (TYPE attribute)
is ext[Any number] (where [Any number] can be any number), vfat, or any
other. If it's not ext[Any number], stop following this guide and tell us
about it. #
# Assuming that the file system is ext[Any number], we can continue. #
# Please remember the LABEL attribute of the problematic file system, we'll
need it. #
# This command transports us to the root of the problematic file system.
Where [LABEL attribute] is the label of the problematic file system. #
cd /media/[LABEL attribute]
# If the command outputs some warning or error messages, stop following this
guide and tell us about it. #
# This part can be very subjective, it all depends on where the problematic
folder is. But basically, for every folder entered you can add a / (forward
slash). #
# This command is very subjective, as stated above. It transports us to the
parent folder of the problematic one (that is, one folder before the
problematic one). In most cases, users of live operating systems won't be
able to access the problematic folder because their user name is different,
so this is why we must go to the parent folder first. Let's assume that the
problematic folder is the personal folder jones, which is normally inside the
home folder of the problematic file system. #
# Note: This is wrong in this case: #
# cd /home/ #
# This is right in this case: #
cd home
# Live operating systems have users, just like normal operating systems. To
know which user you are logged in as, use the whoami command. #
whoami
# In the case of GNU+Linux Trisquel, the user is trisquel. #
# Run as system administrator. This command changes the owner of the jones
folder, from jones (the user) to trisquel (the user). #
sudo chown trisquel jones
# If the command outputs some warning or error messages, tell us about it. #
# Now you should have access to the problematic folder. #
# This ends the guide. #
Best regards, ADFENO.
Have a nice day.
