Another "Boot Pool Status [...] unrecoverable error" question

[AlcSi]

Hi, so, I guess I'll have to make a new USB bootable key, but I just wanted to confirm.

Output of 'zpool status -v' :

Code:

 pool: freenas-boot
 state: ONLINE
status: One or more devices has experienced an unrecoverable error.  An
        attempt was made to correct the error.  Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
        using 'zpool clear' or replace the device with 'zpool replace'.
   see: http://illumos.org/msg/ZFS-8000-9P
  scan: scrub repaired 0 in 0 days 00:02:38 with 0 errors on Sun Oct 20 03:47:38 2019
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          da0p2     ONLINE       0     0     5

errors: No known data errors

  pool: raidp1
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: scrub repaired 0 in 0 days 04:27:28 with 0 errors on Sun Oct 13 04:28:27 2019
config:

        NAME                                            STATE     READ WRITE CKSUM
        raidp1                                          ONLINE       0     0     0
          raidz2-0                                      ONLINE       0     0     0
            gptid/d235c9d8-5d5f-11e5-9c9a-002522264f82  ONLINE       0     0     0
            gptid/d284f8c0-5d5f-11e5-9c9a-002522264f82  ONLINE       0     0     0
            gptid/ae7ce72d-7761-11e6-9f9e-002522264f82  ONLINE       0     0     0
            gptid/d3195df7-5d5f-11e5-9c9a-002522264f82  ONLINE       0     0     0
            gptid/d3619671-5d5f-11e5-9c9a-002522264f82  ONLINE       0     0     0
            gptid/d3a7940d-5d5f-11e5-9c9a-002522264f82  ONLINE       0     0     0

errors: No known data errors

Now, also note that 'smartctl -t long /dev/da0p2' gives the following error :

Code:

/dev/da0p2: Unable to detect device type
Please specify device type with the -d option.

I don't know if it's common for USB keys but I'm guessing it's a bad thing for my boot device, right ?

 

[PhiloEpisteme]

I don't know if it's common for USB keys but I'm guessing it's a bad thing for my boot device, right ?

I wouldn't be surprised if the USB key doesn't support SMART tests. If it is experiencing issues you may want to replace it now while it still works rather than waiting for it outright fail. Don't forget to backup your configs and any encryption keys if you're using pool encryption.