Linux Lite Forums

Full Version: Need to authenticate before accessing internal drives
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
Ok, I can see how text/code would be much better than a pic.

Using multiple folders makes a lot of sense. That clears that up for me. I will try this and get back.

Thank you.

The only thing I can add about the first version of that post is that I used the forum url links directly from postimage, and probably they conflicted with SMF somehow.
Ok, I still have a problem. Here is the mount output:

Code:
paul@Precision:~$ sudo mount -a
[sudo] password for paul:
[mntent]: line 17 in /etc/fstab is bad
[mntent]: line 19 in /etc/fstab is bad
[mntent]: line 21 in /etc/fstab is bad
paul@Precision:~$


Here is the fstab (it had a blank line at the bottom):


Code:
# /etc/fstab: static file system information.
#MUST HAVE BLANK LINE AT BOTTOM
#
# 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/sda1 during installation
#noatime, added for SSD TRIM by pb, 7/2015
UUID=821f7efc-9a0e-482a-a750-0a393503d99e /               ext4    noatime,errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=f0a720b2-5678-48de-b5f4-088e0e8d3e2c none            swap    sw              0       0
#
#NTFS Partitions automount:
# Seagate 400:
UUID=A0103FFB103FD74E /home/paul/seagate400 ntfs defaults,umask=007, uid=1000, gid=1000 0 0
#Seagate 520:
UUID=60426C51426C2E4A /home/paul/seagate520 ntfs defaults,umask=007, uid=1000, gid=1000 0 0
#WD 2TB:
UUID=D872AA8A72AA6D46 /home/paul/wd2000 ntfs defaults,umask=007, uid=1000, gid=1000 0 0


And here is a pic of the permissions (all three folders had exactly the same permissions):


[Image: perms.png]


If this prints well then the problem was with postimage's forum url.


Thanks for your time.
Those UUID's don't look right at all. They should be something like '4f9e3858-d3f2-49da-8504-c728c7ccee88' instead yours are like 'A0103FFB103FD74E' Can you check again with the sudo blkid command please. Also check the formatting of your fstab. Each block of info should be proceeded by a tab eg.

You have: UUID=A0103FFB103FD74E /home/paul/seagate400 ntfs defaults,umask=007, uid=1000, gid=1000 0 0

Should be: UUID=D872AA8A72AA6D46    /home/paul/wd2000    ntfs        defaults,umask=007,uid=1000,gid=1000    0    0

looks like you've just put a space instead of a tab.

You also have spaces after these: umask=007, uid=1000, gid=1000
when there should be none. Should be: umask=007,uid=1000,gid=1000

Much to work on here.
Permissions look good, just need to change the above mentioned fstab.
(07-29-2015, 11:19 PM)paul1149 link Wrote:If this prints well then the problem was with postimage's forum url.

Try to use imgur.com instead as the Guidelines state. Then you wont have any issues Smile
Ok, bingo. I hadn't realized that lines in fstab must be contiguous, delimited only by tabs. Once I substituted tabs for spaces, and took out the spaces after the commas, I was in. Two folders were already mounted so I just rebooted to wipe the slate clean, and it's perfect now.


I did note that the UUIDs looked different from those of the ext4 partitions on the system, so I double checked and it is accurate.


If imgur is a hard and fast rule here let me know and I will comply. But I have to say that I detest the interface there. Postimage.org is so very simple. To get it to work one has to use the Direct Link, though, and then submit it to this forum's image insert facility.


Thanks so much for lending me your valuable time.


BTW, I installed LL on an HP netbook today. Went very well. Speaking of fstab, though, is it necessary to go through the TRIM procedure there and via command line for the sake of the SSD?


Paul
fastb - glad it's working. Only reboot once the sudo mount -a stops producing errors. If you try to reboot on a broken fstab, you won't be able to boot your pc Sad

Imgur - it's not a hard and fast rule, but it would have saved you and I some time. We always try to give the best advice for members Smile

Trim SSD - use this command to check if Trim is supported:

Code:
sudo hdparm -I /dev/sda | grep "TRIM supported"

If it is, follow the guide in the Help Manual Smile If you don't Trim, your SSD life will be reduced, so it's a must do given their cost.

Type carefully in the fstab and always check with sudo mount -a before rebooting Smile
Also re. postimage.org the quality is terrible:

Your image on postimage.org:

[Image: perms.png]

Same permissions tab on imgur.com:

[Image: RtpcwEi.png]
Thanks again. Yes, I did find out the hard way that fstab really is finicky. But it was easy to go in and edit it via the install disk.


I will continue then with postimage, but I will preview each post before sending it in.


Thanks for that TRIM command. I don't think I saw that in the manual, and will save it in my notes.


And thanks for your work on LL.


BW,
Paul
You're welcome Paul. I cringe at your choice of postimage.org, but we can't force you not to use it.

Happy computing Smile
Pages: 1 2 3