Made a Pool from an ext USB volume - does not mount after reboot

[sboutros]

FreeNAS-11.2-U6
Processor:
Intel(R) Xeon(R) CPU X5650 @ 2.67GHz (24 cores)

Memory:
24 GiB

Added an external USB drive and created a pool with it. Used said pool for a week or so. Then applied U6/reboot.
"Disk details not available" for said pool.
Would there be an easy way to update pool definition to point to: da6
and or fix said external volume to the same device #?

Content is not the most critical - it's an rsync of other systems - easy to re-create just didn't realize I would run into this.

Thanks!

 

[Arwen]

In general, USB connections are not reliable for drives. And especially not reliable as continuous connected & mounted. We here in the forums don't recommend or suggest such configurations.

That said, I personally use USB attached media with ZFS for backups and recovery media.

What I would do, is get on the command line and try zpool import to see if the USB device and pool is found. If not, try another USB port and repeat.

Note that some external USB drives claim to work with USB supplied power. But, at times, they can be flaky. So if you have an option to use external power, try that too.

 

[sboutros]

Thank you, that did the trick (zpool import <vol>).
Is there a way to have that happen automatically upon reboot?

 

[sboutros]

Ok, same topic/issue.
My USB drive/volume seems to be in a mystical state.
Is it a correct assumption that the gptid changed since this is a USB drive?
My zpool history cmd shows pool creation and shows a different gptid
(actually, not entirely sure what a gptid is...)

Any ideas how I can rectify the situation at hand as as described below?
status says all good but nothing is found at the mount point /mnt/bc_rsync



root@freenas[~]# zpool status bc_rsync
pool: bc_rsync
state: ONLINE
scan: none requested
config:

NAME STATE READ WRITE CKSUM
bc_rsync ONLINE 0 0 0
da7p2 ONLINE 0 0 0

errors: No known data errors


root@freenas[~]# camcontrol devlist
<ATA HGST HDN726040AL W7JH> at scbus0 target 6 lun 0 (pass0,da0)
<ATA HGST HDN726040AL W7JH> at scbus0 target 7 lun 0 (pass1,da1)
<ATA ST4000VN008-2DR1 SC60> at scbus0 target 10 lun 0 (pass2,da2)
<ATA ST4000VN008-2DR1 SC60> at scbus0 target 11 lun 0 (pass3,da3)
<ATA ST4000VN008-2DR1 SC60> at scbus0 target 12 lun 0 (pass4,da4)
<ATA ST4000VN008-2DR1 SC60> at scbus0 target 13 lun 0 (pass5,da5)
<SanDisk Cruzer Glide 3.0 1.00> at scbus4 target 0 lun 0 (pass6,da6)
<Seagate BUP BK 0304> at scbus5 target 0 lun 0 (da7,pass7)

root@freenas[~]# glabel status
Name Status Components
gptid/fd8764f7-e17a-11e8-8b5e-a4badb40ecf5 N/A da0p2
gptid/fe1d6ff3-e17a-11e8-8b5e-a4badb40ecf5 N/A da1p2
gptid/7f2c384a-fa2f-11e8-b0e4-a4badb40ecf5 N/A da2p2
gptid/802997e6-fa2f-11e8-b0e4-a4badb40ecf5 N/A da3p2
gptid/81322fd6-fa2f-11e8-b0e4-a4badb40ecf5 N/A da4p2
gptid/8226086a-fa2f-11e8-b0e4-a4badb40ecf5 N/A da5p2
gptid/39bcf6bb-6519-11e9-b5dd-a4badb40ecf5 N/A da6p1
gptid/c65d46c0-d36d-11e9-8d2e-a4badb40ecf5 N/A da7p1

root@freenas[~]# zpool history bc_rsync
History for 'bc_rsync':
2019-09-09.21:53:25 zpool create -o cachefile=/data/zfs/zpool.cache -o failmode=continue -o autoexpand=on -O compression=lz4 -O aclmode=passthrough -O aclinherit=passthrough -f -m /bc_rsync -o altroot=/mnt bc_rsync /dev/gptid/c688da5c-d36d-11e9-8d2e-a4badb40ecf5
2019-09-09.21:53:30 zfs inherit mountpoint bc_rsync
2019-09-09.21:53:30 zpool set cachefile=/data/zfs/zpool.cache bc_rsync
2019-09-23.09:37:20 zpool import bc_rsync
2019-09-24.12:32:39 zfs set mountpoint=/mnt/bc_rsync bc_rsync
2019-10-11.14:37:29 zfs set mountpoint=/mnt/bc_rsync bc_rsync

 

[sretalla]

The pool gptid and the disk gptid should not match.

Neither will change without some kind of wipe/destroy operation being involved.

Once you import a pool on a healthy system, that pool will be imported again on reboot automatically.

Look at the output of dmesg after booting to see if something didn't go right during the boot sequence.

 

[sboutros]

This is what I see in dmesg:

umass0: at uhub6, port 2, addr 3 (disconnected)
(da6:umass-sim0:0:0:0): got CAM status 0x44
(da6:umass-sim0:0:0:0): fatal error, failed to attach to device
g_access(944): provider da6 has error 6 set
g_access(944): provider da6 has error 6 set
g_access(944): provider da6 has error 6 set
g_access(944): provider da6 has error 6 set
g_access(944): provider da6 has error 6 set
g_access(944): provider da6 has error 6 set
g_access(944): provider da6 has error 6 set
umass0: detached
ugen2.3: <Seagate BUP BK> at usbus2
umass0 on uhub6
umass0: <Seagate BUP BK, class 0/0, rev 2.10/1.00, addr 3> on usbus2
umass0: SCSI over Bulk-Only; quirks = 0xc101
umass0:4:0: Attached to scbus4

 

[Jailer]

In general, USB connections are not reliable for drives. And especially not reliable as continuous connected & mounted. We here in the forums don't recommend or suggest such configurations.

In case you missed it the first time.

 

[sboutros]

In case you missed it the first time.

No, I get it.
It's not the most critical aspect of the system if the data got lost however I'd love to find a mostly reliable way to use said external USB volume, if possible.