![]() When you are done configuring your templates (see below), launch the AutoFS daemon as root by enabling and starting the rvice.ĭevices are now automatically mounted when they are accessed, they will remain mounted as long as you access them. Open the file /etc/nf and add an entry for automount: To mitigate this, only use if you will always be connected to the share, and do not use your home folder or other commonly used folders lest your file browser reads ahead into the disconnected folder When trying to access the folder, programs will get locked into waiting for a response, and either the connection has to be restored or the process has to be forcibly killed before unmounting is possible. ![]() Note: This can cause problems with resources getting locked if the connection to the share is lost. ![]() home/user/usbstick -fstype=auto,async,nodev,nosuid,umask=000 :/dev/sdb1 etc/autofs/auto.master /- /etc/autofs/auto.template /etc/autofs/auto.template /path/to/folder -options :/device/path # ln -s /var/autofs/net/share_name /media/share_nameĪlternatively, you can have autofs mount your media to a specific folder, rather than inside a common folder. If you still want to automount to a target non-empty directory and want to have the original files available even after the dynamically loaded directories are mounted, you can use autofs to mount them to another directory (e.g. This procedure is however non-destructive, so if you accidentally automount into a live directory you can just change the location in auto.master and restart AutoFS to regain the original contents. The base directory will be mounted on to load the dynamically loaded media, which means any content in the base directory will not be accessible while autofs is on. The base directory will be created if it does not exist on your system. Setting this value to 0 will disable the timeout. I'm currently attempting to remove the entry from /etc/fstab, uninstall autofs, and instead create a cron job that mounts the drive on reboot.Tip: The optional parameter timeout sets the amount of seconds after which to unmount directories. Uninstalling autofs has allowed me access to create new directories within the HDD under the mount point, as well as show it fully mounted when viewed via "sudo blkid -o list" (no longer saying "" but instead "/mnt/datahdd"). ![]() Attempts to ensure that I had permissions and ownership via chown and chmod prove unfruitful. I would get a permissions error when attempting to create a new directory in the mount point (via "sudo mkdir /mnt/datahdd/medialibrary", or via webmin or mc in another attempt). I thought all was well, but then I appeared to be having write issues with the device. which allowed a successful reboot, but the HDD was not mounted on reboot.įollowing step 8 (add the device to fstab after installing autofs) did allow a successful reboot, and showed the HDD to be listed as "" when running "sudo blkid -o list". I then tried to follow the ubuntu-autofs tutorial (listed above), following steps 1 through 7, and then just installing autofs. Steps 1 through 9 cause my HC2 to not respond to SSH or come online (according to my router). mnt/datahdd ext4 defaults 0 2" (I've also tried as 0 for the last digit, same outcome) -Ĭode: Select all sudo nano -Rw /etc/fstab I'm not sure if there is something specific about ODROID that I need to edit as well to get this working? I'm also not knowledgable enough in Linux to even know what I don't know. Do I need to edit the fstab in addition to following the autofs article?Īnd while it doesn't brick the system on reboot, my HDD is still not mounted on reboot. mount_hddsĮDIT: After following this article, I did not edit the fstab. Following some tutorials, whenever I edit the /etc/fstab to include my HDD, I end up bricking the system on reboot (blue light flashes, but system won't come online to SSH into, not sure what its hung up on), and have to reflash the SD card with a fresh install of Armbian. I've had no problem partitioning, formatting, and manually mounting the drive to the system. I've been trying to get a server going for file sharing (Samba) & media streaming (Emby) using a ODROID-HC2 with a 4TB Western Digital HDD, flashed with Armbian Buster (4.14.165).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |