CRITICAL: The following multipaths are not optimal: disk5

Status
Not open for further replies.
K

KentShades

FreeNAS Certified Owner
Joined
Jan 4, 2016
Messages
61
Geom name: disk5
Type: AUTOMATIC
Mode: Active/Passive
UUID: 839d5021-7f1e-11e5-b658-0cc47a204b14
State: DEGRADED
Providers:
1. Name: multipath/disk5
Mediasize: 8001563217920 (7.3T)
Sectorsize: 4096
Mode: r2w2e5
State: DEGRADED
Consumers:
1. Name: da13
Mediasize: 8001563222016 (7.3T)
Sectorsize: 4096
Mode: r3w3e6
State: FAIL
2. Name: da1
Mediasize: 8001563222016 (7.3T)
Sectorsize: 4096
Mode: r3w3e6
State: ACTIVE


Is the drive bad here? I check the volumes, and everything is saying it's cool. But don't see how to fix this.
 
D

dlavigne

Guest
What command is that output from? Also, what is the output of zpool status ? (please use Insert -> Code when pasting)
 
K

KentShades

FreeNAS Certified Owner
Joined
Jan 4, 2016
Messages
61
All good.

Code:
[root@SuperNAS] ~# zpool status
  pool: freenas-boot
state: ONLINE
  scan: scrub repaired 0 in 0h0m with 0 errors on Mon May  2 03:45:12 2016
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            ada2p2  ONLINE       0     0     0
            ada3p2  ONLINE       0     0     0

errors: No known data errors

  pool: tank
state: ONLINE
  scan: scrub repaired 0 in 249h21m with 0 errors on Wed Apr 27 09:21:52 2016
config:

        NAME                                            STATE     READ WRITE CKSUM
        tank                                            ONLINE       0     0     0
          raidz1-0                                      ONLINE       0     0     0
            gptid/c08c0e9e-832a-11e5-8578-0cc47a204b14  ONLINE       0     0     0
            gptid/c0f996e5-832a-11e5-8578-0cc47a204b14  ONLINE       0     0     0
            gptid/c164129a-832a-11e5-8578-0cc47a204b14  ONLINE       0     0     0
            gptid/c1cfa17b-832a-11e5-8578-0cc47a204b14  ONLINE       0     0     0
          raidz1-1                                      ONLINE       0     0     0
            gptid/050996bb-832b-11e5-8578-0cc47a204b14  ONLINE       0     0     0
            gptid/057977f5-832b-11e5-8578-0cc47a204b14  ONLINE       0     0     0
            gptid/05eba0b8-832b-11e5-8578-0cc47a204b14  ONLINE       0     0     0
            gptid/065ef825-832b-11e5-8578-0cc47a204b14  ONLINE       0     0     0
          raidz1-2                                      ONLINE       0     0     0
            gptid/4d739a95-832b-11e5-8578-0cc47a204b14  ONLINE       0     0     0
            gptid/4de7a5b1-832b-11e5-8578-0cc47a204b14  ONLINE       0     0     0
            gptid/4e5aee93-832b-11e5-8578-0cc47a204b14  ONLINE       0     0     0
            gptid/4ec6dc66-832b-11e5-8578-0cc47a204b14  ONLINE       0     0     0
        logs
          gptid/ba5380cd-832b-11e5-8578-0cc47a204b14    ONLINE       0     0     0
        cache
          gptid/8b6b597d-832b-11e5-8578-0cc47a204b14    ONLINE       0     0     0
 
D

dlavigne

Guest
Interesting. The output in your original post, was that from the alert or a command? Also, which "Build" version of FreeNAS (from System -> Information).
 
K

KentShades

FreeNAS Certified Owner
Joined
Jan 4, 2016
Messages
61
Command line. FreeNAS-9.3-STABLE-201602031011 - I am planning on pushing a update currently.
 
K

KentShades

FreeNAS Certified Owner
Joined
Jan 4, 2016
Messages
61
Applied my update to 9.2, I see that 9.10 is also available and 9.2 is now maintenance mode. Should I go to 9.10 now? Looks like the update fixed my issue.

Code:
Geom name: disk5
Type: AUTOMATIC
Mode: Active/Passive
UUID: 839d5021-7f1e-11e5-b658-0cc47a204b14
State: OPTIMAL
Providers:
1. Name: multipath/disk5
   Mediasize: 8001563217920 (7.3T)
   Sectorsize: 4096
   Mode: r2w2e5
   State: OPTIMAL
Consumers:
1. Name: da13
   Mediasize: 8001563222016 (7.3T)
   Sectorsize: 4096
   Mode: r3w3e6
   State: ACTIVE
2. Name: da1
   Mediasize: 8001563222016 (7.3T)
   Sectorsize: 4096
   Mode: r3w3e6
   State: PASSIVE
 
Mr_N

Mr_N

Patron
Joined
Aug 31, 2013
Messages
289
i dont think you can 'upgrade' from 9.3 back to 9.2 :)
 
gpsguy

gpsguy

Active Member
Joined
Jan 22, 2012
Messages
4,472
I *think* the OP has the version numbers mixed up.

I gather he was on FreeNAS-9.3-STABLE-201602031011 and updating it to a newer version of 9.3-xxx

Now, he has discovered that 9.3 is in maintenance mode and wants to know if he should upgrade to 9.10

Mr_N said:
i dont think you can 'upgrade' from 9.3 back to 9.2
Click to expand...
 
C

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
1. You should upgrade to 9.10.
2. If you reboot, those counters and such are cleared, so the issue will appear to have gone away (but it most certainly hasn't).
3. What is the output of smartctl -a /dev/da1?
 
K

KentShades

FreeNAS Certified Owner
Joined
Jan 4, 2016
Messages
61
Will do my upgrade as well! Looks like the drive is bad, and will be doing a replacement. Created a new thread for the replacement as well.


Code:
=== START OF INFORMATION SECTION ===
Vendor:               HGST
Product:              HUH728080AL4200
Revision:             A7J0
Compliance:           SPC-4
User Capacity:        8,001,563,222,016 bytes [8.00 TB]
Logical block size:   4096 bytes
LB provisioning type: unreported, LBPME=0, LBPRZ=0
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca23b4305ac
Serial number:        2EH5VN9V
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Mon Jun  6 10:07:18 2016 PDT
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

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

Current Drive Temperature:     27 C
Drive Trip Temperature:        85 C

Manufactured in week 35 of year 2015
Specified cycle count over device lifetime:  50000
Accumulated start-stop cycles:  9
Specified load-unload count over device lifetime:  600000
Accumulated load-unload cycles:  230
Elements in grown defect list: 0

Vendor (Seagate) cache information
  Blocks sent to initiator = 8191255259381760

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     1248         0      1248    2401463      54304.357           2
write:         0        0         0         0     472501      22849.059           0
verify:        0        0         0         0      35564          0.000           0

Non-medium error count:        0

No self-tests have been logged
 
Last edited:
Ericloewe

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
KentShades said:
Will do my upgrade as well! Looks like the drive is bad, and will be doing a replacement. Created a new thread for the replacement as well.


PHP: 
=== START OF INFORMATION SECTION ===
Vendor:               HGST
Product:              HUH728080AL4200
Revision:             A7J0
Compliance:           SPC-4
User Capacity:        8,001,563,222,016 bytes [8.00 TB]
Logical block size:   4096 bytes
LB provisioning type: unreported, LBPME=0, LBPRZ=0
Rotation Rate:        7200 rpm
Form Factor:          3.5 inches
Logical Unit id:      0x5000cca23b4305ac
Serial number:        2EH5VN9V
Device type:          disk
Transport protocol:   SAS (SPL-3)
Local Time is:        Mon Jun  6 10:07:18 2016 PDT
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Enabled

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

Current Drive Temperature:     27 C
Drive Trip Temperature:        85 C

Manufactured in week 35 of year 2015
Specified cycle count over device lifetime:  50000
Accumulated start-stop cycles:  9
Specified load-unload count over device lifetime:  600000
Accumulated load-unload cycles:  230
Elements in grown defect list: 0

Vendor (Seagate) cache information
  Blocks sent to initiator = 8191255259381760

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     1248         0      1248    2401463      54304.357           2
write:         0        0         0         0     472501      22849.059           0
verify:        0        0         0         0      35564          0.000           0

Non-medium error count:        0

No self-tests have been logged
Click to expand...
What's with the colors?
 
K

KentShades

FreeNAS Certified Owner
Joined
Jan 4, 2016
Messages
61
Not sure, just added it when I added the code, not happening in free NAS. I did the upgrade without any issues. Should I mark the drive offline, and then hit replace on it considering it's showing it as online still?

0675.image_001653C7.png

But when checking command line I get the following:

Code:
Geom name: disk5
Type: AUTOMATIC
Mode: Active/Passive
UUID: 839d5021-7f1e-11e5-b658-0cc47a204b14
State: DEGRADED
Providers:
1. Name: multipath/disk5
   Mediasize: 8001563217920 (7.3T)
   Sectorsize: 4096
   Mode: r2w2e5
   State: DEGRADED
Consumers:
1. Name: da13
   Mediasize: 8001563222016 (7.3T)
   Sectorsize: 4096
   Mode: r3w3e6
   State: FAIL
2. Name: da1
   Mediasize: 8001563222016 (7.3T)
   Sectorsize: 4096
   Mode: r3w3e6
   State: ACTIVE



So disk 5 seems to be bad, but how do I make sure I do a clean replacement on this?
 
Mirfster

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,215
C

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
You have uncorrectable errors per SMART, and the fact that a path has failed confirms the disk is in fact failing.

Do a disk replacement like this:

1. Offline the failed disk per the GUI.
2. Physically remove the disk and install the new disk.
3. Run the command "service ix-multipath start"
4. Replace the disk per the GUI.

If you can't do a hotswap (or don't want to) you can skip step 3 as long as the new disk is in the system on bootup. The ix-multipath service runs on bootup and will create the proper multipath connections for you. Otherwise you must invoke it yourself manually as I described above.
 
M

mav@

iXsystems
iXsystems
Joined
Sep 29, 2011
Messages
1,428
cyberjock said:
If you can't do a hotswap (or don't want to) you can skip step 3 as long as the new disk is in the system on bootup. The ix-multipath service runs on bootup and will create the proper multipath connections for you. Otherwise you must invoke it yourself manually as I described above.
Click to expand...

In 9.10 it should work automagically on disk hot-plug via respective devd events.
 
Status
Not open for further replies.

Important Announcement for the TrueNAS Community.

The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums.

Related topics on forums.truenas.com for thread: "CRITICAL: The following multipaths are not optimal: disk5"

Similar threads

K
  • Locked
Replacing a Drive
Replies
3
Views
978
KentShades
K
parski
ZFS pool migration issue
Replies
2
Views
2K
parski
parski
dexbot
  • Locked
SOLVED Raidz-1 Pool will not import - One or more devices missing from system
2
Replies
24
Views
8K
dexbot
dexbot
I
Unable to import volume
Replies
2
Views
972
Igor Voskresenskiy
I
J
Freenas 11.3U1 thinks that 3 of 4 drives in pool are bad.
Replies
1
Views
2K
jktmas
J
Top