[Howto] Store data on the boot disk

And another alternative: install the LVM plugin, then proceed as in Method 4, but instead of

Zitat von "ppfdez"

Code

mdadm /dev/md100 --create --force --level=linear --raid-devices=1 /dev/sda3

one types

pvcreate /dev/sda3

Then you'll find a new physical volume in the Web GUI, out of which you can create a volume group, a logical volume, and finally a file system on it.

Stefan

I prefer Method 4 described above. However, I understand you're using mdadm which - if I'm correct - enables raid on the newly created partition (/dev/sda3). If I don't want to use raid, is there a way to use in sda3 in OMV, mount it, format it and use it as part of the NAS?
Many thanks in advance for your responses

Unfortunately my account got mistakenly deleted together with all my posts hence I'm re-posting it again for reference. It's a copy from old forum: https://sourceforge.net/apps/p…&hilit=store+data+on+disk
Al credits to the original author, marknewfsd

Zitat

OpenMediaVault is a wonderful NAS solution if you want to build your own system. Is is derived from FreeNAS but uses GNU/Linux instead of FreeBSD. I am really happy with it, but one thing kept bugging me: For some reason, the developers decided that the main file system containing the OS and configuration can not be used for storage.

As I am using an old laptop for my NAS system (which is both cost-efficient and eco-friendly), I do not want to sacrifice my whole 320GB harddisk just for configuration files. I have found a way to work around this limitation in a robust fashion.

I've found 3 ways to do this. (I suggest you to read all the methods and then decide which one is the best for you (Step 3 is the most easiest way).

Method 1
Create a file that will act as the container of all your files. There is only one downside of this; you aren't able to change the size of this container later on.
More information

Method 2
Instead of a file you can use a partition on the disk.

• You must boot from the live cd and reduce the size of partition where you installed OpenMediaVault.
• Create another unallocated partition and then follow the instructions.
• Continue Method 1, but skip the creation of the file.
• Replace “losetup /dev/loop1 /virtualdisk” to “losetup /dev/loop1 /dev/sda3″ (where sda3 is your new partition).
• In lodev script replace “losetup /dev/loop1 /virtualdisk” to “losetup /dev/loop1 /dev/sda3″

Copyright IlgizKs comment on the website of Method 1

Method 3
Volker suggested that I should be able to do this http://by using mount bind.

• Attach an USB stick to your system, mount it.
• Open CLI (Command Line Interface) and write these commands:
  
  
  Code

  cd /
  mkdir /omv/
  cd /media/
  ls

  
  

• Then look which disk is your usb stick.
  
  
  Code

  mount --bind /omv/ /media/usb_stick_name/

  
  (replace usb_stick_name with the name you see with the ls command)

  
  

• Code

  cd ../
  cd usb_stick_name

  
  

• Now create a file by using your favorite file editor. I'll use nano for this;
  
  
  Code

  nano test.txt

  
  Write something in the document, save it and exit the editor.

  
  

• Check if the file you created is really there:
  
  
  Code

  cd /omv/
  ls

  
  

• Create a shared folder on this location (by using the Web UI)
  

  
  

• Now remove your USB Flashdrive
  

  
  

• Check if the share and the folder /media/usb_stick_name are still there.
  Now we've created a solution to store files. All files which are being stored in /media/usb_stick_name will actually be stored in /omv/ (a folder on the first harddisk).
  There is one problem left, this mount command is gone after a reboot. This can be solved by creating a script that will automaticly mount the folder during the boot of the system.
  

  
  

• Code

  nano /etc/init.d/mountfirstdisk

  
  Write this inside the file:

  Code

  ! /bin/sh
  # /etc/init.d/mountfirstdisk
  #
  
  
  ### BEGIN INIT INFO
  # Provides:          mountfirstdisk
  # Required-Start:    $all
  # Required-Stop:     $all
  # Should-Start:
  # Should-Stop:
  # Default-Start:     2 3 4 5
  # Default-Stop:      0 1 6
  # Short-Description: Mounts first disk as storage disk
  ### END INIT INFO
  
  
  
  
  # Carry out specific functions when asked to by the system
  case "$1" in
    start)
      #echo "Starting script blah "
      #echo "Could do more here"
          mount --bind /omv/ /media/8040-309A/
      ;;
    stop)
     #echo "Stopping script blah"
      #echo "Could do more here"
      ;;
    *)
      echo "Usage: /etc/init.d/mountfirstdisk {start|stop}"
      exit 1
      ;;
  esac
  
  
  exit 0

  Alles anzeigen

  
  Save the file and exit the editor.
  

  Code

  update-rc.d mountfirstdisk defaults

  
  

• Now reboot your system to check if everything works. Now simply create a share on the 'fake' usb stick.

I've tried Method 3 out and it works wonderfull. However, I've done and written these steps, but I didn't test them afterwards (by using this guide), so in case something isn't working, please tell me. (Sorry for the buggy layout of each step, this is the fault of the forum system here)

Warning: be sure to test each method first in VirtualBox before applying them into a production system. You don't want to break anything.

Zitat von "ppfdez"

I need more information. CLI commands, df, mounts, gui screens ...........

Thanks for your willingness to look into this
I posted all configuration data at separate thread http://forums.openmediavault.org/viewtopic.php?f=11&t=334 to avoid morphing this one.

I tried to rebuild the array manually as described http://forums.openmediavault.o…p?f=11&t=334&p=1139#p1103
I get clean array on /dev/md0 but after reboot it switched to /dev/md127... described on next post http://forums.openmediavault.o…p?f=11&t=334&p=1139#p1139

Is it due to this missing "mdadm /dev/md100 --create --force --level=linear --raid-devices=1 /dev/sda3" step?

Can anybody experienced comment on this, please?

I know this is an old thread, I'm kinda hoping that someone can help me out. I used method #3 listed above today. It works good, stuff added/removed from the USB shows as being on the HDD and my free space available is listed as what is remaining on the boot disk.

My question is, do I have to keep the USB key connected to the server or can I unmount and remove it? If I have to keep it mounted that's fine, I'll just swap out the one I used with a smaller one I never touch. If I can remove it would just unmounting it be good enough or do I have to update the init.d script to do so?