Hi All,
I have just installed b90 on an E250 with 2 identical SCSI disks and
zfs root. But I keep getting the error
cannot attach /dev/rdsk/c0t8d0 to c0t0d0s0: device is too small
when I execute
zpool attach rpool c0t0d0s0 /dev/rdsk/c0t8d0
It appears to be a labelling problem of the disk but none of the
tricks such as
# prtvtoc /dev/rdsk/c0t0d0s0 | fmthard -s - /dev/rdsk/c0t8d0
fmthard: Partition 0 overlaps partition 2. Overlap is allowed
only on partition on the full disk partition).
appear to make an identical label.
Format reveals the following:
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci at 1f,4000/scsi at 3/sd at 0,0
1. c0t8d0 <SEAGATE-ST336605LSUN36G-0238-33.92GB>
/pci at 1f,4000/scsi at 3/sd at 8,0
I would be happy to believe that this was actually a size error,
except that this is the second reinstall and the disks are marked
identically. Any suggestions welcome.
Maurice Castro
Maurice Castro wrote:> Hi All, > I have just installed b90 on an E250 with 2 identical SCSI disks and > zfs root. But I keep getting the error > > cannot attach /dev/rdsk/c0t8d0 to c0t0d0s0: device is too small > > when I execute > > zpool attach rpool c0t0d0s0 /dev/rdsk/c0t8d0 > > It appears to be a labelling problem of the disk but none of the > tricks such as > > # prtvtoc /dev/rdsk/c0t0d0s0 | fmthard -s - /dev/rdsk/c0t8d0 > fmthard: Partition 0 overlaps partition 2. Overlap is allowed > only on partition on the full disk partition). > > appear to make an identical label. > > Format reveals the following: > > AVAILABLE DISK SELECTIONS: > 0. c0t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> > /pci at 1f,4000/scsi at 3/sd at 0,0 > 1. c0t8d0 <SEAGATE-ST336605LSUN36G-0238-33.92GB> > /pci at 1f,4000/scsi at 3/sd at 8,0 > > I would be happy to believe that this was actually a size error, > except that this is the second reinstall and the disks are marked > identically. Any suggestions welcome. >This error message occurs when the disks are of different size and the disk being attached is smaller. I would double check (using format) that the number of available blocks is the same. Note: to boot you will need to ensure that a Solaris VTOC label is on both disks. If you let ZFS add the mirror without specifying the slice, then ZFS will add an EFI label and the disk will not be bootable. Please see the appropriate docs which provide guidance on configuring boot mirrors. http://www.opensolaris.org/os/community/zfs/docs/zfsadmin.pdf -- richard
These 18gb disks? There a bug which is fixed in b92 which could be causing this? This message posted from opensolaris.org
On Fri, Jun 20, 2008 at 4:12 PM, John-Paul Drawneek <jpd at drawneek.demon.co.uk> wrote:> These 18gb disks?It looks like they''re 36GB: 0. c0t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> ^^^ 1. c0t8d0 <SEAGATE-ST336605LSUN36G-0238-33.92GB> ^^^ ^^^^^^^ It also looks like they are not identical drives. -B -- Brandon High bhigh at freaks.com "The good is the enemy of the best." - Nietzsche
Hi All,
actually the drives are identical and approximately 34GB in formatted
in size. The solution I eventually took was to reinstall the system
and select the 2 disks in the installer and the mirror is created.
Unfortunately, there were other complexities in the process. ZFS boot
disks require an SMI label. So I had to relabel the disk using the
format -e command to get the option to write an SMI label as ZFS had
left an EFI label on the disk. Unfortunately all the installer tells
you is that the label is invalid.
After the reinstall this is what format looks like:
0. c0t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci at 1f,4000/scsi at 3/sd at 0,0
1. c0t8d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci at 1f,4000/scsi at 3/sd at 8,0
If I add a 3rd identical disk:
0. c0t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci at 1f,4000/scsi at 3/sd at 0,0
1. c0t8d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci at 1f,4000/scsi at 3/sd at 8,0
2. c0t9d0 <SEAGATE-ST336605LSUN36G-0638-33.92GB>
/pci at 1f,4000/scsi at 3/sd at 9,0
Note the names are different but it matches c0t8d0''s description
before the mirror was built.
So it appears that the instructions that say all you have to do is
attach the disk are insufficient when it comes to making a mirrored
boot disk under OpenSolaris.
Maurice Castro
On 21/06/2008, at 9:35 AM, Brandon High wrote:
> On Fri, Jun 20, 2008 at 4:12 PM, John-Paul Drawneek
> <jpd at drawneek.demon.co.uk> wrote:
>> These 18gb disks?
>
> It looks like they''re 36GB:
> 0. c0t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
> ^^^
> 1. c0t8d0 <SEAGATE-ST336605LSUN36G-0238-33.92GB>
> ^^^ ^^^^^^^
>
> It also looks like they are not identical drives.
>
> -B
>
> --
> Brandon High bhigh at freaks.com
> "The good is the enemy of the best." - Nietzsche
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
The answer is that an SMI label is required in which the first slice covers the whole disk. A detailed process is described at: http://www.castro.aus.net/~maurice/opensolaris/zfsbootmirror.html Please note that there still may be other issues ie bug 6680633 but at least I can now add an identical disk to the mirror. Maurice Castro On 19/06/2008, at 2:31 PM, Maurice Castro wrote:> Hi All, > I have just installed b90 on an E250 with 2 identical SCSI disks and > zfs root. But I keep getting the error > > cannot attach /dev/rdsk/c0t8d0 to c0t0d0s0: device is too small >