Op 28-1-2010 17:35, Cindy Swearingen schreef:
Thomas,
Excellent and much better suggestion... :-)
You can use beadm to specify another root pool by using the -p option.
The beadm operation will set the bootfs pool property and update the
GRUB entry.
It turns out not to be excellent at all.
Hi Dick,
I have an OpenSolaris release running on my laptop with one disk
so I can't confirm your results below. But before you go the
snapshot route, let me see if I can get some info on the beadm
solution.
I have done similar transitions with LU on Nevada releases and
I can easily boot from
Cindy Swearingen wrote:
On some disks, the default partitioning is not optimal and you have to
modify it so that the bulk of the disk space is in slice 0.
Yes, I know, but in this case the second disk indeed is smaller ;-(
So I wonder, should I reinstall the whole thing on this smaller disk
Hi Dick,
Yes, you can use zfs send|recv to recreate the root pool snapshots on
the other disk in addition to the other steps that are needed for full
root pool recovery is my assessment. See the link below, following the
steps for storing the root pool snapshots as snapshots rather than
files. I
On 28.01.2010 15:55, dick hoogendijk wrote:
Cindy Swearingen wrote:
On some disks, the default partitioning is not optimal and you have to
modify it so that the bulk of the disk space is in slice 0.
Yes, I know, but in this case the second disk indeed is smaller ;-(
So I wonder, should
Thomas,
Excellent and much better suggestion... :-)
You can use beadm to specify another root pool by using the -p option.
The beadm operation will set the bootfs pool property and update the
GRUB entry.
Dick, you will need to update the BIOS to boot from the smaller disk.
Thanks,
Cindy
Op 28-1-2010 16:52, Thomas Maier-Komor schreef:
have you considered creating an alternate boot environment on the
smaller disk, rebooting into this new boot environment, and then
attaching the larger disk after destroy the old boot environment?
beadm might do this job for you...
What a
Op 28-1-2010 17:35, Cindy Swearingen schreef:
Thomas,
Excellent and much better suggestion... :-)
You can use beadm to specify another root pool by using the -p option.
The beadm operation will set the bootfs pool property and update the
GRUB entry.
Dick, you will need to update the BIOS to
Op 28-1-2010 17:35, Cindy Swearingen schreef:
Thomas,
Excellent and much better suggestion... :-)
You can use beadm to specify another root pool by using the -p option.
The beadm operation will set the bootfs pool property and update the
GRUB entry.
Dick, you will need to update the BIOS to
On 01/28/10 12:05, Dick Hoogendijk wrote:
Op 28-1-2010 17:35, Cindy Swearingen schreef:
Thomas,
Excellent and much better suggestion... :-)
You can use beadm to specify another root pool by using the -p option.
The beadm operation will set the bootfs pool property and update the
GRUB entry.
On Thu, 2010-01-28 at 12:34 -0700, Lori Alt wrote:
But those could be copied by send/recv from the larger disk (current
root pool) to the smaller disk (intended new root pool). You won't be
attaching anything until you can boot off the smaller disk and then it
won't matter what's on the
On 01/28/10 14:08, dick hoogendijk wrote:
On Thu, 2010-01-28 at 12:34 -0700, Lori Alt wrote:
But those could be copied by send/recv from the larger disk (current
root pool) to the smaller disk (intended new root pool). You won't be
attaching anything until you can boot off the smaller disk
On 01/28/10 14:19, Lori Alt wrote:
On 01/28/10 14:08, dick hoogendijk wrote:
On Thu, 2010-01-28 at 12:34 -0700, Lori Alt wrote:
But those could be copied by send/recv from the larger disk (current
root pool) to the smaller disk (intended new root pool). You won't be
attaching anything
On Thu, 2010-01-28 at 08:44 -0700, Cindy Swearingen wrote:
Or, if possible, connect another larger disk and attach it to the original
root
disk or even replace the smaller root pool disk with the larger disk.
I go for that one. But since it's a smoewhat older system I only have
IDE and
I think the SATA(2)--SATA(1) connection will negotiate correctly,
but maybe some hardware expert will confirm.
cs
On 01/28/10 15:27, dick hoogendijk wrote:
On Thu, 2010-01-28 at 08:44 -0700, Cindy Swearingen wrote:
Or, if possible, connect another larger disk and attach it to the original
cannot attach c5d0s0 to c4d0s0: device is too small
So I guess I installed OpenSolaris onto the smallest disk. Now I cannot
create a mirrored root, because the device is smaller.
What is the best way to correct this except starting all over with two
disks of the same size (which I don't have)?
Hi Dick,
Based on this message:
cannot attach c5d0s0 to c4d0s0: device is too small
c5d0s0 is the disk you are trying to attach so it must be smaller than
c4d0s0.
Is it possible that c5d0s0 is just partitioned so that the s0 is smaller
than s0 on c4d0s0?
On some disks, the default
17 matches
Mail list logo
