

I tried changing the file access to read and write and that seemed to work but had no effect on Plex. I plan on this getting me back into linux and eventually being proficient enough to help others like you all helped me.Įdit: I followed instructions and immediately hit a wall at step 2 trying to edit permissions. I was running Ubuntu fulltime ~13 years ago as a young nerdy kiddo and abandoned it when my mom got me a Macbook for graduating high school early so I forgot most of what I had learned. No clue why that syntax made any sort of difference, but it did.Įither way, I really appreciate the assistance so much from you all. For some reason, Ubuntu didn't like "/media/HDD-M" but once I changed it to "/media/SG" it worked without issue. Just like that, it read and streamed without a hitch. After following response I realized the original guide I found may have allowed me to screw things up so I followed it backwards and undid everything before trying the link you posted which worked after I messed with the mount point renaming a bit until Ubuntu was satisfied with my efforts. Following that new mount point would lead me to my drive and allow access but made no difference to Plex. It did seem to work but Plex was still blind. I didn't get email notifications with updates to the question for some reason so I just checked and got it all I did manually create an actual mount point under "/media/HDD-M" (HDD-M s the drive name, HDD-Movies) through the initial guide I referenced. If you have any questions I’d be happy to try to explain.Edit2 (SUCCESS): First off, thank you to all who responded! I got my Plex server working perfectly. “man mount” will also have some good information on the subject. You might want to open a terminal and type “man fstab” for more information on the fstab file. Type “sudo mount /opt/plex/videos”, list the directory avgain, and you’ll see the files have returned. List the directory again, you’ll see it’s empty. Now type “sudo umount /opt/plex/videos” (note it’s umount, not mount) to unmount the drive. Verify they’re there by listing the directory: ls -l /opt/plex/videos Well the directory itself is in fact on the SD card, but its contents are on the hard drive.Ĭopy a few files to /opt/plex/videos (they can be anything, don’t have to be videos for the purposes of the test). UUID=f0C81fb5-BEF0-40EB-67854-055afd /opt/plex/videos ext4 defaults 0 0Īfter modifying /etc/fstab, you can reboot for it to take effect, or simply type “sudo mount -a”.Īfter the drive is mounted, you can copy files to /opt/plex/videos and they will be placed on the pidrive even though the directory appears to exist on the SD card. This means that /dev/mmcblk0p6 will be mounted at the root of the filesystem “/”, while /dev/mmcblk0p5 will be mounted on the “/boot” directory. dev/mmcblk0p6 / ext4 defaults,noatime 0 1 So a “typical” Raspi fstab might look like this: The sixth field is the order in which filesystems should be checked via fsck at boot time 0 means don’t check.


The fifth field is used by the “dump” command none of my systems (Raspbian, Linux Mint and Slackware) even have a “dump” command. The fourth field is mount option flags, usually “defaults” for the default options.
PLEX MEDIA SERVER RASPBERRY PI 3 HARD DRIVE WINDOWS
The third field is the type of filesystem on the device, and will most likely be ext4 for a native linux partition, or vfat for a Windows type partition there are a large number of possible types but those are the two most common especially on our Raspberry Pis. This is the “mount point” where the device will be visible to the software. The second field is a directory somewhere in the filesystem with some restrictions it can be anywhere. Drives can also be identified by a “Universal Unique IDentifier”, or UUID in which case the first field is something like UUID=f0C81fb5-BEF0-40EB-67854-055afd using UUIDs is better for reasons I won’t go into right now but will explain if you’re curious there’s some interesting history behind it. The first is the device, and will be something like /dev/mmcblk0p1 or /dev/sda1. The file /etc/fstab is basically a list that maps physical block devices (hard drives) to locations in the filesystem.
