Fileserver: Difference between revisions

From The Munich Maker Lab's Wiki
Jump to navigation Jump to search
(buffalo linkstation)
mNo edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
We are running a Fileserver at the space to store all kinds of stuff, as well as use it for generel data exchange (getting stuff to the laser, anyone?
We are running a Fileserver at the space to store all kinds of stuff, as well as use it for generel data exchange (getting stuff to the laser, anyone?)


== hawking ==
== MuMaShare ==
=== Access ===
* Synology NAS
'''IP: 10.10.20.61'''
* 1 x 2 TB WD Red, 1 x 2 TB WD Green - Raid 1
* 2 Bays spare for further extension
* Spare WD Green on-site
* IP 10.10.20.90


* There's a SMB (windows) share that should be writable to everyone. Try this \\10.10.20.61\share
'''Access via''' SMB, AFP, FTP, SFTP.


=== Hardware ===
Hosts a anonymous share for laser files at \\mumashare\userfiles and features private home-folders for members with accounts. '''Warning:''' There is absolutely no guarantee that your files will stay in there, even though we try to maintain this share on a best-effort basis. If it is unclear to which user files belong to, they might be deleted.
* 2 Intel(R) Xeon(R) 5130 Dual Core @ 2.00GHz
Guest login is "guest" with no password.
* 6GB RAM
Administrator login available via http://10.10.20.90:5000/
* 2x 150GB SATA Bootdrives built into case
* 8x 500GB SATA Drives in hotswappable bays
* 3ware 9550sxu-8lp RAID controller (for the 500GB drives, set in JBOD mode)


=== Setup ===
We are running OpenMediaVault 3 (Erasmus) on Debian Jessie.


==== Software ====
We wanted to run the two boot drives in a software RAID1 array, so we had to install a barebones Debian system and then install OMV ontop, because the OMV installer disks do not seem to support this.
* Install Debian 8 from scratch, setting up the RAID1 in the process.
* Reinstall the bootloader on both drives (setup will only install on one)
dpkg-reconfigure grub-pc
* Install OpenMediaVault Erasmus (only version compatible with Debian Jessie at the time of installation)
  echo "deb http://packages.openmediavault.org/public erasmus main" > /etc/apt/sources.list.d/openmediavault.list
  apt-get update
  apt-get install openmediavault-keyring postfix
  apt-get update
  apt-get install openmediavault
  omv-initsystem
* Reboot
* Log into webinterface (User: admin, PW: openmediavault)
* Change the password
* Install ZFS plugin for OMV following [http://forums.openmediavault.org/index.php/Thread/7633-HOWTO-Instal-ZFS-Plugin-use-ZFS-on-OMV/ this guide]
** The Plugin seems mature enough that you do not need to enable the ZFS testing repository, the normal one seems just fine
** The installation of the plugin itself however did not go through completely on the webinterface. I was required to restart and finish the installation from the commandline with
dpkg --configure -a
** So if you keep getting error messages in the WebUI after the installation, log onto the machine and run this until it produces no more output.
* Setup a ZFS pool: We just setup one pool with all 8 drives, as a RAIDZ2 (the disks are already a bit old). You can do it all on the WebUI, but it'll take time until the pool is initialized, and there's no status information, so just wait (took about 8 hours on our machine)
* Setup the Samba share
** Go to the SMB/CIFS configuration on the WebUI
** Enable the Samba service
** Make sure "Null passwords" are enabled
** Save
** Go to "shares" and add a new share
** Set permissions on the share to "Read/Write/Execute" for everyone (owner,group,others)
** Set Public to "Only guests"
** Activate "Browesable"
** Activate "Recycle bin" if you feel like it (we haven't)
** Save
** Activate configuration
=== Post Reboot ===
The ZFS pool does not get mounted automatically when the machine starts. This leads to a bit of confusion, as the share is still available, but empty. Here's how to fix it:
* Login as root via SSH
<pre>
umount /export /share
zfs mount internal
mount -a
</pre>
Then everything should be fine again.


== Buffalo NAS ==
== Buffalo NAS ==
This is now branded "hawking" - "hawking" used to be a own dedicated server but was moved to this buffalo NAS.
* Buffalo LinkStation Live (HS-DHGL), upgraded to a LinkStation Pro
* Buffalo LinkStation Live (HS-DHGL), upgraded to a LinkStation Pro
* 1.5 TB SATA HDD
* 1.5 TB SATA HDD (NO RAID!)
* IP: 10.10.20.60
* IP: 10.10.20.61
 


=== Fixing it ===
=== Fixing it ===
Line 86: Line 33:
=== Making it into a LinkStation Pro ===
=== Making it into a LinkStation Pro ===
The WebUI was super slow, but the internet says you can just "change" your LinkStation Live into a LinkStation Pro, since they share the same hardware. The Pro lacks a few of the media features, that the Live provides, but is thus much faster. We followed [http://www.nas-hilfe.de/buffalo-linkstation/software/76-wie-mache-ich-aus-einer-linkstation-live-eine-linkstation-pro?start=1 this guide]. Since we did this early on, we had the FW upgrade tool also reset settings and reformat the drive. The upgrade failed once for us, leaving the NAS in the embedded boot mode (without the WebUI). We just ran the upgrade again, and it was all good.
The WebUI was super slow, but the internet says you can just "change" your LinkStation Live into a LinkStation Pro, since they share the same hardware. The Pro lacks a few of the media features, that the Live provides, but is thus much faster. We followed [http://www.nas-hilfe.de/buffalo-linkstation/software/76-wie-mache-ich-aus-einer-linkstation-live-eine-linkstation-pro?start=1 this guide]. Since we did this early on, we had the FW upgrade tool also reset settings and reformat the drive. The upgrade failed once for us, leaving the NAS in the embedded boot mode (without the WebUI). We just ran the upgrade again, and it was all good.
== ToDo ==
* Sync hawking to buffalo


[[Category:Infrastructure]]
[[Category:Infrastructure]]

Latest revision as of 16:16, 10 March 2019

We are running a Fileserver at the space to store all kinds of stuff, as well as use it for generel data exchange (getting stuff to the laser, anyone?)

MuMaShare

  • Synology NAS
  • 1 x 2 TB WD Red, 1 x 2 TB WD Green - Raid 1
  • 2 Bays spare for further extension
  • Spare WD Green on-site
  • IP 10.10.20.90

Access via SMB, AFP, FTP, SFTP.

Hosts a anonymous share for laser files at \\mumashare\userfiles and features private home-folders for members with accounts. Warning: There is absolutely no guarantee that your files will stay in there, even though we try to maintain this share on a best-effort basis. If it is unclear to which user files belong to, they might be deleted. Guest login is "guest" with no password. Administrator login available via http://10.10.20.90:5000/


Buffalo NAS

This is now branded "hawking" - "hawking" used to be a own dedicated server but was moved to this buffalo NAS.

  • Buffalo LinkStation Live (HS-DHGL), upgraded to a LinkStation Pro
  • 1.5 TB SATA HDD (NO RAID!)
  • IP: 10.10.20.61


Fixing it

When we got the LinkStation, it didn't have a harddrive. Putting in a spare 1.5 TB HDD made it go into awkward error beeping mode. Even after a reset, the NAS did not reply to its default IP address. So we added a serial port (according to guide, but soldered an angled pin header into place, instead of the friction fit connector. A serial console with 115200 baud (8N1) shows the device booting but not finding any software and thus looking for an TFTP server on 192.168.11.1.

We downloaded a firmware upgrade for the LinkStation from Buffalo, and gave it its firmware files on the TFTP Server. The machine then booted (visible on the console) and replied to pings, but there was no web interface. Turns out, you still need to install the firmware. So we ran the firmware upgrade, and tada, it took almost forever but the machine then booted up and also opened its web interface (default credentials: admin/password). The Web UI was in japanese, which could be changed in the "Basics" configuration option (the second from the top in the left-hand-side menu), all the way on the bottom. Changing the language needs a reload of the UI (F5).

The process is also described in this guide.

Making it into a LinkStation Pro

The WebUI was super slow, but the internet says you can just "change" your LinkStation Live into a LinkStation Pro, since they share the same hardware. The Pro lacks a few of the media features, that the Live provides, but is thus much faster. We followed this guide. Since we did this early on, we had the FW upgrade tool also reset settings and reformat the drive. The upgrade failed once for us, leaving the NAS in the embedded boot mode (without the WebUI). We just ran the upgrade again, and it was all good.

Retrieved from "https://wiki.munichmakerlab.de/index.php?title=Fileserver&oldid=4014"