Error on freenas-boot

[John Gorst]

FreeNAS-9.3-STABLE-201505130355 HP microserver N54L 8gb 2x3tb mirror, 1x 64gb ssd, 1x 8gb USB boot (SanDisk... can't remember type and still in system resilvering)

Overnight I got the error:

The boot volume state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.
​

I saved the configuration and I have started the process of adding a mirrored USB key to the freenas-boot which I have been meaning to do for ages.

After 15 minutes I did a 'zpool status' to see how things are getting on

Code:

  pool: freenas-boot
state: ONLINE
status: One or more devices is currently being resilvered.  The pool will
    continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
  scan: resilver in progress since Mon Jun 15 10:20:06 2015
        6.51M scanned out of 5.60G at 26.6K/s, 61h8m to go
        5.61M resilvered, 0.11% done
config:

    NAME                                            STATE     READ WRITE CKSUM
    freenas-boot                                    ONLINE       0     0     0
      mirror-0                                      ONLINE       0     0     0
        gptid/93c72004-86a2-11e4-a1fc-a0b3ccdf0943  ONLINE       0     0     1
        da1p2                                       ONLINE       0     0     0  (resilvering)

This seems a little slow to me?

Also the GUI was initially frozen with the 'waiting' box but has now exited before the boot drive has finished resilvering.

1) Is it normal for it to be this slow to resilver? Is this a sign of a problem with the device?

2) Will the appropriate GRUB boot 'magic' be installed automatically or will I need to do it manually, especially as the GUI exited before the resilvering was complete? (found this bug https://bugs.pcbsd.org/issues/6993 ) How can I check that GRUB is installed other than rebooting with only the one USB key installed.

3) Given I am resilvering from a 'dodgy' device, should I actually just make a fresh install on a pair of new USB keys and load on the saved config? (I am about to upgrade to a better box HP DL160 G6, so that may be a good time to do a fresh install?)

4) Which log file is error from SRUBS saved to. I can't find any mention of a bad Scrub to find out exactly what the issue was.

Thanks for any pointers


edit: Things have now speeded up, hopefully all will be good!

Code:

  pool: freenas-boot
state: ONLINE
status: One or more devices is currently being resilvered.  The pool will
    continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
  scan: resilver in progress since Mon Jun 15 10:20:06 2015
        1.11G scanned out of 5.60G at 668K/s, 1h57m to go
        1.11G resilvered, 19.77% done
config:

    NAME                                            STATE     READ WRITE CKSUM
    freenas-boot                                    ONLINE       0     0     0
      mirror-0                                      ONLINE       0     0     0
        gptid/93c72004-86a2-11e4-a1fc-a0b3ccdf0943  ONLINE       0     0     1
        da1p2                                       ONLINE       0     0     0  (resilvering)

errors: No known data errors

 

[hugovsky]

You seem to have a dying USB drive. You should change it ASAP.

 

[John Gorst]

Code:

  pool: freenas-boot
state: ONLINE
  scan: scrub repaired 0 in 0h11m with 0 errors on Mon Jun 15 12:45:51 2015
config:

    NAME                                            STATE     READ WRITE CKSUM
    freenas-boot                                    ONLINE       0     0     0
      mirror-0                                      ONLINE       0     0     0
        gptid/93c72004-86a2-11e4-a1fc-a0b3ccdf0943  ONLINE       0     0     0
        da1p2                                       ONLINE       0     0     0

errors: No known data errors

My mirror of freenas-boot seems to be up and the pool as survived a Scrub and appeared to do it at about 9M/s which is probably reasonable for USB drives?

Using gpart list gives the following information indicating there are two partitions on the new USB key - is this sufficient to assume I can boot from the device?

Code:

Geom name: da1
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 15633374
first: 34
entries: 128
scheme: GPT
Providers:
1. Name: da1p1
   Mediasize: 524288 (512k)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 17408
   Mode: r0w0e0
   rawuuid: 92432a74-133f-11e5-a4e2-a0b3ccdf0943
   rawtype: 21686148-6449-6e6f-744e-656564454649
   label: 1
   length: 524288
   offset: 17408
   type: bios-boot
   index: 1
   end: 1057
   start: 34
2. Name: da1p2
   Mediasize: 8003739648 (7.5G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 544768
   Mode: r1w1e1
   rawuuid: 925b46cc-133f-11e5-a4e2-a0b3ccdf0943
   rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b
   label: 1
   length: 8003739648
   offset: 544768
   type: freebsd-zfs
   index: 2
   end: 15633367
   start: 1064
Consumers:
1. Name: da1
   Mediasize: 8004304896 (7.5G)
   Sectorsize: 512
   Mode: r1w1e2

 

[gpsguy]

You created the mirror incorrectly, ie. the new device should have used a gptid,

When you upgrade to the new box, I recommend doing a fresh install on a new pair of flash drives and restore your old configuration.

Given I am resilvering from a 'dodgy' device, should I actually just make a fresh install on a pair of new USB keys and load on the saved config? (I am about to upgrade to a better box HP DL160 G6, so that may be a good time to do a fresh install?)

 

[John Gorst]

I used the GUI to add the new USB flash drive - shouldn't this automatically use the gptid?
I am just upgrading to the latest version... I wonder if on reboot if the drive will be picked up by its gptid?

 

[John Gorst]

gptid used after a software upgrade and reboot

 

[mjws00]

I think there is an issue with the add mirror code through the GUI. It doesn't use gptid correctly iirc. It adds as your pool shows. Nothing to worry about, but different than adding the mirror at install. You may be able to find the bug report. I'm On my phone so I can't.