I have multiple servers, all with the same configuration of mirrored zfs root pools. I''ve been asked how to take a potentially "damaged" disk from one machine and carry it to another machine, in the event that some hw failure prevents fixing a boot problem in place. So we have one half of mirror of rpool that we want to take to another system that already has an rpool and we want to import the second rpool. The second system has enough disk slots to add the third disk. I believe the answer is to use zpool import to get the id number of the non-native rpool then use zpool import -f <id#> -R /mnt newpool but I don''t really have a way to check this... Thanks Jay -- This message posted from opensolaris.org
On Wed, Jun 16, 2010 at 10:24 AM, Jay Seaman <john.seaman at americas.ing.com> wrote:> zpool import > > to get the id number of the non-native rpoolYou''ll get the names and IDs for any un-imported pools.> then use > zpool import -f <id#> -R /mnt newpoolThat should work. You may have to put the pool id after the -R argument though. You''re renaming to pool in the process, so it may not work in the original host afterwards, since it expects the pool name to be rpool. You could boot a system off the LiveCD (which doesn''t have an rpool) and import it without changing the name. -B -- Brandon High : bhigh at freaks.com
Could you import it back on the original server with Zpool import -f newpool rpool? Jay -----Original Message----- From: Brandon High [mailto:bhigh at freaks.com] Sent: Wednesday, June 16, 2010 2:19 PM To: Seaman, John Cc: zfs-discuss at opensolaris.org Subject: Re: [zfs-discuss] mount zfs boot disk on another server? On Wed, Jun 16, 2010 at 10:24 AM, Jay Seaman <john.seaman at americas.ing.com> wrote:> zpool import > > to get the id number of the non-native rpoolYou''ll get the names and IDs for any un-imported pools.> then use > zpool import -f <id#> -R /mnt newpoolThat should work. You may have to put the pool id after the -R argument though. You''re renaming to pool in the process, so it may not work in the original host afterwards, since it expects the pool name to be rpool. You could boot a system off the LiveCD (which doesn''t have an rpool) and import it without changing the name. -B -- Brandon High : bhigh at freaks.com -------------------------------------------------------------------------------------------------------------------------------------------------------- The information in this Internet e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). Access to this Internet e-mail by anyone else is unauthorized. If you are not the intended recipient of this e-mail, any disclosure, copying, or distribution of it is prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender and immediately and permanently delete it and destroy any copies of it that were printed out. When addressed to our clients any opinions or advice contained in this Internet e-mail is subject to the terms and conditions expressed in any applicable governing ING terms of business or client engagement letter. Visit us at www.ing.com --------------------------------------------------------------------------------------------------------------------------------------------------------
On Wed, Jun 16, 2010 at 11:32 AM, Seaman, John <John.Seaman at americas.ing.com> wrote:> Could you import it back on the original server with > > Zpool import -f newpool rpool?If you''re trying to boot off of it on the original host (which is likely, since it''s the rpool) then you may not be able to if the pool is named something else. There was some discussion on the list of what steps are required to rename the rpool, one of which was creating a new BE. -B -- Brandon High : bhigh at freaks.com
Cindy Swearingen
2010-Jun-16 22:35 UTC
[zfs-discuss] mount zfs boot disk on another server?
Hi Jay, I think you mean you want to connect the disk with a potentially damaged ZFS BE on another system and mount the ZFS BE for possible repair purposes. This recovery method is complicated by the fact that changing the root pool name can cause the original system not to boot. Other potential options that don''t involve moving disks are: 1. Boot from a local or shared CD or netinstall server in single-user mode and import the local root pool. 2. On a Solaris 10 system, you can attempt to boot failsafe mode and roll back the ZFS BE snapshot. 3. Extensive disaster recovery: - Send a remote copy of the ZFS BE snapshot back to the local system - Create a flash archive of the root pool (Solaris 10) Thanks, Cindy On 06/16/10 11:24, Jay Seaman wrote:> I have multiple servers, all with the same configuration of mirrored zfs root pools. I''ve been asked how to take a potentially "damaged" disk from one machine and carry it to another machine, in the event that some hw failure prevents fixing a boot problem in place. So we have one half of mirror of rpool that we want to take to another system that already has an rpool and we want to import the second rpool. The second system has enough disk slots to add the third disk. > > I believe the answer is to use > > zpool import > > to get the id number of the non-native rpool > > then use > zpool import -f <id#> -R /mnt newpool > > but I don''t really have a way to check this... > > Thanks > > Jay