as you can see, full
so I replaced with a larger disk.
it resilvered fine, no errors, however in zpool status, I can see the new disk, yet it does not recognize the new size, and
when I try to
I get the expected error
cannot set property for pool : out of space.
how can I get the system to reconized the new size? devfsadm, reboot -r?
I backed up the data in the pool, so could I just empty the data then try set autoexpand=on again?
first time attempting this, so sorry for basic question.
thanks.
Last edited by jim mcnamara; 11-10-2017 at 12:50 PM..
Actually have a few different issues, wondering if I could get input on (tried reading/searching for an answer, with no luck)
1. Have a v240 running sol9 that needs a bad disk replaced. So, here are the steps I took:
a. detached from mirroring
b. cleared mirroring (metaclear)
c.... (4 Replies)
solaris os run on X86.
bootdisk have been mirrored.but there is one disk miss,I want to replace the fail disk,but after I replace the disk,the system can't boot!
pls help! (2 Replies)
Originally Posted by panos83
Hello there Sir,
according to this old post,
https://www.unix.com/sco/100001-warni...ler-found.html
i try to restore an old image to a new hard disk drive.
The problem is that i don't have basic information such as:
1) Which btld driver do i... (3 Replies)
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)
Scenario1:
VG00 lvm,not mirrored,2 disk of 36GB vg size
VG00 size is under 30G.
Is possible to remove a disk of 36GB and replace "on fly"
with a disk of 300GB on VG00?
Thanks (6 Replies)
I added a disk to a zpool using "zpool add diskname"
My intention was mirror a zpool disk that no mirror; that is a zpool with only one disk. I did not issue the right command. Now, the disk has been added successfully but I cannot remove nor detach it as Solaris 11 thinks it has data on it... (14 Replies)
Hello,
I need some help in recovering ZFS pool. Here is scenerio. There are two disks -
c0t0d0 - This is good disk. I cloned it from other server and boot server from this disk.
c0t1d0 - This is original disk of this server, having errors. I am able to mount it on /mnt. So that I can copy... (1 Reply)
Hello,
I see hard and transport errors on all disks under treso pool and looks like some data corruption too. I want to take backup before, I reboot and replace disk. As of now, there are no slots free on server, so one option is, to break mirror, remove second disk (I need two disks, because... (5 Replies)
On an OmniOS server, I removed a single-disk pool I was using for testing.
Now, when I run zpool import it will show it as FAULTED, since that single disk not available anymore.
# zpool import
pool: fido
id: 7452075738474086658
state: FAULTED
status: The pool was last... (11 Replies)
Discussion started by: priyadarshan
11 Replies
LEARN ABOUT FREEBSD
gptzfsboot
GPTZFSBOOT(8) BSD System Manager's Manual GPTZFSBOOT(8)NAME
gptzfsboot -- GPT bootcode for ZFS on BIOS-based computers
DESCRIPTION
gptzfsboot is used on BIOS-based computers to boot from a filesystem in a ZFS pool. gptzfsboot is installed in a freebsd-boot partition of a
GPT-partitioned disk with gpart(8).
IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptzfsboot only boots from tables with 128 partitions or less.
BOOTING
gptzfsboot tries to find all ZFS pools that are composed of BIOS-visible hard disks or partitions on them. gptzfsboot looks for ZFS device
labels on all visible disks and in discovered supported partitions for all supported partition scheme types. The search starts with the disk
from which gptzfsboot itself was loaded. Other disks are probed in BIOS defined order. After a disk is probed and gptzfsboot determines
that the whole disk is not a ZFS pool member, the individual partitions are probed in their partition table order. Currently GPT and MBR
partition schemes are supported. With the GPT scheme, only partitions of type freebsd-zfs are probed. The first pool seen during probing is
used as a default boot pool.
The filesystem specified by the bootfs property of the pool is used as a default boot filesystem. If the bootfs property is not set, then
the root filesystem of the pool is used as the default. zfsloader(8) is loaded from the boot filesystem. If /boot.config or /boot/config is
present in the boot filesystem, boot options are read from it in the same way as boot(8).
The ZFS GUIDs of the first successfully probed device and the first detected pool are made available to zfsloader(8) in the
vfs.zfs.boot.primary_vdev and vfs.zfs.boot.primary_pool variables.
USAGE
Normally gptzfsboot will boot in fully automatic mode. However, like boot(8), it is possible to interrupt the automatic boot process and
interact with gptzfsboot through a prompt. gptzfsboot accepts all the options that boot(8) supports.
The filesystem specification and the path to zfsloader(8) are different from boot(8). The format is
[zfs:pool/filesystem:][/path/to/loader]
Both the filesystem and the path can be specified. If only a path is specified, then the default filesystem is used. If only a pool and
filesystem are specified, then /boot/zfsloader is used as a path.
Additionally, the status command can be used to query information about discovered pools. The output format is similar to that of zpool
status (see zpool(8)).
The configured or automatically determined ZFS boot filesystem is stored in the zfsloader(8) loaddev variable, and also set as the initial
value of the currdev variable.
FILES
/boot/gptzfsboot boot code binary
/boot.config parameters for the boot block (optional)
/boot/config alternative parameters for the boot block (optional)
EXAMPLES
gptzfsboot is typically installed in combination with a ``protective MBR'' (see gpart(8)). To install gptzfsboot on the ada0 drive:
gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0
gptzfsboot can also be installed without the PMBR:
gpart bootcode -p /boot/gptzfsboot -i 1 ada0
SEE ALSO boot.config(5), boot(8), gpart(8), loader(8), zfsloader(8), zpool(8)HISTORY
gptzfsboot appeared in FreeBSD 7.3.
AUTHORS
This manual page was written by Andriy Gapon <avg@FreeBSD.org>.
BUGS
gptzfsboot looks for ZFS meta-data only in MBR partitions (known on FreeBSD as slices). It does not look into BSD disklabel(8) partitions
that are traditionally called partitions. If a disklabel partition happens to be placed so that ZFS meta-data can be found at the fixed off-
sets relative to a slice, then gptzfsboot will recognize the partition as a part of a ZFS pool, but this is not guaranteed to happen.
BSD September 15, 2014 BSD