4/1/2023 0 Comments Remote wake up openmediavault![]() It is important to mention to not alter the information in between these tags. You can identify entries in /etc/fstab created by the web interface by looking at «openmediavault» tags. ![]() With the mntent entry in config.xml, omv-salt deploy run fstab script writes the appropriate line in /etc/fstab. f767ee54-eb3a-44c5-b159-1840a289c84b /dev/disk/by-label/VOLUME1 /srv/dev-disk-by-label-VOLUME1 ext4 defaults,nofail,user_xattr,usrjquota=er,grpjquota=oup,jqfmt=vfsv0,acl 0 2 0 You can inspect a mntent entry in config.xml it should look like this: Predictable device path of the filesystem.The mount process acts like many other services in openmediavault, first it writes a database entry in config.xml, this entry contains essential information: For the disks to be properly integrated it is better to delete all fstab lines except rootfs and swap, reboot your server and start mounting the disks through the web interface. This is very important, users that come from an existing debian installation with filesystems already present in their fstab file will see that no volumes will be available for creating shared folders even if they are mounted. Drives/filesystems that are not mounted through the web interface are not registered in the backend database, this means you cannot use volumes to create shared folders if they were not mounted properly. The filesystem section of the openmediavault web interface is where you integrate disk volumes to be part of the server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |