01-11-2018
Okay, so you have an EFI GPT partitioned disk.
The last command shows there is just one single primary partition (p1) encompassing the whole disk.
Inside this partition, you have three slices, s0, s1, s2 and s8.
The system refused to use p3 because this partition exists but there are zero sector allocated to it, thus the I/O error.
As you found out, s2 is the 226 GiB partition you wanted.
9 More Discussions You Might Find Interesting
1. Solaris
Hi All,
I have to do disk mirroring, for that I have to create a metadb as disk mirroring have to do with SVM. However I do not have any slice free for metadb.
What are the options? Please suggest (4 Replies)
Discussion started by: kumarmani
4 Replies
2. Solaris
we have a ZFS file system that was created as a pool of just one disk (raid on a SAN) when this was created it was done as a whole disk, and so EFI label.
now we want to mount this file system into an LDOM.
my understanding of how ldom's and disk works this is that we can only do this as a... (1 Reply)
Discussion started by: robsonde
1 Replies
3. Solaris
I'd like to finish setting up this system and then move the secondary or primary disk to another system that is the exact same hardware.
I've done things like this in the past with ufs and disk suite mirroring just fine. But I have yet to do it with a zfs root pool mirror.
Are there any... (1 Reply)
Discussion started by: Metasin
1 Replies
4. Solaris
Hi,
I have Solaris-10 (release-7) box without any non global zone. I have a very critical change after couple of days from application side. For safer side, we want to keep few level of backups just in case of faliure. This server is having three pool
root@prod_ddoa01:/# zpool list
NAME SIZE... (2 Replies)
Discussion started by: solaris_1977
2 Replies
5. Solaris
Hi All;
My server's root partition was encapsulated with VxVM, I try to convert it to ZFS. I successfully de-encapsulated root. Now I try to mirror 2 root disks using ZFS. But I receive following error:
# zpool create rpool mirror c0t0d0s0 c0t1d0s0
invalid vdev specification
use '-f' to... (6 Replies)
Discussion started by: reseki
6 Replies
6. Solaris
Hi,
How to to make a slice and define as ufs from zpool? Please advice me.
Thanks.
---------- Post updated at 01:53 AM ---------- Previous update was at 12:24 AM ----------
Before slice:
Part Tag Flag Cylinders Size Blocks
0 root wm 0 ... (2 Replies)
Discussion started by: mzainal
2 Replies
7. Solaris
Hi everyone,
I am doing housekeeping of my Solaris 11 for zfs snapshot to reduce the snapshot size. I have already cleared the / file system, however the rpool size still not reduced.
Filesystem Size Used Available Capacity Mounted on
rpool/ROOT/solaris-2 98G 6.9G ... (2 Replies)
Discussion started by: freshmeat
2 Replies
8. Solaris
Hi,
I am unable to understand that, in one of my servers while
df -kh
Filesystem Size Used Available Capacity Mounted on
rpool/ROOT/solaris-2 98G 11G 29G 29% /
Even the Root FS filled on 40gb and system becomes unstable.
it is showing... (4 Replies)
Discussion started by: anuragr
4 Replies
9. Solaris
Hi,
I have this fresh installation of Solaris 11.3 sparc.
I have two zfs pools both using two disks in mirroring mode, both are online.
I want to move /system/zones, currently rpool/VARSHARE/zones, from rpool to the other zfs pool so my zones don't consume space on the disks allocated to... (1 Reply)
Discussion started by: X96
1 Replies
FDISK(8) System Manager's Manual FDISK(8)
NAME
fdisk - partition a hard disk [IBM]
SYNOPSIS
fdisk [-hm] [-sn] [file]
OPTIONS
-h Number of disk heads is m
-s Number of sectors per track is n
EXAMPLES
fdisk /dev/hd0 # Examine disk partitions
fdisk -h9 /dev/hd0 # Examine disk with 9 heads
DESCRIPTION
When fdisk starts up, it reads in the partition table and displays it. It then presents a menu to allow the user to modify partitions,
store the partition table on a file, or load it from a file. Partitions can be marked as MINIX, DOS or other, as well as active or not.
Using fdisk is self-explanatory. However, be aware that repartitioning a disk will cause information on it to be lost. Rebooting the sys-
tem immediately is mandatory after changing partition sizes and parameters. MINIX, XENIX, PC-IX, and MS-DOS all have different partition
numbering schemes. Thus when using multiple systems on the same disk, be careful.
Note that MINIX, unlike MS-DOS , cannot access the last sector in a partition with an odd number of sectors. The reason that odd partition
sizes do not cause a problem with MS-DOS is that MS-DOS allocates disk space in units of 512-byte sectors, whereas MINIX uses 1K blocks.
Fdisk has a variety of other features that can be seen by typing h.
Fdisk normally knows the geometry of the device by asking the driver. You can use the -h and -s options to override the numbers found.
SEE ALSO
part(8).
FDISK(8)