cowboyuptx 0 Posted January 9, 2016 Posted January 9, 2016 (edited) Hello everybody... I'm new to emby and I'm having trouble getting emby to have access to 2 out of three of my drives... Emby can only add folders from my external HDD, which is listed as sdd1... All three HDDs are booting up at Mint's startup, and emby is able to see sdb1 and sdc1, but I am not able to navigate inside those drives within the emby GUI... Here's some code that might provide insight as to where I fumbled... Any help is greatly appreciated! plex@plex-TZ68K ~ $ sudo fdisk -l [sudo] password for plex: Disk /dev/sda: 250.1 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0007f670 Device Boot Start End Blocks Id System /dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT /dev/sda2 206848 256952319 128372736 7 HPFS/NTFS/exFAT /dev/sda3 256954366 488396799 115721217 5 Extended /dev/sda5 471803904 488396799 8296448 82 Linux swap / Solaris /dev/sda6 256954368 471803903 107424768 83 Linux Partition table entries are not in disk order WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 1 4294967295 2147483647+ ee GPT Partition 1 does not start on physical sector boundary. Disk /dev/sdc: 1500.3 GB, 1500301910016 bytes 255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x47d9be29 Device Boot Start End Blocks Id System /dev/sdc1 2048 2930274303 1465136128 7 HPFS/NTFS/exFAT WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdd1 1 3907029167 1953514583+ ee GPT AND plex@plex-TZ68K ~ $ sudo blkid /dev/sda1: LABEL="System Reserved" UUID="7A1ED0151ECFC7F9" TYPE="ntfs" /dev/sda2: UUID="80F833A5F833987C" TYPE="ntfs" /dev/sda5: UUID="e881ffcf-37ab-43d1-b1a4-eb00581b7110" TYPE="swap" /dev/sda6: UUID="9f820e61-077d-4975-80eb-838c834ed7b1" TYPE="ext4" /dev/sdb1: LABEL="SAVED BY GRACE" UUID="516A78EA019DAC70" TYPE="ntfs" /dev/sdc1: LABEL="I LOVE YOU !" UUID="543E2FD13E2FAB46" TYPE="ntfs" /dev/sdd2: LABEL="KILLUMINATI - ONE" UUID="E46014BE6014997E" TYPE="ntfs" And this is what my Fstab File looks like # /etc/fstab: static file system information. # # 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/sda6 during installation UUID=9f820e61-077d-4975-80eb-838c834ed7b1 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=e881ffcf-37ab-43d1-b1a4-eb00581b7110 none swap sw 0 0 UUID="E46014BE6014997E" /mnt/external_hdd ntfs-3g defaults 0 0 UUID="543E2FD13E2FAB46" /media/plex/I\040LOVE\040YOU\040! ntfs-3g auto,user,rw 0 0 UUID="516A78EA019DAC70" /media/plex/SAVED\040BY\040GRACE ntfs-3g auto,user,rw 0 0 Many thanks to all of you who aid us recent converts... Edited January 10, 2016 by cowboyuptx
cowboyuptx 0 Posted January 10, 2016 Author Posted January 10, 2016 (edited) Hello? I'm still lost here... hoping somebody out there can help me get these drives mounted in a way that emby can see them... I've looked for answers to this problem but haven't really found much... I found this post from last year where the guy had the exact same problem as me, but I'm not really understanding it... http://emby.media/community/index.php?/topic/23174-emby-cant-access-second-hard-drive/ The solution offered there seemed to be that he would have to make an fstab entry for every single directory he added to emby... So like what does that mean? Would I need to make an fstab entry for every show and possibly every season? That doesn't sound correct... Edited January 10, 2016 by cowboyuptx
brett_1968 1 Posted January 11, 2016 Posted January 11, 2016 I don't mean to be rude, but I don't think you grasp how mount points work. Don't worry we can soon fix that. First a few questions: 1/ How are these drives connected? ie. SATA, USB, etc? 2/ You want to use the entire drives, not just selected directories? 3/ These drives are always connected to the machine?
cowboyuptx 0 Posted January 11, 2016 Author Posted January 11, 2016 (edited) I don't mean to be rude, but I don't think you grasp how mount points work. Don't worry we can soon fix that. First a few questions: 1/ How are these drives connected? ie. SATA, USB, etc? 2/ You want to use the entire drives, not just selected directories? 3/ These drives are always connected to the machine? I take no offense, I believe you're correct in stating that I do not fully understand it. I'm just really glad to have some help! 1/ I have one external HDD and emby has no trouble finding and loading stuff from that USB drive. The 2 HDD's that I need emby to be able to navigate and select media from are internal HDD's connected via SATA. 2/ I do want to be able to access the entire drive(s) and add anything I choose from it to my emby library, but at the same time I don't want to add the entire contents of the drive into my emby library (if that makes sense)... 3/ Yes they are always connected. Thank you for helping me! Edited January 11, 2016 by cowboyuptx
brett_1968 1 Posted January 12, 2016 Posted January 12, 2016 The first thing you need to decide is where you want to mount the drives in the file system, the old-school way is to mount them under "/mnt" but the more recent convention is to put them under "/media". The main difference you will see between the two is with the desktop file managers, in that they usually look in "/media" for mounted devices and so show them in the file manager directly (without having to navigate to "/mnt"). Next you need to know what you are going to name the mount points, ie. disk-1, disk-2 or the drive label etc. This is so you can easily identify the individual drives. and lastly who is going to be able to access these drives, ie. which users can do what, no access, read only, read write etc. Now we can get on with actually mounting the drives: The fstab file contains a list of devices and the parameters required to correctly mount them at system startup. There are 5 main items that need to be included: 1/ the device 2/ the mount point 3/ the file system type 4/ the parameters to mount under 5/ if a filesystem check is require on boot these are contained in one line per mount in the file, so we have: <device> <mount point> <file system> <mount parameters> <file system check> for each device we want to mount. Now for the device you can use a few different things to identify it, dev, label etc but it is recommended to use the "UUID" so that the mount remains static across reboots as some of the other identifiers can change. So the steps you need to do are: you will need to be root or use "sudo" 1/ Create the mount point: mkdir /mnt/mydisk 2/ Change the mount point owner to the user you want chown user:group /mnt/mydisk 3/ Change the access permissions chmod 0755 /mnt/mydisk 4/ Edit fstab 5/ Reboot you will probably have some questions about the file permissions so just ask. good luck
thefirstofthe300 292 Posted January 17, 2016 Posted January 17, 2016 (edited) First off, I believe that file managers do not detect what drives are mounted based on them being mounted in /media. They detect the drives when they are mounted using udev/udisks. If the drives are mounted via fstab, the file manager sees it transparently as part of the file system. I am not trying to be a know-it-all, just trying to set expectations correctly. Second, I think that the issue stems from the fact that the drives are NTFS. NTFS is notoriously bad about permissions under Linux. The best way to solve permissions issues will be to set the permissions at mount. The Arch wiki has a good article on NTFS-3g and the issues with permissions. Based on the aforementioned article, the mount options for each drive should be set to UUID="NTFS-partition-UUID" /your/preferred/mount/point ntfs-3g uid=<emby-username>,gid=<group>,umask=0002 0 0 <emby-username> should be changed to whatever user is running the server (probably emby unless you changed the init's config). Group should be changed to whatever group you want to have access to the files as well. The umask tells your system what to set the octal permissions (link to another good Arch wiki article) to. If you do not wish to set any one of the above, that is ok as long as Emby has read and write permissions to those drives in the end. I hope this helps. As a side note, I would recommend getting rid of the spaces in the mount points. As a rule, removing spaces for root directories that you will be dealing with in the terminal tends to make your life easier in the long run. Edited January 17, 2016 by thefirstofthe300
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now