seems the only way to setup shares is to format/erase disks

[headcaver]

im at the setup stage
under storage it says:

"Which disks should be set up? Everything on these disks will be erased."

i cant see any way around it
those disks are formatted to EXT4

I dont wish to format my disks

any ideas?
thanks

[testeur70]

I have exactly the same question. Do we have to format and loose all our file before installing SaresOs? Is it possible to install this Os on Alt-F without saving and restoring our datas ?
Thanks

[testeur70]

Hello Headcave,
I just managed to recognize my two HDD on my DNS-320L Nas, thanks to JAN (shareos owner).
Do not follow the wizzard that is going to erase all the data on the HDD. The next relese will automaticly do this.
Bellow the command that should be send to the Nas via SSH :

**Please do NOT use the wizard – it creates new volumes and erases the disks**.
Your existing ext4 partitions (sda2, sdb1) can be taken over without erasing.

The next release (0.2.0-beta.17) will have a button for this under Storage
("take over existing drive"). If you don't want to wait, here is the same
right now over SSH (ssh root@<box-IP>, with the password you set in the
setup wizard):

1. Check the partitions:
     blkid /dev/sda2 /dev/sdb1
   Both should show TYPE="ext4" and a UUID.

2. Register the first disk as volume "data" and mount it:
     uci set storage.data=volume
     uci set storage.data.uuid=$(blkid -s UUID -o value /dev/sda2)
     uci set storage.data.fstype=ext4
     uci set storage.data.layout=single
     uci set storage.data.enabled=1
     uci set storage.global=global
     uci set storage.global.apps=data
     uci commit storage
     shareos-storage mount data
     mkdir -p /mnt/data/.shareos && chmod 711 /mnt/data/.shareos

3. The same for the second disk as volume "backup" (without the apps lines):
     uci set storage.backup=volume
     uci set storage.backup.uuid=$(blkid -s UUID -o value /dev/sdb1)
     uci set storage.backup.fstype=ext4
     uci set storage.backup.layout=single
     uci set storage.backup.enabled=1
     uci commit storage
     shareos-storage mount backup

4. Check:  ls /mnt/data /mnt/backup  – your folders are there. Under Storage
   both volumes now appear as mounted; they are mounted again at every start.

5. Under Shares create shares for your existing folders (volume "data", folder
   e.g. the name of your Alt-F share). The files are kept; the share only sets
   who may access them.

Notes: at the first mount ShareOS runs a quick file system check and enables
the ext4 quota feature (for storage limits per user) – your data is not
changed by that. The Alt-F swap partition (sda1) is simply not used.
A backup of important data before changing a system is always a good idea –
you already have one on the second disk.

[UniqueDroid]

Thanks for the question – and thanks @testeur70 for posting the steps!

Since 0.2.0-beta.17 (released yesterday) this works without SSH:

Don’t use the setup wizard for disks with data – it creates new volumes and erases the disks.
Update to beta.17: System → Firmware → Check now → install (or download the .sysupgrade.tar from the release).
Storage → Drives: every partition (or RAID array) with an existing file system now shows a “Take over sdXn” button. Click it, give the volume a name – it is mounted as it is, nothing is erased.
The first volume also becomes the apps area. An Alt-F RAID 1 is taken over as a mirror.
Under Shares, create shares for your existing folders. The files stay as they are; the share only sets who may access them.

On the first mount, ShareOS runs a quick file system check and enables the ext4 quota feature (for per-user storage limits). Your files are not changed. A swap partition from Alt-F is simply not used.

If you already followed the SSH steps above, there is nothing more to do – the volumes stay as they are after the update.

More on switching from Alt-F: docs/SWITCHING.md

Jan