System info:
Single Opteron on a Supermicro board, 12GB ECC Registered RAM, 6 750GB WD Green drives, 1 640GB WD Black, Asus DVD-RW, 8GB USB drive on motherboard header, Highpoint (I know, I bought it before I had ever heard of FreeNAS...) Rocket Raid 4320.
The green drives are attached to the 4320, the Black and the DVD-RW are attached to SATA ports on the system board.
For whatever reason when I try to set the RR 4320 to non-RAID mode it does not appear to work and I cannot see the green drives in FreeNAS. When I reboot and check the RR 4320 BIOS it shows the card set to RAID mode again (reboot or cold boot, same result). I created 6 JBODs with the green drives and then I could see them in FreeNAS. This is where the weirdness begins: half of the drives show up as multipath devices and half show up as normal drives in the FreeNAS GUI.
If I open a shell...
In the FreeNAS GUI I see, under View Multipaths:
and, under View Disks:
I know almost nothing about multipath, but after some searching I found a thread on the forums here where someone had un-natural multipath devices showing up in FreeNAS. The problem appeared to be solved by using gmultipath destroy <disk#> then gpart recover <driveID>. This is a test system so I thought I'd give it a shot. gmultipath destroy disk3 removed the listing in View Multipaths. gpart recover da5 (or anything else reasonable) accomplished nothing. If anyone wants the exact error message I'd be happy to do it again. I could not find any way to make the drive show up in FreeNAS again until I rebooted the machine and it appeared as, once again: multipath/disk3 da5. :bangheadonwall:
If it makes any difference I was able to create a volume with two of the multipath drives.
I have no idea why this is happening, including why my (not) very expensive RAID card will not switch to non-RAID mode and stay that way. (I also tried mixed mode which also appeared to accomplish nothing at all.)
I did not create all of the JBODs at the same time. I created two initially when I first booted the machine, then created the other four later. They were created in the order they appear in the RR4320 BIOS, though. That is to say that I started at the top of the list and worked my way down. Why it should choose da1, da2, and da5 to call multipath devices I cannot imagine.
Any help is greatly appreciated.
Single Opteron on a Supermicro board, 12GB ECC Registered RAM, 6 750GB WD Green drives, 1 640GB WD Black, Asus DVD-RW, 8GB USB drive on motherboard header, Highpoint (I know, I bought it before I had ever heard of FreeNAS...) Rocket Raid 4320.
The green drives are attached to the 4320, the Black and the DVD-RW are attached to SATA ports on the system board.
For whatever reason when I try to set the RR 4320 to non-RAID mode it does not appear to work and I cannot see the green drives in FreeNAS. When I reboot and check the RR 4320 BIOS it shows the card set to RAID mode again (reboot or cold boot, same result). I created 6 JBODs with the green drives and then I could see them in FreeNAS. This is where the weirdness begins: half of the drives show up as multipath devices and half show up as normal drives in the FreeNAS GUI.
If I open a shell...
Code:
[root@freenas ~]# camcontrol devlist <HPT DISK 0-0 4.00> at scbus0 target 0 lun 0 (da0,pass0) <HPT DISK 0-1 4.00> at scbus0 target 1 lun 0 (da1,pass1) <HPT DISK 0-2 4.00> at scbus0 target 2 lun 0 (da2,pass2) <HPT DISK 0-3 4.00> at scbus0 target 3 lun 0 (da3,pass3) <HPT DISK 0-4 4.00> at scbus0 target 4 lun 0 (da4,pass4) <HPT DISK 0-5 4.00> at scbus0 target 5 lun 0 (da5,pass5) <HPT RCM DEVICE 4.00> at scbus0 target 32 lun 0 (pass6) <WDC WD6401AALS-00J7B1 05.00K05> at scbus1 target 0 lun 0 (ada0,pass7) <ASUS DRW-24B1ST 1.04> at scbus6 target 0 lun 0 (cd0,pass8) <PNY USB 2.0 FD 1100> at scbus8 target 0 lun 0 (pass9,da6)
In the FreeNAS GUI I see, under View Multipaths:
Code:
Name Status LUN ID multipath/disk3 DEGRADED ... da5 ACTIVE 00193c0000000000 multipath/disk1 DEGRADED ... da1 ACTIVE 00193c0000000000 multipath/disk2 DEGRADED ... da2 ACTIVE 00193c0000000000
and, under View Disks:
Code:
Name Serial Disk Size ada0 WD-WMAT... 640.1 GB da0 750.0 GB da3 750.0 GB da4 750.0 GB
I know almost nothing about multipath, but after some searching I found a thread on the forums here where someone had un-natural multipath devices showing up in FreeNAS. The problem appeared to be solved by using gmultipath destroy <disk#> then gpart recover <driveID>. This is a test system so I thought I'd give it a shot. gmultipath destroy disk3 removed the listing in View Multipaths. gpart recover da5 (or anything else reasonable) accomplished nothing. If anyone wants the exact error message I'd be happy to do it again. I could not find any way to make the drive show up in FreeNAS again until I rebooted the machine and it appeared as, once again: multipath/disk3 da5. :bangheadonwall:
If it makes any difference I was able to create a volume with two of the multipath drives.
I have no idea why this is happening, including why my (not) very expensive RAID card will not switch to non-RAID mode and stay that way. (I also tried mixed mode which also appeared to accomplish nothing at all.)
I did not create all of the JBODs at the same time. I created two initially when I first booted the machine, then created the other four later. They were created in the order they appear in the RR4320 BIOS, though. That is to say that I started at the top of the list and worked my way down. Why it should choose da1, da2, and da5 to call multipath devices I cannot imagine.
Any help is greatly appreciated.