unknown serial in gui

[boecko]

Hi,

i've installed FreeNAS as a VMWare-ESX-Guest.
Two NEW SATA-Disks (each 1TB) are attached as RAW-Devices (createType="vmfsPassthroughRawDeviceMap") and build a ZFS-Mirror-Volume

It seems to me that GUI is out of sync with the actual ZFS-Pool.

Code:

# zpool status -v
  pool: vg1
 state: ONLINE
 scrub: scrub completed after 5h14m with 0 errors on Tue Oct 11 04:54:04 2011
config:

	NAME        STATE     READ WRITE CKSUM
	vg1         ONLINE       0     0     0
	  mirror    ONLINE       0     0     0
	    da1p2   ONLINE       0     0     0
	    da2p2   ONLINE       0     0     0

errors: No known data errors

In the GUI, the da2-disk is missing.


How can i correct this issue?

I cant't find any serial in /data/freenas-v1.db, so where does this info come from?
da2 is show as replacement alternative, but maybe it's just a UUID-missmatch.

Thanks

boecko

 

[92MB/s]

Hi boecko,
there's the same with me. Not only the serial is missing, also the drive has no name (ada0, ada1,...)
I'm not shure, if this is serious, or just a cosmetic error.

It happend to my FreeNAS, after I detached 1 of the 5 harddrives, to see if RAID-Z does recovering, after drive replacement. So I got this one drive, deleted the partitions and connected it again. After FreeNAS came up, and me klicking on <Replace> in View All Volumes-->View Disks, and several screen updates bei pressing <F5>, the alert LED changed from flashig-red, to steady-green again, and my zpool was healthy again. So I was happy,... at first.
But this test was with allmost no data on the drives.

In the second test, I copied 500 GB Data into the zpool, formated the same drive I took before with fat32 and powerd up FreeNAS again.
Then things changed, compared to the test before. First clicking <Replace>, and screen update with <F5> over 2 hours didn't help and seemed to do nothing. Still the red-flashing LED...
Then I rebooted the system and everthing was announced as healthy. So I was happy at first. But then I saw the missing drive name and the other things mentioned before.

So, if you discover anything (or somebody else here), please let me know.
I don't really care about drive-names and things, as long everthing works the right way.

Anybody out there who knows more about this?

Greets,
92MB/s

 

[boecko]

small update, it has to do with the output of

Code:

sysctl -b kern.geom.confxml

The "unknown" is a subsequent fault, because the webgui doesn't know the name.

• gui searches for the uuid in the xml to get the name
• invokes smartctl -i /dev/<name> to get the serial

My first uuid is found in the XML. The second not.=> go figure.

 

[boecko]

So the solution is

• dump xml
  
  Code:

  $ cd /data
  $ sysctl -b kern.geom.confxml  > geom.xml
  

• search for the missing device in the <provider>-tags
  In my case it was ad2p2 - you should check the XML for your working UUID
• copy the rawuuid
• replace the uuid in the freenas-v1.db
  
  Code:

  $ cd /data
  $ sqlite3 freenas-v1.db
  sqlite> SELECT disk_identifier FROM storage_disk WHERE disk_name='da2';
  {uuid}572f5347-f2c8-11e0-a5ca-000c29617b1c
  ….
  UPDATE storage_disk SET disk_identifier = '{uuid}<rawuuid>' WHERE disk_name='<YOURDISK>';
  ...
  

  
  

I'm guessing this happens when the geometry has changed for the kernel. Why ?