Sector size (logical/physical): 512 bytes / 512 bytes The first and easiest is using "lsusb": lsusbīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 002 Device 002: ID 80ee:0021 VirtualBox USB Tabletīus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubįdisk is also a great tool and will show if you even have partitions setup for the drive: sudo fdisk -lĭisk /dev/sda: 20 GiB, 21474836480 bytes, 41943040 sectors There are several ways to determine if your USB is connected and working. So, we need to make sure the sub directories are being created while the USB is connected so we can setup proper permissions on the directories. So what is happening is the pi see's those directories as real directories, because they are, but when you mount a USB on top of those directories they no longer exist since the USB is now actively showing its directories. The funny thing about USBs in linux is that you can create the sub directories without the USB connected and the directories will really be created, but once the USB is connected, those directories will not show up until the USB is disconnected once again. We need to make sure the USB is connected when we setup your sub directories, so we can assign permission to the folders on the USB. UUID="UUID from sudo blkid" /mount_point auto defaults,nofail 0 0 The syntax of your file would need to look something like: #Mount for External Drive I like to reference the Ubuntu Community Fstab document, since it's pretty good. dev/sda5: UUID="6eb0352f-2592-440f-bc9a-7895ad91c340" TYPE="swap" PARTUUID="8e94f8d6-05"īasically, we want to mount the USB drive on boot at the right mount point and with the right permissions, and skip mounting if it's taking too long or not physically connected so the pi can boot the machine just in case the USB is disconnected. To get the UUID of all devices: sudo blkid The proper way to mount devices in fstab would be by using the UUID of the device that will be mounted because sometimes the device names will change, but not the UUID and then we can assign the right options.
We can setup the USB drives in fstab the right way once we get to that part of the problem. whoamiįstab can be a little tricky, especially with USB drives. The command "whoami" will print to the terminal who is the currently logged in user. I personally prefer to run deluged as my user I log in with because of all the permission problems I ran into. What user account are you using to login to the pi? The boot script and deluge auth file from howtogeek are setup for the user "pi." Is that the user account you are logging in with? If not, we need to find out who you are logging in with so we can get the right settings in place. Once the drive is mounted, we need to create the folders and setup permissions on those newly created files and folders with the right user and settings.We need to setup /etc/fstab file to use the proper syntax and options and mount the external drive.
Once we know this, we can begin to assign proper settings for the user and the files and folders What user are you logging in with and would like to run the deluge daemon at boot?
0 kommentar(er)
