On Fri, Apr 16, 2010 at 4:41 PM, Brandon High bh...@freaks.com wrote:
When I set up my opensolaris system at home, I just grabbed a 160 GB
drive that I had sitting around to use for the rpool.
Just to follow up, after testing in Virtualbox, my initial plan is
very close to what worked. This is
I have certainly moved a root pool from one disk to another, with the
same basic process, ie:
- fuss with fdisk and SMI labels (sigh)
- zpool create
- snapshot, send and recv
- installgrub
- swap disks
I looked over the root pool recovery section in the Best Practices guide
at the time,
Yes, I apologize. I didn't notice you were running the OpenSolaris
release. What I outlined below would work on a Solaris 10 system.
I wonder if beadm supports a similar migration. I will find out
and let you know.
Thanks,
Cindy
On 04/19/10 17:22, Brandon High wrote:
On Mon, Apr 19, 2010 at
Brandon,
You can use the OpenSolaris beadm command to migrate a ZFS BE over
to another root pool, but you will also need to perform some manual
migration steps, such as
- copy over your other rpool datasets
- recreate swap and dump devices
- install bootblocks
- update BIOS and GRUB entries to
On Tue, Apr 20, 2010 at 12:55:10PM -0600, Cindy Swearingen wrote:
You can use the OpenSolaris beadm command to migrate a ZFS BE over
to another root pool, but you will also need to perform some manual
migration steps, such as
- copy over your other rpool datasets
- recreate swap and dump
Hi Brandon,
I think I've done a similar migration before by creating a second root
pool, and then create a new BE in the new root pool, like this:
# zpool create rpool2 mirror disk-1 disk2
# lucreate -n newzfsBE -p rpool2
# luactivate newzfsBE
# installgrub ...
reboot to newzfsBE
I don't think
On Mon, Apr 19, 2010 at 7:42 AM, Cindy Swearingen
cindy.swearin...@oracle.com wrote:
I don't think LU cares that the disks in the new pool are smaller,
obviously they need to be large enough to contain the BE.
It doesn't look like OpenSolaris includes LU, at least on x86-64.
Anyhow, wouldn't
On Mon, Apr 19, 2010 at 4:21 PM, Brandon High bh...@freaks.com wrote:
I think I remember someone posting a method to copy the boot drive's layout
with prtvtoc and fmthard, but I don't remember the exact syntax.
Apparently Google and the man pages know the answer.
prtvtoc /dev/rdsk/c5t0d0s2 |
On Apr 19, 2010, at 4:33 PM, Brandon High wrote:
On Mon, Apr 19, 2010 at 4:21 PM, Brandon High bh...@freaks.com wrote:
I think I remember someone posting a method to copy the boot drive's layout
with prtvtoc and fmthard, but I don't remember the exact syntax.
Apparently Google and the man
When I set up my opensolaris system at home, I just grabbed a 160 GB
drive that I had sitting around to use for the rpool.
Now I'm thinking of moving the rpool to another disk, probably ssd,
and I don't really want to shell out the money for two 160 GB drives.
I'm currently using ~ 18GB in the
On 04/17/10 11:41 AM, Brandon High wrote:
When I set up my opensolaris system at home, I just grabbed a 160 GB
drive that I had sitting around to use for the rpool.
Now I'm thinking of moving the rpool to another disk, probably ssd,
and I don't really want to shell out the money for two 160 GB
On 04/16/10 07:41 PM, Brandon High wrote:
1. Attach the new drives.
2. Reboot from LiveCD.
3. zpool create new_rpool on the ssd
Is step 2 actually necessary? Couldn't you create a new BE
# beadm create old_rpool
# beadm activate old_rpool
# reboot
# beadm delete rpool
It's the same number
On 04/16/10 08:57 PM, Frank Middleton wrote:
AFAIK the official syntax for installing the MBR is
# installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk
/dev/rdsk/ssd
Sorry, that's for SPARC. You had the installgrub down correctly...
___
On Fri, Apr 16, 2010 at 5:57 PM, Frank Middleton
f.middle...@apogeect.com wrote:
Is step 2 actually necessary? Couldn't you create a new BE
# beadm create old_rpool
# beadm activate old_rpool
# reboot
# beadm delete rpool
Right now, my boot environments are named after the build it's
On 04/16/10 09:53 PM, Brandon High wrote:
Right now, my boot environments are named after the build it's
running. I'm guessing that by 'rpool' you mean the current BE above.
No, I didn't :-(. Please ignore that part - too much caffeine :-).
I figure that by booting to a live cd / live usb,
15 matches
Mail list logo
