![]() ![]() These aren’t file level permissions, you can think of this as a layer above that which grants access to the share at all. Give yourself, for example, read/write permissions to access the scratch share. You have to grant privileges to everyone that you want to be able to access the share if you are using Samba, FTP or AFP (NFS works differently). Now select the newly created shared folder and click privileges in the toolbar. You will be asked to save pending configuration changes. Set permissions as needed, for most cases the default will be fine, these are file level permissions. The system automatically suggests a relative path, this is almost always fine. In my case the name is “scratch” and I want it on /dev/sda1, the drive I’ve just formatted. Enter a name and pick the drive you want this share to be created on. Click Storage > Shared Folders on the menu and then click the + on the toolbar to create a new shared folder. For this tutorial I’ll set up the scratch drive. There will be one for family photos and videos, one for each family member and a shared scratch drive. ![]() I’m planning on creating a number of shared folders. If you now run “lsblk -f” at a terminal you’ll see something like this: NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT OVM will ask you to confirm you want to mount this file system and then ask you to commit the pending configuration changes. Optionally set a warning threshold, I prefer 95% as I find after the initial load the amount of data grows quite slowly. When the process is complete close the dialog, this automatically opens the mount settings. ![]() You’ll see a dialog with progress while they system works. Since we’re changing the format of the drive it has to be completely formatted which will take a while, at least 10 minutes on a drive of this size. Since this is just a storage drive EXT4 is a good choice. The file system type you choose depends somewhat on what you want to do with the drive. On the creation settings page select the drive you’d like to create a file system on (/dev/sda in our case) and the file system type. Select Storage > File Systems from the menu and then click the + create / mount button in the menu. You’ll then see output looking something like this: Creating a Filesystem A secure wipe will take a long time and we just need the existing drive structure gone so select quick. You’ll then be asked if you want to perform a quick wipe or a secure wipe. Naturally, you’ll be asked to confirm that you want to wipe the drive. Select the drive you want to work with and then click the “Wipe” button in the tool bar. The mmcblk0 device is the SD card which store the operating system and sda is the attached USB drive. You’ll be presented with a list of the disks attached to your device. From the home page select Storage > Disks in the menu. OMV 6 has basic tools to remove the existing partitions and create new ones but it’s not entirely clear that they exist. While we can certainly mount this on our Raspberry Pi we’re asking for trouble in the long term as file permissions will become a pain to deal will – much better to just use EXT4 or one of the other natively supported file systems. In our case we’re attaching a 4TB portable (2.5″ drive) which is formatted as a single NTFS partition. Since this is a Raspberry Pi we’re working with the drive is attached via USB3 and most drives like that come with a filesystem already installed. ![]() We’ll be attaching a USB hard drive which has an NTFS partition on it. This article assumes you have a Raspberry Pi 4 with OMV 6 installed and working correctly. In this article we’ll add a storage drive. In an earlier article we installed OMV and did the most basic set up. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |