Posts by GiuseppeChillemi

    Hi,
    I have a RAID6 degraded array, 1 of 12 is not working.


    Which is the correct procedure to remove the HD, add a new one and let it growt ?


    Also, this time I want to add 1 spare drive. Is it possible ?

    Hi,
    I have a failing drive. It is one of a 12x3TB RAID 6 ARRAY.
    I wish to add the new replacement BEFORE replacing the failing one because in such large array everything could happen: 2 other drives could fail while the failing one could remain functional until the end of the replacement process.


    Is it possible to add the replacement drive without removing the failing one and instruct open media vault which one will be replaced at the end of the process ?

    Hi,
    I wish to move my installation to an old 2015 dual opteron board to a 2011 dual xeon.
    My setup has: IBM1015, HP SAS EXPANDER, 2 array of 12 + 6 drives.
    I have currently installed OMV on an USB KEYS.


    Which is the correct procedure to move/migrate my setup and config to another system ?

    Hi,
    I have lot of "critical target error" on SDN during reboot and quota checking


    ...
    Apr 4 22:43:15 openmediavault24 kernel: [ 421.392108] md/raid:md127: read error corrected (8 sectors at 503193480 on sdn)
    Apr 4 22:43:15 openmediavault24 kernel: [ 424.683141] sd 0:0:13:0: [sdn] Unhandled sense code
    Apr 4 22:43:15 openmediavault24 kernel: [ 424.683143] sd 0:0:13:0: [sdn] Result: hostbyte=invalid driverbyte=DRIVER_SENSE
    Apr 4 22:43:15 openmediavault24 kernel: [ 424.683146] sd 0:0:13:0: [sdn] Sense Key : Medium Error [current]
    Apr 4 22:43:15 openmediavault24 kernel: [ 424.683149] Info fld=0x1dfe1f90
    Apr 4 22:43:15 openmediavault24 kernel: [ 424.683151] sd 0:0:13:0: [sdn] Add. Sense: Unrecovered read error
    Apr 4 22:43:15 openmediavault24 kernel: [ 424.683154] sd 0:0:13:0: [sdn] CDB: Read(10): 28 00 1d fe 1f 90 00 00 08 00
    Apr 4 22:43:15 openmediavault24 kernel: [ 424.683160] end_request: critical target error, dev sdn, sector 503193488
    Apr 4 22:43:15 openmediavault24 kernel: [ 424.685224] md/raid:md127: read error corrected (8 sectors at 503193488 on sdn)
    Apr 4 22:43:15 openmediavault24 kernel: [ 743.486699] sd 0:0:13:0: [sdn] Unhandled sense code
    Apr 4 22:43:15 openmediavault24 kernel: [ 743.486703] sd 0:0:13:0: [sdn] Result: hostbyte=invalid driverbyte=DRIVER_SENSE
    Apr 4 22:43:15 openmediavault24 kernel: [ 743.486707] sd 0:0:13:0: [sdn] Sense Key : Medium Error [current]
    Apr 4 22:43:15 openmediavault24 kernel: [ 743.486711] Info fld=0x65ac1ba8
    Apr 4 22:43:15 openmediavault24 kernel: [ 743.486713] sd 0:0:13:0: [sdn] Add. Sense: Unrecovered read error
    Apr 4 22:43:15 openmediavault24 kernel: [ 743.486717] sd 0:0:13:0: [sdn] CDB: Read(10): 28 00 65 ac 1b a8 00 00 08 00
    Apr 4 22:43:15 openmediavault24 kernel: [ 743.486724] end_request: critical target error, dev sdn, sector 1705778088
    Apr 4 22:43:15 openmediavault24 kernel: [ 743.507659] md/raid:md127: read error corrected (8 sectors at 1705778088 on sdn)
    Apr 4 22:43:15 openmediavault24 kernel: [ 748.937687] sd 0:0:13:0: [sdn] Unhandled sense code
    Apr 4 22:43:15 openmediavault24 kernel: [ 748.937691] sd 0:0:13:0: [sdn] Result: hostbyte=invalid driverbyte=DRIVER_SENSE
    Apr 4 22:43:15 openmediavault24 kernel: [ 748.937694] sd 0:0:13:0: [sdn] Sense Key : Medium Error [current]
    Apr 4 22:43:15 openmediavault24 kernel: [ 748.937698] Info fld=0x665207e8
    Apr 4 22:43:15 openmediavault24 kernel: [ 748.937699] sd 0:0:13:0: [sdn] Add. Sense: Unrecovered read error
    Apr 4 22:43:15 openmediavault24 kernel: [ 748.937704] sd 0:0:13:0: [sdn] CDB: Read(10): 28 00 66 52 07 e8 00 00 08 00
    Apr 4 22:43:15 openmediavault24 kernel: [ 748.937710] end_request: critical target error, dev sdn, sector 1716652008
    Apr 4 22:43:15 openmediavault24 kernel: [ 748.967483] md/raid:md127: read error corrected (8 sectors at 1716652008 on sdn)
    Apr 4 22:43:15 openmediavault24 kernel: [ 758.539407] sd 0:0:13:0: [sdn] Unhandled sense code
    Apr 4 22:43:15 openmediavault24 kernel: [ 758.539411] sd 0:0:13:0: [sdn] Result: hostbyte=invalid driverbyte=DRIVER_SENSE
    Apr 4 22:43:15 openmediavault24 kernel: [ 758.539415] sd 0:0:13:0: [sdn] Sense Key : Medium Error [current]
    Apr 4 22:43:15 openmediavault24 kernel: [ 758.539418] Info fld=0x665207f8
    .....

    Hi, I wish to use this server to build an iSCSI STORAGE.


    It will have 8 146gb sas drives
    and
    10gbe hp n550 nic.


    Has omv all drivers needed ?
    How I could the onboard controller in it mode ? If I can't, is there another solution ?

    Thanks, last tru:


    IPMI
    ECC
    Socket 1151
    VT-x and VT-D well implemented
    2 10/100/1000
    1 PCi-e 3.0 slot
    Different x8 x4 slots
    SAS Controller able to connect to HP Extender.


    (Note I have added the last line and removed Socket 1151 and Virtual Machine Offload engine)

    I would look at the asrock rack boards. I really like mine. That cpu only 16 pci express lanes so it is going to be tough to find a board with lots of pci-e slots. I also couldn't find a socket 1150 board that has NICs with tcp offloading. I guess you could add pci-e card to do that.

    If I remove the "Xeon 1231 v3" requirement (socket 1150), and change it to any socket 1151 xeon, what you would suggest ? It is Ok eany board up to EATX.

    Hi,
    in my current setup I use 2 SAS boards: a reflashed IBM 1015 as SAS controller and a 24 ports HP SAS expander.
    Which motherboard do you suggest that could support this expander (has a SAS controller built in) and has those features:


    IPMI
    ECC
    Xeon E31231 V3 support
    VT-x and VT-D well implemented
    2 10/100/1000 LAN with virtual machine offload engine
    1 PCi-e 3.0 slot
    Different x8 x4 slots.

    Hi,
    when a drive has been kicked of from the array it was not quick to understand which one failed.
    At the same time when I add new drives it is difficult too to discover the correct letter (not so difficult ;-)


    I propose to add color codes to part of the menu':


    Examples:


    Physical drive part:


    RED: drive kicked off from the array
    GREED: drives not used in any array
    YELLOW: Drive used in arrays


    SMART session.


    RED: Failed drives.
    YELLOW: drives you need to take a look too


    And so on.


    They are only proposals. Color codes are really usefull to quick understand and identify..

    Hi,
    here part of the log of another drive which is the same model of the one kicked off from the array:


    1 Raw_Read_Error_Rate POSR-- 118 099 006 - 183694432
    3 Spin_Up_Time PO---- 091 091 000 - 0
    4 Start_Stop_Count -O--CK 100 100 020 - 115
    5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0
    7 Seek_Error_Rate POSR-- 072 060 030 - 17864468
    9 Power_On_Hours -O--CK 099 099 000 - 1086


    Seek_error_rate and Raw_Read_Error_Rate seem out of boundaries.


    I have another 2 disk and they show all similar number but they are still on the array.


    Model is SEAGATE ST3000DM001. They all have been removed from external enclosures.


    All the remaining array show no errors.


    Regards,
    Giuseppe Chillemi

    It light is on.
    It has been kicked out of the array. I have found it "isolated" while all the other were working.
    I whish to understand if it is a driver failure (which should be recognized by SMART log) or another kind of problem.


    Regards,
    Giuseppe Chillemi