-
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
Help with DEGRADED multipath
- Thread starter Tomer
- Start date
- Status
kdragon75
Wizard
- Joined
- Aug 7, 2016
- Messages
- 2,457
It may not be the disk. As one path the that disk is up and working, Its would seem as likely to be a bad port, cable, HBA, or expander. We need to identify the disk and cable path in question. Do you have your drive bays labeled by disk serial number?
Hi.
I have 20+ disk in my bay, so labaling is preety hard..
Anyway i can identify bay11 via led on or off..
Chris Moore
Hall of Famer
- Joined
- May 2, 2015
- Messages
- 10,080
If that works for you. Some people have had difficulty with getting that function to work. Would you be so kind as to share your hardware configuration with us? It is generally best if we have some idea what we are working with when we offer suggestions.
There is also this script that may help you identify drives if there is any question:
Utility: disklist.pl, for listing partition, gptid, slot, devices, disktype, serial num, & multipath
https://forums.freenas.org/index.ph...ktype-serial-num-multipath.59319/#post-421424
Chris Moore
Hall of Famer
- Joined
- May 2, 2015
- Messages
- 10,080
If you are sure that you want to replace the disk, this resource might help with the steps involved.
Replacing a failed/failing disk
https://forums.freenas.org/index.php?resources/replacing-a-failed-failing-disk.75/
Once you are certain you have identified the correct physical disk, you would offline it through the GUI. It is important that you are sure that you are pulling out the correct physical disk as we had a user this past week that removed the wrong disk and ended up with two disks out of the pool when their pool was only designed to support one failure. They were using mirrors.
It is generally best if you tell us (in addition to the hardware) what your pool configuration is. It can shape our guidance to know details like that.
Hi all. thanks for supporting:)
my hardware is -hp-dl360G7 with 2X HBA adapter's and a old netapp draw.. containing 24disks(model NAJ-0801) FreeNAS-11.0-RELEASE (a2dc21583)
thanks for the script: the output..
also gmultipath status shows:
sas info:
any help resolving that issue will be great...if any more info needed it is not a problem...thanks.
my hardware is -hp-dl360G7 with 2X HBA adapter's and a old netapp draw.. containing 24disks(model NAJ-0801) FreeNAS-11.0-RELEASE (a2dc21583)
thanks for the script: the output..
also gmultipath status shows:
sas info:
any help resolving that issue will be great...if any more info needed it is not a problem...thanks.
- Joined
- Jul 3, 2015
- Messages
- 926
In my experience of multipathed systems then its quite common to see one path fail as a result of an impending disk failure. At this time I would assume its the drive as thats the easiest and replace it. If however the problem should re-appear with a new drive in the same location then that should start sending alarm bells.
- Joined
- Jul 3, 2015
- Messages
- 926
Just noticed this in one of your outputs:
multipath/disk19 OPTIMAL da41 (ACTIVE)
da20 (PASSIVE)
multipath/disk19-65239471 OPTIMAL da40 (ACTIVE)
da19 (PASSIVE)
This looks like like two multipathed devices have been given the same name albeit with a small difference '-65239471'.
Its a bit late now for this system but I think its always worth naming your multipath devices before building your pool and giving them a better naming scheme reflecting their physical location in the system. So for example on your system with one JBOD 'J1S5'. FreeNAS will auto name the multipath device disk1, disk2, etc but you can do the following:
gmultipath destroy disk1
gmultipath label -v J1S5 /dev/da4 /da27
Do this BEFORE you build your pool and then once all the devices are named you can create the pool from the UI as you would normally.
Now based on the initial output you gave at the top of the thread you would know without any guess work that 'J1S5' is the drive with the issue. Offline the drive, remove and replace. Then name your new device using its associated da numbers (which are often the same as the last but do check to be sure) gmultipath label -v J1S5 /dev/da4 /da27 then replace the drive via the UI and all your names are back to good again.
Its worth noting that these drive names are stored on the drive itself so its not a god idea to move drives from one bay to another without renaming the drives otherwise you'll get very confused.
multipath/disk19 OPTIMAL da41 (ACTIVE)
da20 (PASSIVE)
multipath/disk19-65239471 OPTIMAL da40 (ACTIVE)
da19 (PASSIVE)
This looks like like two multipathed devices have been given the same name albeit with a small difference '-65239471'.
Its a bit late now for this system but I think its always worth naming your multipath devices before building your pool and giving them a better naming scheme reflecting their physical location in the system. So for example on your system with one JBOD 'J1S5'. FreeNAS will auto name the multipath device disk1, disk2, etc but you can do the following:
gmultipath destroy disk1
gmultipath label -v J1S5 /dev/da4 /da27
Do this BEFORE you build your pool and then once all the devices are named you can create the pool from the UI as you would normally.
Now based on the initial output you gave at the top of the thread you would know without any guess work that 'J1S5' is the drive with the issue. Offline the drive, remove and replace. Then name your new device using its associated da numbers (which are often the same as the last but do check to be sure) gmultipath label -v J1S5 /dev/da4 /da27 then replace the drive via the UI and all your names are back to good again.
Its worth noting that these drive names are stored on the drive itself so its not a god idea to move drives from one bay to another without renaming the drives otherwise you'll get very confused.
- Joined
- Jul 3, 2015
- Messages
- 926
Like @Chris Moore said, offline the drive via the UI, physically remove it and replace it with a new one. Then via the UI select the off-lined drive and click replace selecting your newly installed drive.
- Status
Similar threads
- Locked
