TrueNAS and multipaths & Dashboard

SubnetMask

Contributor
Joined
Jul 27, 2017
Messages
129
I'm currently running FreeNAS 11.1-U7, and to be honest, due to bad, unexplained experiences with I believe it was 11.2 where the system would just halt and reboot for no reason that could be determined, I'm a 'bit' gunshy about upgrading (11.1-U7 has been ROCK SOLID). However, I'm experimenting with TrueNAS Core 12.0-U3 for the possibility of upgrading.

The first thing that I've found is it seems multipaths are flaky (or at least appear to be). On my 'test' system, I have 11 disks, six 6TB and five 4TB, all SAS with a dual expander backplane and dual SAS controllers on the server. All disks show up in Multipaths, but when I go to create a pool, not all of the multipaths show up. As you can see below, four of the 11 show up as their active 'singlepath' name. Any thoughts on this?


1619565138494.png


The other thing is on the dashboard. The 'System Information' is fine, but the 'CPU' and 'Memory' just sit there with the 'spinning wheels'. The systems been up for 18 minutes and the browser has been connected for 17 of those minutes, and it never stopped 'spinning' or populated the panes. I've rebooted the system a few times and tried different browsers, no change. Even after it had been up for a few days, it was the same. Any ideas?

1619565415419.png
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
As you can see below, four of the 11 show up as their active 'singlepath' name. Any thoughts on this?
What do you see with gmultipath list ?

The other thing is on the dashboard. The 'System Information' is fine, but the 'CPU' and 'Memory' just sit there with the 'spinning wheels'.
Maybe something to do with the middleware... maybe try a restart (service middlewared restart) or look in the middleware logs /var/log/middleware.log
 

SubnetMask

Contributor
Joined
Jul 27, 2017
Messages
129
gmultipath list gives me the following, which matches up with the 'Multipaths' list in the UI:
Code:
truenas% gmultipath list
Geom name: disk8
Type: AUTOMATIC
Mode: Active/Passive
UUID: 0bc3ce32-a7a4-11eb-9ad3-90b11c0fb45a
State: OPTIMAL
Providers:
1. Name: multipath/disk8
   Mediasize: 6001175125504 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   State: OPTIMAL
Consumers:
1. Name: da21
   Mediasize: 6001175126016 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: ACTIVE
2. Name: da10
   Mediasize: 6001175126016 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: PASSIVE

Geom name: disk4
Type: AUTOMATIC
Mode: Active/Passive
UUID: 0b0a07a7-a7a4-11eb-9ad3-90b11c0fb45a
State: OPTIMAL
Providers:
1. Name: multipath/disk4
   Mediasize: 6001175125504 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   State: OPTIMAL
Consumers:
1. Name: da20
   Mediasize: 6001175126016 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: ACTIVE
2. Name: da9
   Mediasize: 6001175126016 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: PASSIVE

Geom name: disk6
Type: AUTOMATIC
Mode: Active/Passive
UUID: 0b616393-a7a4-11eb-9ad3-90b11c0fb45a
State: OPTIMAL
Providers:
1. Name: multipath/disk6
   Mediasize: 6001175125504 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   State: OPTIMAL
Consumers:
1. Name: da19
   Mediasize: 6001175126016 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: ACTIVE
2. Name: da8
   Mediasize: 6001175126016 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: PASSIVE

Geom name: disk7
Type: AUTOMATIC
Mode: Active/Passive
UUID: 0b8f5d25-a7a4-11eb-9ad3-90b11c0fb45a
State: OPTIMAL
Providers:
1. Name: multipath/disk7
   Mediasize: 6001175125504 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   State: OPTIMAL
Consumers:
1. Name: da18
   Mediasize: 6001175126016 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: ACTIVE
2. Name: da7
   Mediasize: 6001175126016 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: PASSIVE

Geom name: disk9
Type: AUTOMATIC
Mode: Active/Passive
UUID: 0bf6281a-a7a4-11eb-9ad3-90b11c0fb45a
State: OPTIMAL
Providers:
1. Name: multipath/disk9
   Mediasize: 6001175125504 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   State: OPTIMAL
Consumers:
1. Name: da17
   Mediasize: 6001175126016 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: ACTIVE
2. Name: da6
   Mediasize: 6001175126016 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: PASSIVE

Geom name: disk5
Type: AUTOMATIC
Mode: Active/Passive
UUID: 0b32edf6-a7a4-11eb-9ad3-90b11c0fb45a
State: OPTIMAL
Providers:
1. Name: multipath/disk5
   Mediasize: 6001175125504 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r0w0e0
   State: OPTIMAL
Consumers:
1. Name: da16
   Mediasize: 6001175126016 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: ACTIVE
2. Name: da5
   Mediasize: 6001175126016 (5.5T)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r1w1e1
   State: PASSIVE

Geom name: disk12
Type: AUTOMATIC
Mode: Active/Passive
UUID: c68ca5bc-12c9-11e9-a106-0007430c5064
State: OPTIMAL
Providers:
1. Name: multipath/disk12
   Mediasize: 4000787029504 (3.6T)
   Sectorsize: 512
   Mode: r0w0e0
   State: OPTIMAL
Consumers:
1. Name: da15
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
2. Name: da3
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Mode: r1w1e1
   State: PASSIVE

Geom name: disk1
Type: AUTOMATIC
Mode: Active/Passive
UUID: 5ef8a0ef-3939-11ea-8566-9840bb99dbd8
State: OPTIMAL
Providers:
1. Name: multipath/disk1
   Mediasize: 4000787029504 (3.6T)
   Sectorsize: 512
   Mode: r0w0e0
   State: OPTIMAL
Consumers:
1. Name: da14
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
2. Name: da2
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Mode: r1w1e1
   State: PASSIVE

Geom name: disk2
Type: AUTOMATIC
Mode: Active/Passive
UUID: 5f175017-3939-11ea-8566-9840bb99dbd8
State: OPTIMAL
Providers:
1. Name: multipath/disk2
   Mediasize: 4000787029504 (3.6T)
   Sectorsize: 512
   Mode: r0w0e0
   State: OPTIMAL
Consumers:
1. Name: da13
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
2. Name: da1
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Mode: r1w1e1
   State: PASSIVE

Geom name: disk3
Type: AUTOMATIC
Mode: Active/Passive
UUID: 5f28a153-3939-11ea-8566-9840bb99dbd8
State: OPTIMAL
Providers:
1. Name: multipath/disk3
   Mediasize: 4000787029504 (3.6T)
   Sectorsize: 512
   Mode: r0w0e0
   State: OPTIMAL
Consumers:
1. Name: da12
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
2. Name: da0
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Mode: r1w1e1
   State: PASSIVE

Geom name: disk26
Type: AUTOMATIC
Mode: Active/Passive
UUID: b614a777-2982-11ea-ad36-d4ae52916505
State: OPTIMAL
Providers:
1. Name: multipath/disk26
   Mediasize: 4000787029504 (3.6T)
   Sectorsize: 512
   Mode: r0w0e0
   State: OPTIMAL
Consumers:
1. Name: da11
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Mode: r1w1e1
   State: ACTIVE
2. Name: da4
   Mediasize: 4000787030016 (3.6T)
   Sectorsize: 512
   Mode: r1w1e1
   State: PASSIVE

truenas% 


I copied the middlewared.log off and skimmed through it, but nothing jumped out at me. I also tried restarting the middleware, but no effect (Wouldn't rebooting the machine accomplish the same end result?).
 

Attachments

  • middleware.txt
    199.1 KB · Views: 178

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Wouldn't rebooting the machine accomplish the same end result?
Not if there's a race condition... if something that's needed isn't yet started during boot, perhaps something was hung waiting for it, which the restart might have allowed a "try again" which wasn't happening automatically. Anyway, no-go, so bad luck on that attempt.

which matches up with the 'Multipaths' list in the UI
If there's nothing there in the system, at least we know why the GUI is missing things.

Perhaps going through dmesg will shed some light on it.
 

SubnetMask

Contributor
Joined
Jul 27, 2017
Messages
129
Not if there's a race condition... if something that's needed isn't yet started during boot, perhaps something was hung waiting for it, which the restart might have allowed a "try again" which wasn't happening automatically. Anyway, no-go, so bad luck on that attempt.

That makes sense.

If there's nothing there in the system, at least we know why the GUI is missing things.

Not sure I follow. What do you mean 'If there's nothing there in the system'? The list of disks/multipaths under 'Storage > Multipaths' matches the output from gmultipath list, aside from the obvious formatting differences.
 
Last edited:
Top