Release of openmediavault 6 (Shaitan)
After a long development phase i am happy to announce the release of openmediavault 6 (Shaitan).
A big thank you goes to all translators, forum moderators and bug reporters for their contributions and support.
The main new features of openmediavault 6:
- Based on Debian 11 (Bullseye).
- Completely new user interface written from scratch.
- Add some new plugins that are based on containers. These are e.g. S3, OwnTone, PhotoPrism, WeTTY, FileBrowser, Onedrive. Please note that not all platforms are supported because the upstream base containers are only available for specific CPU architectures.
- Enhanced ISO installer. Ensure that /media is unmounted to allow installation to USB devices. This will allow the installation from USB to USB device.
- /dev/disk/by-label filesystem device files are not supported anymore because they are not unique and predictable.
- The file system page will only show file systems configured by openmediavault from now on. This is the standard behavior of the user interface that all other pages use.
- openmediavault can’t be installed side-by-side with graphical environments anymore.
- Replace pam_tally2 by pam_faillock.
- Replace CLI tool omv-update by omv-upgrade.
- Use systemd watchdog instead of separate daemon.
- Add option to FTP settings to display the home directory of the user in the browse list.
- Enhance the SMART temperature monitoring configuration. Global settings can be overwritten per device. Please check your settings whether the migration was correct or reconfigure them if necessary.
- Remove ability to cleanup system logs. This is no longer possible because the data is now fetched from the systemd journal, which cannot be cleaned per unit.
- Support ed25519 SSH public keys in the user settings dialog.
- Add recycle bin support for SMB home directories.
- Add the ability to copy and apply the permissions of a shared folder to its ACL page.
- Disable the ‘Access control list’ button on the shared folder page if the selected entry is located on a non-POSIX compliant file system.
- Enhance the configuration of times of scheduled jobs.
- Disable SMB NetBIOS support by default. You can enable it via the OMV_SAMBA_NMBD_ENABLE environment variable.
- Statically DNS servers will take precedence over the DNS servers received from the DHCP server.
- Force avahi-daemon to only use ethernet, bond and wifi network interfaces that are configured via the UI.
- …
The whole changelog for openmediavault 6 can be viewed here.
More information about the omv-extras.org plugins can be found here.
WARNING … Upgrading from openmediavault 5 might cause problems on systems that are using USB hardware based on JMicron controllers. Have a look here and here for more information.
WARNING … Side-by-side installation with graphical environments will be prevented technically.
The ISO image can be downloaded here. You can also install openmediavault 6 on every Debian 11 based distribution, e.g. using the Netinst ISO images, Raspbian or … if your platform is not supported. You will find a guide here how you can do that.
Existing openmediavault 5 installations can be migrated by running the omv-release-upgrade command in the CLI.
If you have any questions, feel free to post them in the forum or have a look into our troubleshooting section.
OpenMediaVault 6: вышла новая версия для NAS
OpenMediaVault 6 — новая версия системы для NAS на базе Debian 11 который поставляется с новым пользовательским интерфейсом, написанным с нуля. Кроме того, OMV позволит вам иметь все функции сетевого хранилища, какие только можно себе представить. Он также включает поддержку протоколов SSH для безопасного удаленного подключения для администрирования, SFTP и FTP для загрузки или скачивания файлов, RSync для синхронизации файлов, клиент BitTorrent и т. д. И это почти ничего, так как он имеет модульную конструкцию, поэтому вы можете добавить еще больше функций благодаря его плагинам.
С другой стороны, стоит отметить, что OpenMediaVault зарекомендовал себя как надежное решение NAS, и знание того, что за ним стоит Debian, означает силу, безопасность и стабильность. OpenMediaVault появился в 2009 году как преемник известного FreeNAS (теперь называется TrueNAS), основанный на FreeBSD.. Кроме того, это не просто преемник, у него есть один из первых разработчиков FreeNAS, работающий над OMV, но теперь использующий другую систему.
Проект был специально разработан для использования в в домашних условиях из-за простоты управления или для МСП, хотя он не ограничивается этими сегментами и может дать гораздо больше от себя. Благодаря простому веб-интерфейсу у вас будет хорошее готовое к использованию решение NAS, не требующее дополнительных навыков работы с компьютером. И теперь вы можете пользоваться всеми новыми функциями, включенными в OpenMediaVault 6, последнюю стабильную версию этого проекта:
- Основан на Debian 11, а не на Debian 10, как в серии 5.x.
- Новый графический интерфейс, полностью разработанный с нуля, чтобы быть более чистым, современным, простым в использовании и соответствовать последним тенденциям.
- Плагины на основе контейнеров (S3, OwnTone, PhotonPrism, WeTTY, FileBrowser, Ondrive, мониторинг SMART и т. д.)
- Поддержка корзины для SMB
- Множество других улучшений, в том числе большое количество исправлений ошибок.
Если у вас уже есть OpenMediaVault 5.x и вы хотите обновиться до OMV 6, вы должны быть осторожны и убедиться, что ваше оборудование не использует USB-драйверы JMicron, так как это может вызвать проблемы, как обнаружили некоторые пользователи. Во всех остальных случаях можете обновляться без опаски. И помните, OMV 5 подходит к концу в конце июня 2022 года, после чего прекращается поддержка, и больше не будет никаких обновлений исправлений и исправлений безопасности для устранения уязвимостей. Поэтому важно переходить на версию 6.x proton…
Помните, что ISO-образ OpenMediaVault 6 также можно найти для архитектуры ARM, чтобы использовать NAS на базе Raspberry Pi.
Дополнительная информация от OpenMediaVault – Официальный сайт
Содержание статьи соответствует нашим принципам редакционная этика. Чтобы сообщить об ошибке, нажмите здесь.
Полный путь к статье: Любители Linux » Общие » Ресурсы » OpenMediaVault 6: вышла новая версия для NAS
Getting Started with Openmediavault 6
January 22nd, 2022 — Rev 0.1 (First Draft)
January 24th, 2022 — Rev 0.2 Added Note boxes
January 29th, 2022 — Rev 0.3 Fixed drafting errors in “A Basic Data Drive”.
December 12th, 2022 — Rev 1.0 Links to the Utilities and Maintenance doc, updated links, various minor revisions and edits. Removed 3rd party translation links.
January 26th, 2023 — Rev 1.1 Updated multiple screen shots to reflect changes in the top menu of the GUI .
May 10th, 2023 — Rev 1.2 Note on OMV-Extras config, various minor formatting changes.
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’s Server Essentials, but extends far beyond the role of a basic File Server with additional functionality added VIA plugin’s and Dockers. Openmediavault is designed to work with popular client operating systems and multiple filesystem types, utilizing proven data sharing techniques on small and medium sized Local Area Networks.
In meeting the needs of it’s intended users, individuals and small-to-medium-sized businesses, Openmediavault is designed for flexibility.
History
Openmediavault’s history began with Volker Theile, who was the only active developer of the FreeNAS project by the end of 2009. Volker became interested in completely rewriting FreeNAS, for use on Linux. Initially, he named the rewritten package coreNAS. Shortly thereafter, Volker discarded the name coreNAS in favor of openmediavault. Openmediavault’s initial release was on 17 October 2011. It’s built upon very mature and proven software layers and is under constant development. Openmediavault relies on the Debian project and uses their system and repositories as a base. The project focus is on creating and maintaining a stable and extensible NAS system that is intuitive and easy to use.
Purpose
The purpose of openmediavault is to provide a NAS system that is highly “extensible” with value added plugin’s and access to numerous Dockers that are desirable and beneficial to home users and small businesses at little to no cost.
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. While openmediavault is free, donations to cover Web site costs, hardware for testing, and other unavoidable expenses are needed and very much appreciated.
Donate to openmediavault (Main project development) and
Donate to omv-extras.org (Support for Single Board Computers and Development of Plugins.)
About this Guide
In computing, generally speaking, there are several ways to do the same thing. By extension, methods and methodology become progressively more advanced as a user’s skill level increases. With these notes in mind, methods found in this guide may not be considered as “Best Practice”, especially from a hardened security perspective. The purpose and intent of this guide is to provide a walk-through to get users up and running as quickly and easily as possible.
This guide contains links to external sources of information and software. It’s best used on a PC connected to the Internet.
This is a community document and a work in progress. Input and feedback are welcome and can be sent to: omvguide@gmail.com
Beginners:
This document is intended for beginners who will, primarily, be using the openmediavault’s GUI . Beginners are assumed to have basic knowledge of 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 → Quick Start Guide.
A Cautionary Note for Advanced Users:
Many of the configuration files traditionally used to customize Debian Linux are controlled by the openmediavault system database. As a result, manual edits of configuration files may be overwritten as of the next, “on-demand”, configuration change in the openmediavault GUI . Further, it is possible to “break” openmediavault with alterations and permissions changes to the files of the boot drive, on the command line. In the beginning it’s best to rely, primarily, on the GUI for configuration and control. Otherwise, before attempting to customize the operating system, backing up the boot drive is highly recommended.
Linux Experts, Admin’s, and Developers:
Users in this category may prefer the information available on the Project’s Wiki.
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 Debian.org
64 bit hardware (amd64):
The openmediavault project maintains convenient, fully integrated, openmediavault/Debian → installation ISO’s installation ISO’s. This is the best method for getting openmediavault up and running quickly.
32 bit Hardware (i386):
While openmediavault is supported by 32 bit Debian installations, it’s a two step scripted process referenced in; Installing OMV6 on i386 (32-bit) platforms. 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. Supported platforms are the Raspberry Pi, models 2B and higher, and various ARM platforms supported by the Armbian Project.
Minimum Hardware requirements
Openmediavault/Debian will run on I386, AMD64, and select ARM platforms with 1GB of ram or less, but performance expectations should be adjusted accordingly. The system boot drive should have a minimum of 8GB capacity.
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. At least 1 GB of RAM would be preferred.
If flash media is used, (USB thumb-drives, SD-cards, etc.) the system boot drive should have at least 16GB capacity, for longer life.
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’s SATA or SAS ports can be a factor if future storage expansion is needed.
A case design that accommodates the physical installation of additional hard drives can be helpful.
Integrated video is preferred over add-on Video cards. With openmediavault’s headless server design, add-on Video cards are an excessive and unnecessary power drain with no performance benefit. Installing a high end, high powered Video card in a headless server is analogous to installing a 65 to 200 watt light bulb in a closet, without a switch, and closing the door.
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, Raspberry PI OS , and Openmediavault. While most will support file server operations for a few users, if running server add-on’s or Dockers is a requirement, research supported SBC’s carefully before buying. Armbian’s or openmediavault’s forums may be of assistance, 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. Accordingly, SBC users should read the ending cautionary note in Operating System Backup.
Raspberry PI’s
(Hereafter referred to as “R-PI’s”.) Given the current market for SBC’s, the majority of SBC users will likely be owners of R-PI’s.
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. Performance is poor. What 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’s a software or permissions problem. In other 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’s are very easily over stressed and, during periods where the CPU is running at 100%, they may not respond to external input. With this performance limitation in mind, earlier versions of the R-PI (2B and 3X models) should be used only as a basic file server for 1 or 2 user home environments, where multitasking is less likely. If running automated tasks, it’s best to 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 USB Power — A Common Raspberry PI problem
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. Since mobile devices are low powered, they’re not capable of re-processing high 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 PassMark score for each concurrent 1080p transcoded stream. (See the advice article here) However note that this advice applies to pre-2011 Intel and AMD CPU’s. Look up an older CPU here → PassMark CPU Benchmarks
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. CPU’s with Quick Sync, to include Celeron and 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.
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’s lean configuration, boot times can be fast. Boot times of 1 minute and Shutdown times of 20 seconds are common, even when using relatively slow flash media such as USB thumb-drives and SD-cards. (Recent models can be quite fast – check their benchmarks.)
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’s file server functions are running from RAM.
Conclusion – for Linux file server operations, fast boot media is not important.
“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. In the traditional role of a NAS as a File Server, when the server boots, the Linux kernel and most of the necessary processes required to act as a File Server are loaded into RAM — the fastest possible media for execution.
Navigating openmediavault’s WEB/ GUI interface is another matter. Loading WEB pages may call files from the boot drive which may make the server appear to be slower, when using slow media. However, the speed of the boot drive has little impact on overall file server function and actual NAS file serving performance.
* The above assumes that adequate RAM has been provisioned. *
Final Notes on Choosing a Boot Drive
Openmediavault’s boot requirements are very modest: 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 is an easy process. Given this consideration, some users prefer USB thumb-drives and other external flash media to internal drives. Further, given the ease of operating system 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, and SD-cards branded A1 for their improved random read/write performance. USB3 thumb-drives and A1 spec ‘ed SD-cards are faster and, generally speaking, more reliable than similar items with older specifications.
While boot drive size matters, bigger is not always better. An acceptable size trade off for wear leveling and the speed of cloning is between 16 and 32GB.
“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 The Flash Memory Plugin.
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. (Does not apply to ARM platforms. ARM platforms can not virtualize i386 or amd64 operating systems.)
There’s no penalty for starting with a smaller boot drive. Moving to a larger drive, if needed, can be done later.)
| Warning | |
| Buying flash devices on-line, even from reputable retailers, comes with the substantial risk of buying fakes. Buying flash drives, in sealed packaging, from walk-in retail stores with liberal return policies is recommended. The use of cheap generics, fakes or knockoffs is highly discouraged. They tend to have a short life and they’re known to cause problems, even if they initially test error-free. 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. If they fail error testing, return them for a refund. | |
unixforum.org
[ON] Доступен дистрибутив для создания сетевых хранилищ OpenMediaVault 6
Обсуждение новостей, соответствующих тематике форума
1 сообщение • Страница 1 из 1
rssbot Бот Сообщения: 6002 ОС: gnu/linux
[ON] Доступен дистрибутив для создания сетевых хранилищ OpenMediaVault 6
Сообщение rssbot » 05.05.2022 08:48
После двух лет с момента формирования прошлой значительной ветки опубликован стабильный релиз дистрибутива OpenMediaVault 6, позволяющего быстро развернуть сетевое хранилище (NAS, Network-Attached Storage). Проект OpenMediaVault основан в 2009 году после раскола в стане разработчиков дистрибутива FreeNAS, в результате которого наряду с основанным на FreeBSD классическим FreeNAS было создано ответвление, разработчики которого поставили перед собой цель перевести дистрибутив на ядро Linux и пакетную базу Debian. Для загрузки подготовлены установочные образы OpenMediaVault для архитектуры x86_64 (868 МБ).
- Пакетная база обновлена до Debian 11 «Bullseye».
- Предложен новый интерфейс пользователя, полностью переписанный с нуля.
Проект OpenMediaVault рассматривает в качестве приоритетных направлений разработки расширение поддержки встраиваемых устройств и создание гибкой системы установки дополнений, в то время как ключевым направлением развития FreeNAS является задействование возможностей файловой системы ZFS. По сравнению с FreeNAS, достаточно сильно переработан механизм установки дополнений, вместо смены «прошивки» целиком для обновления OpenMediaVault используются штатные средства обновления отдельных пакетов и полноценный инсталлятор, позволяющий выбирать необходимые компоненты в процессе установки.
Управляющий web-интерфейс OpenMediaVault написан на PHP и отличается загрузкой данных по мере необходимости при помощи технологии Ajax без перезагрузки страниц (web-интерфейс FreeNAS написан на языке Python с использованием фреймворка Django). В интерфейсе присутствуют функции организации совместного доступа к данным и разделения привилегий (в том числе поддержка ACL). Для мониторинга можно использовать SNMP (v1/2c/3), кроме того присутствует встроенная система отправки уведомлений о проблемах на email (включая отслеживание состояния дисков через S.M.A.R.T. и контроль работы системы обеспечения бесперебойного питания).
Из связанных с организацией работы хранилища базовых сервисов можно отметить: SSH/SFTP, FTP, SMB/CIFS, клиент DAAP, RSync, клиент BitTorrent, NFS и TFTP. В качестве файловой системы можно использовать EXT3, EXT4, XFS и JFS. Так как дистрибутив OpenMediaVault изначально нацелен на расширение функциональности через подключение дополнений, отдельно развиваются плагины с реализацией поддержки AFP (Apple Filing Protocol), сервера BitTorrent, сервера iTunes/DAAP, LDAP, iSCSI target, UPS, LVM и антивируса (ClamAV). Поддерживается создание программных RAID (JBOD/0/1/5/6) с использованием mdadm.
Последний раз редактировалось rssbot 05.05.2022 09:37, всего редактировалось 1 раз.
Причина: Updated upstream