On Thursday 29 October 2009 11:36:38 Robert Noland wrote: > Ok, if you are getting this... It may be helpful if you can run "zdb > -uuu zroot", so I can see what is going on with the root block pointer. > I think you should be able to do that from fixit. Also note that you > don't have the latest version of the loader if it is printing "lld", > though as long as all of the drives are detected it likely won't make a > difference. The "can't read MOS" error is the first attempt to read > from the pool after probing all of the devices to sort out the > configuration. Everything up to this point reads data directly from the > vdev labels on each drive, so this is the first time that it tries to > read from the pool. > Sorry I forgot about this part. Here is zdb -uuu zroot Uberblock magic = 0000000000bab10c version = 13 txg = 111 guid_sum = 14036990686815153767 timestamp = 1257636491 UTC = Sat Nov 7 23:28:11 2009 rootbp = [L0 DMU objset] 400L/200P DVA[0]=<0:110004a000:400> DVA[1]=<0:40038400:400> DVA[2]=<0:1980041c00:400> fletcher4 lzjb LE contiguous birth=111 fill=126 cksum=7e96f92e7:357c99e1eb9:b7d10db3a713:1ac2df05bd147aReceived on Mon Nov 09 2009 - 07:48:21 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:57 UTC