Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: How to clear a removed single-disk pool from being listed by zpool import?
Operating Systems Solaris How to clear a removed single-disk pool from being listed by zpool import? Post 303021842 by priyadarshan on Saturday 18th of August 2018 05:55:47 AM
Old 08-18-2018
I completely reinstalled OmniOS, and I was able to replicate the issue with these steps:


- Install a second NVMe drive
- Install FreeBSD on that and boot from it
- Boot again, this time from OmniOS
- Import the FreeBSD pool (on second NVMe)
- Poweroff without exporting it
- Remove FreeBSD NVMe from server
- Boot from OmniOS

At that point, zpool import will show message as original post.

In that state, there is nothing one can do to remove the stray label from boot disk.

Although not a real bug, I reported that to Illumos devs as feature request, i.e., to be able to remove stray leftover labels caused by above steps.

I am adding the "solved" tag, and I will report back with updates as soon as I have them.


Thanks to all for the help and advice!
 

10 More Discussions You Might Find Interesting

1. Solaris

( VxVM ) How to add the removed disk back to previous disk group

Previously , i remove the disk by #vxdg -g testdg -k rmdisk testdg02 But i got error when i -k adddisk bash-2.03# vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online invalid c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies

2. Solaris

unable to import zfs pool

# zpool import pool: emcpool1 id: 5596268873059055768 state: UNAVAIL status: One or more devices are missing from the system. action: The pool cannot be imported. Attach the missing devices and try again. see: Sun Message ID: ZFS-8000-3C config: emcpool1 ... (7 Replies)
Discussion started by: fugitive
7 Replies

3. Solaris

Import zpool with missing slog device

Hello, I have a problem on my backup server. I lost my system hdd and my separate ZIL device while the system crashs and now I'm in trouble. The old system was running under the least version of osol/dev (snv_134) with zfs v22. After the server crashs I was very optimistic of solving the problems... (2 Replies)
Discussion started by: ron2105
2 Replies

4. BSD

Unable to create zfs zpool in FreeBSD 8.2: no such pool or dataset

I am trying to test simple zfs functionality on a FreeBSD 8.2 VM. When I try to run a 'zpool create' I receive the following error: # zpool create zfspool /dev/da0s1a cannot create 'zfspool': no such pool or dataset # zpool create zfspool /dev/da0 cannot create 'zfspool': no such pool or... (3 Replies)
Discussion started by: bstring
3 Replies

5. Solaris

13 disk raidz2 pool lost

Hi guys, I appreciate any help in this regard, we have lost sensitive data in the company. One box with 2 disk mirrored and a 3ware controller handling 13 disks in a raidz2 pool. Suddenly the box restart and keeps "Reading ZFS config" for hours. Unplugging disk by disk we isolate the disk... (3 Replies)
Discussion started by: tatxo
3 Replies

6. Solaris

Using liveupgrade on single ZFS pool

Hi Guys, I have a single ZFS pool with 2 disk which is mirrored if i create a new BE with lucreate should i specify which disk where the new BE should be created? (7 Replies)
Discussion started by: batas
7 Replies

7. Solaris

Add disk to zpool

Hi, Quick question. I have a data zpool that consists of 1 disk. pool: data state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM data ONLINE 0 0 0 c0t50002AC0014B06BEd0 ONLINE... (2 Replies)
Discussion started by: general_lee
2 Replies

8. Solaris

Zpool import/export error

A backup/clone script of ours was recently ran. It normally only clones the rpool and renames in rpoolA. Something must've changed as it found another one of our pools that it shouldn't have. It exported that pool unbeknownst to us. Later on when a coworker realized the other pool was missing he... (2 Replies)
Discussion started by: beantownmp
2 Replies

9. Solaris

Zpool with 3 2-way mirrors in a pool

I have a single zpool with 3 2-way mirrors ( 3 x 2 way vdevs) it has a degraded disk in mirror-2, I know I can suffer a single drive failure, but looking at this how many drive failures can this suffer before it is no good? On the face of it, I thought that I could lose a further 2 drives in each... (4 Replies)
Discussion started by: fishface
4 Replies

10. Solaris

Replace zpool with another disk

issue, I had a zpool which was full pool_temp1 199G 197G 1.56G 99% ONLINE - pool_temp2 199G 196G 3.09G 98% ONLINE - as you can see, full so I replaced with a larger disk. zpool replace pool_temp1 c3t600144F0FF8BA036000058CC1DB80008d0s0... (2 Replies)
Discussion started by: rrodgers
2 Replies

LEARN ABOUT MOJAVE

bootctl

BOOTCTL(1)                                                            bootctl                                                           BOOTCTL(1)

NAME

       bootctl - Control the firmware and boot manager settings

SYNOPSIS

       bootctl [OPTIONS...] status

       bootctl [OPTIONS...] list

       bootctl [OPTIONS...] update

       bootctl [OPTIONS...] install

       bootctl [OPTIONS...] remove

DESCRIPTION

       bootctl checks, updates, installs or removes the boot loader from the current system.

       bootctl status checks and prints the currently installed versions of the boot loader binaries and all current EFI boot variables.

       bootctl list displays all configured boot loader entries.

       bootctl update updates all installed versions of systemd-boot, if the current version is newer than the version installed in the EFI system
       partition. This also includes the EFI default/fallback loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is
       created if there is no current entry. The created entry will be added to the end of the boot order list.

       bootctl install installs systemd-boot into the EFI system partition. A copy of systemd-boot will be stored as the EFI default/fallback
       loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is created and added to the top of the boot order list.

       bootctl remove removes all installed versions of systemd-boot from the EFI system partition, and removes systemd-boot from the EFI boot
       variables.

       If no command is passed, status is implied.

OPTIONS

       The following options are understood:

       -h, --help
           Print a short help text and exit.

       --version
           Print a short version string and exit.

       --path=
           Path to the EFI System Partition (ESP). If not specified, /efi, /boot, and /boot/efi are checked in turn. It is recommended to mount
           the ESP to /boot, if possible.

       -p, --print-path
           This option modifies the behaviour of status. Just print the path to the EFI System Partition (ESP) to standard output and exit.

       --no-variables
           Do not touch the EFI boot variables.

EXIT STATUS

       On success, 0 is returned, a non-zero failure code otherwise.

SEE ALSO

       Boot loader specification[1] systemd boot loader interface[2]

NOTES

        1. Boot loader specification
           https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec

        2. systemd boot loader interface
           https://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface

systemd 237                                                                                                                             BOOTCTL(1)
All times are GMT -4. The time now is 09:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy