> [EMAIL PROTECTED] said:
> > But I don't see how copying a label will do any good. Won't that just
> > confuse ZFS and make it think it's talking to one of the other disks?
>
> No, the disk label doesn't contain any ZFS info, it just tells the disk
> drivers (scsi_vhci, in this case) where the
[EMAIL PROTECTED] said:
> But I don't see how copying a label will do any good. Won't that just
> confuse ZFS and make it think it's talking to one of the other disks?
No, the disk label doesn't contain any ZFS info, it just tells the disk
drivers (scsi_vhci, in this case) where the disk slices
On Tue, Aug 21, 2007 at 03:55:59PM -0700, Marion Hakanson wrote:
> [EMAIL PROTECTED] said:
> > With this OS version, format is giving lines such as:
> > 9. c2t2104D9600099d0
> > /[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]/pci1077,[EMAIL
> > PROTECTED]/[EMAIL PROTECTED],0/[EMAIL
> If the disk/LUN was really not reformatted, you might be able to restore
> the label by first converting the disk to EFI, and then copying a label
> from one of the working disks.
Well, you might get somewhere by putting an EFI label on (because then
the top of the data portion will move down th
[EMAIL PROTECTED] said:
> With this OS version, format is giving lines such as:
> 9. c2t2104D9600099d0
> /[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]/pci1077,[EMAIL
> PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0
> whereas, again to my recollection, previously the drive man
> On Tue, Aug 21, 2007 at 02:56:11PM -0700, Eric Schrock wrote:
> > What does 'zdb -l /dev/dsk/s0' show for each device?
>
> bash-3.00# zdb -l /dev/dsk/c2t2104D9600099d0s0
> cannot open '/dev/dsk/c2t2104D9600099d0s0': I/O error
> bash-3.00# zdb -l /dev/dsk/c2t2104D9600099d0s1
> cannot
On Tue, Aug 21, 2007 at 03:09:47PM -0700, Eric Schrock wrote:
> There are no ZFS-recognizable labels on this device. Did you explicitly
> create it on slice 2? From the looks of things, it seems like your disk
> label is corrupt...
Not at all (to my recollection, I specified the devices as
"c2t2
There are no ZFS-recognizable labels on this device. Did you explicitly
create it on slice 2? From the looks of things, it seems like your disk
label is corrupt...
- Eric
On Tue, Aug 21, 2007 at 05:00:37PM -0500, Jeff Bachtel wrote:
> On Tue, Aug 21, 2007 at 02:56:11PM -0700, Eric Schrock wrote
On Tue, Aug 21, 2007 at 02:56:11PM -0700, Eric Schrock wrote:
> What does 'zdb -l /dev/dsk/s0' show for each device?
bash-3.00# zdb -l /dev/dsk/c2t2104D9600099d0s0
cannot open '/dev/dsk/c2t2104D9600099d0s0': I/O error
bash-3.00# zdb -l /dev/dsk/c2t2104D9600099d0s1
cannot open '/dev/dsk
What does 'zdb -l /dev/dsk/s0' show for each device?
- Eric
On Tue, Aug 21, 2007 at 04:45:40PM -0500, Jeff Bachtel wrote:
> On Tue, Aug 21, 2007 at 01:39:26PM -0700, Richard Elling wrote:
> > Jeff Bachtel wrote:
> > >On Tue, Aug 21, 2007 at 09:38:17AM -0700, Richard Elling wrote:
> > >>can you se
On Tue, Aug 21, 2007 at 01:39:26PM -0700, Richard Elling wrote:
> Jeff Bachtel wrote:
> >On Tue, Aug 21, 2007 at 09:38:17AM -0700, Richard Elling wrote:
> >>can you see the LUN in format?
> >
> >Yes. Additionally, I can dd from the rdsk device to a file, and get
> >enough data to confirm that the d
After reinstalling a snv62 machine and upgrade a snv64a machine to
snv70, I'm running into "no pools available to import" when I try to
import two existing pools (that were previously mounted on these
machines).
On one host (a new install, I wiped out the snv62 install) the hint
I'm getting is:
A
12 matches
Mail list logo
