Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

Freenas-boot pool DEGRADED while scrub boot pool itself twice!!

Western Digital Drives - The Preferred Drives of FreeNAS and TrueNAS CORE

nonjtjt

Neophyte
Joined
May 29, 2020
Messages
4
Hi there,
I experience this twice in a month.
degraded 1.png

From the alarm date-time tag The boot pool was DEGRADED while scrubbing the boot pool itself.
I already reinstall the OS in new USB stick.
But afraid of happening again.

I have zfs check down here. vvvvv

This one is the first time:
Code:
  pool: freenas-boot
 state: DEGRADED
status: One or more devices has experienced an error resulting in data
        corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
        entire pool from backup.
   see: http://illumos.org/msg/ZFS-8000-8A
  scan: scrub repaired 0 in 0 days 00:02:51 with 204 errors on Sat May  9 03:47:51 2020
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  DEGRADED     0     0   204
          da0p2     DEGRADED     0     0   408  too many errors

errors: Permanent errors have been detected in the following files:

        freenas-boot/ROOT/default@2020-04-26-14:44:27:/usr/local/lib/migrate93/django/db/models/query_utils.py
        freenas-boot/ROOT/default@2020-04-26-14:44:27:/usr/local/lib/migrate93/freenasUI/services/migrations/0154_auto__add_field_ssh_ssh_host_ed25519_key__add_field_ssh_ssh_host_ed255.py
        freenas-boot/ROOT/default@2020-04-26-14:44:27:/usr/local/lib/migrate93/django/contrib/gis/db/backends/spatialite/__pycache__/__init__.cpython-37.pyc
        freenas-boot/ROOT/default@2020-04-26-14:44:27:/usr/local/lib/migrate93/django/conf/locale/lt/LC_MESSAGES/django.mo
        freenas-boot/ROOT/default@2020-04-26-14:44:27:/usr/local/lib/migrate93/django/contrib/gis/db/backends/spatialite/__pycache__/adapter.cpython-37.pyc
        freenas-boot/ROOT/default@2020-04-26-14:44:27:/usr/local/lib/migrate93/django/contrib/formtools/tests/tests.py
        freenas-boot/ROOT/default@2020-04-26-14:44:27:/usr/local/lib/migrate93/django/conf/locale/ar/__pycache__/formats.cpython-37.pyc
        freenas-boot/ROOT/default@2020-04-26-14:44:27:/usr/local/lib/migrate93/django/conf/locale/sv/formats.py
        freenas-boot/ROOT/default@2020-04-26-14:44:27:/usr/local/lib/migrate93/django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo
        freenas-boot/ROOT/default@2020-04-26-14:44:27:/usr/local/share/locale/es/LC_MESSAGES/gnupg2.mo
        freenas-boot/ROOT/default@2020-04-26-14:44:27:/usr/local/lib/migrate93/django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo
        freenas-boot/ROOT/default@2020-04-26-14:44:27:/usr/local/share/locale/hu/LC_MESSAGES/glib20.mo
        freenas-boot/ROOT/default@2020-04-26-14:44:27:/usr/local/lib/migrate93/django/conf/locale/be/LC_MESSAGES/django.mo

and many many moreeeee


And This is the latest:
Code:
  pool: freenas-boot
 state: DEGRADED
status: One or more devices has experienced an error resulting in data
        corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
        entire pool from backup.
   see: http://illumos.org/msg/ZFS-8000-8A
  scan: scrub repaired 0 in 0 days 00:04:29 with 98 errors on Sat May 30 03:49:29 2020
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  DEGRADED     0     0    98
          da0p2     DEGRADED     0     0   197  too many errors

errors: Permanent errors have been detected in the following files:

        freenas-boot/ROOT/11.3-U3.1@2020-05-09-02:26:23:/usr/local/lib/perl5/5.30/unicore/lib/SB/UP.pl
        freenas-boot/ROOT/11.3-U3.1@2020-05-09-02:26:23:/usr/local/lib/perl5/site_perl/mach/5.30/sys/vtoc.ph
        freenas-boot/ROOT/11.3-U3.1@2020-05-09-02:26:23:/usr/local/lib/perl5/site_perl/mach/5.30/sys/wait.ph
        freenas-boot/ROOT/11.3-U3.1@2020-05-09-02:26:23:/usr/local/lib/perl5/5.30/pod/perliol.pod
        freenas-boot/ROOT/11.3-U3.1@2020-05-09-02:26:23:/usr/local/lib/perl5/5.30/unicore/lib/STerm/Y.pl
        freenas-boot/ROOT/11.3-U3.1@2020-05-09-02:26:23:/usr/local/lib/perl5/5.30/unicore/lib/Lb/XX.pl
        freenas-boot/ROOT/11.3-U3.1@2020-05-09-02:26:23:/usr/local/lib/perl5/5.30/unicore/lib/Sc/Arab.pl
        freenas-boot/ROOT/11.3-U3.1@2020-05-09-02:26:23:/usr/local/lib/perl5/site_perl/mach/5.30/sys/cdefs.ph
        freenas-boot/ROOT/11.3-U3.1@2020-05-09-02:26:23:/usr/local/lib/perl5/site_perl/mach/5.30/sysexits.ph

and many many moreeeee


Anyone have an idea?
Does this happening because scrubbing boot pool? If turn off boot pool scrub will this problem solve? So how to do that, if it is the right way to do.
Does boot pool needed to be scrub? Shouldn't it be only read when start the freenas and let go? There're no change after start on boot pool right?

Regard
 

Tigersharke

BOfH in User's clothing
Administrator
Moderator
Joined
May 18, 2016
Messages
759
STRONGLY recommend transferring your boot pool from usb stick to an SSD or HDD. The old approved method of implementing boot pools on usb stick is no longer recommended and also now actively discouraged. Even the very best USB sticks are not intended for the continual or near continual use that FreeNAS will cause, therefore they develop problems and eventually fail.
 

Basil Hendroff

Neophyte Sage
Joined
Jan 4, 2014
Messages
1,409
@Tigersharke While I agree that SSD is the preferred approach, when using small form factor h/w for FreeNAS such as HP microservers, SATA slots are at a premium so USB boot is still an attractive option. Given the choice, I would use SSD. An external SSD-USB drive, I guess, is an option, but that would detract from the compact form factor.

@nonjtjt Change to SSD if you are able to, otherwise, this post may be useful https://www.ixsystems.com/community/threads/boot-drive-degrades.57500/. If you have to use USB, mirrored USB boot drives are definitely recommended.
 
Last edited:

Heracles

Neophyte Sage
Joined
Feb 2, 2018
Messages
903
Agree with @Basil Hendroff here... All my 3 servers are running from USB sticks for that very reason : I will rather have these bays used for data storage HD than for boot device. For my 2 main servers, I mirrored them and I do regular backups with TrueCommand. Should I end up in trouble, I prefer to re-install and restore instead of loosing space or reducing redundancy. Being powered off most of the time, Thanatos' boot is not even mirrored...
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
2,729
Small M.2 SSDs aren't expensive, and work well with a USB->M.2 adapter. They're also an option.
 
Top