segator

Members
  • Posts

    175
  • Joined

  • Last visited

Posts posted by segator

  1. SMART report seems OK. Cables are easiest thing to check. Both ends of SATA and power. Are these all motherboard connections?

    yes, my motherboard have 12 sata connnection on 2 controllers a marvel an intel.

    I don't know exactly this disk what controller is connected because I use Disk enclousure, Tomorrow I check all, Thanks

  2. Today unraid get disk errors(when 'mover' process)

    See Image

    ID_0e021888b39be5be2e744d2eade018ec

     

    Two days ago I updated to unraid6 beta15 from 14b

     

    SMART DATA

    smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.19.4-unRAID] (local build)
    Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
    
    === START OF READ SMART DATA SECTION ===
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
      3 Spin_Up_Time            0x0027   220   142   021    Pre-fail  Always       -       5958
      4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       1628
      5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
      7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
      9 Power_On_Hours          0x0032   088   088   000    Old_age   Always       -       8895
    10 Spin_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
    11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
    12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       588
    192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       84
    193 Load_Cycle_Count        0x0032   174   174   000    Old_age   Always       -       79873
    194 Temperature_Celsius     0x0022   116   099   000    Old_age   Always       -       36
    196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
    197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
    198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       0
    199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       1
    200 Multi_Zone_Error_Rate   0x0008   200   200   000    Old_age   Offline      -       83

     

    Log say lot of times this..

    Apr 22 14:51:14 aina kernel: md: disk1 read error, sector=2577964672
    Apr 22 14:51:14 aina kernel: md: disk1 read error, sector=2577964680
    Apr 22 14:51:14 aina kernel: md: disk1 read error, sector=2577964688
    Apr 22 14:51:14 aina kernel: md: disk1 read error, sector=2577964696
    Apr 22 14:51:14 aina kernel: md: disk1 read error, sector=2577964704
    Apr 22 14:51:14 aina kernel: md: disk1 read error, sector=2577964712
    Apr 22 14:51:14 aina kernel: md: disk1 read error, sector=2577964720
    Apr 22 14:51:14 aina kernel: md: disk1 read error, sector=2577964728
    Apr 22 14:51:14 aina kernel: md: disk1 read error, sector=2577964736
    Apr 22 14:51:14 aina kernel: md: disk1 read error, sector=2577964744
    Apr 22 14:51:14 aina kernel: md: disk1 read error, sector=2577964752
    Apr 22 14:51:14 aina kernel: md: disk1 read error, sector=2577964760
    Apr 22 14:51:14 aina kernel: md: disk1 read error, sector=2577964768
    Apr 22 14:52:40 aina kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 acti                                                on 0x0
    Apr 22 14:52:40 aina kernel: ata6.00: irq_stat 0x40000001
    Apr 22 14:52:40 aina kernel: ata6.00: failed command: READ DMA EXT
    Apr 22 14:52:40 aina kernel: ata6.00: cmd 25/00:00:20:60:ab/00:02:da:00:00/e0 ta                                                g 18 dma 262144 in
    Apr 22 14:52:40 aina kernel:         res 51/40:2f:f0:60:ab/00:01:da:00:00/e0 Ema                                                sk 0x9 (media error)
    Apr 22 14:52:40 aina kernel: ata6.00: status: { DRDY ERR }
    Apr 22 14:52:40 aina kernel: ata6.00: error: { UNC }
    Apr 22 14:52:40 aina kernel: ata6.00: configured for UDMA/133
    Apr 22 14:52:40 aina kernel: sd 6:0:0:0: [sdd] UNKNOWN Result: hostbyte=0x00 dri                                                verbyte=0x08
    Apr 22 14:52:40 aina kernel: sd 6:0:0:0: [sdd] Sense Key : 0x3 [current] [descri                                                ptor]
    Apr 22 14:52:40 aina kernel: sd 6:0:0:0: [sdd] ASC=0x11 ASCQ=0x4
    Apr 22 14:52:40 aina kernel: sd 6:0:0:0: [sdd] CDB:
    Apr 22 14:52:40 aina kernel: cdb[0]=0x28: 28 00 da ab 60 20 00 02 00 00
    Apr 22 14:52:40 aina kernel: blk_update_request: I/O error, dev sdd, sector 3668                                                664560
    Apr 22 14:52:40 aina kernel: ata6: EH complete
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664496
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664504
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664512
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664520
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664528
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664536
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664544
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664552
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664560
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664568
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664576
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664584
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664592
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664600
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664608
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664616
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664624
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664632
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664640
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664648
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664656
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664664
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664672
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664680
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664688
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664696
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664704
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664712
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664720
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664728
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664736
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664744
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664752
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664760
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664768
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664776
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664784
    Apr 22 14:52:40 aina kernel: md: disk1 read error, sector=3668664792
    

     

    Do you think I need to replace the disk? If I need to change drive, I want to install new 8TB but for this I need to change parity drive to 8TB drive and actual 6TB parity drive to data replace drive. How I can do that without lose nothing?

     

    read errors means that the data is corrupted?

     

    Thanks for all.

  3. Very Interesting all statics info, thanks.

     

    But If I use raid5, I have performance  + extra data protection(like second parity drive, that unraid not support native),

    6TB drive 10K RPM is more expensive than 3 normal 3TB drive.

    Anyway I could use two SSD 1TB Drive SSD(cache drive) to "solve/ignore" the unraid write speed problem.

     

  4. I have the next  plugins and dockers.

     

    plugins

    Dynamic active stream

    cache directories

    s3 sleep

    autoFAN

    systemInformation

    docker search

    system stats

    system temp

    SNAP

    Virtual machine(All KVM VM mount on cache dir)

     

     

    Docker(all mount on cache or /mnt/user/...)

     

    Crashplan

    mariaDB

    owncloud

    plexMediaServer

    ReverseProxy

    ruTorrent

     

  5. I Can't get parity drive spin down, I have SSD cache drive, I undestand if the mover is not doing nothing the parity drive no need to spin up and do nothing.

     

    Well My Parity drive is Always writing something for each 5 seconds I can see write counter increment in 2 or 3 bytes, but I don't know what is the thing that cause this.

    I don't have process mounting on /mnt/user0.....

    I don't understand what is the problem :(

  6. Hi,

     

    You now how to on press server power button, UnraidOS do a gracefull shutdown?

    stop smb,nfs.... stop array.. and shutdown..

     

    I don't have any problem going to server webpage and do it mannualy but my girlfriend don't know how to do and don't know learn to do.

     

    Thanks!

  7. I have asrock C2550D4I runing unraid 6b14 WORK PERFECT but its necesary update marvel firmware(old versions have a bug that the sata disconnects the HDD  on intensive process like parity check)

     

    After update bios and marvel controller(very easy process) all work perfect, Power consumption 34W all HDD spin down WIth a Gold PSU.

     

    The only problem I have if that I cannot control Fan speed from unRAID :( I want to stop fans when HDD Spin down.

  8. Solved,

     

    KVM support LVM passthru

     

    example

     

    < disk type='block' device='disk' >

    < source dev='/dev/vgpool/test'/ >

     

    you need to create manually the LVM struct from unraid

     

    The Drive is OUT of the array, SNAP plugin  Not support LVM I think.

     

    Work well but performance it's not improved :(

  9. Well for your answers I can understand that the drives are OK, and yet I can use on my unRAID server.

     

    This value.. what's mean?

    188  Command Timeout  0x0032  100  098  000  Old age  Always  Never  8590065719

     

    Thanks for all

  10. I have 2x ST32000542AS 2TB

     

    I see some values that I think is bad.

     

    Disk 2 attached to port: sdb

    ID# ATTRIBUTE NAME FLAG VALUE WORST THRESH TYPE UPDATED FAILED RAW VALUE

    1 Raw Read Error Rate 0x000f 111 099 006 Pre-fail Always Never 30744169

    3 Spin Up Time 0x0003 100 100 000 Pre-fail Always Never 0

    4 Start Stop Count 0x0032 099 099 020 Old age Always Never 1953

    5 Reallocated Sector Ct 0x0033 100 100 036 Pre-fail Always Never 0

    7 Seek Error Rate 0x000f 071 060 030 Pre-fail Always Never 38758436838

    9 Power On Hours 0x0032 086 086 000 Old age Always Never 12289

    10 Spin Retry Count 0x0013 100 100 097 Pre-fail Always Never 0

    12 Power Cycle Count 0x0032 100 100 020 Old age Always Never 895

    183 Runtime Bad Block 0x0032 100 100 000 Old age Always Never 0

    184 End-to-End Error 0x0032 100 100 099 Old age Always Never 0

    187 Reported Uncorrect 0x0032 100 100 000 Old age Always Never 0

    188 Command Timeout 0x0032 100 098 000 Old age Always Never 8590065719

    189 High Fly Writes 0x003a 100 100 000 Old age Always Never 0

    190 Airflow Temperature Cel 0x0022 075 049 045 Old age Always Never 25 (Min/Max 22/25)

    194 Temperature Celsius 0x0022 025 051 000 Old age Always Never 25 (0 14 0 0 0)

    195 Hardware ECC Recovered 0x001a 043 018 000 Old age Always Never 30744169

    197 Current Pending Sector 0x0012 100 100 000 Old age Always Never 0

    198 Offline Uncorrectable 0x0010 100 100 000 Old age Offline Never 0

    199 UDMA CRC Error Count 0x003e 200 200 000 Old age Always Never 0

    240 Head Flying Hours 0x0000 100 253 000 Old age Offline Never 207021718648330

    241 Total LBAs Written 0x0000 100 253 000 Old age Offline Never 4137080360

    242 Total LBAs Read 0x0000 100 253 000 Old age Offline Never 3015114723

     

     

    Disk 3 attached to port: sdc

    ID# ATTRIBUTE NAME FLAG VALUE WORST THRESH TYPE UPDATED FAILED RAW VALUE

    1 Raw Read Error Rate 0x000f 114 099 006 Pre-fail Always Never 66560523

    3 Spin Up Time 0x0003 100 100 000 Pre-fail Always Never 0

    4 Start Stop Count 0x0032 099 099 020 Old age Always Never 1989

    5 Reallocated Sector Ct 0x0033 100 100 036 Pre-fail Always Never 0

    7 Seek Error Rate 0x000f 067 060 030 Pre-fail Always Never 68804620599

    9 Power On Hours 0x0032 086 086 000 Old age Always Never 12386

    10 Spin Retry Count 0x0013 100 100 097 Pre-fail Always Never 0

    12 Power Cycle Count 0x0032 100 100 020 Old age Always Never 889

    183 Runtime Bad Block 0x0032 100 100 000 Old age Always Never 0

    184 End-to-End Error 0x0032 100 100 099 Old age Always Never 0

    187 Reported Uncorrect 0x0032 100 100 000 Old age Always Never 0

    188 Command Timeout 0x0032 100 099 000 Old age Always Never 4295032886

    189 High Fly Writes 0x003a 099 099 000 Old age Always Never 1

    190 Airflow Temperature Cel 0x0022 074 050 045 Old age Always Never 26 (Min/Max 21/26)

    194 Temperature Celsius 0x0022 026 050 000 Old age Always Never 26 (0 13 0 0 0)

    195 Hardware ECC Recovered 0x001a 044 015 000 Old age Always Never 66560523

    197 Current Pending Sector 0x0012 100 100 000 Old age Always Never 0

    198 Offline Uncorrectable 0x0010 100 100 000 Old age Offline Never 0

    199 UDMA CRC Error Count 0x003e 200 200 000 Old age Always Never 0

    240 Head Flying Hours 0x0000 100 253 000 Old age Offline Never 223896645154297

    241 Total LBAs Written 0x0000 100 253 000 Old age Offline Never 289126755

    242 Total LBAs Read 0x0000 100 253 000 Old age Offline Never 2410213088

     

     

    I need to change this drives before crash? Server alarm about 'Command Timeout' on this two drives

     

    I don't like values Raw Read Error Rate and Seek Error Rate and Hardware ECC Recovered

     

    What do you think?

     

    And if I want to change this 2 drives with 1 6TB(Yes I Have 6TB drive on parity, I can add 6TB drive data)

    what is the procedure?

  11. I'm interested in this setup. Can you post the .cfg file you used or a short description of how you implemented it? I'm really new to this so I may need some guidance. Thanks!

    Hi, sorry I deleted CFG because I migrate to KVM(less CPU usage) if you are interested i Can help you to setup but

    The performance is bad if  you want to share with NFS/CIFS mounts.

     

    I Desestimated in Home use, beucase downlaod station saturate all the system with the mount system.

    I'm trying to use p9fs KVM mounts in XPenology but Xpenology don't have support with p9 mounts.. :(

    /

  12. I having lot of this in syslog.

     

    pr  1 08:48:33 Tower kernel: ata11.00: exception Emask 0x0 SAct 0x80000 SErr 0x0 action 0x6 frozen

    Apr  1 08:48:33 Tower kernel: ata11.00: failed command: WRITE FPDMA QUEUED

    Apr  1 08:48:33 Tower kernel: ata11.00: cmd 61/20:98:80:23:00/00:00:00:00:00/40 tag 19 ncq 16384 out

    Apr  1 08:48:33 Tower kernel:        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

    Apr  1 08:48:33 Tower kernel: ata11.00: status: { DRDY }

    Apr  1 08:48:33 Tower kernel: ata11: hard resetting link

    Apr  1 08:48:34 Tower kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

    Apr  1 08:48:34 Tower kernel: ata11.00: supports DRM functions and may not be fully accessible

    Apr  1 08:48:34 Tower kernel: ata11.00: supports DRM functions and may not be fully accessible

    Apr  1 08:48:34 Tower kernel: ata11.00: configured for UDMA/133

    Apr  1 08:48:34 Tower kernel: ata11.00: device reported invalid CHS sector 0

    Apr  1 08:48:34 Tower kernel: ata11: EH complete

     

    what's mean, something wrong with disks?

  13. yes it's work but i have another idea.

    If i set rutorrent save temporal download on a cache drive and when end move to /mnt/user0/xxxx

     

    /mnt/user0 is non Cache array, direct write on array.

    I think, I don't have the mover problem.

    But i don't have if is correctly to save directly to /mnt/user0