Getting hard drive to work (GParted)

[timmyk.2]

timmy@timmy-desktop:~$ sudo blkid
[sudo] password for timmy: 
/dev/sda1: UUID="8997d846-b673-4b84-8633-f3632749cc3e" TYPE="ext4" 
/dev/sdb1: UUID="6f3ff036-efe7-4d04-bc9e-b28f9459a177" TYPE="ext4" 
/dev/sdb5: UUID="aedafaac-c9a8-4eff-bb5f-313e14797e73" TYPE="swap" 
timmy@timmy-desktop:~$

[Bashing-om]

timmyk.2; OK;

Auto mount. edit the file " /etc/fstab ".
Standard operating procedure is to make a back up file prior to editing, never can tell what might perchance.

sudo cp /etc/fstab /etc/fstab-16sep2014

open the file in the text editor with admin privileges, here I use gedit:

gksudo gedit /etc/fstab

and insert these lines:

#sda1 automount created 16Sep2014 mount point /mnt/data
UUID=8997d846-b673-4b84-8633-f3632749cc3e /mnt/data               ext4    defaults  0       0

Now, reload " /etc/fstab " check and see if there are errors:

sudo mount -a

If there are no errors reported by the mount command;
Reboot and let's see the effect. The partition is automounted, and ready immediately for use, and does not require to be manually (UN)mounted, the system will take care of it.

easy as falling out of bed

wide awake

[timmyk.2]

Hmm... I did all that, and at the "sudo mount -a" command I got

timmy@timmy-desktop:~$ sudo mount -a
mount: mount point /mnt/data does not exist

I'm assuming I was supposed to insert those lines at the bottom of the file? Also, I don't know if this is normal or not, but at the "gksudo gedit /etc/fstab" command I got

(gedit:3754): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

[Elfy]

sudo mkdir /mnt/data
sudo mount -a

the /mnt/data folder hasn't been created previously - hence it won't mount there

[timmyk.2]

OK, I did all that, and no errors came up. However, after a reboot, it's not automounted, and even if I manually mount it, I can't put anything on it.

[Bashing-om]

timmyk.2; Hey !

We are making progress !

I bet it is mounted !
Post back:

mount
cat /etc/mtab
ls -al /mnt
ls -al /mnt/data

and let's get ready to 'chown' that mount point to "you" .. to resolve this issue.

so I think

[timmyk.2]

timmy@timmy-desktop:~$ mount
/dev/sdb1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
/dev/sdb1 on /mnt/data type ext4 (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=timmy)

timmy@timmy-desktop:~$ cat /etc/mtab
/dev/sdb1 / ext4 rw,errors=remount-ro 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0
none /sys/fs/cgroup tmpfs rw 0 0
none /sys/fs/fuse/connections fusectl rw 0 0
none /sys/kernel/debug debugfs rw 0 0
none /sys/kernel/security securityfs rw 0 0
udev /dev devtmpfs rw,mode=0755 0 0
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0
tmpfs /run tmpfs rw,noexec,nosuid,size=10%,mode=0755 0 0
none /run/lock tmpfs rw,noexec,nosuid,nodev,size=5242880 0 0
none /run/shm tmpfs rw,nosuid,nodev 0 0
none /run/user tmpfs rw,noexec,nosuid,nodev,size=104857600,mode=0755 0 0
none /sys/fs/pstore pstore rw 0 0
/dev/sdb1 /mnt/data ext4 rw 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0
systemd /sys/fs/cgroup/systemd cgroup rw,noexec,nosuid,nodev,none,name=systemd 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,user=timmy 0 0

timmy@timmy-desktop:~$ ls -al /mnt
total 12
drwxr-xr-x  3 root root 4096 Sep 17 10:44 .
drwxr-xr-x 22 root root 4096 Sep 14 09:10 ..
drwxr-xr-x 22 root root 4096 Sep 14 09:10 data

timmy@timmy-desktop:~$ ls -al /mnt/data
total 116
drwxr-xr-x  22 root root  4096 Sep 14 09:10 .
drwxr-xr-x   3 root root  4096 Sep 17 10:44 ..
drwxr-xr-x   2 root root  4096 Sep 14 09:10 bin
drwxr-xr-x   3 root root  4096 Sep 14 09:10 boot
drwxr-xr-x   2 root root  4096 Sep  8 12:07 cdrom
drwxr-xr-x   4 root root  4096 Jul 22 16:13 dev
drwxr-xr-x 153 root root 12288 Sep 17 11:02 etc
drwxr-xr-x   3 root root  4096 Apr 10 15:11 home
lrwxrwxrwx   1 root root    36 Sep 14 09:10 initrd.img -> boot/initrd.img-3.13.0-35-lowlatency
lrwxrwxrwx   1 root root    36 Sep 13 21:42 initrd.img.old -> boot/initrd.img-3.13.0-32-lowlatency
drwxr-xr-x  23 root root  4096 Sep 14 09:09 lib
drwx------   2 root root 16384 Sep  8 12:02 lost+found
drwxr-xr-x   3 root root  4096 Jul 22 15:48 media
drwxr-xr-x   3 root root  4096 Sep 17 10:44 mnt
drwxr-xr-x   4 root root  4096 Sep 13 23:37 opt
drwxr-xr-x   2 root root  4096 Apr 10 15:11 proc
drwx------   7 root root  4096 Sep 16 22:00 root
drwxr-xr-x  12 root root  4096 Jul 22 16:15 run
drwxr-xr-x   2 root root 12288 Sep 14 09:10 sbin
drwxr-xr-x   2 root root  4096 Jul 22 15:48 srv
drwxr-xr-x   2 root root  4096 Mar 12  2014 sys
drwxrwxrwt   9 root root  4096 Sep 17 13:19 tmp
drwxr-xr-x  10 root root  4096 Jul 22 15:48 usr
drwxr-xr-x  12 root root  4096 Jul 22 16:18 var
lrwxrwxrwx   1 root root    33 Sep 14 09:10 vmlinuz -> boot/vmlinuz-3.13.0-35-lowlatency
lrwxrwxrwx   1 root root    33 Sep 13 21:42 vmlinuz.old -> boot/vmlinuz-3.13.0-32-lowlatency
timmy@timmy-desktop:~$

[Bashing-om]

timmyk.2; HUH ??

timmy@timmy-desktop:~$ mount
/dev/sdb1 on / type ext4 (rw,errors=remount-ro)
##as opposed to:
/dev/sdb1 on /mnt/data type ext4 (rw)

I sure messed this one up - small slip of the paste here on my part !
MY sincere apologies !

Back to the file "/etc/fstab" that line for 'sda1's' UUID should be:

8997d846-b673-4b84-8633-f3632749cc3e

Not even "6f3ff036-efe7-4d04-bc9e-b28f9459a177"
My mind set must have gotten in the way of what was right !

That re-done, we look at the permissions for access to 'sda1' !

again, sorry, I will correct the posting to what is true.

the good thing is;

it's 'buntu

it is all fixable

[timmyk.2]

OK, so I changed the incorrect code to

#sda1 automount created 16Sep2014 mount point /mnt/data UUID=8997d846-b673-4b84-8633-f3632749cc3e /mnt/data               ext4    defaults  0       0

Now there are no errors when I type in

sudo mount -a

However, when I rebooted, the hard drive does not appear in the file manager and there is no icon on the desktop like there was before.

[Bashing-om]

timmyk.2; OK !

Whewhh, I feel better !

The device not now appearing in nautilus is expected behavior as "nautilus" does not see that mount point.
If it is your desire that nautilus does see it, -as some do not want it - will have to change the mount point.

sudo mkdir /media/timmy/data

and back to "/etc/fstab" and change "/mnt/data" to :

/media/timmy/data

In both places.

Now are we ready to look at the access' to 'sda1' ??

step by step, a little

at the time