Hello everybody!
I'm posting here because I have some issues with my newly acquired hardware running FreeNAS 9.3.
My setup is as follows:
One DELL R720 connected to a DELL MD3060e using two LSI 9207-8e HBA cards.
I created a volume with 4 RAIDZ2 volumes (10 disks each), and a spare pool of 2 disks, totaling 42 disks.
I the made some tests, unplugging one of my drives. Everything is fine, one of the spares automatically replaces the dead one.
When I replug the failed drive, it’s detected. But when I try to add my new HDD to my spare pool using the volume manager (extend volume option, selecting “spare”); my server crashes and reboot.
The thing is, when I try the EXACT same procedure after reboot, my second spare is added to the spare pool without an error…
After some digging, I found that when I replace my failed HDD, the multipath is created for this disk, but FreeNAS does not detect it!
I have an error in the WebGUI: CRITICAL: "The following multipaths are not optimal: diskXX"
When I go to the multipath menu, I see that my diskXX is broken (which is fine), but the system doesn't update the new multipath for the replaced disk....
Examples with a failed Disk16:
The old path is present but broken, and the new is optimal.
Is there a way to force the system to rescan the disks, update the paths by destroying the old one ?
Thanks in advance for your support.
Sorry if my question is trivial, but I'm new with FreeNAS AND multipathing :D
I'm posting here because I have some issues with my newly acquired hardware running FreeNAS 9.3.
My setup is as follows:
One DELL R720 connected to a DELL MD3060e using two LSI 9207-8e HBA cards.
I created a volume with 4 RAIDZ2 volumes (10 disks each), and a spare pool of 2 disks, totaling 42 disks.
I the made some tests, unplugging one of my drives. Everything is fine, one of the spares automatically replaces the dead one.
When I replug the failed drive, it’s detected. But when I try to add my new HDD to my spare pool using the volume manager (extend volume option, selecting “spare”); my server crashes and reboot.
The thing is, when I try the EXACT same procedure after reboot, my second spare is added to the spare pool without an error…
After some digging, I found that when I replace my failed HDD, the multipath is created for this disk, but FreeNAS does not detect it!
I have an error in the WebGUI: CRITICAL: "The following multipaths are not optimal: diskXX"
When I go to the multipath menu, I see that my diskXX is broken (which is fine), but the system doesn't update the new multipath for the replaced disk....
Examples with a failed Disk16:
Code:
gmultipath list [...] Geom name: disk16 Type: AUTOMATIC Mode: Active/Passive UUID: 82e8b398-d206-11e4-a0c1-549f350e26c2 State: BROKEN Providers: 1. Name: multipath/disk16 Mediasize: 4000787029504 (3.7T) Sectorsize: 512 Mode: r1w1e2 State: BROKEN Geom name: disk7-144294579 Type: AUTOMATIC Mode: Active/Passive UUID: 35576f50-c9ae-11e4-9101-549f350e2682 State: OPTIMAL Providers: 1. Name: multipath/disk7-144294579 Mediasize: 4000787029504 (3.7T) Sectorsize: 512 Mode: r0w0e0 State: OPTIMAL Consumers: 1. Name: da14 Mediasize: 4000787030016 (3.7T) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE 2. Name: da56 Mediasize: 4000787030016 (3.7T) Sectorsize: 512 Mode: r1w1e1 State: PASSIVE
The old path is present but broken, and the new is optimal.
Is there a way to force the system to rescan the disks, update the paths by destroying the old one ?
Thanks in advance for your support.
Sorry if my question is trivial, but I'm new with FreeNAS AND multipathing :D
