[Solved] Internal extra hdd's fail to mount at boot with FSTAB

15goudreau · 2014-08-09 18:18:55

Hey guys,

So I've been encountering this annoying issue with Arch so far that I haven't been able to figure out. I have two extra internal hdds that do not mount at bootup. If I click on them in files, it prompts me to enter in my user password and then it will mount them in media as new volume and new volume1.

I edited my FSTAB to include the correct UUID and defaults under the options. However they do not mount at boot. I have to mount them manually which works fine, it's just annoying as my dropbox folder is synced to my extra hdd, and it complains every time I login. Is there something I'm doing wrong? Thanks in advanced!

Last edited by 15goudreau (2014-08-10 17:46:00)

headkase · 2014-08-09 18:21:30

Post your /etc/fstab file contents and also the output of the "mount" command.

Edit: Also post the output of "lsblk -fs"

Last edited by headkase (2014-08-09 18:23:16)

15goudreau · 2014-08-09 18:45:03

fstab

#
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# /dev/sda3
UUID=0990670e-b850-44c4-b4ea-7615b4442159       /               ext4            rw,relatime,data=ordered        0 1

# /dev/sda4
UUID=AE61-E51A          /boot/efi       vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro    0 2

# /dev/sda5
UUID=cfeeea26-0dbb-4a51-82e4-89e06c420cb4       /home           ext4            rw,relatime,data=ordered        0 2

# /dev/sdb1
UUID=584E0A574E0A2DF6   /run/media/taylor/New\ Volume    ntfs    defaults   0  2

# /dev/sdc1
UUID=8660EE7660EE6C7D   /run/media/taylor/New\ Volume1   ntfs   defaults   0  2

lsblk -fs

[taylor@Archer ~]$ lsblk -fs
NAME  FSTYPE LABEL           UUID                                 MOUNTPOINT
sda1  ntfs   System Reserved 001497E41497DACC                     
└─sda                                                             
sda2  ntfs                   D8E2A7D4E2A7B562                     
└─sda                                                             
sda3  ext4                   0990670e-b850-44c4-b4ea-7615b4442159 /
└─sda                                                             
sda4  vfat                   AE61-E51A                            /boot/efi
└─sda                                                             
sda5  ext4                   cfeeea26-0dbb-4a51-82e4-89e06c420cb4 /home
└─sda                                                             
sdb1  ntfs   New Volume      584E0A574E0A2DF6                     /run/media/taylor/New Volume
└─sdb                                                             
sdc1  ntfs   New Volume      8660EE7660EE6C7D                     /run/media/taylor/New Volume1
└─sdc

for mounting I would use

sudo mount /dev/sdb1 /run/media/taylor/New\ Volume

Last edited by 15goudreau (2014-08-09 18:45:44)

Slithery · 2014-08-09 18:48:23

Read the wiki.

You need to be using ntfs-3g as the filesystem type.

headkase · 2014-08-09 19:03:12

For the mount command, just:

mount

By itself. Post the output of that.

loqs · 2014-08-09 20:57:17

@slithery are you sure for I just tried removing ntfs-3g and an fstab entry with type ntfs worked on boot.
The two failing ntfs mounts are under /run/media. So do the two mount points exist at the time the mounts are attempted.
There should be two failed mount units from systemd's attempt to mount the filesystems

systemctl --failed

Should list the units so you can get the names and then

systemctl status mountpoint.mount

15goudreau · 2014-08-09 21:06:20

sudo mount

[taylor@Archer ~]$ sudo mount
[sudo] password for taylor: 
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=4056476k,nr_inodes=1014119,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda3 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
configfs on /sys/kernel/config type configfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
/dev/sda4 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda5 on /home type ext4 (rw,relatime,data=ordered)
tmpfs on /run/user/120 type tmpfs (rw,nosuid,nodev,relatime,size=811868k,mode=700,uid=120,gid=120)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=811868k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/sdb1 on /run/media/taylor/New Volume type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
/dev/sdc1 on /run/media/taylor/New Volume1 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)

sudo systemctl --failed

0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

changing to ntfs-3g didn't work.

Last edited by 15goudreau (2014-08-09 21:10:08)

loqs · 2014-08-09 21:18:37

If you change one of the missing ntfs mounts mountpoints to /mnt just as a test does that allow it to mount on boot?

15goudreau · 2014-08-09 22:27:59

@ loqs. That did work. So why can't I mount it to /media like arch wants... hmmm

15goudreau · 2014-08-09 22:29:02

the other drive that I tried to mount within the fstab gives me an error when trying to access it now.

Error mounting system-managed device /dev/sdb1: Command-line `mount "/run/media/taylor/New\\"' exited with non-zero exit status 32: mount: /etc/fstab: parse error: ignore entry at line 15.
mount: unknown filesystem type 'Volume'

loqs · 2014-08-09 22:47:35

15goudreau wrote:

@ loqs. That did work. So why can't I mount it to /media like arch wants... hmmm

From your mount listing

run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)

/run being tmpfs (which is normal ) means it starts as an empty directory then populated with some entries by tmpfiles.d the rest of its contents comes from programs executing later in boot
So at the point the fstab is parsed and mount attempted it seems /run/media/taylor/New\ Volume and /run/media/taylor/New\ Volume1 do not exist so the mount fails.
From udisks2 looks like udisks2 is creating the paths and doing the mounting
Hope that explains it a little better
Edit:
If the new error is still occurring:
What command produced the new error?
Can you post /etc/fstab as it is now

Last edited by loqs (2014-08-09 23:16:47)

15goudreau · 2014-08-10 01:26:46

The error was occurring whenever I tried to mount it in fstab like that. I forgot to mention it in the OP. So is there nothing that can be done? It seems like a huge hassle to have to enter in a password to access my harddrives and on top of that have to relink dropbox each startup.

fstab as it is now

#
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# /dev/sda3
UUID=0990670e-b850-44c4-b4ea-7615b4442159       /               ext4            rw,relatime,data=ordered        0 1

# /dev/sda4
UUID=AE61-E51A          /boot/efi       vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro    0 2

# /dev/sda5
UUID=cfeeea26-0dbb-4a51-82e4-89e06c420cb4       /home           ext4            rw,relatime,data=ordered        0 2

# /dev/sdb1
UUID=584E0A574E0A2DF6   /run/media/taylor/New\ Volume    ntfs   defaults   0  2

# /dev/sdc1
UUID=8660EE7660EE6C7D   /mnt   ntfs   defaults   0  2

headkase · 2014-08-10 01:28:46

You do know that "ntfs" is built-into the kernel and provides read-only access. "ntfs-3g" is a separate package you install and provides both read and write access.

ntfs != ntfs-3g

15goudreau · 2014-08-10 01:47:29

I understand headkase, but it didn't work with ntfs or ntfs-3g. I can worry about read/write access after I get the drives to mount properly. Although with what loqs said above I'm not sure if I can.

headkase · 2014-08-10 01:54:58

For:

# /dev/sdc1
UUID=8660EE7660EE6C7D   /mnt   ntfs   defaults   0  2

You are putting the mount directly onto the /mnt folder, which is wrong.

Create a folder (before mounting) in /mnt, like say "/mnt/name" where "name" is your choice. Then in the fstab entry instead of "/mnt" replace that with "/mnt/name" so it doesn't take the entire folder but rather mounts on the sub-folder.

headkase · 2014-08-10 01:58:31

For:

# /dev/sdb1
UUID=584E0A574E0A2DF6   /run/media/taylor/New\ Volume    ntfs   defaults   0  2

You are mounting within your run/media/taylor folder. When the fstab is parsed, early in boot, this folder may not exist yet - it may only exist when you log into your user later on in the boot process. Try making a folder in /mnt, as instructed above, for this mountpoint too and changing the mountpoint to that folder. Because /mnt will always exist where the /run/media/* is not always guaranteed to exist.

15goudreau · 2014-08-10 02:04:34

right, but if I mount the drive to /mnt/folder, (I understand that it needs a folder "name") that will at least allow it to be mounted in the same place, which I guess is good for dropbox but then instead of having access through the File manager Devices I have to sift through computer>mnt>file. I know it seems like it is splitting hairs, and maybe I am just being difficult, but I feel like this isn't the easiest most streamline way to get my drives mounted so that they can be seen under Devices, and I do not have to enter in my password each time.

headkase · 2014-08-10 02:08:37

Mountpoints need an empty folder to mount onto. So, /mnt/folder1 where "folder1" is empty then in your fstab you would have /mnt/folder1 as the location and when mounted the contents of folder1 would change from empty to whatever the contents of the mount had.

You can also put the mountpoints inside of your home folder if you like, just mount them onto some empty folders there. It might not matter but make sure / is first in fstab, followed by /home, and then followed by the mountpoints you could put in your home folder.

Depending on how your desktop environment mounts folders you could also edit your sudoers file so that "sudo mount" and "sudo umount" do not need a password. Again, depending on your environment, that might work.

Edit: put this in your sudoers (using visudo!):

bill ALL = NOPASSWD: /usr/bin/mount
bill ALL = NOPASSWD: /usr/bin/umount

Replace "bill" (my username) with your own.

Last edited by headkase (2014-08-10 02:11:09)

Trilby · 2014-08-10 02:11:31

Mount them in a location that will exist during the boot process (/mnt can work, but creating a /media might be better and more flexible). Then just configure your file manager to display those folders in the side pane like it does folders under /run/username/media.

15goudreau · 2014-08-10 02:23:28

That should work. It's unfortunate that this is the workaround but it'll will suffice for my purposes. Thanks guys for the help.

headkase · 2014-08-10 02:27:16

You're welcome but you should see your thread through to fully solved. And when it is solved, not before, edit your first post and put "[Solved]" on the beginning of the title without quotes.

Last edited by headkase (2014-08-10 02:27:39)

loqs · 2014-08-10 09:57:56

If its enough that the filesystems are available on user login this should see the filesystems mounted where you want them under /run/media and probably show in your filemanager as expected
Create a script file or append this to one thats already executed on login

udisksctl mount --block-device /dev/disk/by-uuid/584E0A574E0A2DF6
udisksctl mount --block-device /dev/disk/by-uuid/8660EE7660EE6C7D

edit /usr/share/polkit-1/actions/org.freedesktop.udisks2.policy
in the block starting

  <action id="org.freedesktop.udisks2.filesystem-mount-system">

change allow_active to yes (from a script it may need allow_any instead not tested this)

    <defaults>
      <allow_any>auth_admin</allow_any>
      <allow_inactive>auth_admin</allow_inactive>
      <allow_active>yes</allow_active>
    </defaults>
  </action>

This will stop udisksctl from producing a popup prompting for your password but obviously relaxes security on udisksctl

Last edited by loqs (2014-08-10 10:26:28)

15goudreau · 2014-08-10 17:45:49

Alright, so what I did was I created the directories /media/volume1 and /media/volume2 I edited my fstab to mount the drives there with the ntfs-3g (thanks headkase!). The nautilis file manager found the drives after I edited its configuration file. So now I can access the drives without being prompted for a password and dropbox links up without having to relink on reboot. Thanks all for the different suggestions and helping me troubleshoot! - marked solved.

Arch Linux

#1 2014-08-09 18:18:55

[Solved] Internal extra hdd's fail to mount at boot with FSTAB

#2 2014-08-09 18:21:30

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#3 2014-08-09 18:45:03

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#4 2014-08-09 18:48:23

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#5 2014-08-09 19:03:12

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#6 2014-08-09 20:57:17

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#7 2014-08-09 21:06:20

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#8 2014-08-09 21:18:37

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#9 2014-08-09 22:27:59

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#10 2014-08-09 22:29:02

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#11 2014-08-09 22:47:35

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#12 2014-08-10 01:26:46

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#13 2014-08-10 01:28:46

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#14 2014-08-10 01:47:29

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#15 2014-08-10 01:54:58

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#16 2014-08-10 01:58:31

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#17 2014-08-10 02:04:34

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#18 2014-08-10 02:08:37

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#19 2014-08-10 02:11:31

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#20 2014-08-10 02:23:28

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#21 2014-08-10 02:27:16

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#22 2014-08-10 09:57:56

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

#23 2014-08-10 17:45:49

Re: [Solved] Internal extra hdd's fail to mount at boot with FSTAB

Board footer