9.3 - Gui issues after power outage

[ThomasNAS]

Hi,

after a power outage the dataset / volume list was empty. I imported the datasets gain via geli key and password. Looks good at the beginning. But in the dropdown no volume in the dropdown to mount a volume (I could add a screenshot afterwards, if required)
I tried it with both of my pools. No success. Interesting is that they are all visible on the left menu.

After no success via GUI I tried to import it via CLI, just for testing

[root@NSBAAM01] zpool import
[root@NSBAAM01] zpool import hcssv001
[root@NSBAAM01] zpool import fsz002
[root@NSBAAM01] /mnt# zfs set mountpoint=/mnt/fsz002 fsz002
[root@NSBAAM01] /mnt# zfs set mountpoint=/mnt/hcssv001 hcssv001
[root@NSBAAM01] zfs mount -a

[root@NSBAAM01] /mnt/hcssv001# ls
./ ../ backups/ hcssv001_psds0001/ hcssv001_psds0002/ jails/ media01/ nfstest/



At least this is working (also for pool 1). After restarting cifs service, also my shares are working now fine again.
I my nooby opionion the zfs pools are completely fine and there is only a issue with the "freenas layer". Gui dataset / volume list is still empty
I found this post, but I'm not sure if this could be also the solution for me.

Any ideas?


infos to my system, tell me if you need more:

Version: FreeNAS-9.3-STABLE-201602031011


Overview pools / disks
pool 1 (2 RG) (degraded, after power outage 1 disks failed. But should be no big issue at the moment)
Jun 14 23:06:56 NSBAAM01 ada1: <WDC WD30EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
Jun 14 23:06:56 NSBAAM01 ada2: <WDC WD30EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
Jun 14 23:06:56 NSBAAM01 ada3: <WDC WD30EFRX-68AX9N0 80.00A80> ATA-9 SATA 3.x device
Jun 14 23:06:56 NSBAAM01 ada4: <WDC WD30EFRX-68EUZN0 80.00A80> ATA-9 SATA 3.x device
Jun 14 23:06:56 NSBAAM01 ada5: <WDC WD30EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
Jun 14 23:06:56 NSBAAM01 ada6: <WDC WD30EFRX-68EUZN0 82.00A82> ATA-9 SATA 3.x device
Jun 14 23:06:56 NSBAAM01 da0: <ATA WDC WD30EFRX-68E 0A82> Fixed Direct Access SCSI-6 device
Jun 14 23:06:56 NSBAAM01 da5: <ATA WDC WD30EFRX-68E 0A82> Fixed Direct Access SCSI-6 device
Jun 14 23:06:56 NSBAAM01 da6: <ATA WDC WD30EFRX-68E 0A82> Fixed Direct Access SCSI-6 device
Jun 14 23:06:56 NSBAAM01 da7: <ATA WDC WD30EFRX-68E 0A82> Fixed Direct Access SCSI-6 device


pool 2 (1 RG)
Jun 14 23:06:56 NSBAAM01 da1: <ATA Samsung SSD 750 1B6Q> Fixed Direct Access SCSI-6 device
Jun 14 23:06:56 NSBAAM01 da2: <ATA Samsung SSD 750 1B6Q> Fixed Direct Access SCSI-6 device
Jun 14 23:06:56 NSBAAM01 da3: <ATA Samsung SSD 750 1B6Q> Fixed Direct Access SCSI-6 device
Jun 14 23:06:56 NSBAAM01 da4: <ATA Samsung SSD 750 1B6Q> Fixed Direct Access SCSI-6 device

Show : zpool list

NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
freenas-boot 119G 8.39G 111G - - 7% 1.00x ONLINE -
fsz002 1.80T 1.04T 773G - 22% 58% 1.00x ONLINE -
hcssv001 27.2T 14.3T 13.0T - 13% 52% 1.22x DEGRADED -

Show : zfs list

NAME USED AVAIL REFER MOUNTPOINT
freenas-boot 8.39G 107G 31K none
freenas-boot/.system 217M 107G 135M legacy
freenas-boot/.system/configs-0dc2ca1e7fa9464d8c4d7c4fd81f6855 62.5M 107G 62.5M legacy
freenas-boot/.system/cores 11.4M 107G 11.4M legacy
freenas-boot/.system/rrd-0dc2ca1e7fa9464d8c4d7c4fd81f6855 25K 107G 25K legacy
freenas-boot/.system/samba4 104K 107G 104K legacy
freenas-boot/.system/syslog-0dc2ca1e7fa9464d8c4d7c4fd81f6855 8.23M 107G 8.23M legacy
freenas-boot/ROOT 8.16G 107G 25K none
freenas-boot/ROOT/Initial-Install 8.16G 107G 524M /
freenas-boot/ROOT/Initial-Install-Clone 1K 107G 512M /
freenas-boot/ROOT/Wizard-2016-02-23_22:21:55 1K 107G 513M legacy
freenas-boot/ROOT/Wizard-2016-02-24_17:34:02 1K 107G 513M legacy
freenas-boot/ROOT/Wizard-2016-02-27_17:52:17 1K 107G 513M /
freenas-boot/ROOT/Wizard-2016-02-27_18:23:27 1K 107G 513M /
freenas-boot/ROOT/Wizard-2016-02-27_22:19:39 1K 107G 515M /
freenas-boot/ROOT/Wizard-2016-07-14_20:13:51 1K 107G 8.14G /
freenas-boot/ROOT/Wizard-2016-07-14_20:33:41 1K 107G 8.14G /
freenas-boot/ROOT/default 7.41M 107G 516M legacy
freenas-boot/grub 6.97M 107G 6.79M legacy
fsz002 775G 520G 140K /mnt
fsz002/hcn0005 1.55G 520G 1.55G /mnt/hcn0005
fsz002/psm0003 141G 520G 141G -
fsz002/pss0004 632G 520G 629G /mnt/pss0004
hcssv001 11.4T 7.58T 166K /mnt
hcssv001/backups 2.05T 7.58T 2.05T /mnt/backups
hcssv001/hcssv001_psds0001 5.20G 495G 5.20G /mnt/hcssv001_psds0001
hcssv001/hcssv001_psds0002 16.4G 484G 16.4G /mnt/hcssv001_psds0002
hcssv001/jails 153K 7.58T 153K /mnt/jails
hcssv001/media01 9.35T 7.58T 9.32T /mnt/media01
hcssv001/nfstest 153K 7.58T 153K /mnt/nfstest
hcssv001/test2_zvol 5.08G 7.59T 1.77M -

LOG after actions from GUI

Show : import pool 1

Jun 14 23:34:25 NSBAAM01 GEOM_ELI: Device gptid/883f05e0-9765-11e6-be31-0cc47a1a4ce4.eli created.
Jun 14 23:34:25 NSBAAM01 GEOM_ELI: Encryption: AES-XTS 128
Jun 14 23:34:25 NSBAAM01 GEOM_ELI: Crypto: hardware
Jun 14 23:34:27 NSBAAM01 GEOM_ELI: Device gptid/8a6587c1-9765-11e6-be31-0cc47a1a4ce4.eli created.
Jun 14 23:34:27 NSBAAM01 GEOM_ELI: Encryption: AES-XTS 128
Jun 14 23:34:27 NSBAAM01 GEOM_ELI: Crypto: hardware
Jun 14 23:34:29 NSBAAM01 GEOM_ELI: Device gptid/894eb9da-9765-11e6-be31-0cc47a1a4ce4.eli created.
Jun 14 23:34:29 NSBAAM01 GEOM_ELI: Encryption: AES-XTS 128
Jun 14 23:34:29 NSBAAM01 GEOM_ELI: Crypto: hardware
Jun 14 23:34:31 NSBAAM01 syslog-ng[5159]: I/O error occurred while writing; fd='18', error='Host is down (64)'
Jun 14 23:34:31 NSBAAM01 syslog-ng[5159]: Syslog connection broken; fd='18', server='AF_INET(192.168.1.153:514)', time_reopen='60'
Jun 14 23:34:31 NSBAAM01 GEOM_ELI: Device gptid/3612d04d-dd73-11e5-8338-0cc47a1a4ce4.eli created.
Jun 14 23:34:31 NSBAAM01 GEOM_ELI: Encryption: AES-XTS 128
Jun 14 23:34:31 NSBAAM01 GEOM_ELI: Crypto: hardware
Jun 14 23:34:33 NSBAAM01 GEOM_ELI: Device gptid/3496695e-dd73-11e5-8338-0cc47a1a4ce4.eli created.
Jun 14 23:34:33 NSBAAM01 GEOM_ELI: Encryption: AES-XTS 128
Jun 14 23:34:33 NSBAAM01 GEOM_ELI: Crypto: hardware
Jun 14 23:34:35 NSBAAM01 GEOM_ELI: Device gptid/3557b5ed-dd73-11e5-8338-0cc47a1a4ce4.eli created.
Jun 14 23:34:35 NSBAAM01 GEOM_ELI: Encryption: AES-XTS 128
Jun 14 23:34:35 NSBAAM01 GEOM_ELI: Crypto: hardware
Jun 14 23:34:37 NSBAAM01 GEOM_ELI: Device gptid/a78481a2-e86d-11e5-8338-0cc47a1a4ce4.eli created.
Jun 14 23:34:37 NSBAAM01 GEOM_ELI: Encryption: AES-XTS 128
Jun 14 23:34:37 NSBAAM01 GEOM_ELI: Crypto: hardware
Jun 14 23:34:39 NSBAAM01 GEOM_ELI: Device gptid/33bad624-dd73-11e5-8338-0cc47a1a4ce4.eli created.
Jun 14 23:34:39 NSBAAM01 GEOM_ELI: Encryption: AES-XTS 128
Jun 14 23:34:39 NSBAAM01 GEOM_ELI: Crypto: hardware
Jun 14 23:34:41 NSBAAM01 GEOM_ELI: Device gptid/8743a447-9765-11e6-be31-0cc47a1a4ce4.eli created.
Jun 14 23:34:41 NSBAAM01 GEOM_ELI: Encryption: AES-XTS 128
Jun 14 23:34:41 NSBAAM01 GEOM_ELI: Crypto: hardware
Jun 14 23:35:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot -r "fsz002/pss0004@auto-20180614.2335-1w"
Jun 14 23:35:01 NSBAAM01 autosnap.py: [tools.autosnap:337] Failed to create snapshot 'fsz002/pss0004@auto-20180614.2335-1w': cannot open 'fsz002/pss0004': dataset does not exist

Show : import pool 2

Jun 14 23:41:03 NSBAAM01 manage.py: [middleware.exceptions:37] [MiddlewareError: Failed to geli detach gptid/883f05e0-9765-11e6-be31-0cc47a1a4ce4: geli: Cannot destroy device gptid/883f05e0-9765-11e6-be31-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [storage.forms:986] [MiddlewareError: Failed to geli detach gptid/883f05e0-9765-11e6-be31-0cc47a1a4ce4: geli: Cannot destroy device gptid/883f05e0-9765-11e6-be31-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [middleware.exceptions:37] [MiddlewareError: Failed to geli detach gptid/8a6587c1-9765-11e6-be31-0cc47a1a4ce4: geli: Cannot destroy device gptid/8a6587c1-9765-11e6-be31-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [storage.forms:986] [MiddlewareError: Failed to geli detach gptid/8a6587c1-9765-11e6-be31-0cc47a1a4ce4: geli: Cannot destroy device gptid/8a6587c1-9765-11e6-be31-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [middleware.exceptions:37] [MiddlewareError: Failed to geli detach gptid/894eb9da-9765-11e6-be31-0cc47a1a4ce4: geli: Cannot destroy device gptid/894eb9da-9765-11e6-be31-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [storage.forms:986] [MiddlewareError: Failed to geli detach gptid/894eb9da-9765-11e6-be31-0cc47a1a4ce4: geli: Cannot destroy device gptid/894eb9da-9765-11e6-be31-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [middleware.exceptions:37] [MiddlewareError: Failed to geli detach gptid/3612d04d-dd73-11e5-8338-0cc47a1a4ce4: geli: Cannot destroy device gptid/3612d04d-dd73-11e5-8338-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [storage.forms:986] [MiddlewareError: Failed to geli detach gptid/3612d04d-dd73-11e5-8338-0cc47a1a4ce4: geli: Cannot destroy device gptid/3612d04d-dd73-11e5-8338-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [middleware.exceptions:37] [MiddlewareError: Failed to geli detach gptid/3496695e-dd73-11e5-8338-0cc47a1a4ce4: geli: Cannot destroy device gptid/3496695e-dd73-11e5-8338-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [storage.forms:986] [MiddlewareError: Failed to geli detach gptid/3496695e-dd73-11e5-8338-0cc47a1a4ce4: geli: Cannot destroy device gptid/3496695e-dd73-11e5-8338-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [middleware.exceptions:37] [MiddlewareError: Failed to geli detach gptid/3557b5ed-dd73-11e5-8338-0cc47a1a4ce4: geli: Cannot destroy device gptid/3557b5ed-dd73-11e5-8338-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [storage.forms:986] [MiddlewareError: Failed to geli detach gptid/3557b5ed-dd73-11e5-8338-0cc47a1a4ce4: geli: Cannot destroy device gptid/3557b5ed-dd73-11e5-8338-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [middleware.exceptions:37] [MiddlewareError: Failed to geli detach gptid/a78481a2-e86d-11e5-8338-0cc47a1a4ce4: geli: Cannot destroy device gptid/a78481a2-e86d-11e5-8338-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [storage.forms:986] [MiddlewareError: Failed to geli detach gptid/a78481a2-e86d-11e5-8338-0cc47a1a4ce4: geli: Cannot destroy device gptid/a78481a2-e86d-11e5-8338-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [middleware.exceptions:37] [MiddlewareError: Failed to geli detach gptid/33bad624-dd73-11e5-8338-0cc47a1a4ce4: geli: Cannot destroy device gptid/33bad624-dd73-11e5-8338-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [storage.forms:986] [MiddlewareError: Failed to geli detach gptid/33bad624-dd73-11e5-8338-0cc47a1a4ce4: geli: Cannot destroy device gptid/33bad624-dd73-11e5-8338-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [middleware.exceptions:37] [MiddlewareError: Failed to geli detach gptid/8743a447-9765-11e6-be31-0cc47a1a4ce4: geli: Cannot destroy device gptid/8743a447-9765-11e6-be31-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:03 NSBAAM01 manage.py: [storage.forms:986] [MiddlewareError: Failed to geli detach gptid/8743a447-9765-11e6-be31-0cc47a1a4ce4: geli: Cannot destroy device gptid/8743a447-9765-11e6-be31-0cc47a1a4ce4.eli (error=16).
]
Jun 14 23:41:05 NSBAAM01 syslog-ng[5159]: I/O error occurred while writing; fd='30', error='Host is down (64)'
Jun 14 23:41:05 NSBAAM01 syslog-ng[5159]: Syslog connection broken; fd='30', server='AF_INET(192.168.1.153:514)', time_reopen='60'
Jun 14 23:41:42 NSBAAM01 GEOM_ELI: Device gptid/f9347c10-4de7-11e6-b39c-0cc47a1a4ce4.eli created.
Jun 14 23:41:42 NSBAAM01 GEOM_ELI: Encryption: AES-XTS 128
Jun 14 23:41:42 NSBAAM01 GEOM_ELI: Crypto: hardware
Jun 14 23:41:44 NSBAAM01 GEOM_ELI: Device gptid/f9675383-4de7-11e6-b39c-0cc47a1a4ce4.eli created.
Jun 14 23:41:44 NSBAAM01 GEOM_ELI: Encryption: AES-XTS 128
Jun 14 23:41:44 NSBAAM01 GEOM_ELI: Crypto: hardware
Jun 14 23:41:46 NSBAAM01 GEOM_ELI: Device gptid/f9013b05-4de7-11e6-b39c-0cc47a1a4ce4.eli created.
Jun 14 23:41:46 NSBAAM01 GEOM_ELI: Encryption: AES-XTS 128
Jun 14 23:41:46 NSBAAM01 GEOM_ELI: Crypto: hardware
Jun 14 23:41:48 NSBAAM01 GEOM_ELI: Device gptid/f999e24e-4de7-11e6-b39c-0cc47a1a4ce4.eli created.
Jun 14 23:41:48 NSBAAM01 GEOM_ELI: Encryption: AES-XTS 128
Jun 14 23:41:48 NSBAAM01 GEOM_ELI: Crypto: hardware

Show : Log from statsvfs

Jun 14 23:45:04 NSBAAM01 collectd[3903]: statvfs(/mnt/backups) failed: No such file or directory
Jun 14 23:45:04 NSBAAM01 collectd[3903]: statvfs(/mnt/hcssv001_psds0001) failed: No such file or directory
Jun 14 23:45:04 NSBAAM01 collectd[3903]: statvfs(/mnt/hcssv001_psds0002) failed: No such file or directory
Jun 14 23:45:04 NSBAAM01 collectd[3903]: statvfs(/mnt/jails) failed: No such file or directory
Jun 14 23:45:04 NSBAAM01 collectd[3903]: statvfs(/mnt/media01) failed: No such file or directory
Jun 14 23:45:04 NSBAAM01 collectd[3903]: statvfs(/mnt/nfstest) failed: No such file or directory

Maybe also intersting. I saw failed jobs from "autosnap.py" until the volume was mounted

Show : Log from autosnap.py

...
Jun 14 23:40:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot -r "fsz002/pss0004@auto-20180614.2340-1w"
Jun 14 23:40:01 NSBAAM01 autosnap.py: [tools.autosnap:337] Failed to create snapshot 'fsz002/pss0004@auto-20180614.2340-1w': cannot open 'fsz002/pss0004': dataset does not exist
Jun 14 23:40:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot -r "fsz002/pss0004@auto-20180614.2340-3m"
Jun 14 23:40:01 NSBAAM01 autosnap.py: [tools.autosnap:337] Failed to create snapshot 'fsz002/pss0004@auto-20180614.2340-3m': cannot open 'fsz002/pss0004': dataset does not exist
Jun 14 23:41:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot -r "fsz002/pss0004@auto-20180614.2341-1w"
Jun 14 23:41:01 NSBAAM01 autosnap.py: [tools.autosnap:337] Failed to create snapshot 'fsz002/pss0004@auto-20180614.2341-1w': cannot open 'fsz002/pss0004': dataset does not exist
Jun 14 23:41:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot -r "fsz002/pss0004@auto-20180614.2341-3m"
Jun 14 23:41:01 NSBAAM01 autosnap.py: [tools.autosnap:337] Failed to create snapshot 'fsz002/pss0004@auto-20180614.2341-3m': cannot open 'fsz002/pss0004': dataset does not exist
Jun 14 23:42:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot -r "fsz002/pss0004@auto-20180614.2342-1w"
Jun 14 23:42:01 NSBAAM01 autosnap.py: [tools.autosnap:337] Failed to create snapshot 'fsz002/pss0004@auto-20180614.2342-1w': cannot open 'fsz002/pss0004': dataset does not exist
Jun 14 23:42:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot -r "fsz002/pss0004@auto-20180614.2342-3m"
Jun 14 23:42:01 NSBAAM01 autosnap.py: [tools.autosnap:337] Failed to create snapshot 'fsz002/pss0004@auto-20180614.2342-3m': cannot open 'fsz002/pss0004': dataset does not exist
Jun 14 23:43:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot -r "fsz002/pss0004@auto-20180614.2343-1w"
Jun 14 23:43:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot -r "fsz002/pss0004@auto-20180614.2343-3m"
Jun 14 23:43:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs destroy -r -d "fsz002/pss0004@auto-20180606.1700-1w"
Jun 14 23:43:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs destroy -r -d "fsz002/pss0004@auto-20180606.2100-1w"
Jun 14 23:43:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs destroy -r -d "fsz002/pss0004@auto-20180607.1600-1w"
Jun 14 23:43:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs destroy -r -d "fsz002/pss0004@auto-20180607.2300-1w"
Jun 14 23:43:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs destroy -r -d "fsz002/pss0004@auto-20180606.1600-1w"
Jun 14 23:43:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs destroy -r -d "fsz002/pss0004@auto-20180606.2000-1w"
Jun 14 23:43:01 NSBAAM01 autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs destroy -r -d "fsz002/pss0004@auto-20180606.1300-1w"

...

Show : zpool history pool 1

2018-06-10.00:00:11 zpool scrub hcssv001
2018-06-10.23:30:02 zfs snapshot hcssv001/backups@auto-20180610.2330-2m
2018-06-10.23:30:07 zfs destroy -r -d hcssv001/backups@auto-20180411.2330-2m
2018-06-11.02:00:02 zfs snapshot hcssv001/media01@auto-20180611.0200-12w
2018-06-11.02:00:07 zfs destroy -r -d hcssv001/media01@auto-20180319.0200-12w
2018-06-11.23:30:02 zfs snapshot hcssv001/backups@auto-20180611.2330-2m
2018-06-11.23:30:07 zfs destroy -r -d hcssv001/backups@auto-20180412.2330-2m
2018-06-12.23:30:02 zfs snapshot hcssv001/backups@auto-20180612.2330-2m
2018-06-12.23:30:07 zfs destroy -r -d hcssv001/backups@auto-20180413.2330-2m
2018-06-14.23:39:01 zpool import hcssv001
2018-06-14.23:39:01 zfs snapshot hcssv001/backups@auto-20180614.2339-2m
2018-06-14.23:39:02 zfs destroy -r -d hcssv001/backups@auto-20180414.2330-2m
2018-06-14.23:39:07 zfs destroy -r -d hcssv001/backups@auto-20180415.2330-2m
2018-06-14.23:39:21 zfs set mountpoint=/mnt hcssv001

Show : zpool history pool 1

2018-06-12.04:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.0400-1w
2018-06-12.05:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.0500-1w
2018-06-12.05:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.0500-1w
2018-06-12.06:00:02 zfs snapshot -r fsz002/pss0004@auto-20180612.0600-1w
2018-06-12.06:00:07 zfs destroy -r -d fsz002/pss0004@auto-20180605.0600-1w
2018-06-12.07:00:02 zfs snapshot -r fsz002/pss0004@auto-20180612.0700-1w
2018-06-12.07:00:07 zfs destroy -r -d fsz002/pss0004@auto-20180605.0700-1w
2018-06-12.08:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.0800-1w
2018-06-12.08:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.0800-1w
2018-06-12.09:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.0900-1w
2018-06-12.09:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.0900-1w
2018-06-12.10:00:02 zfs snapshot -r fsz002/pss0004@auto-20180612.1000-1w
2018-06-12.10:00:07 zfs destroy -r -d fsz002/pss0004@auto-20180605.1000-1w
2018-06-12.11:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.1100-1w
2018-06-12.11:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.1100-1w
2018-06-12.12:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.1200-1w
2018-06-12.12:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.1200-1w
2018-06-12.13:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.1300-1w
2018-06-12.13:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.1300-1w
2018-06-12.14:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.1400-1w
2018-06-12.14:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.1400-1w
2018-06-12.15:00:02 zfs snapshot -r fsz002/pss0004@auto-20180612.1500-1w
2018-06-12.15:00:07 zfs destroy -r -d fsz002/pss0004@auto-20180605.1500-1w
2018-06-12.16:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.1600-1w
2018-06-12.16:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.1600-1w
2018-06-12.17:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.1700-1w
2018-06-12.17:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.1700-1w
2018-06-12.18:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.1800-1w
2018-06-12.18:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.1800-1w
2018-06-12.19:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.1900-1w
2018-06-12.19:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.1900-1w
2018-06-12.20:00:02 zfs snapshot -r fsz002/pss0004@auto-20180612.2000-1w
2018-06-12.20:00:07 zfs destroy -r -d fsz002/pss0004@auto-20180605.2000-1w
2018-06-12.21:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.2100-1w
2018-06-12.21:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.2100-1w
2018-06-12.22:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.2200-1w
2018-06-12.22:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.2200-1w
2018-06-12.23:00:01 zfs snapshot -r fsz002/pss0004@auto-20180612.2300-1w
2018-06-12.23:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180605.2300-1w
2018-06-12.23:30:02 zfs snapshot -r fsz002/pss0004@auto-20180612.2330-3m
2018-06-12.23:30:07 zfs destroy -r -d fsz002/pss0004@auto-20180313.2330-3m
2018-06-13.00:00:02 zfs snapshot -r fsz002/pss0004@auto-20180613.0000-1w
2018-06-13.00:00:07 zfs destroy -r -d fsz002/pss0004@auto-20180606.0000-1w
2018-06-13.01:00:01 zfs snapshot -r fsz002/pss0004@auto-20180613.0100-1w
2018-06-13.01:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180606.0100-1w
2018-06-13.02:00:01 zfs snapshot -r fsz002/pss0004@auto-20180613.0200-1w
2018-06-13.02:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180606.0200-1w
2018-06-13.03:00:01 zfs snapshot -r fsz002/pss0004@auto-20180613.0300-1w
2018-06-13.03:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180606.0300-1w
2018-06-13.04:00:01 zfs snapshot -r fsz002/pss0004@auto-20180613.0400-1w
2018-06-13.04:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180606.0400-1w
2018-06-13.05:00:01 zfs snapshot -r fsz002/pss0004@auto-20180613.0500-1w
2018-06-13.05:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180606.0500-1w
2018-06-13.06:00:02 zfs snapshot -r fsz002/pss0004@auto-20180613.0600-1w
2018-06-13.06:00:07 zfs destroy -r -d fsz002/pss0004@auto-20180606.0600-1w
2018-06-13.07:00:01 zfs snapshot -r fsz002/pss0004@auto-20180613.0700-1w
2018-06-13.07:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180606.0700-1w
2018-06-13.08:00:01 zfs snapshot -r fsz002/pss0004@auto-20180613.0800-1w
2018-06-13.08:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180606.0800-1w
2018-06-13.09:00:01 zfs snapshot -r fsz002/pss0004@auto-20180613.0900-1w
2018-06-13.09:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180606.0900-1w
2018-06-14.23:42:43 zpool import fsz002
2018-06-14.23:43:01 zfs set mountpoint=/mnt fsz002
2018-06-14.23:43:01 zfs snapshot -r fsz002/pss0004@auto-20180614.2343-1w
2018-06-14.23:43:01 zfs snapshot -r fsz002/pss0004@auto-20180614.2343-3m
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180606.1700-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180606.2100-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.1600-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.2300-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180606.1600-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180606.2000-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180606.1300-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.2200-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.1200-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.0700-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.2100-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.1700-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.1900-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.1100-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.0500-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.0300-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180606.1400-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180314.2330-3m
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.0000-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180606.1900-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.1500-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180606.2200-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.0100-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.1000-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.0400-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180606.2300-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.2000-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.0900-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.1300-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180606.1800-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180606.1500-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.1800-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180606.1000-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.0800-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180607.0600-1w
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180315.2330-3m
2018-06-14.23:43:01 zfs destroy -r -d fsz002/pss0004@auto-20180606.1100-1w
2018-06-14.23:43:02 zfs destroy -r -d fsz002/pss0004@auto-20180607.0200-1w
2018-06-14.23:43:02 zfs destroy -r -d fsz002/pss0004@auto-20180607.1400-1w
2018-06-14.23:43:07 zfs destroy -r -d fsz002/pss0004@auto-20180606.1200-1w
2018-06-15.00:00:06 zfs destroy -r -d fsz002/pss0004@auto-20180608.0000-1w

 

[Chris Moore]

This right here is why you should never ever run your NAS without a UPS. Having a UPS means also having the service setup to have the UPS automatically shut down the NAS when the battery gets low.

Sent from my SAMSUNG-SGH-I537 using Tapatalk