Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
flashmemory_plugin_for_omv6 [2021/04/26 21:21] – [The Purpose of the Plugin] crashtest | flashmemory_plugin_for_omv6 [2022/07/31 17:17] (current) – removed crashtest | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{ : | ||
- | \\ | ||
- | \\ | ||
- | \\ | ||
- | < | ||
- | |||
- | {{ : | ||
- | |||
- | ====== FlashMemory Plugin For OMV6 ====== | ||
- | \\ | ||
- | \\ | ||
- | 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. | ||
- | \\ | ||
- | \\ | ||
- | [[https:// | ||
- | [[https:// | ||
- | [[https:// | ||
- | [[https:// | ||
- | \\ | ||
- | \\ | ||
- | ===== The FlashMemory Plugin ===== | ||
- | The FlashMemory Plugin was designed to make booting from USB thumbdrives and SD-cards feasible, and a practical alternative to booting from a hard drive or SSD. Using USB Thumbdrives enables easy [[https:// | ||
- | \\ | ||
- | This plugin is **REQUIRED** or a flash boot drive will have a short life. For an in-depth explanation see; [[https:// | ||
- | \\ | ||
- | |||
- | ==== Prerequisites ==== | ||
- | |||
- | * Applies to amd64 ISO installations only. The FlashMemory Plugin is installed by default during scripted installs. (R-PI' | ||
- | * OMV-Extras must be installed. | ||
- | |||
- | There are two methods for installing OMV-Extras\\ | ||
- | - Install by OMV-Extras by plugin → [[https:// | ||
- | - Installation by script | ||
- | \\ | ||
- | ---- | ||
- | ===== Install FlashMemory Plugin ===== | ||
- | - Under **System**, **Plugins** scroll to the **openmediavault-flashmemory** plugin. | ||
- | - Install by script | ||
- | \\ | ||
- | ===== FlashMemory, | ||
- | \\ | ||
- | ==== Why is the FlashMemory Plugin Required? ==== | ||
- | \\ | ||
- | === 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. | ||
- | |||
- | To extend the life of flash media, most modern flash devices have "wear leveling" | ||
- | |||
- | 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 === | ||
- | 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. | ||
- | \\ | ||
- | It's worth noting that SSD's would benefit from the FlashMemory plugin as well. | ||
- | \\ | ||
- | |||
- | |||
- | |||