Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
flashmemory_plugin_for_omv6 [2021/04/26 01:39] – crashtest | flashmemory_plugin_for_omv6 [2022/01/13 14:47] – [Installation] crashtest | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{ : | + | |
- | \\ | + | |
- | \\ | + | |
\\ | \\ | ||
< | < | ||
Line 10: | Line 8: | ||
\\ | \\ | ||
\\ | \\ | ||
- | 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. | + | 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. |
\\ | \\ | ||
\\ | \\ | ||
Line 17: | Line 15: | ||
[[https:// | [[https:// | ||
[[https:// | [[https:// | ||
+ | \\ | ||
\\ | \\ | ||
===== The FlashMemory Plugin ===== | ===== The FlashMemory Plugin ===== | ||
- | The FlashMemory Plugin | + | The FlashMemory Plugin |
+ | alternative to booting from a hard drive or SSD. | ||
+ | enable easy [[https:// | ||
+ | options, quick recovery from boot drive failure and it saves a SATA port for a | ||
+ | data storage drive.\\ | ||
+ | \\ | ||
+ | This plugin is **REQUIRED**, for a flash media boot drive, or it will have a short life. For an in-depth | ||
\\ | \\ | ||
==== Prerequisites ==== | ==== Prerequisites ==== | ||
- | * Applies | + | * This procedure applies |
- | * OMV-Extras must be installed. | + | * OMV-Extras must be installed. |
- | - Install by OMV-Extras by plugin → [[https:// | + | |
- | - Installation by script | + | |
- | ---- | + | ==== Installation ==== |
+ | For OMV6; installing OMV-Extras is accomplished by copying | ||
+ | and pasting the following wget command, on your server' | ||
+ | \\ | ||
- | ===== Install FlashMemory | + | '' |
- | Under **System**, **Plugins** scroll to the **openmediavault-flashmemory** plugin. | + | Highlight |
- | \\ | + | **Note:** If you're unsure of how to get on the command line, see this reference for → [[https:// |
- | {{ :underconstruction.jpg?200|}} | + | |
\\ | \\ | ||
+ | When the script is complete, OMV-Extra' | ||
+ | |||
---- | ---- | ||
+ | With OMV extra' | ||
+ | \\ | ||
+ | \\ | ||
+ | * Installation on the command line:\\ | ||
+ | \\ | ||
+ | '' | ||
- | ==== FlashMemory - Additional Setup ==== | + | Again, paste the above into the command line, as described above.\\ |
+ | \\ | ||
+ | * Installation within the GUI: | ||
+ | The Flashmemory plugin can now be found under, **System**, **Plugins** | ||
+ | |||
+ | \\ | ||
+ | ---- | ||
+ | \\ | ||
==== Why is the FlashMemory Plugin Required? ==== | ==== Why is the FlashMemory Plugin Required? ==== | ||
+ | \\ | ||
=== Wear Leveling === | === Wear Leveling === | ||
- | |||
While modern flash media drive is solid state, it’s life is limited by the number of write cycles it can withstand before it goes “read-only”. When an OEM specified number of flash memory blocks refuse to erase, the device’s controller will set it “read only”. At that point, the device’s useful life is over. | While modern flash media drive is solid state, it’s life is limited by the number of write cycles it can withstand before it goes “read-only”. When an OEM specified number of flash memory blocks refuse to erase, the device’s controller will set it “read only”. At that point, the device’s useful life is over. | ||
- | To extend the life of flash media, most modern flash devices have wear leveling built into their controllers. If blocks are written, but not erased, they experience no wear. If blocks are erased, the next new write is set on adjacent blocks that have never been written before. As data is erased and written, blocks are used starting at the beginning of the device’s available storage address range and proceeding, in sequence, working toward the end. When the end of the range is reached, the process starts at the beginning and cycles through again. This wear leveling process avoids writing a single location to failure, and spreads wear evenly throughout. | + | To extend the life of flash media, most modern flash devices have "wear leveling" |
- | + | ||
- | With wear leveling and two drives of the same type, a drive that is twice the size will last roughly two times longer than the smaller drive. This may seem like is a strong vote for using a larger flash drive. However, when backups are considered, drives of twice the size also take twice as long to image and their image files are twice as large. (When using flash media as a boot drive, a practical trade-off should be considered in the suggested 16 to 32GB range.) | + | |
+ | With wear leveling and using two drives of the same type, a drive that is twice the size will last roughly two times longer than the smaller drive. This may seem like is a strong vote for using a larger flash drive. However, when backups are considered, drives of twice the size also take twice as long to image and their image files are twice as large. (When using flash media as a boot drive, a practical trade-off should be considered in the 16 to 32GB range.) | ||
+ | \\ | ||
+ | \\ | ||
=== The Purpose of the Plugin === | === The Purpose of the Plugin === | ||
- | + | Most writes to OMV's boot drive are entries being appended to log files. | |
- | Most writes to OMV's boot drive are entries being appended to log files. | + | \\ |
+ | The primary purpose of the Flash Memory Plugin is to reduce the frequency of writes to flash media by consolidating very small writes into one, larger, bulk write that is flushed to the boot drive on shutdown. | ||
\\ | \\ | ||
- | The primary purpose of the Flash Memory Plugin is to reduce the frequency of writes to flash media by consolidating very small writes into one, larger, bulk write as shutdown. | + | It's worth noting |
\\ | \\ | ||