Can Minim Server Be Installed On Free Nas

Posted on
Thread Rating:
  • 3 Vote(s) - 4.33 Average
  1. 5) Enter the IP address of the FreeNAS box. This is why we want it to be static. Enter the name of the print queue (if you copied my printcap, it's 'lp' without quotes) 6) Install drivers and click through the rest of the wizard. Do not print test page. 7) Right click on the printer and open up properties.
  2. A FreeNAS server can do a lot more than only storing and sharing files over the network. If you have a decently-powered machine, you can take advantage of the free resources via virtual machines, instead of leaving them at idle. In this article, we will guide you through creating your own VM in FreeNAS. Basic Requirement.
  3. FreeNAS is a free and open source Network Attached Storage (NAS) software based on FreeBSD. While FreeNAS will install and boot on nearly any 64-bit x86 PC (or virtual machine), selecting the correct hardware is highly important to allowing FreeNAS to do what it does best: protect your data.

Installing and Upgrading¶. The FreeNAS ® operating system has to be installed on a separate device from the drives which hold the storage data. With only one disk drive, the FreeNAS ® web interface is available, but there is no place to store any data. And storing data is, after all, the whole point of a NAS system. Home users experimenting with FreeNAS ® can install FreeNAS ® on an. Ideally, FreeNAS should be installed on a small SSD or even a flash drive (though standard hard drives also work fine in a pinch), and the system should feature one or more reliable hard drives.

[Tutorial] Installing MinimServer on FreeNAS or FreeBSD
Post: #61
RE: [Tutorial] Installing MinimServer on FreeNAS or FreeBSD
In this section of code:
pid='$(cat '${MINIMPIDFILE}' 2>/dev/null)'
if [ -n '$pid' ]; then
cmdline='$(cat /proc/$pid/cmdline tr '0' ' ' 2>/dev/null)'
else
cmdline=
fi
if [ -z '$cmdline' ]; then
if [ -s '${OUTFILE}' ]; then
cat '${OUTFILE}' 1>&2
else
echo 'Failed to start Minim${WS}' 1>&2
fi
exit 1
fi

the startd script is looking for the minimserver.pid file to be non-null and checking whether /proc/$pid/cmdline is also non-null. If the minimserver.pid file is non-null and /proc/$pid/cmdline is null, the 'Failed to start' message will be produced.
Does /proc/$pid/cmdline work on BSD? If it doesn't, this would explain the error message.
The other possibility is that the minimserver.pid file is non-null and /proc/$pid/cmdline is null because of some startup sequencing/timing issue. If this is the case, adding a short delay into this check might solve the problem.
I can't check this myself because it is working for me on Linux.
Post: #62
RE: [Tutorial] Installing MinimServer on FreeNAS or FreeBSD
(11-02-2020 08:44)simoncn Wrote: In this section of code:
pid='$(cat '${MINIMPIDFILE}' 2>/dev/null)'
if [ -n '$pid' ]; then
cmdline='$(cat /proc/$pid/cmdline tr '0' ' ' 2>/dev/null)'
else
cmdline=
fi
if [ -z '$cmdline' ]; then
if [ -s '${OUTFILE}' ]; then
cat '${OUTFILE}' 1>&2
else
echo 'Failed to start Minim${WS}' 1>&2
fi
exit 1
fi

the startd script is looking for the minimserver.pid file to be non-null and checking whether /proc/$pid/cmdline is also non-null. If the minimserver.pid file is non-null and /proc/$pid/cmdline is null, the 'Failed to start' message will be produced.
Does /proc/$pid/cmdline work on BSD? If it doesn't, this would explain the error message.
The other possibility is that the minimserver.pid file is non-null and /proc/$pid/cmdline is null because of some startup sequencing/timing issue. If this is the case, adding a short delay into this check might solve the problem.
I can't check this myself because it is working for me on Linux.

There is no procfs mounted by default on FreeBSD. So I wouldn't count on it, although in my jail it is there as part of some dependency. Nor will this work on a mac. Why not check $(uname) and do something like
ps auxww grep minim grep mserver.jar awk {print $2}

for *BSD and Darwin?
Post: #63
RE: [Tutorial] Installing MinimServer on FreeNAS or FreeBSD
Thanks for confirming the cause of the problem.
This script is part of the Linux version of MinimServer. As I have said previously, the Linux scripts are not intended to support the Mac.
I cannot add BSD-dependent behaviour to these scripts because I have no way to test or support this.
Your suggestion can give a false positive by matching other MinimServer processes. It is necessary to check for a process that has the specific PID in the minimserver.pid file, perhaps using something like:
ps ww -p $pid
and then extracting the command line from the ps output.
I will not be pursuing this any further as the current code is working correctly on Linux
Post: #64
RE: [Tutorial] Installing MinimServer on FreeNAS or FreeBSD
Then just tell users to mount procfs. Add that to prerequisites in instructions. On FreeBSD,
$ mount -t procfs proc /proc

and/or add it to /etc/fstab if it is not there.
28-02-2020, 06:04 (This post was last modified: 28-02-2020 06:06 by imush.)
RE: [Tutorial] Installing MinimServer on FreeNAS or FreeBSD
Meanwhile I still have some trouble with my network. minimserver disappears from upnp queries after some time.
I obtained a tool to run ssdp queries and I see this for the minimserver:
HTTP/1.1 200 OK
SERVER: Posix/200112.0 UPnP/1.1 ohNet/1.0
CACHE-CONTROL: max-age=1800
EXT:
LOCATION: http://192.168.1.5:9791/9efa022f-bcd6-41ed-a223-01abcaf1f139/Upnp/device.xml
BOOTID.UPNP.ORG: 1
CONFIGID.UPNP.ORG: 1
ST: uuid:9efa022f-bcd6-41ed-a223-01abcaf1f139
USN: uuid:9efa022f-bcd6-41ed-a223-01abcaf1f139

So it expires after 30 minutes. Shouldn't ohnet send a new broadcast once in a while? Who sets the max-age=1800? My Oppo BDP-105 sits on the same network behind the same switch and it does not disappear. The player entry is as follows:
HTTP/1.1 200 OK
CACHE-CONTROL: max-age=1800
DATE: Fri, 28 Feb 2020 04:55:06 GMT
EXT:
LOCATION: http://192.168.1.15:2870/dmr.xml
SERVER: OPPO PLAYER UPnP/1.0 DLNADOC/1.50
ST: urn:schemas-upnp-org:service:AVTransport:1
USN: uuid:140479c0-58f3-1cef-84bf-0022de8b940b::urn:schemas-upnp-org:service:AVTransport:1
Post: #66
RE: [Tutorial] Installing MinimServer on FreeNAS or FreeBSD
MinimServer/ohNet does send an SSDP 'alive' notification before the 30 minutes elapses. This is probably being dropped by your router or switch for some reason. The SSDP message you have posted looks like an M-SEARCH response, not an 'alive' notification.
Please start another thread if you want to discuss how the UPnP protocol works and how to further investigate what might be happening with your network setup. It seems unlikely that this issue is related to whether MinimServer is runnng on Linux or FreeNAS.
22-06-2020, 09:46 (This post was last modified: 22-06-2020 09:50 by Hibiki.)
RE: [Tutorial] Installing MinimServer on FreeNAS or FreeBSD
Hi all,
I'm using FreeNAS 11.3-U3.1.
I created a Jail by following the tutorial provided by airflow (and improved for the automatic startup by imush).
For the dependencies, I use pkg install and it works perfectly.
I confirm I have the same error message when I type 'service minimserver start':
Starting minimserver.
Failed to start MinimServer

However it starts anyway
By typing 'service minimserver stop', it works perfectly.
I also confirm that out of the Jail, by doing iocage stop Minimserver (my Jail's name) and the iocage start Minimserver, it works well!
I notice something:
When I'm in /usr/local/share and I typed 'minimserver/bin/startc', I have no error message.
When I typed 'minimserver/bin/startd', I got the 'Failed to start MinimServer' but it started anyway.
So it confirms as Simoncn said that it is linked to startd script.
I didn't bring anything here.. Except that I confirm to have the same issue
And I would like to thank all for their effort on FreeNAS (FreeBSD) for making MinimServer alive!
I have a question about several instances of MinimServer (one for Classical, one for other genres and one for 'garbage / to be tagged'):
Do I have to follow a Linux thread on this topic?
Is there any restriction on FreeNAS (FreeBSD) to use the same Jail for having multiple MinimServer instances?
I will try to make it alive
27-06-2020, 15:08 (This post was last modified: 27-06-2020 15:10 by Hibiki.)
RE: [Tutorial] Installing MinimServer on FreeNAS or FreeBSD
So, I tried to make multiple instances within FreeNAS with the following access paths:
/usr/local/share/minimserver
/usr/local/share/minimserver-2/minimserver
/usr/local/share/minimserver-3/minimserver
I changed http.port and ohnet.port on every instances to never get the 2 same port numbers.
Is it really important for ohnet.port?
So basically, I have for the first instance:
http.port = 9790
ohnet.port = 9791

The second one:
http.port = 9792
ohnet.port = 9793

And the third one:
http.port = 9794
ohnet.port = 9795

All can be manually launched.
Then I tried to modify the script for the automatic launch at boot.
Just before, I sent the commands:
/usr/bin/sed -i -- 's/-eo pid,user,vsz,stat,args/-exo pid,user,vsz,stat,args/g' /usr/local/share/minimserver-2/minimserver/bin/stopall
/usr/bin/sed -i -- 's/-eo pid,user,vsz,stat,args/-exo pid,user,vsz,stat,args/g' /usr/local/share/minimserver-3/minimserver/bin/stopall

Then I modified the script /etc/rc.d/minimserver like this:
#!/bin/sh
#
# $FreeBSD: /usr/local/etc/rc.d/minimserver, 2020/02/03 05:55:56 isaac Exp $
#
# PROVIDE: minimserver
# KEYWORD: FreeBSD
#
# minimserver startup
#
. /etc/rc.subr
minimserver_enable=${minimserver_enable}
minimserver_flags=${minimserver_flags}
name=minimserver
rcvar=minimserver_enable
minimserver1_path=/usr/local/share/minimserver
minimserver2_path=/usr/local/share/minimserver-2/minimserver
minimserver3_path=/usr/local/share/minimserver-3/minimserver
start_cmd=minimserver_start
stop_cmd=minimserver_stop
minimserver_start() {
PATH=${PATH}:/usr/local/sbin:/usr/local/bin
export PATH
LANG=en_US.UTF-8
export LANG
LC_CTYPE=en_US.UTF-8
export LC_CTYPE
LC_ALL=en_US.UTF-8
export LC_ALL
checkyesno minimserver_enable && echo 'Starting minimserver.' &&
${minimserver1_path}/bin/startd ${minimserver_flags}
${minimserver2_path}/bin/startd ${minimserver_flags}
${minimserver3_path}/bin/startd ${minimserver_flags}
}
minimserver_stop() {
checkyesno minimserver_enable && echo 'Stopping minimserver.' &&
${minimserver1_path}/bin/stopall
${minimserver2_path}/bin/stopall
${minimserver3_path}/bin/stopall
}
load_rc_config ${name}
run_rc_command '$1'

And it doesn't really work.. Inside the Jail when I type : service minimserver stop the first time I got (while all instances were running):
[email protected]:/etc/rc.d # service minimserver stop
Stopping minimserver.
Stopping MinimServer process 20226
No MinimServer instances are running
No MinimServer instances are running

Only the first instance is stopped, the two others are running..
I tried a second time:
[email protected]:~ # service minimserver stop
Stopping minimserver.
No MinimServer instances are running
No MinimServer instances are running
No MinimServer instances are running

No change..
With:
[email protected]:/etc/rc.d # service minimserver start
Starting minimserver.
Failed to start MinimServer
Failed to start MinimServer
Failed to start MinimServer

Only the first instance is starting..
When I exit the Jail and I stop the Jail (iocage stop Minimserver).
I restart the Jail (iocage start Minimserver), it starts all MinimServer instances (?!)
Where am I wrong?
When I changed
checkyesno minimserver_enable && echo 'Starting minimserver.' &&
${minimserver1_path}/bin/startd ${minimserver_flags}
${minimserver2_path}/bin/startd ${minimserver_flags}
${minimserver3_path}/bin/startd ${minimserver_flags}

to
checkyesno minimserver_enable && echo 'Starting minimserver.' &&
${minimserver1_path}/bin/startd ${minimserver_flags} &&
${minimserver2_path}/bin/startd ${minimserver_flags} &&
${minimserver3_path}/bin/startd ${minimserver_flags}

Nothing started at all (I thought I missed the '&&' to split the same command on several lines).
May you help me, please?
Cheers
Post: #69
RE: [Tutorial] Installing MinimServer on FreeNAS or FreeBSD
(12-02-2020 15:25)imush Wrote: Then just tell users to mount procfs. Add that to prerequisites in instructions. On FreeBSD,
$ mount -t procfs proc /proc

and/or add it to /etc/fstab if it is not there.

Hi imush,
I tried this command and I got:
[email protected]:/etc # mount -t procfs proc /proc
mount: proc: Operation not permitted

File /etc/fstab is not existing also.. I do not know if it is linked..
Thanks for the help
Post: #70
RE: [Tutorial] Installing MinimServer on FreeNAS or FreeBSD
If it helps I am successfully running two instances of Minimserver on FreeNAS-11.3-U3.2 in a single jail and have configured startup in the jail as follows:
1. Create the file /etc/rc.d/minimserver with the following contents:
#!/bin/sh
PATH=${PATH}:/usr/local/sbin:/usr/local/bin
export PATH
LANG=en_US.UTF-8
export LANG
LC_CTYPE=en_US.UTF-8
export LC_CTYPE
LC_ALL=en_US.UTF-8
export LC_ALL
/usr/local/share/minimhome-audio/minimserver/bin/startd
/usr/local/share/minimhome-radio/minimserver/bin/startd
2. Make the file executable:
chmod +x /etc/rc.d/minimserver
3. Edit the file /etc/rc.conf and add the line:
minimserver_enable='YES'
« Next Oldest Next Newest »


User(s) browsing this thread: 1 Guest(s)
Contact Us MinimServer Home Return to Top Return to Content Lite (Archive) Mode RSS Syndication
1. What is FreeNAS?
FreeNAS is a Free and Open Source Network Attached Storage (NAS) software appliance. This means that you can use FreeNAS to share data over file-based sharing protocols, including CIFS for Windows users, NFS for Unix-like operating systems, and AFP for Mac OS X users. FreeNAS uses the ZFS file system to store, manage, and protect data. ZFS provides advanced features like snapshots to keep old versions of files, incremental remote backups to keep your data safe on another device without huge file transfers, and intelligent compression, which reduces the size of files so quickly and efficiently that it actually helps transfers happen faster.
2. Why would I use FreeNAS?
The benefit of using a NAS is that all your important files can be stored in a central location, allowing you to access them from multiple devices simultaneously, while also keeping your backup and redundancy resources in one place. FreeNAS lets you install programs for other purposes, such as bittorrent clients, media streaming servers, and cloud backup services, so it can fulfill many roles of a home server as well.
3. What do I need to get started with FreeNAS?

To use FreeNAS, you’ll need standard PC hardware with a 64-bit processor and at least 8GB of RAM. The FreeNAS® operating system is installed to at least one device that is separate from the storage disks. The Operating System Device can be an SSD, a small hard drive, or a USB stick. We recommend a minimum size of 8GB. A device with 16GB or more provides additional room for boot environments. Assassin`s creed odyssey uplay activation code free. Free online driver scanner and installer.

To get started with FreeNAS, write the installation file to the Install Media, typically a USB drive. Keep in mind there are two separate devices, the Operating System Device and the Install Media. One device contains the install media, while the other will contain the FreeNAS Operating System after installation. Be careful to select the correct device during installation. FreeNAS cannot be installed onto the same device that contains the installer. After installation, remove the Install Media Device. It might also be necessary to adjust the BIOS configuration to boot from the new FreeNAS operating system device. Once you start your FreeNAS system for the first time you should be provided with an IP address after boot. Point your web browser at the IP address of the FreeNAS system from any computer with a web browser on the network and you’re good to go! Read the FreeNAS Documentation for more information.

4. Is FreeNAS Safe and Secure?
FreeNAS is based on the highly secure FreeBSD operating system and follows security best practices in development. However, FreeNAS is not designed as security software and it depends on being protected from hostile traffic by a properly configured firewall. FreeNAS supports 256-bit encryption to prevent drives from being read if they’re physically removed from the system, but this doesn’t protect against data being read in transit over the network or via compromised user credentials. Like all software, FreeNAS depends on good security practices to keep data safe.
5. What else can I do with FreeNAS?
FreeNAS supports a number of third-party plugins, including Transmission for bittorrent, btsync to sync with a wide variety of devices without exposing your data to others, and OwnCloud to host your own cloud services server.
6. Can FreeNAS be used as a Media Server?
It sure can! FreeNAS includes support for a wide variety of third-party software plugins, including Plex Media Server. Plex Media Server allows FreeNAS to stream television shows, movies, and music to a wide variety of devices. If you’re concerned about system requirements, the FreeNAS Mini Storage Device from iXsystems has enough power to support 1080p HD video and still run normal FreeNAS operations.
7. Why does FreeNAS only support the ZFS filesystem?
Can Minim Server Be Installed On Free Nas
FreeNAS is designed around the OpenZFS filesystem, which enables many of the advanced features of FreeNAS such as data integrity, early indication of faulty drives, and the ability to boot into a previous working copy of the operating system after a failed upgrade. Other filesystems, including UFS, NTFS, FAT, EXT2 and EXT3 are supported “read only”, in order to allow data migration onto a ZFS volume.
8. How do I upgrade FreeNAS?
FreeNAS provides a built-in Update Manager, allowing the administrator to determine when to apply system patches and new features. When the system is updated, a copy of the current operating system is added to the boot menu, making it easy to revert to the previous version of the operating system should the update fail. Administrators can also track different versions of FreeNAS, in order to test new drivers and features, knowing that they can still return to the previous version of the operating system from the boot menu.
9. Where can I get help with FreeNAS?
There are many resources for FreeNAS troubleshooting, including the Community Forums and IRC channel. There is also extensive documentation here. However, if you require professional support, this is only available on the iXsystems TrueNAS storage arrays, which are built on the same codebase and have the same familiar UI as FreeNAS. Learn more about TrueNAS.
10. What if I don't want to build my own hardware for FreeNAS?
Many commercially available home servers work well as FreeNAS devices. If you want a device that’s designed specifically for FreeNAS, consider a FreeNAS Mini or FreeNAS Certified server from iXsystems, the developers of FreeNAS. If you want to use FreeNAS in a scenario that requires high availability or very high performance, consider a TrueNAS Unified Storage Appliance. For more information, visit iXsystems.com/storage.
11. Why is FreeNAS 64-bit only?
FreeNAS requires a 64-bit processor. This is because the memory requirements for FreeNAS are not supported by 32-bit PCs. Additionally, FreeNAS leverages modern technologies that will not function as intended under 32-bit. For the last version of FreeNAS that supports 32-bit, the official release can be downloaded at http://download.freenas.org/9.2.1.9/RELEASE/x86/. Please be aware that this version is no longer maintained and is unlikely to receive software or security updates.
12. What are the hardware requirements for FreeNAS?

Install Freenas On Ubuntu

The hardware requirements for FreeNAS depends very strongly on the how you’re planning to use it. Since this is such a complex topic, we’ve dedicated an entire page to the FreeNAS Hardware Requirements.
13. Can I downgrade from FreeNAS Corral to FreeNAS 9.10?

Install Freenas On Vmware

Yes, with some minor caveats.
If you initially upgraded from FreeNAS 9.10 to FreeNAS Corral, reboot the system, highlight “Boot Environment Menu” from the boot menu, and select the previous 9.10 installation from the boot menu. This will instruct the system to return to FreeNAS 9.10 and its configuration. You can then use System -> Boot to permanently set the FreeNAS 9.10 entry as the default.
Note that the initial upgrade to FreeNAS Corral migrated the 9.10 configuration into the FreeNAS Corral configuration format. The FreeNAS Corral configuration file format is different from a FreeNAS 9.10 configuration. This means that you should not attempt to restore a configuration that was saved on FreeNAS Corral while booted into FreeNAS 9.10.
If you upgraded your pool using FreeNAS Corral, you may receive an error when FreeNAS 9.10 tries to mount the pool. If you need assistance resolving any boot errors, please create a post on the FreeNAS Forums.