I am going to upgrade my Unraid with my old pc motherboard and cpu.  I will be going from an old AMD Athlon CPU to a Intel i5.  I will also be adding an additional 16GB or ram and a 2TB m.2 drive to upgrade my cache drive.

 

Is there anything that I need to know before swapping out to the new hardware?  I have read that I need to just makre sure that I keep the cables in the same location for the drives and take some pictures of the existing layout.  Also backup my flash just incase.  Anything else?

 

TIA, Keith

Edited December 20, 20232 yr by opiekeith

1. Current Parity check

2. Run smart test on drives (just to make sure there are no pending issues)

3. Stop all dockers & vm's

4. Turn off auto start for the array

5. Down load diagnostics

6. Stop the Array

7. Make a backup of the flash drive

8. Take a screen shot of drive assignments on the the main page

9. Cable placement shouldn't matter but drive assignment does (assign correct drive/Serial # to useage, IE Parity, Cache, Disk1 etc..)

10. Make your hardware changes.

11. Start it up..

12. Make your drive assignments.

13. Double, Triple check drive assignments.

14. You will have to start the array manually since auto start is off.

 

Someone correct me if I'm wrong... or missed something.

 

Edited December 20, 20232 yr by Russ Uno

Did not think of some of the things you listed.  TY.  I will start my parity check since it takes some time.

If you do a Parity check, the SMART tests might not be necessary since the Parity check will already have read every single block of each drives of the Array.

Maybe for the Pools ?

I just noticed that during my party check my new (to me) drive that I just added to replace a failed drive has some read errors.  I will wait for the party check to finish to investigate.

 

--Keith

I would do a long smart test on the drive(s) in question..

I know it's a pain and time consuming, I just did the same thing, the short test let some stuff slide by while the long test showed some errors.

Better to catch it now than trying to fight it in a hardware upgrade and wonder what caused it.

 

9 minutes ago, Russ Uno said:

I would do a long smart test on the drive(s) in question..

I know it's a pain and time consuming, I just did the same thing, the short test let some stuff slide by while the long test showed some errors.

Better to catch it now than trying to fight it in a hardware upgrade and wonder what caused it.

 

I 100% agree.  That will also allow me to return it if it finds anything more serious.  Better to be safe than sorry.

 

--Keith

So how long should I expect for it to take for the extended SMART test to take to finish on the 6TB drive?  Also after the parity check, the read errors never incremented after the first set.

 

and, should I close out this post and start a new one in the HD section, since it seems that my issue now is HD related?

Edited December 21, 20232 yr by opiekeith

Well I think it was 3 hrs or so for a 1TB drive for the Long Smart Test... So it could take a while.

This still could be hardware related and not the Disk itself if it was caused by loose cables.

Some place I read a post and it lead me to Western Digital about SATA Cables and their drives.

They require a SATA connector that has bumps inside to secure it in place..

Found it, WD SATA Cables

I had an issue a while back with errors on parity check that I thought was a fairly new drive (WD) but turned out to be cable connections.

I only have a couple WD drives all others are Seagate..

These are def not new drives.  This one has the following:

"Accumulated power on time, hours minutes 43712"

 

I just buy used SAS drives to connect to my IT Flashed HBA.  I have no problem waiting, its been on 2% for awhile now.  I don't want to click around much in the GUI, but the Smart health status shows passed.  After the test, I will double check to make sure the cable is good.  I did have to disable the 3rd pin on this drive, where I added some tape to the pin.

 

i will check to see if the percentage has increased any tomorrow.

I ended up stopping the test after 14 hours and it was on 2% the whole time.  Here is the SMART report from that.  I have also uploaded the latest diagnostics.

 

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.1.64-Unraid] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               HGST
Product:              HUS726060AL5215
Revision:             D7J0
Compliance:           SPC-4
User Capacity:        6,001,175,126,016 bytes [6.00 TB]
Logical block size:   512 bytes
Physical block size:  4096 bytes
LU is fully provisioned
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca2426feb40
Serial number:        NAHZK2ZS
Device type:          disk
Transport protocol:   SAS (SPL-4)
Local Time is:        Fri Dec 22 06:37:26 2023 PST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled
Read Cache is:        Enabled
Writeback Cache is:   Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Current Drive Temperature:     33 C
Drive Trip Temperature:        85 C

Manufactured in week 52 of year 2015
Specified cycle count over device lifetime:  50000
Accumulated start-stop cycles:  27
Specified load-unload count over device lifetime:  600000
Accumulated load-unload cycles:  1677
Elements in grown defect list: 261

Vendor (Seagate Cache) information
  Blocks sent to initiator = 80134226334187520

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:          0      753         0       753   98043026    3167084.029          15
write:         0     4297         0      4297   19402902     875973.236          73
verify:        0        0         0         0     204724          5.341           0

Non-medium error count:        0

SMART Self-test log
Num  Test              Status                 segment  LifeTime  LBA_first_err [SK ASC ASQ]
     Description                              number   (hours)
# 1  Background long   Failed in segment -->       7   43715          13150208 [0x3 0x5d 0x1]

Long (extended) Self-test duration: 51471 seconds [14.3 hours]

Background scan results log
  Status: waiting until BMS interval timer expires
    Accumulated power on time, hours:minutes 43737:16 [2624236 minutes]
    Number of background scans performed: 229,  scan progress: 0.00%
    Number of background medium scans performed: 229

   #  when        lba(hex)    [sk,asc,ascq]    reassign_status
   1 43668:51  0000000007aca6e8  [3,11,0]   Recovered via rewrite in-place
   2 43668:48  0000000003c663c8  [3,11,0]   Recovered via rewrite in-place
   3 43668:47  0000000002cac718  [3,11,0]   Recovered via rewrite in-place
   4 43668:47  0000000002c78930  [3,11,0]   Recovered via rewrite in-place
   5 43668:46  0000000001cc1208  [3,11,0]   Recovered via rewrite in-place
   6 43668:46  0000000001c10ed0  [3,11,0]   Recovered via rewrite in-place
   7 43668:41  0000000000c78de0  [3,11,0]   Recovered via rewrite in-place
   8 43668:41  0000000000c60b58  [3,11,0]   Recovered via rewrite in-place
   9 43668:41  0000000000c23930  [3,11,0]   Recovered via rewrite in-place
  10 43668:41  0000000000c11068  [3,11,0]   Recovered via rewrite in-place
  11 43668:41  0000000000c11060  [3,11,0]   Recovered via rewrite in-place

General statistics and performance log page:
  General access statistics and performance:
    Number of read commands: 14648407550
    Number of write commands: 4776372095
    number of logical blocks received: 1710885225927
    number of logical blocks transmitted: 6185710994363
    read command processing intervals: 0
    write command processing intervals: 0
    weighted number of read commands plus write commands: 0
    weighted read command processing plus write command processing: 0
  Idle time:
    Idle time intervals: 1235886083
      in seconds: 61794304.150
      in hours: 17165.084

Protocol Specific port log page for SAS SSP
relative target port id = 1
  generation code = 3
  number of phys = 1
  phy identifier = 0
    attached device type: SAS or SATA device
    attached reason: power on
    reason: unknown
    negotiated logical link rate: phy enabled; 6 Gbps
    attached initiator port: ssp=1 stp=1 smp=1
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5000cca2426feb41
    attached SAS address = 0x500605b006585f70
    attached phy identifier = 0
    Invalid DWORD count = 4
    Running disparity error count = 0
    Loss of DWORD synchronization count = 1
    Phy reset problem count = 0
relative target port id = 2
  generation code = 3
  number of phys = 1
  phy identifier = 1
    attached device type: no device attached
    attached reason: unknown
    reason: power on
    negotiated logical link rate: phy enabled; unknown
    attached initiator port: ssp=0 stp=0 smp=0
    attached target port: ssp=0 stp=0 smp=0
    SAS address = 0x5000cca2426feb42
    attached SAS address = 0x0
    attached phy identifier = 0
    Invalid DWORD count = 0
    Running disparity error count = 0
    Loss of DWORD synchronization count = 0
    Phy reset problem count = 0

 

hades-diagnostics-20231222-0844.zip

Edited December 22, 20232 yr by opiekeith

1 hour ago, opiekeith said:

Elements in grown defect list: 261

This doesn't look, also the long test failed, disk should be replaced.

I submitted for a return and replacement drive.  Hoping to get a new one this time around.