All four hard drives not appearing when attempting to create new zpool via GUI

[leenux_tux]

Not sure if this is a bug, however, somethings definitely not right so I figured I would post it anyway....

Background info....
Had a few hard drive issues, SMART was reporting some bad sectors for two of my drives (3X2TB RAIDz) backed off all my data, destroyed the zpool, ran loads of different tests (including manufacturers tests), initially errors found, however, after doing a low level format all looks OK, very odd.....

Purchased a new hard drive as I figured I would make use of the spare slot I have in my Chenbro case and do some speed tests for RAIDz (with four drives) versus RAID10. I use VMWare via iSCSI quite a lot. Once I was happy I had made the right choice for my hard drive config I can then re-create all relevant volumes and start loading the data back............

Installed the new drive (Western Digital WD20EURS), booted up FreeNAS, went to the GUI to create a RAIDz with all four drives and...................... eh ? Only three drives showing ?..............ada0, ada1 and ada2. (see here)

Rebooted the system to make sure all drives were being seen by the motherboard, all looks OK.
Checked "dmesg" to make sure FreeNAS is seeing the drive, yep, all there (relevant output below)

--------------------------------------------------------------------------------------------
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <WDC WD20EURS-63S48Y0 51.0AB51> ATA-8 SATA 2.x device
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <ST2000DL004 HD204UI 1AQ10001> ATA-8 SATA 2.x device
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada2 at ahcich2 bus 0 scbus3 target 0 lun 0
ada2: <SAMSUNG HD204UI 1AQ10003> ATA-8 SATA 2.x device
ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
ada3 at ahcich3 bus 0 scbus4 target 0 lun 0
ada3: <ST2000DL004 HD204UI 1AQ10001> ATA-8 SATA 2.x device
ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
-----------------------------------------------------------------------------


Note The new drive IS being seen (ada0). But ada3 isn't. I tried swapping the drives around and it's always ada3 that is not seen by the "Create New Volume" part of the FreeNAS GUI ??.

Here is the other strange thing though, when I click on "Import Volume" all four drives appeared. See here.

I know the drives can be "used" by FreeNAS as I created a RAID10 zpool via the command line using the following commands.....

zpool create TANK mirror ada0 ada2
zpool add TANK mirror ada1 ada3

(output from zpool status)
-----------------------------------------------------------------------------


-------------------------------------------------------------------------------


I had to reboot the box before I could auto-import the pool though. The pool then appeared in "Storage" on FreeNAS GUI.

Apologies if this is not a "bug", but like I said, it's definitely not right !!

 

[William Grzybowski]

This is known to be a possible bug in 8.0.x. Reporting bugs usually go better if you're running the latest release ;)

 

[leenux_tux]

This is known to be a possible bug in 8.0.x. Reporting bugs usually go better if you're running the latest release ;)

I'm running version 8.0.4, P3 ??

 

[pirateghost]

I'm running version 8.0.4, P3 ??

Maybe you didnt see the latest version on the front page?