Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
omv6_new_user_guide [2022/07/02 12:34] – crashtest | omv6_new_user_guide [2022/07/31 17:13] (current) – removed crashtest | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | < | ||
- | |||
- | {{ : | ||
- | |||
- | \\ | ||
- | |||
- | ====== Getting Started with Openmediavault 6 ====== | ||
- | \\ | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | \\ | ||
- | Version History: \\ | ||
- | January 22nd, 2021 - Rev 0.1 (First Draft)\\ | ||
- | January 24th, 2021 - Rev 0.2 Added Note boxes\\ | ||
- | January 29th, 2021 - Rev 0.3 Fixed drafting errors in "A Basic Data Drive" | ||
- | |||
- | {{ : | ||
- | |||
- | This document can be converted to a PDF file, in the user's language of choice (see the following), on Windows, Mac's and popular Linux desktop platforms. Select the printer icon on the upper right corner of this web page. When prompted at the client, select “print to PDF”, name and save the file. | ||
- | \\ | ||
- | * [[https:// | ||
- | * [[https:// | ||
- | * [[https:// | ||
- | * [[https:// | ||
- | {{ : | ||
- | \\ | ||
- | ===== Introduction to Openmediavault ===== | ||
- | |||
- | |||
- | Openmediavault is a File Server / NAS system designed to work on most modern IBM compatible PC systems, to include typical amd64 or i386 PC’s and select ARM devices. Openmediavault can be thought of as filling a role similar to Microsoft' | ||
- | |||
- | In meeting the needs of it's intended users, individuals and small-to-medium-sized businesses, Openmediavault is designed for flexibility. | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | ==== History ==== | ||
- | |||
- | Openmediavault' | ||
- | \\ | ||
- | \\ | ||
- | ==== Purpose ==== | ||
- | |||
- | The purpose of openmediavault | ||
- | |||
- | One of the ambitions of the openmediavault project is to make advanced NAS technologies and features available to inexperienced users in an easy to use WEB GUI, thereby making it possible for people, without extensive knowledge of Linux, to gain easy access to advanced technologies. | ||
- | \\ | ||
- | \\ | ||
- | ==== Getting Involved ==== | ||
- | |||
- | If businesses and home users find openmediavault to be beneficial, please consider supporting the project with a modest donation. | ||
- | |||
- | [[https:// | ||
- | [[https:// | ||
- | |||
- | {{ : | ||
- | |||
- | ===== About this Guide ===== | ||
- | |||
- | In computing, generally speaking, there are several ways to do the same thing. | ||
- | extension, | ||
- | skill level increases. | ||
- | not be considered as “Best Practice”, | ||
- | perspective. | ||
- | to get users up and running as quickly and easily as possible. | ||
- | * This guide contains links to external sources of information and software. | ||
- | * This is a community document and a work in progress. | ||
- | |||
- | {{ : | ||
- | |||
- | ==== Beginners: ==== | ||
- | |||
- | This document is intended for beginners who will, primarily, be using the openmediavault' | ||
- | computers and their LAN systems, and a Windows or Apple PC. | ||
- | The focus of this guide will be to take a technically easy route, for the widest possible cross section of new users, toward accomplishing | ||
- | basic tasks using methods and processes that are easy to understand and duplicate. | ||
- | |||
- | ==== Advanced Users: ==== | ||
- | |||
- | Openmediavault was designed to be intuitive for advanced users and beginners alike. | ||
- | After the installation is complete, for a streamlined setup, see | ||
- | the → [[https:// | ||
- | \\ | ||
- | \\ | ||
- | === A Cautionary Note for Advanced Users: === | ||
- | |||
- | Many of the configuration files traditionally used to customize Debian Linux are controlled by the openmediavault system database. | ||
- | In the beginning it's best to rely, primarily, on the GUI for configuration and control. | ||
- | backing up the boot drive is highly recommended. | ||
- | \\ | ||
- | \\ | ||
- | ==== Linux Experts, Admin' | ||
- | |||
- | Users in this category may prefer the information available on | ||
- | the [[https:// | ||
- | |||
- | {{ : | ||
- | |||
- | ===== Hardware ===== | ||
- | |||
- | Hardware requirements to run openmediavault are very modest, however, actual hardware requirements for specific “use cases” vary widely. | ||
- | The following is intended only as general guidance. | ||
- | \\ | ||
- | |||
- | ==== Compatibility: | ||
- | |||
- | Openmediavault 6.X is currently supported by Debian 11, “Bullseye”. | ||
- | Compatible hardware and other requirements of Debian Linux are available | ||
- | at [[https:// | ||
- | \\ | ||
- | \\ | ||
- | ==== 64 bit hardware (amd64): ==== | ||
- | |||
- | The openmediavault project maintains convenient, fully integrated, openmediavault/ | ||
- | for getting openmediavault up and running quickly. | ||
- | \\ | ||
- | \\ | ||
- | |||
- | ==== 32 bit Hardware (i386): ==== | ||
- | |||
- | While openmediavault is supported by 32 bit Debian installations, | ||
- | process referenced in; | ||
- | [[https:// | ||
- | The openmediavault project does not provide integrated 32 bit installation ISO's. | ||
- | \\ | ||
- | |||
- | |||
- | ==== ARM Hardware: ==== | ||
- | |||
- | The openmediavault project provides scripted installation support for ARM Single Board Computer (SBC) platforms. | ||
- | models 2B and higher, and the various ARM platforms supported by the [[https:// | ||
- | \\ | ||
- | \\ | ||
- | ==== Minimum Hardware requirements ==== | ||
- | |||
- | Openmediavault/ | ||
- | \\ | ||
- | \\ | ||
- | |||
- | ==== Recommended Minimum requirements ==== | ||
- | |||
- | For basic File Server operations - 1 or 2 users:\\ | ||
- | * Intel Core 2 Duo or equivalent AMD processor and 1GB of RAM. | ||
- | * Any of the ARM Single Board Computers supported by openmediavault. | ||
- | If flash media is used, (USB thumb-drives, | ||
- | \\ | ||
- | \\ | ||
- | |||
- | ==== Recommended Hardware and Considerations for a good use experience ==== | ||
- | |||
- | === amd64 === | ||
- | \\ | ||
- | * Intel i3 (or equivalent AMD processor), 4GB ram or better (ECC preferred) and a 16GB system boot drive will provide good performance in home or small business use cases. | ||
- | * As the number of NAS users increase and server processes are added, processing power and memory requirements increase. | ||
- | * For file caching, in support of normal file system operations, performance is better with more RAM. | ||
- | * The number of a Motherboard' | ||
- | * A case design that accommodates the physical installation of additional hard drives can be helpful. | ||
- | * Integrated video is preferred over add-on Video cards. | ||
- | \\ | ||
- | \\ | ||
- | === ARM - Single Board Computers: === | ||
- | |||
- | Performance levels vary greatly among the various models of **Single Board Computer** | ||
- | (hereafter referred to as an “**SBC**”) that are supported by Armbian, Raspbian, and | ||
- | openmediavault. | ||
- | running server add-on' | ||
- | before buying. | ||
- | or [[https:// | ||
- | along with Internet product reviews.\\ | ||
- | \\ | ||
- | When considering an SBC as a primary NAS server for home use, note that support for SBC's is | ||
- | **for the current openmediavault release only**. | ||
- | ending cautionary note in | ||
- | [[https:// | ||
- | \\ | ||
- | \\ | ||
- | == Raspberry PI's == | ||
- | |||
- | (Hereafter referred to as “R-PI' | ||
- | Given the current market for SBC's, the majority of SBC users will likely be owners of R-PI' | ||
- | \\ | ||
- | Openmediavault runs well on the R-PI 4. While openmediavault will run on an R-PI model 2B | ||
- | and the various models of the R-PI 3, it is not recommended. | ||
- | exactly does “poor performance” mean? In this context, if the R-PI's CPU is running at 100%, | ||
- | openmediavault my not show up on the local network and / or network shares may not open. | ||
- | This may give the false impression that there' | ||
- | instances, the WEB GUI login page may not respond.\\ | ||
- | \\ | ||
- | These issues may appear to be software related, but that's not always the case. Older R-PI' | ||
- | are very easily over stressed and, during periods where the CPU is running at 100%, they may | ||
- | not respond to external input. | ||
- | the R-PI (2B and 3X models) should be used only as a basic file server for 1 or 2 user home | ||
- | environments, | ||
- | schedule them to run in the early morning hours when user access would not be affected.\\ | ||
- | \\ | ||
- | In addition, R-PI's suffer from USB under powering in models 2B and 3X. See notes regarding | ||
- | this issue in | ||
- | [[https:// | ||
- | \\ | ||
- | \\ | ||
- | ==== Where CPU Power may be Needed – “Transcoding” ==== | ||
- | |||
- | If a user's primary consideration is setting a up a media server, CPU selection may need | ||
- | careful consideration.\\ | ||
- | \\ | ||
- | Transcoding is a process for translating media file formats into types that mobile devices | ||
- | understand. | ||
- | resolution media files smoothly so the processing burden is often transferred to the media | ||
- | server.\\ | ||
- | \\ | ||
- | \\ | ||
- | === Pre-2011 Intel and AMD CPU's === | ||
- | |||
- | Plex, a popular media server, recommends at least 2000 on the CPU's [[https:// | ||
- | concurrent 1080p transcoded stream. ([[https:// | ||
- | However note that this advice applies to __pre-2011__ Intel and AMD CPU' | ||
- | Look up an older CPU here → [[https:// | ||
- | {{ : | ||
- | |||
- | === 2011 and Newer Intel CPU's === | ||
- | |||
- | As of the beginning of the Sandy Bridge CPU series in 2011 and later, a core has been added | ||
- | to **Intel** CPU's for the sole purpose of video transcoding. | ||
- | [[https:// | ||
- | Atom models that are relatively low powered, do a good job of transcoding for portable devices.\\ | ||
- | \\ | ||
- | If NAS administrators have numerous smart phone users, in their homes or businesses, who will | ||
- | be watching transcoded video on the small screen, CPU loading and Video processing features | ||
- | may require some additional thought and research.\\ | ||
- | \\ | ||
- | Additional reading → [[https:// | ||
- | \\ | ||
- | \\ | ||
- | ==== Selecting a Boot Drive ==== | ||
- | |||
- | Nearly any type of hard drive, SSD, or flash device (USB thumb-drives and SD-cards) 8GB or | ||
- | larger, will function as an openmediavault boot drive. | ||
- | However, some notions of achieving a “Faster” or a “Better Performing NAS server” by using | ||
- | certain types of fast boot media should be dispelled. | ||
- | Server boot requirements and considerations are different when compared to desktop and | ||
- | business workstation requirements.\\ | ||
- | \\ | ||
- | * Given openmediavault' | ||
- | * Typically servers are rebooted no more than once a week. When automated, a reboot event is usually scheduled after-hours when users are not affected. | ||
- | * After the boot process is complete, most of openmediavault' | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | * “The WEB/GUI is more responsive with fast media.”\\ | ||
- | \\ | ||
- | This is the single instance where an SSD or a spinning hard drive may create the illusion of higher performance. | ||
- | \\ | ||
- | Navigating openmediavault' | ||
- | * **The above assumes that adequate RAM has been provisioned.** * \\ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | === Final Notes on Choosing a Boot Drive === | ||
- | |||
- | Openmediavault' | ||
- | While some users prefer traditional hard drives or SSD's, the boot requirement can be served with USB thumb-drives and SD-cards, 8GB or larger.\\ | ||
- | \\ | ||
- | With USB connections on the //outside// of a PC case, cloning | ||
- | USB drives for operating system backup ((Redirect to OMV6 maintenance when it exists.)) is | ||
- | an easy process. | ||
- | external flash media to internal drives. | ||
- | recovery in the event of a boot drive failure, beginners are encouraged to consider using | ||
- | flash media.\\ | ||
- | \\ | ||
- | **If flash media is used:** \\ | ||
- | __**New**__ name brand drives are recommended such as Samsung, SanDisk, etc. While not | ||
- | absolutely essential; **USB3** thumb-drives are preferred, due to their more advanced | ||
- | controllers, | ||
- | **USB3** thumb-drives and **A1** spec' | ||
- | \\ | ||
- | While boot drive size matters, bigger is not always better. | ||
- | \\ | ||
- | “**Wear leveling**” will be explained during the installation and configuration of the | ||
- | flash-memory plugin. Note that the flash-memory plugi* is **required** to boot from **flash media**. | ||
- | It's purpose and installation are detailed in [[https:// | ||
- | \\ | ||
- | Use-case exceptions where boot media larger than 32GB may be useful: | ||
- | \\ | ||
- | * Running applications that utilize WEB interfaces, such as Plex, Emby, etc. | ||
- | * Hosting Web or Media Servers with extensive content. | ||
- | * Hosting Virtualized Guest operating systems with desktops. | ||
- | \\ | ||
- | There' | ||
- | \\ | ||
- | < | ||
- | < | ||
- | <table width=" | ||
- | <tr> | ||
- | <td colspan=" | ||
- | < | ||
- | </td> | ||
- | </tr> | ||
- | <tr> | ||
- | <td style=" | ||
- | Buying flash devices on-line, even from reputable retailers, comes with the substantial risk of buying fakes. | ||
- | In addition, to detect fakes or defective media even when new; all SD-cards and USB thumb-drives should be formatted and tested in accordance with the process outlined under Format and Testing Flash Media. | ||
- | </tr> | ||
- | </ | ||
- | </ | ||
- | </ | ||
- | ==== Hardware - The Bottom Line ==== | ||
- | |||
- | Again, openmediavault/ | ||
- | compatible PC or Laptop produced in the last 10 years could be re-purposed as an | ||
- | openmediavault server.\\ | ||
- | However, it should be noted that newer hardware is, generally speaking, more power | ||
- | efficient and it's higher performing. | ||
- | that is on-line, 24 hours a day, can easily pay for newer more power efficient | ||
- | equipment over time.\\ | ||
- | Further, the supported ARM platforms are both power efficient and capable of | ||
- | providing file server functions in a home environment. | ||
- | expectations should be adjusted in accordance with the capabilities of the hardware.)\\ | ||
- | |||
- | {{ : | ||
- | |||
- | ===== Installing OMV on Single Board Computers (SBC' | ||
- | Installation guides for SBC installations are available → [[https:// | ||
- | |||
- | {{ : | ||
- | |||
- | ===== Installing OMV on i386 32-bit Platforms ===== | ||
- | |||
- | An installation guide for 32-bit installations is available → [[https:// | ||
- | |||
- | {{ : | ||
- | |||
- | ===== amd64 (64-bit) Platforms ===== | ||
- | |||
- | This guide assumes the user will be installing from a CD, burned from an image found | ||
- | in [[https:// | ||
- | using 64 bit hardware. | ||
- | software source, is provided below. | ||
- | \\ | ||
- | \\ | ||
- | ==== Downloading ==== | ||
- | |||
- | Beginners should download the latest __stable__ version from | ||
- | [[https:// | ||
- | copy or download the SHA or MD5 checksums for the ISO. The checksum value will | ||
- | be used with the MD5 SHA checksum utility. | ||
- | selecting “**All Files**”, next to the file name drop down.) \\ | ||
- | \\ | ||
- | < | ||
- | < | ||
- | <table width=" | ||
- | <tr> | ||
- | <td colspan=" | ||
- | < | ||
- | </td> | ||
- | </tr> | ||
- | <tr> | ||
- | <td style=" | ||
- | If users install Beta or Release Candidate versions of openmediavault, | ||
- | a “< | ||
- | not be resolved, which may result in lost data. Plan accordingly, | ||
- | backup</ | ||
- | </tr> | ||
- | </ | ||
- | </ | ||
- | </ | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | === Verify the download === | ||
- | |||
- | After the download is complete, verify the download with a [[https:// | ||
- | MD5 and SHA hashes check for image corruption that may have occurred during the download. | ||
- | \\ | ||
- | < | ||
- | < | ||
- | <table width=" | ||
- | <tr> | ||
- | <td colspan=" | ||
- | < | ||
- | </td> | ||
- | </tr> | ||
- | <tr> | ||
- | <td style=" | ||
- | < | ||
- | downloading and it's pointless to build a server with flawed software. | ||
- | < | ||
- | be noticed until well after your server is built and in use. Headaches can be avoided by checking the image. | ||
- | </tr> | ||
- | </ | ||
- | </ | ||
- | </ | ||
- | \\ | ||
- | \\ | ||
- | ==== Installing - amd64 Platforms ==== | ||
- | |||
- | === Burning a source CD === | ||
- | |||
- | Assuming a CD/DVD drive is installed; in most cases, double clicking an installation file, with an “.ISO” extension, will | ||
- | trigger a CD burning utility on a Windows Computer or a MAC. If help is needed for | ||
- | this process, see the following link.\\ | ||
- | [[https:// | ||
- | \\ | ||
- | |||
- | === Creating a Bootable ISO Thumb-drive === | ||
- | |||
- | For PC's without an Optical drive; the openmediavault ISO can be installed using a | ||
- | Thumbdrive as the ISO source, and install the Debian/ | ||
- | For assistance in creating a bootable ISO thumb-drive, | ||
- | [[https:// | ||
- | \\ | ||
- | *Before creating an ISO thumb-drive, | ||
- | utilities and process described below in, [[https:// | ||
- | \\ | ||
- | \\ | ||
- | \\ | ||
- | ** If installing to a standard hard drive or SSD, skip | ||
- | to → [[https:// | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | === Preparing Flash Media === | ||
- | |||
- | To use flash media as a boot drive, a couple utilities are recommended: | ||
- | [[https:// | ||
- | [[https:// | ||
- | * [[https:// | ||
- | * [[https:// | ||
- | Simply unzip h2testw_1.4 onto the desktop, open the folder, and double click the | ||
- | executable.\\ | ||
- | \\ | ||
- | Due to the rise in counterfeit media and media that reports a fake size, it' | ||
- | recommended that all USB thumb-drives and SD-cards, new or used, be formatted with | ||
- | **SDFormatter** and tested with **h2testw1.4** | ||
- | \\ | ||
- | ---- | ||
- | |||
- | == Format and Test Flash Media == | ||
- | |||
- | Using SDFormatter, | ||
- | (While SDFormatter was designed for SD-cards, it can format USB thumb-drives for | ||
- | error testing. SDFormatter will detect a USB thumb-drive.)\\ | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | {{ :: | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ :: | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | {{ :: | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | {{ :: | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ :: | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ :: | ||
- | \\ | ||
- | \\ | ||
- | After H2testw verifies the USB thumb-drive, | ||
- | |||
- | {{ : | ||
- | |||
- | ==== amd64 – Openmediavault Installation ==== | ||
- | \\ | ||
- | If your PC platform won't boot onto a CD or USB thumb-drive with the installation | ||
- | ISO, it may be necessary to change the boot order in BIOS, to set the CD/DVD drive | ||
- | or USB boot to the top of the boot order. | ||
- | this topic. → [[https:// | ||
- | \\ | ||
- | If difficulties are encountered during the ISO installation, | ||
- | [[https:// | ||
- | |||
- | {{ :: | ||
- | \\ | ||
- | An installation walk-through: | ||
- | If offered a choice, chose the text install. \\ | ||
- | \\ | ||
- | < | ||
- | |||
- | {{ : | ||
- | \\ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | < | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | |||
- | ---- | ||
- | |||
- | \\ | ||
- | < | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | |||
- | ---- | ||
- | |||
- | |||
- | \\ | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | < | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | < | ||
- | < | ||
- | < | ||
- | \\ | ||
- | * If installing to a USB drive, at this point, it is possible to an error may | ||
- | pop-up regarding partitioning the drive, and recommend a reboot. | ||
- | recommendation. | ||
- | time around. *\\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | The system installs..........\\ | ||
- | \\ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | < | ||
- | < | ||
- | < | ||
- | \\ | ||
- | While the advice given in this screen is true, without testing, there' | ||
- | to know which Debian archive mirror is best. Without testing, picking your | ||
- | country or the closest location to your country would be the logical choice. | ||
- | \\ | ||
- | |||
- | ---- | ||
- | |||
- | \\ | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | \\ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | < | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | |||
- | ---- | ||
- | < | ||
- | \\ | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | ==== First Boot ==== | ||
- | \\ | ||
- | Allow the installation to boot. Normally, the text above the login prompt will | ||
- | provide an IP address to be used for opening the console in a web browser. \\ | ||
- | \\ | ||
- | **If an IP address is available**, | ||
- | to → [[https:// | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | **1.) No address from the DHCP server:** \\ | ||
- | Normally, DHCP will assign an IP address to openmediavault and the address will be | ||
- | printed to the screen. | ||
- | observed. | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | This is usually due to a slow response from your DHCP server, during a fast boot | ||
- | process.\\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | An easy method of finding the IP address is: \\ | ||
- | At the login prompt type '' | ||
- | Enter your previously set root **password**. \\ | ||
- | At the # prompt type: '' | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | To access the WEB control panel, the IP address for the wired Ethernet interface | ||
- | is needed. | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | **2. A random IP address is assigned, that is __not__ in the user's network:** \\ | ||
- | In the following example, the actual network is 192.168.**1**.0/ | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | This is usually a one time event where the fix is simple – simply login as | ||
- | **root** and type '' | ||
- | second time around.\\ | ||
- | \\ | ||
- | On very rare occasions, depending on the model and type of router, it may | ||
- | be necessary to reboot the router AND follow that with a reboot of the OMV server.\\ | ||
- | \\ | ||
- | **With a known IP address**, proceed to [[https:// | ||
- | |||
- | |||
- | {{ : | ||
- | |||
- | ===== Initial Configuration ===== | ||
- | \\ | ||
- | ==== Web console login ==== | ||
- | \\ | ||
- | In a web browser' | ||
- | Set the language of your choice. \\ | ||
- | The user name is '' | ||
- | \\ | ||
- | (In the following, by clicking on the **eye icon** , the default password would | ||
- | be shown unmasked.) \\ | ||
- | |||
- | {{ : | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | After the first successful logon, the following prompt is displayed: \\ | ||
- | \\ | ||
- | < | ||
- | {{ : | ||
- | \\ | ||
- | < | ||
- | |||
- | {{ : | ||
- | |||
- | ===== Quick Start Guide for Advanced Users: ===== | ||
- | |||
- | |||
- | * In the left hand column, start at the top with System, and work your way down, | ||
- | choosing and activating the services and features needed for your use case. | ||
- | * For amd64 and i386 users, a static address for the openmediavault server and setting the address of a [[https:// | ||
- | (*SBC users, see the section, | ||
- | [[https:// | ||
- | As an example: | ||
- | security, and ANYCAST which will direct DNS queries to a nearby server with low | ||
- | network latency. | ||
- | features. [[https:// | ||
- | * For a browseable network share, a minimum of one shared folder would need to be configured and that folder would need to be added to SMB/CIF to be visible on the network. | ||
- | |||
- | {{ : | ||
- | |||
- | {{ : | ||
- | |||
- | ===== Basic Openmediavault Configuration ===== | ||
- | \\ | ||
- | This section will guide new users through the initial setup of openmediavault. | ||
- | addresses how to add a plugin, enabling OMV-Extras, how to setup a shared folder | ||
- | and make it browseable on the network with an SMB/CIF share. | ||
- | \\ | ||
- | \\ | ||
- | |||
- | ==== Change Password ==== | ||
- | \\ | ||
- | < | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | < | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | ==== System Settings ==== | ||
- | \\ | ||
- | Under **System**, **Workbench**: | ||
- | \\ | ||
- | < | ||
- | |||
- | {{ : | ||
- | \\ | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | < | ||
- | (The arrow is “< | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | < | ||
- | |||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | === Server Notifications === | ||
- | Under **System**, **Notification**, | ||
- | \\ | ||
- | If enabled, E-mail setting entries are required if users want to take advantage of | ||
- | automated server notifications and reports. | ||
- | and scripts, in **Scheduled Jobs** for example, can use this information to E-mail a | ||
- | report of task execution or status, as users may deem necessary.\\ | ||
- | \\ | ||
- | To gather the required information for entry in the **Settings** window, users should | ||
- | refer to the SMTP settings for their E-mail clients. | ||
- | **SSL/TLS** secured E-mail connections.\\ | ||
- | \\ | ||
- | < | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | Under **System**, **Notification**, | ||
- | \\ | ||
- | Select various functions for error reporting.\\ | ||
- | \\ | ||
- | If using a minimalist platform, such as older hardware or SBC' | ||
- | system resources, memory, etc., may become bothersome. | ||
- | resources would eliminate excess E-mails, while maintaining **Storage reports** on hard | ||
- | drive health and file system errors.\\ | ||
- | {{ : | ||
- | \\ | ||
- | < | ||
- | < | ||
- | <table width=" | ||
- | <tr> | ||
- | <td colspan=" | ||
- | < | ||
- | </td> | ||
- | </tr> | ||
- | <tr> | ||
- | <td style=" | ||
- | Using < | ||
- | monitoring of hard drives is < | ||
- | self-tests are enabled on spinning drives in the < | ||
- | may notify the user of hard drive errors < | ||
- | </tr> | ||
- | </ | ||
- | </ | ||
- | </ | ||
- | \\ | ||
- | \\ | ||
- | For an explanation of drive self-tests and an example of how to set up a drive self-test, see the section; | ||
- | [[https:// | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | Under, **Network**, | ||
- | \\ | ||
- | **Hostname: | ||
- | The hostname is the name that will appear on your network and on the command line. While the default is fine, if desired, the hostname can be changed here. \\ | ||
- | \\ | ||
- | **Domain name:** \\ | ||
- | The default is fine. If needed, the Domain suffix can be changed here. (Very few users will use Fully Qualified Domain Names.) | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | === Network Interfaces – SBC Users === | ||
- | |||
- | Part of the SBC installation process was setting the wired interface to DHCP. SBC | ||
- | users should consider leaving their wired network interface set to DHCP, until Docker ((Redirect to OMV6 maintenance when it exists.)) | ||
- | and Portainer ((Redirect to OMV6 maintenance when it exists.)) are installed.\\ | ||
- | |||
- | If a static IP address is needed: \\ | ||
- | Note that your SBC has been assigned an IP address by your LAN's DHCP server. | ||
- | (Typically, a router.) See your router' | ||
- | “Static”, | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | === Network Interfaces – i386/amd64 Users === | ||
- | |||
- | Under, **System**, **Network**, | ||
- | |||
- | Highlight / click on the **interface** line found under the **Device** column, and ] | ||
- | click the **Edit** button. | ||
- | \\ | ||
- | (The interface name may not be the traditional Linux eth0. A variety of different | ||
- | names may be found, such as **eno1** or others.) \\ | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | * The following is an example only. If users are unsure of the entries needed for | ||
- | the following screen, leave **IPv4** set to **DHCP** and skip **Network**, | ||
- | {{ : | ||
- | \\ | ||
- | * It is recommended that users assign a **static IP address**, to the new openmediavault | ||
- | server, that is outside the address range of the network' | ||
- | * In many cases, the Netmask will be as shown and the Gateway address will be the address of the user's router. | ||
- | * If Ipv6 is not needed, leave it at the default setting – Disabled. | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | While not visible in the screen capture above, it is recommended that users consider | ||
- | using a public DNS server address. | ||
- | [[https:// | ||
- | **DNSSEC**, for better security, and **ANYCAST**, | ||
- | are closer to user locations. | ||
- | \\ | ||
- | Enter the selected address in the **DNS IP address field**. | ||
- | the remaining fields under **Advanced settings** should remain at the defaults.\\ | ||
- | \\ | ||
- | < | ||
- | < | ||
- | <table width=" | ||
- | <tr> | ||
- | <td colspan=" | ||
- | < | ||
- | </td> | ||
- | </tr> | ||
- | <tr> | ||
- | <td style=" | ||
- | < | ||
- | cutting it off</ | ||
- | different from the static IP address chosen by the user, when the new address is | ||
- | changed, saved and applied, the GUI web page will stop responding. | ||
- | and expected. | ||
- | your Web browser to reconnect. | ||
- | </tr> | ||
- | </ | ||
- | </ | ||
- | </ | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | **(Optional)** \\ | ||
- | Under **System**, **Power Management**: | ||
- | The **Settings** window allows for the automation of various power related tasks, such as an scheduled reboot. \\ | ||
- | \\ | ||
- | In the **Power button** drop down, amd64 and i386 users should select the action preferred. \\ | ||
- | Since power buttons are not available on some SBC installations, | ||
- | {{ : | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | Under **System**, **Update Management**, | ||
- | \\ | ||
- | First, click on the **Check** button , to refresh available updates for your platform. \\ | ||
- | (This may take a few minutes.) \\ | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | When the **Install** button is clicked, all applicable upgrades will be installed. | ||
- | (Recommended for beginners.) \\ | ||
- | ** *Note* ** that it is possible to “selectively” upgrade by highlighting specific | ||
- | packages. A click on a package, combined with the **Shift** key can select a range of | ||
- | packages or, if using the **Crtl** key, specific packages can be selected for installation. | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | While upgrades are taking place, a progress window will appear. | ||
- | the “**Close**” button will be grayed out. | ||
- | {{ : | ||
- | \\ | ||
- | When upgrades are complete, the Close button with be active. | ||
- | confirmation banner may appear. | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | ==== OMV-Extras ==== | ||
- | \\ | ||
- | (The following does not apply to **SBC** or **i386**- 32bit users. | ||
- | install, OMV-Extras is installed with openmediavault by default.) \\ | ||
- | \\ | ||
- | **amd64** users will have a basic set of plugin' | ||
- | File Server. | ||
- | installation of OMV-Extras is required. \\ | ||
- | \\ | ||
- | < | ||
- | < | ||
- | <table width=" | ||
- | <tr> | ||
- | <td colspan=" | ||
- | < | ||
- | </td> | ||
- | </tr> | ||
- | <tr> | ||
- | <td style=" | ||
- | For < | ||
- | < | ||
- | flash-memory plugin is < | ||
- | </tr> | ||
- | </ | ||
- | </ | ||
- | </ | ||
- | |||
- | \\ | ||
- | ---- | ||
- | === Installing OMV-Extras === | ||
- | \\ | ||
- | To enable OMV-Extras, running a command line is required, as follows: \\ | ||
- | \\ | ||
- | '' | ||
- | \\ | ||
- | This can be done in two different ways, by SSH client or a scheduled task. Chose | ||
- | one of the two methods as follows. \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | === Installing OMV-Extras using an SSH Client (Preferred) === | ||
- | \\ | ||
- | New users should consider installing and using PuTTY. | ||
- | into their server from a Windows, Mac, or Linux client. | ||
- | on-going maintenance tasks and, if needed, repairs. | ||
- | and using PuTTY can be | ||
- | found → [[https:// | ||
- | \\ | ||
- | * Open PuTTY and connect to the server' | ||
- | * Login as '' | ||
- | * Copy the command line (above) with (**Ctrl+C**). | ||
- | \\ | ||
- | {{ : | ||
- | * Hit **Enter**. | ||
- | * DO NOT close the PuTTY window or the command will abort. | ||
- | \\ | ||
- | When finished, the script will state **Done** and the **root prompt** will return. | ||
- | window can now be closed. | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | === Installing OMV-Extras using a Scheduled Task === | ||
- | \\ | ||
- | A scheduled task allows Admin' | ||
- | \\ | ||
- | Under **System**, **Scheduled Tasks**, Click the **Create** button. \\ | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | In the **Create** Window: | ||
- | |||
- | * **Uncheck Enable**. | ||
- | * Copy the Command line above with (**Ctrl+C**) and paste it (**Ctrl+V**) into the **Command field**. \\ | ||
- | {{ : | ||
- | |||
- | < | ||
- | |||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | Highlight the **Task** and click the **Run** button. \\ | ||
- | {{ : | ||
- | \\ | ||
- | When the “**Run Scheduled Task**” dialog box pops up, click **Start**. | ||
- | running, the **Close** button will be grayed out.) When the task is finished, click | ||
- | the Close button. \\ | ||
- | A reboot may be necessary, for **OMV-Extras** to show up in the left column under | ||
- | **System**. \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | (**Optional**, | ||
- | Under **System**, **OMV-Extras**, | ||
- | In **Settings**, | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | To insure that all plugins are available, go back to **System**, **Plugins**, | ||
- | the **Check** button. | ||
- | additional plugins. \\ | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | |||
- | ==== A Basic Data Drive ==== | ||
- | \\ | ||
- | === General === | ||
- | \\ | ||
- | Openmediavault is capable of setting up basic Linux file systems in the GUI up to, and including “Copy on Write” file systems such as BTRFS and ZFS which combine check summed files, RAID functions, and Logical Volume Management into a single package. | ||
- | \\ | ||
- | Until some experience is gained, it is recommended that Linux/NAS beginners use | ||
- | single disks with a native Linux file system. | ||
- | following, **EXT4** will be used with a single data drive. \\ | ||
- | \\ | ||
- | Some Windows users will want to use USB attached hard drives that are formatted NTFS by Windows. | ||
- | \\ | ||
- | A far easier and better approach would be to format all server connected drives, | ||
- | using openmediavault' | ||
- | as described in [[https:// | ||
- | and [[https:// | ||
- | Samba (SMB/CIF) network shares understand the Windows file format and can be | ||
- | configured to accommodate DOS and extended file attributes. | ||
- | “transparent translator” for Windows data storage. \\ | ||
- | \\ | ||
- | === RAID+USB = Potential Problems === | ||
- | Setting up RAID of any type using “USB to drive” connections is highly | ||
- | discouraged. | ||
- | (there are several varieties) may filter some the characteristics of hard | ||
- | drives, fail to pass SMART stat's and ATA drive commands, delay the assembly | ||
- | of a RAID array, etc. While USB may work in some RAID cases, it's not as | ||
- | reliable as using a standard hard drive interface. If RAID of any type is | ||
- | considered to be a requirement, | ||
- | \\ | ||
- | If users choose to use RAID over USB connections, | ||
- | \\ | ||
- | RAID is often confused with **backup** which is far more important. | ||
- | information, | ||
- | in [[https:// | ||
- | ((Redirect to OMV6 maintenance when it exists.)) | ||
- | \\ | ||
- | \\ | ||
- | === Data Storage - Size matters === | ||
- | In general terms, beginners should do a rough calculation of their storage | ||
- | requirement. When selecting a data drive, the initial fill rate should be between | ||
- | 25 and 50%. As an example, if the calculated data to be stored on the NAS is 1TB, | ||
- | the selected drive should be between 2 and 4TB. With 50%+ drive free space | ||
- | (2 to 3TB) additional data can be accommodated, | ||
- | immediate future. | ||
- | storage. | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | === Data Drive Set Up === | ||
- | |||
- | < | ||
- | < | ||
- | <table width=" | ||
- | <tr> | ||
- | <td colspan=" | ||
- | < | ||
- | </td> | ||
- | </tr> | ||
- | <tr> | ||
- | <td style=" | ||
- | | ||
- | </tr> | ||
- | </ | ||
- | </ | ||
- | </ | ||
- | |||
- | ---- | ||
- | \\ | ||
- | (With a data drive installed or connected) \\ | ||
- | \\ | ||
- | Under **Storage**, | ||
- | \\ | ||
- | < | ||
- | prompted for confirmation, | ||
- | “< | ||
- | < | ||
- | |||
- | {{ : | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | |||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | Under **Storage**, | ||
- | < | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | click on < | ||
- | {{ : | ||
- | \\ | ||
- | < | ||
- | creation has completed successfully</ | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | When the format is complete and the **Format** dialog box is closed, the | ||
- | **File Systems - Create** window will, automatically, | ||
- | If needed, the **Mount** Window can be found again under, **Storage**, | ||
- | Click the **Create** Icon and select **Mount**. \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | {{ : | ||
- | \\ | ||
- | < | ||
- | < | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | |||
- | {{ : | ||
- | \\ | ||
- | \\ | ||
- | {{ : | ||
- | |||
- | ===== Creating A Network Share ===== | ||
- | Network shares are the primary reason for setting up and running a NAS. While easy access to data provides convenience to users, storing and backing up data in a centralized location makes it much more manageable. | ||
- | \\ | ||
- | ==== Setting up a Shared Folder ==== | ||
- | The majority of the files and folders in a new openmediavault installation are | ||
- | controlled by the root user. One of the purposes of a **Shared Folder** is to set | ||
- | permissions that will allow regular users access to folders and files used for | ||
- | data storage. | ||
- | folder created in the following will be the foundation for creating a “**Network | ||
- | Share**”, covered later. | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | Under **Storage**, | ||
- | \\ | ||
- | In the following example, next to; \\ | ||
- | \\ | ||
- | **Name: | ||
- | **Device: | ||
- | **Path:** Accept the default \\ | ||
- | **Permissions: | ||
- | {{ : | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | ==== Creating a SMB/CIF “Samba” Network Share ==== | ||
- | \\ | ||
- | In order to make your shared folder viewable in a client' | ||
- | under **Network**, | ||
- | (Server Messaging Block) protocol. | ||
- | network share an easy task. \\ | ||
- | \\ | ||
- | Under **Services**, | ||
- | LAN's workgroup name has been changed from the default, **WORKGROUP**, | ||
- | in the **Workgroup** field. | ||
- | defaults. \\ | ||
- | {{ : | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | Under **Services**, | ||
- | **Create** button. \\ | ||
- | \\ | ||
- | In the Create window, set the following: \\ | ||
- | **Shared folder**: Click on the drop down and select **Music** (or the name for | ||
- | the shared folder previously created.) \\ | ||
- | **Public: | ||
- | \\ | ||
- | Check the boxes for, **Extended attributes** and **Store DOS attributes**. | ||
- | the remaining settings at defaults.) \\ | ||
- | {{ : | ||
- | \\ | ||
- | Scroll down and Click **Save** and confirm with “**Apply**” when the yellow banner | ||
- | appears. \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | The final result should appear as follows. \\ | ||
- | {{ : | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | ==== Explore the New Network Share ==== | ||
- | You should now have a browseable Server with a Network share named Music, so let's take a look. \\ | ||
- | \\ | ||
- | At a network client, open Windows explorer. | ||
- | it. There' | ||
- | {{ : | ||
- | \\ | ||
- | < | ||
- | < | ||
- | <table width=" | ||
- | <tr> | ||
- | <td colspan=" | ||
- | < | ||
- | </td> | ||
- | </tr> | ||
- | <tr> | ||
- | <td style=" | ||
- | A few minutes may be required for the Windows Network to “Discover” the new | ||
- | server. | ||
- | </tr> | ||
- | </ | ||
- | </ | ||
- | </ | ||
- | \\ | ||
- | If users are using **Windows 10** PC's, and the server and share does not | ||
- | appear at a client, see this networking | ||
- | [[https:// | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | Now let's look at the server' | ||
- | {{ : | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | {{ : | ||
- | \\ | ||
- | **Congratulations!** | ||
- | additional network shares. | ||
- | [[https:// | ||
- | to create and make additional shares visible on your network. | ||
- | |||
- | {{ : | ||
- | |||
- | ===== The Flash Memory Plugin - amd64 users only ===== | ||
- | |||
- | **amd64** users who installed openmediavault from the ISO image to a **flash media** drive: \\ | ||
- | The installation of the Flash Memory plugin is required.\\ | ||
- | \\ | ||
- | For an explanation of the Flash Memory Plugin, with installation instructions, | ||
- | this → [[https:// | ||
- | |||
- | {{ : | ||
- | |||
- | ===== Hard Drive Health and SMART ===== | ||
- | |||
- | Hard drives are the hardware component most likely to fail, in a server, over | ||
- | time. With continuous use, spinning hard drives last roughly 4 to 7 years, | ||
- | but there are notable exceptions where hard drive life may be significantly | ||
- | shorter or longer. \\ | ||
- | Given that storage failure is inevitable, the best overall strategy to avoid | ||
- | losing data is 100% backup of the entire data store. | ||
- | important to monitor the condition of a server' | ||
- | silent data corruption and, unknowingly, | ||
- | backup device. \\ | ||
- | Another characteristic of hard drives is that they rarely fail all at once. | ||
- | While it is possible for a drive to fail abruptly, and without notice, it is | ||
- | a fairly rare occurrence. | ||
- | gradually accelerating toward a point in time where they become unreadable. | ||
- | This unfortunate circumstance, | ||
- | unreadable hard drive, might be avoidable with automated testing and | ||
- | monitoring. \\ | ||
- | \\ | ||
- | To protect the server' | ||
- | recommended.\\ | ||
- | ---- | ||
- | ==== Enable SMART ==== | ||
- | |||
- | In the **Settings** window, **SMART** is enabled by default but it's necessary | ||
- | to enable SMART monitoring of each device.\\ | ||
- | \\ | ||
- | < | ||
- | click on the < | ||
- | {{ : | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | **In Storage, S.M.A.R.T., Devices, Edit:** \\ | ||
- | \\ | ||
- | In the **Device** field: Select the drive to monitored with the drop down arrow. \\ | ||
- | < | ||
- | < | ||
- | {{ : | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | ==== Drive Self-Tests ==== | ||
- | Drive self-tests are a tool for early discovery of hard drive issues. | ||
- | Periodic testing of hard drives will uncover the majority of hard drive | ||
- | issues as they begin to develop and, hopefully, before a drive fails | ||
- | completely. | ||
- | short tests, for an individual hard drive. | ||
- | self-test is run every Sunday at 1:00AM) \\ | ||
- | \\ | ||
- | A **Short** self-test runs for a few minutes and is an “on-line” procedure, | ||
- | meaning that drives are still accessible during the test. A **Long** self-test | ||
- | is an “off-line” test, meaning drives are not accessible during the test. | ||
- | While a Short test does a quick check of a drive' | ||
- | does everything in a Short test then checks the media (platters) for bad | ||
- | sectors and other imperfections. | ||
- | reallocating bad sectors. | ||
- | \\ | ||
- | The down side of a Long test is that it is L-O-N-G, where drive size and spindle speed are factors in the length of the test. Long tests are off-line and, since entire platter surfaces are scanned, it may push a drive that's beginning to fail closer to an actual failure as the test detects and attempts to repair problems. | ||
- | \\ | ||
- | There are many opinions on which tests to use and the frequency of testing. | ||
- | \\ | ||
- | * Some data center admins schedule short self-tests once a week and a long test once every 30 to 60 days. (Remember, when scheduling a Long self-test, schedule it for after-hours periods where the server is not in use.) | ||
- | * Some home NAS admin' | ||
- | There' | ||
- | monitor drive health, in avoiding data corruption and loss. \\ | ||
- | \\ | ||
- | ---- | ||
- | === Enable Drive Self-Tests === | ||
- | \\ | ||
- | < | ||
- | {{ : | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | \\ | ||
- | In the **Device** field, use the **drop down arrow** to select a drive. | ||
- | Again, the following selections will run a Short Self-Test every Sunday at 01:00AM. \\ | ||
- | {{ : | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | \\ | ||
- | ---- | ||
- | |||
- | ==== SMART Attributes ==== | ||
- | |||
- | There are numerous SMART attributes to consider. | ||
- | standardized among the various drive OEM's and many have little to no practical meaning | ||
- | to the end user. Given the variation between drive OEM's, the interpretation of a specific | ||
- | SMART stat may require going to the drive OEM's support site. | ||
- | \\ | ||
- | A good explanation of individual SMART attributes, and a brief explanation for | ||
- | each, can be | ||
- | found -> [[https:// | ||
- | \\ | ||
- | Where spinning drives are concerned, thanks to the ongoing | ||
- | [[https:// | ||
- | correlation has been made between impending drive failure and specific SMART stat' | ||
- | \\ | ||
- | < | ||
- | \\ | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | \\ | ||
- | Any one count of the above stats may be meaningless, | ||
- | \\ | ||
- | **SMART 199 - UltraDMA CRC errors** \\ | ||
- | While not directly linked to drive failure, it's worth noting that counts on SMART stat 199 are usually hardware or cable related. | ||
- | |||
- | ---- | ||
- | |||
- | |||
- | ==== Drive Failure - The Bottom Line ==== | ||
- | When using scheduled drive self-tests in conjunction with SMART E-mail notifications | ||
- | [[https:// | ||
- | server admin' | ||
- | the data corruption and data loss due to a failing hard drive. | ||
- | |||
- | {{ : | ||
- | |||
- | ===== Final Installation Notes: ===== | ||
- | |||
- | 1. Permissions for the shared folder created in this guide, and the SMB network share layered on top of it, are completely open. While these permission settings are OK for home environments, | ||
- | As users gain knowledge and experience, they should consider tightening up permissions on the underlying Shared Folders and SMB/CIFS network shares. \\ | ||
- | \\ | ||
- | 2. **Important** | ||
- | |||
- | ---- | ||
- | |||
- | ===== New User - Server Utilities and Maintenance for OMV6 ===== | ||
- | |||
- | The Utilities and Maintenance guide is still being drafted. | ||
- | of [[https:// | ||
- | ---- | ||
- | |||
- | |||
- | ===== A Closing Note ===== | ||
- | |||
- | We, who support the openmediavault project, hope that you’ll find your openmediavault server to be | ||
- | enjoyable, efficient, and easy to use.\\ | ||
- | \\ | ||
- | If you found this guide to be helpful, please consider a modest donation to support the | ||
- | hosting costs of this server (OMV-Extras) and the project (Openmediavault). \\ | ||
- | \\ | ||
- | **OMV-Extras.org** | ||
- | \\ | ||
- | < | ||
- | <form action=" | ||
- | <input type=" | ||
- | <input type=" | ||
- | <input type=" | ||
- | <img alt="" | ||
- | </ | ||
- | </ | ||
- | \\ | ||
- | \\ | ||
- | **www.openmediavault.org** | ||
- | \\ | ||
- | < | ||
- | <form action=" | ||
- | <input name=" | ||
- | <input name=" | ||
- | <input style=" | ||
- | <img loading=" | ||
- | </ | ||
- | </ | ||
- | |||
- | |||
- | \\ | ||
- | \\ | ||
- | \\ | ||