Prev: SunRay with different displays
Next: The IP address previously set on the network interface is no longeravailable
From: rocker on 16 Dec 2009 09:48 Hi I have mirrored the two internal disks on a V490 for my rpool. I want to take a SAN LUN which is the same size as the internal disks, add it to the mirror, remove the two internal disks from the mirror effectively breaking the mirror, simply making the SAN LUN as my rpool. Will the below process work: Again rpool is an existing mirror using 2 internal disks add SAN LUN to rpool # zpool attach rpool c4t60060E800547670000004767000003D8d0 3 way mirror created... so now wait for it to resilver remove internal disks # zpool detach rpool c1t1d0s0 # zpool detach rpool c2t1d0s0 Setup OBP boot-device boot string. Will rpool be bootable if I do this? Thank you
From: Zfs.. on 16 Dec 2009 10:51 On Dec 16, 2:48 pm, rocker <rocke.robert...(a)pwgsc.gc.ca> wrote: > Hi > > I have mirrored the two internal disks on a V490 for my rpool. I want > to take a SAN LUN which is the same size as the internal disks, add it > to the mirror, remove the two internal disks from the mirror > effectively breaking the mirror, simply making the SAN LUN as my > rpool. > > Will the below process work: > > Again rpool is an existing mirror using 2 internal disks > > add SAN LUN to rpool > > # zpool attach rpool c4t60060E800547670000004767000003D8d0 > > 3 way mirror created... so now wait for it to resilver > > remove internal disks > > # zpool detach rpool c1t1d0s0 > # zpool detach rpool c2t1d0s0 > > Setup OBP boot-device boot string. Will rpool be bootable if I do > this? > > Thank you You need to install the boot block to make the device bootable. The command is something like installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/ rdsk/c4t60060E800547670000004767000003D8d0
From: cindy on 16 Dec 2009 10:59 On Dec 16, 7:48 am, rocker <rocke.robert...(a)pwgsc.gc.ca> wrote: > Hi > > I have mirrored the two internal disks on a V490 for my rpool. I want > to take a SAN LUN which is the same size as the internal disks, add it > to the mirror, remove the two internal disks from the mirror > effectively breaking the mirror, simply making the SAN LUN as my > rpool. > > Will the below process work: > > Again rpool is an existing mirror using 2 internal disks > > add SAN LUN to rpool > > # zpool attach rpool c4t60060E800547670000004767000003D8d0 > > 3 way mirror created... so now wait for it to resilver > > remove internal disks > > # zpool detach rpool c1t1d0s0 > # zpool detach rpool c2t1d0s0 > > Setup OBP boot-device boot string. Will rpool be bootable if I do > this? > > Thank you Hi Rocker, A few things to think about/to do: 1. I'm not so good with SAN-level stuff, but I thought not all SAN disks are bootable so be sure that they are. 2. The SAN disks will need an SMI label and a slice 0. When you attach them, you'll need to specify the slice identifier. For example, on my 3510 ARRAY, and I don't think these disks are bootable, the syntax would look like this: # zpool attach rpool c0t0d0s0 c1t226000C0FFA001ABd7s0 Your syntax above is missing the s0. 3. Apply boot blocks to the SAN disks after they are attached and have resilvered successfully. 4. Confirm that the SAN disks boot successfully before you de-attach your internal disks. See this section for more examples: http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#Replacing.2FRelabeling_the_Root_Pool_Disk Thanks, Cindy
From: rocker on 16 Dec 2009 13:03 On Dec 16, 10:59 am, cindy <cindy.swearin...(a)sun.com> wrote: > On Dec 16, 7:48 am, rocker <rocke.robert...(a)pwgsc.gc.ca> wrote: > > > > > > > Hi > > > I have mirrored the two internal disks on a V490 for my rpool. I want > > to take a SAN LUN which is the same size as the internal disks, add it > > to the mirror, remove the two internal disks from the mirror > > effectively breaking the mirror, simply making the SAN LUN as my > > rpool. > > > Will the below process work: > > > Again rpool is an existing mirror using 2 internal disks > > > add SAN LUN to rpool > > > # zpool attach rpool c4t60060E800547670000004767000003D8d0 > > > 3 way mirror created... so now wait for it to resilver > > > remove internal disks > > > # zpool detach rpool c1t1d0s0 > > # zpool detach rpool c2t1d0s0 > > > Setup OBP boot-device boot string. Will rpool be bootable if I do > > this? > > > Thank you > > Hi Rocker, > > A few things to think about/to do: > > 1. I'm not so good with SAN-level stuff, but I thought not all SAN > disks are bootable > so be sure that they are. > > 2. The SAN disks will need an SMI label and a slice 0. When you attach > them, you'll > need to specify the slice identifier. For example, on my 3510 ARRAY, > and I don't think > these disks are bootable, the syntax would look like this: > > # zpool attach rpool c0t0d0s0 c1t226000C0FFA001ABd7s0 > > Your syntax above is missing the s0. > > 3. Apply boot blocks to the SAN disks after they are attached and have > resilvered > successfully. > > 4. Confirm that the SAN disks boot successfully before you de-attach > your internal disks. > > See this section for more examples:http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Gu... > > Thanks, > > Cindy- Hide quoted text - > > - Show quoted text - Hi Cindy We've booted of SAN for a while and it works great. HDS & EMC are fine, IBM pretty much doesn't work with the Sun's or HP's. Lovely ;D Re. slice 0, I thought it was assumed, but I will add that to my process. Re. SAN, it's funny when I try and make an alternate BE for DR purposes. I change the disk label to SMI, create the rpool2, and lucreate. Lucreate fails with the usual: # lucreate -n new-zfsBE-1 -p rpool2 Analyzing system configuration. ERROR: ZFS pool <rpool1> does not support boot environments I go back and check SAN disk, and the label is set back to EFI? If I create a BE on a local disk, it works fine once I set the label to SMI. Why or how on earth does the label change on the HDS SAN LUN when I do a lucreate? FC drivers? Sorry, this one is off topic but I had to ask / rant. Cheers
From: cindy on 16 Dec 2009 14:19 On Dec 16, 11:03 am, rocker <rocke.robert...(a)pwgsc.gc.ca> wrote: > On Dec 16, 10:59 am, cindy <cindy.swearin...(a)sun.com> wrote: > > > > > On Dec 16, 7:48 am, rocker <rocke.robert...(a)pwgsc.gc.ca> wrote: > > > > Hi > > > > I have mirrored the two internal disks on a V490 for my rpool. I want > > > to take a SAN LUN which is the same size as the internal disks, add it > > > to the mirror, remove the two internal disks from the mirror > > > effectively breaking the mirror, simply making the SAN LUN as my > > > rpool. > > > > Will the below process work: > > > > Again rpool is an existing mirror using 2 internal disks > > > > add SAN LUN to rpool > > > > # zpool attach rpool c4t60060E800547670000004767000003D8d0 > > > > 3 way mirror created... so now wait for it to resilver > > > > remove internal disks > > > > # zpool detach rpool c1t1d0s0 > > > # zpool detach rpool c2t1d0s0 > > > > Setup OBP boot-device boot string. Will rpool be bootable if I do > > > this? > > > > Thank you > > > Hi Rocker, > > > A few things to think about/to do: > > > 1. I'm not so good with SAN-level stuff, but I thought not all SAN > > disks are bootable > > so be sure that they are. > > > 2. The SAN disks will need an SMI label and a slice 0. When you attach > > them, you'll > > need to specify the slice identifier. For example, on my 3510 ARRAY, > > and I don't think > > these disks are bootable, the syntax would look like this: > > > # zpool attach rpool c0t0d0s0 c1t226000C0FFA001ABd7s0 > > > Your syntax above is missing the s0. > > > 3. Apply boot blocks to the SAN disks after they are attached and have > > resilvered > > successfully. > > > 4. Confirm that the SAN disks boot successfully before you de-attach > > your internal disks. > > > See this section for more examples:http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Gu... > > > Thanks, > > > Cindy- Hide quoted text - > > > - Show quoted text - > > Hi Cindy > > We've booted of SAN for a while and it works great. HDS & EMC are > fine, IBM pretty much doesn't work with the Sun's or HP's. Lovely ;D > > Re. slice 0, I thought it was assumed, but I will add that to my > process. > > Re. SAN, it's funny when I try and make an alternate BE for DR > purposes. I change the disk label to SMI, create the rpool2, and > lucreate. Lucreate fails with the usual: > > # lucreate -n new-zfsBE-1 -p rpool2 > Analyzing system configuration. > ERROR: ZFS pool <rpool1> does not support boot environments > > I go back and check SAN disk, and the label is set back to EFI? If I > create a BE on a local disk, it works fine once I set the label to > SMI. Why or how on earth does the label change on the HDS SAN LUN when > I do a lucreate? FC drivers? > > Sorry, this one is off topic but I had to ask / rant. > > Cheers The above lucreate ERROR is pointing to rpool1, not rpool2. Weird. My SAN disk experience is nil but I would like to see the syntax that you used to create rpool2 and rpool1. I assuming you have root pools on two different disks. Even if the disk label is SMI, you still a need a slice from which to boot. Cindy
|
Next
|
Last
Pages: 1 2 3 4 Prev: SunRay with different displays Next: The IP address previously set on the network interface is no longeravailable |