smart prefailure attribute

  • I just installed these four new WD Red hard drives in my new built system, and today I received this message.
    One is for OMV, and four is for RAID 10. I hope my hard drives not dying this fast...



    Edit: I ran a short-selft test, and all the drives are passed.


    Code
    cat /proc/mdstat
    Personalities : [raid10]
    md127 : active raid10 sdb[0] sde[3] sdd[2] sdc[1]
          5860270080 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU]





  • I did the long-run test, and I found one of the disk has ATA Error Count.
    Now I got this errors.

    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    Einmal editiert, zuletzt von tinh_x7 ()

  • I re-arranged my SATA cables, so it has better cable management/air flow.
    Now I have ATA Error and ACPI Error.


    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro



  • OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

  • OK from your spec I do not see anything out of the ordinary.


    Are all WD red drives new?
    Do you have those syslog message/errors for all WD reds?


    It is most likely some incompatibility - see my thread about a year ago!


    You can try:
    Change sata cable
    Disable alpm in bios
    Different kernel

  • I swapped out two new Sata cables for two drives, and changed kernel boot to 3.2.0.
    Now I have OMV drive error: EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro


    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    2 Mal editiert, zuletzt von tinh_x7 ()

  • Here's my HDDs copy speed:


    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

  • I think we aren't getting anywhere.


    I have the disadvantage if only using taptalk for now and most of the code u posted is unreadable - so I might have missed something


    From my understanding u posted two different errors in this thread


    Sata related fpdma queued error
    Acpi error



    The 1st can be due to a number if reasons, cable, backplane, insufficient power supply, kernel issue, alpm issue, bug in drive fw.


    Also see here:
    http://lime-technology.com/wik…rive_interface_issue_.234


    U said that u exchanged cables and I haven't read that those errors are still there so they are either solved by the cable exchange or kernel change



    The 2nd acpi issue I have no clue but: load bios defaults, update bios
    U could still try the back ports kernel

  • After swapped out new sata cables, and improved cable management, I don't have any more fpdma error, but just a OMV remount-ro error.
    I'm also switched to kernel 3.2.0.


    I resolved the ACPI error by added 'ACPI=off' into my grub settings.
    However, if ACPI is off, then my rtcwake is unable to shutdown.


    Code
    rtcwake: open failed: /sys/class/rtc/rtc0/device/power/wakeup: No such file or directory 
    rtcwake: /dev/rtc0 not enabled for wakeup events


    Edit: I''ve tried both Kernel with fast boot disabled and enabled, but the errors still persist.


    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    9 Mal editiert, zuletzt von tinh_x7 ()

  • I'm also notice that my sleep time and wake up time are incorrect:
    they suppose to be 22:40, and wakeup is 16:00.
    I'm using /etc/crontab to created the schedule.
    My hwclock showing correct local time.


    Code
    40 22 * * 1-4 root /usr/sbin/rtcwake -m disk -s 62400


    OMV v5.0
    Asus Z97-A/3.1; i3-4370
    32GB RAM Corsair Vengeance Pro

    2 Mal editiert, zuletzt von tinh_x7 ()

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!