Posts by tom_tav

    I use Raid5 with XFS for my media & nas server since years. Imho a good and easy solution for a media center.


    In your case it will be Raid1.


    P.S. did see your encryption requirement ... if you want to have your data secure, from paranoid point of view i wouldnt do it on the same machine where you run services like sickbeard or others with connection to the internet

    Yes, you are right, there are some small issues with the ZFS plugin, in OMV3 also. But if one is familiar with the basic ZFS CLI commands that should be no big problem.

    CLI is no problem. I just try to avoid setups where you always have to fight with the gui and manually added changes.


    Like my netatalk 3x upgrade for omv 2. I ended up deinstalling netatalk from omv completely and added the new one. If its too much of a hazzle it makes more sense to skip GUI then and just do it with linux. But thats only if its a pure NAS.
    Dont misunderstand me, i love omv. Its just open for me to decide if i move the new array to a bare linux/nas setup or if i upgrade one of my omv machines.

    Thanks Leo, did see that post already. Still wonder if kernel support in 3.x is same as in 4.x ZFS related. All the small problems with zfs and omv 2.x did turn me away from using zfs back then.

    I have to add another question. Maybe i will add a fibre card & iscsi to the machine. Afaik i need to use the 3.x kernel for iscsi.


    Does the OMV3 / ZFS work with the 3.x kernel too?

    Need to upgrade one of my HP54GL NAS machines. Right now im using OMV 2.x, SW Raid 5 with 2TB drives and XFS.


    Now i will upgrade to OMV 3.x, 4x 10TB drives. Machine has 16GB of ram.


    I have some LSI9260 raid controllers laying around. Not sure which combination i should use:


    A. ZFS (is the implementation into OMV3 now good?) .. 16GB ram is a little bit small for a 40TB raid too


    B. SW Raid 5 + XFS (which i use right now)


    C: HW Raid 5 (LSI9260) + XFS


    D: ???



    Suggestions very welcome :)


    Thanks - Tom

    Regarding the 2nd controller for installation. I can move the omv boot drive to the temporary controller to avoid sync/delay problems and to have all raid drives on the same controller.


    Nevertheless after doing the replacement when i remove the 2nd controller the drive designations would change ...

    Whats the best way to exchange a raid5 disc (5 discs, xfs) in omv? Its still working but needs replacement due to smart status.


    I plan to put in another sas controller so i can add the drive to the raid as spare and do a replacement, my current controller has no more free ports.


    I assume this will lead to a faster rebuild time and less stress for the remaining drives then to put out the drive, put in the new one and do a rebuild/resync.



    Can this be done with the gui?


    With mdadm it would be somehow like that:


    # mdadm /dev/md0 --add /dev/sdf1
    # mdadm /dev/md0 --replace /dev/sda1 --with /dev/sdf1


    ---


    I wonder what happens when i remove the 2nd temporary controller again. The new drive will become sda1 instead of sdf1. How should i handle this?

    Thanks sub, that seems to be the case. I was distracted by value, worst, tresh and didnt look so much into raw value



    Seagate information is super helpful: http://knowledge.seagate.com/articles/en_US/FAQ/203971en :huh:



    Quote from sgt

    Seagate uses the SeaTools diagnostic software to test the SMART status of the drive. SeaTools does not analyze attributes or thresholds. As a practical matter, the technology supporting SMART is constantly being improved. Each new design incorporates improvements that increase the accuracy of the SMART prediction. As a matter of policy, Seagate does not publish attributes and thresholds.
    Therefore, if you wish to test the drive for physical integrity, please use our SeaTools diagnostic software.

    continue of ext status:


    General Purpose Log Directory Version 1
    SMART Log Directory Version 1 [multi-sector log support]
    GP/S Log at address 0x00 has 1 sectors [Log Directory]
    GP/S Log at address 0x01 has 1 sectors [Summary SMART error log]
    GP/S Log at address 0x02 has 5 sectors [Comprehensive SMART error log]
    GP/S Log at address 0x03 has 5 sectors [Ext. Comprehensive SMART error log]
    GP/S Log at address 0x06 has 1 sectors [SMART self-test log]
    GP/S Log at address 0x07 has 1 sectors [Extended self-test log]
    GP/S Log at address 0x09 has 1 sectors [Selective self-test log]
    GP/S Log at address 0x10 has 1 sectors [NCQ Command Error]
    GP/S Log at address 0x11 has 1 sectors [SATA Phy Event Counters]
    GP/S Log at address 0x21 has 1 sectors [Write stream error log]
    GP/S Log at address 0x22 has 1 sectors [Read stream error log]
    GP/S Log at address 0x80 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x81 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x82 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x83 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x84 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x85 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x86 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x87 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x88 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x89 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x8a has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x8b has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x8c has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x8d has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x8e has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x8f has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x90 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x91 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x92 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x93 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x94 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x95 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x96 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x97 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x98 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x99 has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x9a has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x9b has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x9c has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x9d has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x9e has 16 sectors [Host vendor specific log]
    GP/S Log at address 0x9f has 16 sectors [Host vendor specific log]
    GP/S Log at address 0xa1 has 20 sectors [Device vendor specific log]
    GP Log at address 0xa2 has 2248 sectors [Device vendor specific log]
    GP/S Log at address 0xa8 has 129 sectors [Device vendor specific log]
    GP/S Log at address 0xa9 has 1 sectors [Device vendor specific log]
    GP Log at address 0xb0 has 2928 sectors [Device vendor specific log]
    GP/S Log at address 0xbd has 252 sectors [Device vendor specific log]
    GP Log at address 0xbe has 65535 sectors [Device vendor specific log]
    GP Log at address 0xbf has 65535 sectors [Device vendor specific log]
    GP/S Log at address 0xc0 has 1 sectors [Device vendor specific log]
    GP/S Log at address 0xe0 has 1 sectors [SCT Command/Status]
    GP/S Log at address 0xe1 has 1 sectors [SCT Data Transfer]


    SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
    No Errors Logged


    SMART Extended Self-test Log Version: 1 (1 sectors)
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Short offline Completed without error 00% 53717 -
    # 2 Short offline Completed without error 00% 53693 -
    # 3 Short offline Completed without error 00% 53668 -
    # 4 Short offline Completed without error 00% 53644 -
    # 5 Short offline Completed without error 00% 53620 -
    # 6 Short offline Completed without error 00% 53596 -
    # 7 Short offline Completed without error 00% 53572 -
    # 8 Short offline Completed without error 00% 53547 -
    # 9 Short offline Completed without error 00% 53523 -
    #10 Short offline Completed without error 00% 53499 -
    #11 Short offline Completed without error 00% 53475 -
    #12 Short offline Completed without error 00% 53451 -
    #13 Short offline Completed without error 00% 53427 -
    #14 Short offline Completed without error 00% 53403 -
    #15 Short offline Completed without error 00% 53379 -
    #16 Short offline Completed without error 00% 53355 -
    #17 Short offline Completed without error 00% 53331 -
    #18 Short offline Completed without error 00% 53307 -
    #19 Short offline Completed without error 00% 53283 -


    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.


    SCT Status Version: 3
    SCT Version (vendor specific): 522 (0x020a)
    SCT Support Level: 1
    Device State: Active (0)
    Current Temperature: 32 Celsius
    Power Cycle Min/Max Temperature: 26/36 Celsius
    Lifetime Min/Max Temperature: 19/45 Celsius
    Under/Over Temperature Limit Count: 0/0
    SCT Temperature History Version: 2
    Temperature Sampling Period: 10 minutes
    Temperature Logging Interval: 59 minutes
    Min/Max recommended Temperature: 14/55 Celsius
    Min/Max Temperature Limit: 10/60 Celsius
    Temperature History Size (Index): 128 (124)


    Index Estimated Time Temperature Celsius
    125 2016-10-31 06:56 30 ***********


    (cut out unnecc data)


    123 2016-11-05 10:50 32 *************
    124 2016-11-05 11:49 32 *************


    SCT Error Recovery Control:
    Read: Disabled
    Write: Disabled


    SATA Phy Event Counters (GP Log 0x11)
    ID Size Value Description
    0x000a 2 4 Device-to-host register FISes sent due to a COMRESET
    0x0001 2 0 Command failed due to ICRC error
    0x0003 2 0 R_ERR response for device-to-host data FIS
    0x0004 2 0 R_ERR response for host-to-device data FIS
    0x0006 2 0 R_ERR response for device-to-host non-data FIS
    0x0007 2 0 R_ERR response for host-to-device non-data FIS

    Hello Guys!



    One of my raid drives turned red. I dont figure out what triggered it. Pls can you explain me my problem. Thanks!!!


    smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.16.0-0.bpo.4-amd64] (local build)
    Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net


    === START OF INFORMATION SECTION ===
    Model Family: Seagate Barracuda LP
    Device Model: ST32000542AS
    Serial Number: 6XW067VW
    LU WWN Device Id: 5 000c50 0163e31d3
    Firmware Version: CC34
    User Capacity: 2,000,398,934,016 bytes [2.00 TB]
    Sector Size: 512 bytes logical/physical
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: 8
    ATA Standard is: ATA-8-ACS revision 4
    Local Time is: Sat Nov 5 13:49:38 2016 CET


    ==> WARNING: A firmware update for this drive may be available,
    see the following Seagate web pages:
    http://knowledge.seagate.com/articles/en_US/FAQ/207931en
    http://knowledge.seagate.com/articles/en_US/FAQ/213915en


    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled


    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED


    General SMART Values:
    Offline data collection status: (0x00) Offline data collection activity
    was never started.
    Auto Offline Data Collection: Disabled.
    Self-test execution status: ( 0) The previous self-test routine completed
    without error or no self-test has ever
    been run.
    Total time to complete Offline
    data collection: ( 633) seconds.
    Offline data collection
    capabilities: (0x73) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    No Offline surface scan supported.
    Self-test supported.
    Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 1) minutes.
    Extended self-test routine
    recommended polling time: ( 255) minutes.
    Conveyance self-test routine
    recommended polling time: ( 2) minutes.
    SCT capabilities: (0x103f) SCT Status supported.
    SCT Error Recovery Control supported.
    SCT Feature Control supported.
    SCT Data Table supported.


    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
    1 Raw_Read_Error_Rate POSR-- 114 099 006 - 61508647
    3 Spin_Up_Time PO---- 100 100 000 - 0
    4 Start_Stop_Count -O--CK 099 099 020 - 1343
    5 Reallocated_Sector_Ct PO--CK 100 100 036 - 2
    7 Seek_Error_Rate POSR-- 051 039 030 - 4685956071260
    9 Power_On_Hours -O--CK 039 039 000 - 53724
    10 Spin_Retry_Count PO--C- 100 100 097 - 0
    12 Power_Cycle_Count -O--CK 100 100 020 - 193
    183 Runtime_Bad_Block -O--CK 100 100 000 - 0
    184 End-to-End_Error -O--CK 100 100 099 - 0
    187 Reported_Uncorrect -O--CK 100 100 000 - 0
    188 Command_Timeout -O--CK 100 095 000 - 17181442125
    189 High_Fly_Writes -O-RCK 099 099 000 - 1
    190 Airflow_Temperature_Cel -O---K 066 055 045 - 34 (Min/Max 26/36)
    194 Temperature_Celsius -O---K 034 045 000 - 34 (0 19 0 0)
    195 Hardware_ECC_Recovered -O-RC- 045 015 000 - 61508647
    197 Current_Pending_Sector -O--C- 100 100 000 - 0
    198 Offline_Uncorrectable ----C- 100 100 000 - 0
    199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
    240 Head_Flying_Hours ------ 100 253 000 - 165094247936316
    241 Total_LBAs_Written ------ 100 253 000 - 2136475912
    242 Total_LBAs_Read ------ 100 253 000 - 1724895301
    ||||||_ K auto-keep
    |||||__ C event count
    ||||___ R error rate
    |||____ S speed/performance
    ||_____ O updated online
    |______ P prefailure warning

    N3 runs with pam and everything on omv, here everything works.


    Unrelated to OMV? Yes, true if questions how omv does things internally are unrelated. And yes, if its just ok to ask the one millionth question like "is this motherboard good for omv"....


    little bit wondering.... but hey, its your decision.


    p.s. thinking if it makes sense for me to post here howtos or other infos ... cause this is unrelated for me too to help others here, im no omv member ... ;)

    Guys, new question where i got stuck (maybe i should go to bed....)


    Im playing around with a special configuration (on stoneburner):


    I have an extra LXC container with netatalk3 running, in addition to the netatalk3 in the root system.


    Reason: this LXC container is connected to another ethernet card to provide a second (isolated) backup system for a different lan segment (i know the lxc isolation is not perfect, but i can live with that for now)


    So far so good. What im wondering ... how is the user authentication (shared folder access rights) handled between omv and netatalk? My netatalk3 on the root system works fine. Im thinking about connecting the netatalk3 lxc instance to the root system for user authentication, so i can manage the users still from omv gui.

    I know, but i am a plex pass user .... did ask myself for what ... not many new functions and features released in the last year. But thats another story...