packinpennies
Cadet
- Joined
- Feb 11, 2018
- Messages
- 9
Hi,
My system was running stable with the boot pool living on a mirrored set of flash drives. Recently one failed, and the other went to a degraded state and showed errors as well, so I decided to replace the flash drives with an internal SSD. I took a backup of the FreeNAS configuration, and then booted from a flash drive with the installation media on it and installed it to the SSD. Next, I went to the web GUI and uploaded the config backup I took recently.
After rebooting, I noticed the pool had a handful of errors, so I ran a scrub. This is the result when I input zpool status -v into the shell:
Clearly this is not ideal. So, I did a fresh install and loaded from my config with the same result.
My question is, does this indicate that my SSD is damaged/corrupted, or just that the config I took was corrupted to begin with? I really don't want to have to go purchase another SSD.
Thanks!
My system was running stable with the boot pool living on a mirrored set of flash drives. Recently one failed, and the other went to a degraded state and showed errors as well, so I decided to replace the flash drives with an internal SSD. I took a backup of the FreeNAS configuration, and then booted from a flash drive with the installation media on it and installed it to the SSD. Next, I went to the web GUI and uploaded the config backup I took recently.
After rebooting, I noticed the pool had a handful of errors, so I ran a scrub. This is the result when I input zpool status -v into the shell:
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:00:02 with 30 errors on Sun Feb 3 12:11:52 2019 config: NAME STATE READ WRITE CKSUM freenas-boot DEGRADED 0 0 72 ada4p2 DEGRADED 0 0 186 too many errors errors: Permanent errors have been detected in the following files: <metadata>:<0x26> freenas-boot/ROOT/default@2019-02-03-16:57:45:<0x0> freenas-boot/ROOT/default@2019-02-03-16:57:45:/data freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/lib/python3.6/site-packages/idna/__pycache__/intranges.cpython-36.opt-1.pyc freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/lib/python3.6/lib-dynload freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/www/dojo/dojox/charting/widget/BidiSupport.js.map freenas-boot/ROOT/default@2019-02-03-16:57:45:/boot/modules/amdgpu_vega10_sos_bin.ko freenas-boot/ROOT/default@2019-02-03-16:57:45:/conf/base/etc/rc.shutdown.local freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/lib/python3.6/site-packages/pytz/zoneinfo/Australia freenas-boot/ROOT/default@2019-02-03-16:57:45:/boot/modules/radeon_SUMO_uvd_bin.ko freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/lib/python3.6/site-packages/dojango/forms/__pycache__/formsets.cpython-36.opt-1.pyc freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/lib/python3.6/site-packages/flask/__pycache__/logging.cpython-36.pyc freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/lib/python3.6/site-packages/ldap/controls/__pycache__/libldap.cpython-36.pyc freenas-boot/ROOT/default@2019-02-03-16:57:45:/boot/modules/radeon_TAHITI_uvd_bin.ko freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/lib/python3.6/site-packages/django/contrib/auth/__pycache__/checks.cpython-36.opt-1.pyc freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/lib/python3.6/site-packages/babel/locale-data/lv.dat freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/www/freenasUI/sharing/__pycache__ freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/bin/hptraidconf freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/lib/python3.6/site-packages/botocore/docs/__pycache__/paginator.cpython-36.opt-1.pyc freenas-boot/ROOT/default@2019-02-03-16:57:45:/boot/modules/radeon_bonaire_uvd_bin.ko freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/share/locale/ja_JP.SJIS/LC_COLLATE freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/www/freenasUI/plugins/__pycache__ freenas-boot/ROOT/default@2019-02-03-16:57:45:/usr/local/lib/python3.6/site-packages/pytz/zoneinfo/Etc freenas-boot/ROOT/default@2019-02-03-16:57:45:/boot/modules/radeon_hawaii_uvd_bin.ko freenas-boot/ROOT/default@2019-02-03-16:57:45:/boot/modules/amdgpu_tonga_mec2_bin.ko
Clearly this is not ideal. So, I did a fresh install and loaded from my config with the same result.
My question is, does this indicate that my SSD is damaged/corrupted, or just that the config I took was corrupted to begin with? I really don't want to have to go purchase another SSD.
Thanks!