If a folder is created via SSH under /data/ like /data/New-folder, it will not appear as a normal share in ReadyNAS OS 6's web GUI. What needs to be edited to make that folder become a normal share? Specifically which terminal commands needs to be executed and which files needs to be edited?

tigerten wrote: you can create volume under SSH for ReadyDATA. I would assume possible with ReadyNAS as well. Yes. Netgear has a utility called rnutil. It has quite a few "personalities" event_push push a system event to the UI get_disk_info print a list of all attached disks and disk information check_ups_drv check and possibly start network ups drivers rn_shutdown shutdown readynasd and system gracefully rn_lcd LCD display remote_access start a remote access session for tech support volume_util perform volume operations mkhomedir_helper home subvolume creator for PAM disk_event_handler handler for disk events hotplug_event notifier for hotplug events md_event notifier for MD RAID events start_raids start all MD RAID arrays volume_schedule start volume schedule job spindown_schedule start spindown schedule job backup_md backup MD RAID superblocks bit_rot_event bit rot events firmware_update check for firmware update apt_wait Wait for an APT lock to release create_system_log Create system log archive diagnostics Run system diagnostics blink Locate the NAS with LEDs bluetooth_event Bluetooth events dump_sysflags List systype flags or check if flag is set for system clamav_event ClamAV events antivirus_scan_rootfscan antivirus in rootfs The personality is determined by the executable file name. For instance, /usr/bin/volume_util is a link to rnutil, and when you execute the link you can run the volume_util command set. (you can alternatively run rnutil volume_util directly). The volume_util commands are: root@NAS:~# volume_util help Usage: volume_util [-c NAME] [-c NAME D1,..,DN] [-c NAME LEVEL D1,..,DN] [-c NAME LEVEL D1,..,DN KEY_FILE] [-d NAME|UUID] [-x NAME|UUID] [-e] [-e TYPE] [-v NAME LEVEL D1,...,DN] [-f NAME DISK] [-S DISK] [-F DISK] [-s TYPE..] -c Create pool NAME is the desired pool name LEVEL is the desired RAID level (0,1,5,6,10) D1,..,DN is the list of disk channels to use, zero-based you may specify the disk by controller and channel, so '0,1' means chassis 0, channels 0 and 1 '1:3,1:4' means chassis 1, channels 3 and 4 if you do not specify any channels, all available channels will be used KEY_FILE is the encryption key passphrase file for encrypted volumes -d Delete pool NAME is the desired pool name UUID is the UUID of the desired pool -x Export pool NAME is the desired pool name UUID is the UUID of the desired pool -e Expand pool TYPE is one of 'auto', 'expand', 'extend', or 'xraid' auto - automatically do all forms of expansion expand - expand to fill all space on all current disks (disk replacement) extend - extend pool to use available new disks (disk addition) xraid - grow pool to use available space on some current disks (partial disk replacement) -f Flex-RAID add parity NAME is the desired pool name D1,..,DN is the list of disk channels to use, zero-based you may specify the disk by controller and channel, so '0,1' means chassis 0, channels 0 and 1 '1:3,1:4' means chassis 1, channels 3 and 4 -E Flex-RAID expand NAME is the desired pool name D1,..,DN is the list of disk channels to use, zero-based you may specify the disk by controller and channel, so '0,1' means chassis 0, channels 0 and 1 '1:3,1:4' means chassis 1, channels 3 and 4 -v Vdev expand pool NAME is the desired pool name LEVEL is the desired RAID level (0,1,5,6,10) D1,..,DN is the list of disk channels to use, zero-based you may specify the disk by controller and channel, so '0,1' means chassis 0, channels 0 and 1 '1:3,1:4' means chassis 1, channels 3 and 4 -S Make a disk a hot spare DISK is the disk channel to use, zero-based -F Format disk DISK is the disk channel to use, zero-based -r Automatically repair degraded pools -O Forcibly optimize swap array -s Show volume information TYPE is any combination of 'disk', 'raid', 'pool', or 'enclosure' separated by a space so '-s disk raid' would show disks and raids What rnutil doesn't seem to have is a mechanism to create a public share.You can create a home folder for a user account with rnutil mkhomedir_helper - which is a specialized share, but not public. root@NAS:~# mkhomedir_helper Usage: mkhomedir_helper <username> root@NAS:~# There possibly could be some other tool that can create a public share, but I don't know what it is. As Sandshark says, there is a repair script that Netgear support uses that might give you more clues. https://gitlab.codycook.us/readynas-scripts/share_lun_ui_fix.sh If you download it to the NAS with wget, you will need to add the --no-check-certificate option.

I managed to make the BTRFS subvolume that was created via CLI visible in the web admin 😄 I added it like thissqlite3 /var/readynasd/db.sq3 INSERT INTO share (id, zfs_name, type, volume_id, name, path, user_access, group_access, everyone_access, non_owner_delete, user_id, group_id, update_ts) VALUES (13, 'data/TestTest', 'share', 'data', 'TestTest', '/data/TestTest', 7, 7, 7, 0, 99, 99, CURRENT_TIMESTAMP); .exit

I know a little bit more now. But it's still not a complete method for creating a share via CLI. I wish Netgear was more transparent and released technical documentation. tigerten Create a separate thread for the issue with your USB drive. It is probably solvable.

eton wrote: If a folder is created via SSH under /data/ like /data/New-folder, it will not appear as a normal share in ReadyNAS OS 6's web GUI. What needs to be edited to make that folder become a normal share? Specifically which terminal commands needs to be executed and which files needs to be edited? Among other things, a share is a BTRFS subvolume, and not an ordinary folder. The best thing is to rename new-folder to a temporary name, and then create the share properly using the web ui. Then copy the contents into the share, and delete the original folder. You can do the copy from ssh using --ref-link - that will transfer more quickly, and won't double the disk space.

Ah, BTRFS subvolume!I know how to create a share via the web GUI. The question is how to dot it via terminal.How is this accomplished?Please reply with full command example for `--ref-link`.

Making a folder appear as a volume in OS 6 GUI?

19 Replies

StephenB
Guru
Apr 15, 2023
eton wrote:

If a folder is created via SSH under /data/ like /data/New-folder, it will not appear as a normal share in ReadyNAS OS 6's web GUI. What needs to be edited to make that folder become a normal share? Specifically which terminal commands needs to be executed and which files needs to be edited?

Among other things, a share is a BTRFS subvolume, and not an ordinary folder.

The best thing is to rename new-folder to a temporary name, and then create the share properly using the web ui. Then copy the contents into the share, and delete the original folder. You can do the copy from ssh using --ref-link - that will transfer more quickly, and won't double the disk space.
- eton
  Luminary
  Apr 15, 2023
  Ah, BTRFS subvolume!
  I know how to create a share via the web GUI. The question is how to dot it via terminal.
  How is this accomplished?
  Please reply with full command example for `--ref-link`.
  - StephenB
    Guru
    Apr 16, 2023
    eton wrote:
    
    I know how to create a share via the web GUI. The question is how to do it via terminal.
    
    How is this accomplished?
    
    Not sure how to set up everything the ReadyNAS application needs, so my basic advice is don't.
    
    eton wrote:
    
    Please reply with full command example for `--ref-link`.
    
    It's an option for cp.

Forum Discussion

Making a folder appear as a volume in OS 6 GUI?

19 Replies

Related Content

Orbi's main unit making clicking/rattling sounds

RN102 OS6 Home folder

Problems downloading make to ReadyNAS RN 212

1002030001 Commit failed when creating a new folder

Pb avec Home folder

NETGEAR Academy

ProSupport for Business