lsblk -f
shows that the data partition (sda2) is mounted, so there should be no problem. Everything is in order.In your file manager go to FILE SYSTEM > mnt/DATA and use the folders you created there.
lsblk -f
shows that the data partition (sda2) is mounted, so there should be no problem. Everything is in order.Okay. I can no longer open specific ssd and hdd directly but I can access them from the filesystem. It looks like a third hdd on my computer.austin.texas wrote:Your fstab looks good, and the result you got for the command,lsblk -f
shows that the data partition (sda2) is mounted, so there should be no problem. Everything is in order.
In your file manager go to FILE SYSTEM > mnt/DATA and use the folders you created there.
Which is why I don't use UUID's - they're pointless, confusing and hard to use.ALbin75 wrote:If it is going to be arround 30 random characters, that is unreadable for the human mind it would be good to list this UUID identity.
Code: Select all
LABEL=MINT / ext4 noatime,errors=remount-ro 0 1
LABEL=DATA /mnt/DATA ext4 defaults,noatime 0 0
LABEL=SWAP none swap sw 0 0
#
# don't automount other linux OS:
LABEL=UBUN /mnt/UBUN ext4 defaults,noatime,noauto 0 0
In this case UUID's go with partitions, but yes it's **supposed to be** a "Universally unique" number identifying a partition...but that's not even true because if you copy an entire partition you also copy its UUID (and the LABEL...).Even if I still dont know what UUID is. "Universally unique identifier" perhaps it means the identity of my hdd?
Code: Select all
ls -la /mnt/DATA
ok.austin.texas wrote:Please post the result of the command:(That is ls -la /mnt/DATA. Use small L not 1. )Code: Select all
ls -la /mnt/DATA
Okay that sounds good. I can change the name to lets say. HDD?Flemur wrote:Which is why I don't use UUID's - they're pointless, confusing and hard to use.ALbin75 wrote:If it is going to be arround 30 random characters, that is unreadable for the human mind it would be good to list this UUID identity.
Next time you mess around with a new partition, make life easier for yourself and give it a LABEL with gparted when you create it (or you can define the LABEL on an existing but unmounted partition), then your entries in the /etc/fstab file would be like these:Much nicer than the UUID nonsense, yes?Code: Select all
LABEL=MINT / ext4 noatime,errors=remount-ro 0 1 LABEL=DATA /mnt/DATA ext4 defaults,noatime 0 0 LABEL=SWAP none swap sw 0 0 # # don't automount other linux OS: LABEL=UBUN /mnt/UBUN ext4 defaults,noatime,noauto 0 0
In this case UUID's go with partitions, but yes it's **supposed to be** a "Universally unique" number identifying a partition...but that's not even true because if you copy an entire partition you also copy its UUID (and the LABEL...).Even if I still dont know what UUID is. "Universally unique identifier" perhaps it means the identity of my hdd?
I can't see any reason for a human to use UUIDs rather then LABELs.
As far as I know you can call it anything (dunno about how many characters, limit), but SSD and HDD refer to the disk drives, not partitions...you might want to label your Mint partition "MINT", data partitions "DATA", etc.ALbin75 wrote:Okay that sounds good. I can change the name to lets say. HDD?
Easy for me to remember since the other one is an SSD.
Probably safest to use gparted, and if you have everything working for the (non-system) HDD you can do that from a running Linux by unmounting the HDD partition(s), change/define the label, remount. For the OS, you need to do it from a LiveDVD/USB boot because the "/" partition can't be unmounted in a running system.If I do that I could use the lines above in the terminal to fix it?
But I'd better wait until I do any more changes.
Code: Select all
$ sudo blkid
/dev/sda1: LABEL="MINT" UUID="d7a3e26f-..." TYPE="ext4" PARTUUID="07c537f5-01"
/dev/sda2: LABEL="UBUN" UUID="8c59a1c3-..." TYPE="ext4" PARTUUID="07c537f5-02"
/dev/sda7: LABEL="DATA" UUID="1633cae6-..." TYPE="ext4" PARTUUID="07c537f5-07"
...
Code: Select all
sudo chown -R $USER /mnt/DATA
Code: Select all
ls -la /mnt/DATA
Okay Like this then.austin.texas wrote:Your result of the command ls -la /mnt/DATA shows /mnt/DATA to be owned by root.
Change the ownership to the current user, with this command:Then again post the result ofCode: Select all
sudo chown -R $USER /mnt/DATA
Code: Select all
ls -la /mnt/DATA
Code: Select all
mkdir /mnt/DATA/Music_mp3s
Thansk. It works. I now own my hdd.austin.texas wrote:OK. Now you can use it.
Make a directory, or several directories to use.
EXAMPLE: to make a directory named Music_mp3s:Code: Select all
mkdir /mnt/DATA/Music_mp3s
It is the same thing.ALbin75 wrote:I don't know if it is different from just right clicking inside the folder and create new folder.
I mentioned previously that you can make a Bookmark in the file manager the same way you make a Bookmark in your web browser.ALbin75 wrote:It would be nice to be able to make an active shortcut in homefolder.
If you can't see what is taking up that 50GB of space, it is possible that the lost+found contains files that you no longer need. You can delete that lost+found, but then you should create a new (empty) one.ALbin75 wrote:Do uou now why 50gb of the empty harddrive is being used?
Also can I delete the folder named LOst and found that's inside nmt DATA?
Code: Select all
sudo rm /mnt/DATA/lost+found
Code: Select all
cd /mnt/DATA
Code: Select all
sudo mklost+found
If lost+found is empty, forget about it. It does serve a purpose - but it is not something you would normally have to worry about.ALbin75 wrote:The lost and found folder seems to be completely empty. In view I checked show hidden files. No different. Also it can't contain any files that I would need since this harddrive has been added last, after mint 18 and all other software.
It should be a clean empty newly formated hdd. Do I really need to have this lost and found directory in my hdd? Is there some purpose with it?
I gave you the answer to that previously - add noauto to the fstab line.ALbin75 wrote:Also can I in this state use a comand that will stop the hdd from auto mounting at boot?
You created those folders when you entered the command:ALbin75 wrote: I deleted the extra partition that was still inside sda. I used a disk tool to do that. (big mistake...)
After that there was magically a home folder inside mnt DATA. It looked really good. And all the folders were empty. Everything worked good.
mkdir Documents Downloads Music Pictures Videos
When it gets stuck, is there a message that says, "Press S to skip mounting" ?ALbin75 wrote:I then reboot and I'm stuck. I can no longer boot. When sda2 partition on sda isn't found my system refuse to move on to normal boot from ssd.
Guess I'm out of options and have to make use of the new installation
fstab is not what you need. fstab only contains a few instructions used during boot. Grub is what controls which partition and which operating system is booted.ALbin75 wrote:I found fstab. I moved it to usb stick but no change.
Code: Select all
mkdir Documents Downloads Music Pictures Videos
I gave you the answer to that previously - add noauto to the fstab line.ALbin75 wrote:Also can I in this state use a comand that will stop the hdd from auto mounting at boot?
# Mount sda2 at /mnt/DATA
UUID=9c1b3f85-4a25-4de8-a75a-12372fef6f31 /mnt/DATA ext4 defaults,noatime 0 2
Anyway, right now it looks like this:# Mount 1TB DATA partition at /mnt/DATA
UUID=9c1b3f85-4a25-4de8-a75a-12372fef6f31 /mnt/DATA ext4 defaults,noatime,noauto 0 2