Upgraded from 13.0-U.2 to 13.0-U6.1 - Pool Offline

[wittend]

Not much joy, I don't think.
I will try to respond in order:

Code:

bear% zfs list -t filesystem -r -o name,mountpoint boot-pool/.system
NAME                                                        MOUNTPOINT
boot-pool/.system                                           legacy
boot-pool/.system/configs-f51bc31246e14c8b928ca7d405891bbf  legacy
boot-pool/.system/cores                                     legacy
boot-pool/.system/rrd-f51bc31246e14c8b928ca7d405891bbf      legacy
boot-pool/.system/samba4                                    legacy
boot-pool/.system/services                                  legacy
boot-pool/.system/syslog-f51bc31246e14c8b928ca7d405891bbf   legacy
boot-pool/.system/webui                                     legacy

Code:

bear% zfs mount | grep "boot-pool/.system"
boot-pool/.system               /var/db/system
boot-pool/.system/cores         /var/db/system/cores
boot-pool/.system/samba4        /var/db/system/samba4
boot-pool/.system/syslog-f51bc31246e14c8b928ca7d405891bbf  /var/db/system/syslog-f51bc31246e14c8b928ca7d405891bbf
boot-pool/.system/rrd-f51bc31246e14c8b928ca7d405891bbf  /var/db/system/rrd-f51bc31246e14c8b928ca7d405891bbf
boot-pool/.system/configs-f51bc31246e14c8b928ca7d405891bbf  /var/db/system/configs-f51bc31246e14c8b928ca7d405891bbf
boot-pool/.system/webui         /var/db/system/webui
boot-pool/.system/services      /var/db/system/services

Code:

bear% sudo zpool import
   pool: BigPool
     id: 12719548412266318029
  state: ONLINE
status: One or more devices were being resilvered.
 action: The pool can be imported using its name or numeric identifier.
 config:


        BigPool                                         ONLINE
          raidz1-0                                      ONLINE
            gptid/e4b02a68-4cb0-11ed-a5e8-bc5ff4664310  ONLINE
            gptid/e4aac4e3-4cb0-11ed-a5e8-bc5ff4664310  ONLINE
            gptid/e4a77d50-4cb0-11ed-a5e8-bc5ff4664310  ONLINE
            gptid/e4ac0488-4cb0-11ed-a5e8-bc5ff4664310  ONLINE

Code:

bear% zpool import -N BigPool
cannot import 'BigPool': no such pool available
bear% sudo zpool import -N BigPool
cannot import 'BigPool': insufficient replicas
        Destroy and re-create the pool from
        a backup source.

Code:

bear% zpool status -v BigPool
cannot open 'BigPool': no such pool
bear% sudo zpool status -v BigPool
cannot open 'BigPool': no such pool

Code:

bear% zfs list -t filesystem -r BigPool
cannot open 'BigPool': dataset does not exist
bear% sudo zfs list -t filesystem -r BigPool
cannot open 'BigPool': dataset does not exist

There being no "backup source" that I know of, my world may now be a few TB smaller than it was.
Right?

Thanks,
Dave

 

[winnielinnie]

cannot import 'BigPool': insufficient replicas

Are all the member disks available?

Code:

glabel status

 

[wittend]

I'm not sure what this means:

Code:

bear% glabel status
                                      Name  Status  Components
gptid/962803fe-4caf-11ed-9729-bc5ff4664310     N/A  ada0p1
gptid/5476963c-6d1b-11ed-8ec5-bc5ff4664310     N/A  ada1p1
gptid/e4a77d50-4cb0-11ed-a5e8-bc5ff4664310     N/A  ada4p2
gptid/e4ac0488-4cb0-11ed-a5e8-bc5ff4664310     N/A  ada5p2
gptid/e4a704fc-4cb0-11ed-a5e8-bc5ff4664310     N/A  ada5p1
gptid/e49ffe38-4cb0-11ed-a5e8-bc5ff4664310     N/A  ada4p1
gptid/e4a19437-4cb0-11ed-a5e8-bc5ff4664310     N/A  ada3p1
gptid/e4aac4e3-4cb0-11ed-a5e8-bc5ff4664310     N/A  ada3p2
gptid/e4a9b3bf-4cb0-11ed-a5e8-bc5ff4664310     N/A  ada2p1
gptid/e4b02a68-4cb0-11ed-a5e8-bc5ff4664310     N/A  ada2p2

Dave

 

[winnielinnie]

All disks/partitions required for the pool's sole RAIDZ1 vdev are detected by the system.

Not sure why you're getting hit with "insufficient replicas".

What was the leadup to this? Apparently, the last status message in regards to BigPool was that it was in the middle of a resilver process. (But why? Was a disk failing? Did you configure a hot spare, per chance?)

 

[wittend]

No hot spare.

I wanted to see the exact model number of the drives to check the price and consider adding more. I wanted (perhaps) to create a new pool or something because I always get errors when working with git clone folders or anything with symbolic links.

I bumped one of the data cables and evidently corrupted one of the drives. I tried to understand how to repair things but only got more confused. Perhaps I interrupted the resilvering process. I did not understand what that was, and did not know that it was already going on. I waslooking for something like 'rebuild mirrors' or 'rebuild RAID'.

dave

 

[winnielinnie]

Unless you can backtrack and memorize what you did, it sounds like you inadvertently destroyed your pool, and hence your data.

Even if you can remember everything, it doesn't mean you can undo the damage; especially when dealing with entire drives and the resilver process of a pool.

You might try to see if you can import the pool in a degraded state:

Code:

zpool import -fFnN BigPool

 

[wittend]

I'm not sure if that did anything. As a regular user it returns 'no such pool'. As su, it returns nothing.

Code:

bear% zpool import -fFnN BigPool
cannot import 'BigPool': no such pool available
bear% sudo zpool import -fFnN BigPool
Password:
bear% bear% zpool import -fFnN BigPool
cannot import 'BigPool': no such pool available
bear% sudo zpool import -fFnN BigPool
Password:
bear%

 

[winnielinnie]

Can you try without the "-n" flag?

Code:

zpool import -fFN BigPool

 

[wittend]

When I run that with sudu via SSH terminal, I get:

Code:

bear% sudo zpool import -fFN BigPool
Password:
cannot import 'BigPool': no such pool or dataset
        Destroy and re-create the pool from
        a backup source.

When I run the same command from an attached console (kbd+ monitor), I get a raft of stuff that changes with repeated invocations. None of it looks promising, but it talks about different volumes each time.

I'm expecting a 10 port PCIe -> SATA controller later today. That should help cleanup the rat's nest of wires. I'm gong to keep watching this thing until that arrives.

Assuming that the clouds don't miraculously part by then, I will take this apart and start clean.

I must thank everyone who has made suggestions.
At least I can walk away from this car wreck with a lot of new information and maybe even a little more knowledge concerning how this works and what tools exist to manage it.
As always, that is the second best possible outcome.

Thanks,

Dave

 

[Davvo]

I'm expecting a 10 port PCIe -> SATA controller later today. That should help cleanup the rat's nest of wires. I'm gong to keep watching this thing until that arrives.

Really make sure to read the following resource before using that.

Multiply your problems with SATA Port Multipliers and cheap SATA controllers

In the last year or two, we've had a resurgence of users asking about SATA Port Multipliers and cheap SATA controllers. Please, do NOT use port multipliers, and use cheap SATA controllers only after extensive research. SATA controllers and SATA...

www.truenas.com

 

[wittend]

Thanks!