Re: [zfs-discuss] addendum: zpool UNAVAIL even though disk is online: another label issue?
Victor Latushkin wrote: I think you need to get a closer look at your another disk. Is it possible to get result of (change controller/target numbers as appropriate if needed) dd if=/dev/rdsk/c8t0d0p0 bs=1024k count=4 | bzip2 -9 > c8t0d0p0.front.bz2 while booted off OpenSolaris CD? not anymore - I realised I had no relevant data on the box, so I re-installed to get going again. thx Michael -- Michael Schuster http://blogs.sun.com/recursion Recursion, n.: see 'Recursion' ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] addendum: zpool UNAVAIL even though disk is online: another label issue?
On 18.09.09 23:51, michael schuster wrote: Cindy Swearingen wrote: Michael, Get some rest. :-) Then see if you can import your root pool while booted from the LiveCD. that's what I tried - I'm never even shown "rpool", I probably wouldn't have mentioned localpool at all if I had ;-) After you get to that point, you might search the indiana-discuss archive for tips on resolving the pkg-image-update no grub menu problem. if I don't see rpool, that's not going to be the next step for me, right? Right. For me it loks like something happened to the partitioning of your root disks so while grub is still there and working in cannot find any partition it can recognize and load menu.lst from. I think you need to get a closer look at your another disk. Is it possible to get result of (change controller/target numbers as appropriate if needed) dd if=/dev/rdsk/c8t0d0p0 bs=1024k count=4 | bzip2 -9 > c8t0d0p0.front.bz2 while booted off OpenSolaris CD? Cheers, victor thx Michael Cindy On 09/18/09 12:08, michael schuster wrote: Cindy Swearingen wrote: Michael, ZFS handles EFI labels just fine, but you need an SMI label on the disk that you are booting from. Are you saying that localtank is your root pool? no... (I was on the plane yesterday, I'm still jet-lagged), I should have realised that that's strange. I believe the OSOL install creates a root pool called rpool. I don't remember if its configurable. I didn't do anything to change that. This leads me to the assumption that the disk I should be looking at is actually c8t0d0, the "other" disk in the format output. Can you describe the changes other than the pkg-image-update that lead up to this problem? 0) pkg refresh; pkg install SUNWipkg 1) pkg image-update (creates opensolaris-119) 2) pkg mount opensolaris-119 /mnt 3) cat /mnt/etc/release (to verify I'd indeed installed b123) 4) pkg umount opensolaris-119 5) pkg rename opensolaris-119 opensolaris-123 # this failed, because it's active 6) pkg activate opensolaris-118 # so I can rename the new one 7) pkg rename ... 8) pkg activate opensolaris-123 9) reboot thx Michael Cindy On 09/18/09 11:05, michael schuster wrote: michael schuster wrote: All, this morning, I did "pkg image-update" from 118 to 123 (internal repo), and upon reboot all I got was the grub prompt - no menu, nothing. I found a 2009.06 CD, and when I boot that and run "zpool import", I get told localtank UNAVAIL insufficient replicas c8t1d0ONLINE some research showed that disklabel changes sometimes cause this, so I ran format: AVAILABLE DISK SELECTIONS: 0. c8t0d0 /p...@0,0/pci108e,5...@7/d...@0,0 1. c8t1d0 /p...@0,0/pci108e,5...@7/d...@1,0 Specify disk (enter its number): 1 selecting c8t1d0 [disk formatted] Note: capacity in disk label is smaller than the real disk capacity. Select to adjust the label capacity. [..] partition> print Current partition table (original): Total disk sectors available: 781401310 + 16384 (reserved sectors) Part TagFlag First Sector Size Last Sector 0usrwm 256 372.60GB 781401310 1 unassignedwm 0 0 0 2 unassignedwm 0 0 0 3 unassignedwm 0 0 0 4 unassignedwm 0 0 0 5 unassignedwm 0 0 0 6 unassignedwm 0 0 0 8 reservedwm 7814013118.00MB 781417694 Format already tells me that the label doesn't align with the disk size ... should I just do "expand", or should I change the first sectore of partition 0 to be 0? I'd appreciate advice on the above, and on how to avoid this in the future. I just found out that this disk has been EFI-labelled, which I understand isn't what zfs like/expects. what to do now? TIA Michael ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] addendum: zpool UNAVAIL even though disk is online: another label issue?
Cindy Swearingen wrote: Michael, Get some rest. :-) Then see if you can import your root pool while booted from the LiveCD. that's what I tried - I'm never even shown "rpool", I probably wouldn't have mentioned localpool at all if I had ;-) After you get to that point, you might search the indiana-discuss archive for tips on resolving the pkg-image-update no grub menu problem. if I don't see rpool, that's not going to be the next step for me, right? thx Michael Cindy On 09/18/09 12:08, michael schuster wrote: Cindy Swearingen wrote: Michael, ZFS handles EFI labels just fine, but you need an SMI label on the disk that you are booting from. Are you saying that localtank is your root pool? no... (I was on the plane yesterday, I'm still jet-lagged), I should have realised that that's strange. I believe the OSOL install creates a root pool called rpool. I don't remember if its configurable. I didn't do anything to change that. This leads me to the assumption that the disk I should be looking at is actually c8t0d0, the "other" disk in the format output. Can you describe the changes other than the pkg-image-update that lead up to this problem? 0) pkg refresh; pkg install SUNWipkg 1) pkg image-update (creates opensolaris-119) 2) pkg mount opensolaris-119 /mnt 3) cat /mnt/etc/release (to verify I'd indeed installed b123) 4) pkg umount opensolaris-119 5) pkg rename opensolaris-119 opensolaris-123 # this failed, because it's active 6) pkg activate opensolaris-118 # so I can rename the new one 7) pkg rename ... 8) pkg activate opensolaris-123 9) reboot thx Michael Cindy On 09/18/09 11:05, michael schuster wrote: michael schuster wrote: All, this morning, I did "pkg image-update" from 118 to 123 (internal repo), and upon reboot all I got was the grub prompt - no menu, nothing. I found a 2009.06 CD, and when I boot that and run "zpool import", I get told localtank UNAVAIL insufficient replicas c8t1d0ONLINE some research showed that disklabel changes sometimes cause this, so I ran format: AVAILABLE DISK SELECTIONS: 0. c8t0d0 /p...@0,0/pci108e,5...@7/d...@0,0 1. c8t1d0 /p...@0,0/pci108e,5...@7/d...@1,0 Specify disk (enter its number): 1 selecting c8t1d0 [disk formatted] Note: capacity in disk label is smaller than the real disk capacity. Select to adjust the label capacity. [..] partition> print Current partition table (original): Total disk sectors available: 781401310 + 16384 (reserved sectors) Part TagFlag First Sector Size Last Sector 0usrwm 256 372.60GB 781401310 1 unassignedwm 0 0 0 2 unassignedwm 0 0 0 3 unassignedwm 0 0 0 4 unassignedwm 0 0 0 5 unassignedwm 0 0 0 6 unassignedwm 0 0 0 8 reservedwm 7814013118.00MB 781417694 Format already tells me that the label doesn't align with the disk size ... should I just do "expand", or should I change the first sectore of partition 0 to be 0? I'd appreciate advice on the above, and on how to avoid this in the future. I just found out that this disk has been EFI-labelled, which I understand isn't what zfs like/expects. what to do now? TIA Michael -- Michael Schuster http://blogs.sun.com/recursion Recursion, n.: see 'Recursion' ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] addendum: zpool UNAVAIL even though disk is online: another label issue?
Michael, Get some rest. :-) Then see if you can import your root pool while booted from the LiveCD. After you get to that point, you might search the indiana-discuss archive for tips on resolving the pkg-image-update no grub menu problem. Cindy On 09/18/09 12:08, michael schuster wrote: Cindy Swearingen wrote: Michael, ZFS handles EFI labels just fine, but you need an SMI label on the disk that you are booting from. Are you saying that localtank is your root pool? no... (I was on the plane yesterday, I'm still jet-lagged), I should have realised that that's strange. I believe the OSOL install creates a root pool called rpool. I don't remember if its configurable. I didn't do anything to change that. This leads me to the assumption that the disk I should be looking at is actually c8t0d0, the "other" disk in the format output. Can you describe the changes other than the pkg-image-update that lead up to this problem? 0) pkg refresh; pkg install SUNWipkg 1) pkg image-update (creates opensolaris-119) 2) pkg mount opensolaris-119 /mnt 3) cat /mnt/etc/release (to verify I'd indeed installed b123) 4) pkg umount opensolaris-119 5) pkg rename opensolaris-119 opensolaris-123 # this failed, because it's active 6) pkg activate opensolaris-118 # so I can rename the new one 7) pkg rename ... 8) pkg activate opensolaris-123 9) reboot thx Michael Cindy On 09/18/09 11:05, michael schuster wrote: michael schuster wrote: All, this morning, I did "pkg image-update" from 118 to 123 (internal repo), and upon reboot all I got was the grub prompt - no menu, nothing. I found a 2009.06 CD, and when I boot that and run "zpool import", I get told localtank UNAVAIL insufficient replicas c8t1d0ONLINE some research showed that disklabel changes sometimes cause this, so I ran format: AVAILABLE DISK SELECTIONS: 0. c8t0d0 /p...@0,0/pci108e,5...@7/d...@0,0 1. c8t1d0 /p...@0,0/pci108e,5...@7/d...@1,0 Specify disk (enter its number): 1 selecting c8t1d0 [disk formatted] Note: capacity in disk label is smaller than the real disk capacity. Select to adjust the label capacity. [..] partition> print Current partition table (original): Total disk sectors available: 781401310 + 16384 (reserved sectors) Part TagFlag First Sector Size Last Sector 0usrwm 256 372.60GB 781401310 1 unassignedwm 0 0 0 2 unassignedwm 0 0 0 3 unassignedwm 0 0 0 4 unassignedwm 0 0 0 5 unassignedwm 0 0 0 6 unassignedwm 0 0 0 8 reservedwm 7814013118.00MB 781417694 Format already tells me that the label doesn't align with the disk size ... should I just do "expand", or should I change the first sectore of partition 0 to be 0? I'd appreciate advice on the above, and on how to avoid this in the future. I just found out that this disk has been EFI-labelled, which I understand isn't what zfs like/expects. what to do now? TIA Michael ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] addendum: zpool UNAVAIL even though disk is online: another label issue?
Cindy Swearingen wrote: Michael, ZFS handles EFI labels just fine, but you need an SMI label on the disk that you are booting from. Are you saying that localtank is your root pool? no... (I was on the plane yesterday, I'm still jet-lagged), I should have realised that that's strange. I believe the OSOL install creates a root pool called rpool. I don't remember if its configurable. I didn't do anything to change that. This leads me to the assumption that the disk I should be looking at is actually c8t0d0, the "other" disk in the format output. Can you describe the changes other than the pkg-image-update that lead up to this problem? 0) pkg refresh; pkg install SUNWipkg 1) pkg image-update (creates opensolaris-119) 2) pkg mount opensolaris-119 /mnt 3) cat /mnt/etc/release (to verify I'd indeed installed b123) 4) pkg umount opensolaris-119 5) pkg rename opensolaris-119 opensolaris-123 # this failed, because it's active 6) pkg activate opensolaris-118 # so I can rename the new one 7) pkg rename ... 8) pkg activate opensolaris-123 9) reboot thx Michael Cindy On 09/18/09 11:05, michael schuster wrote: michael schuster wrote: All, this morning, I did "pkg image-update" from 118 to 123 (internal repo), and upon reboot all I got was the grub prompt - no menu, nothing. I found a 2009.06 CD, and when I boot that and run "zpool import", I get told localtank UNAVAIL insufficient replicas c8t1d0ONLINE some research showed that disklabel changes sometimes cause this, so I ran format: AVAILABLE DISK SELECTIONS: 0. c8t0d0 /p...@0,0/pci108e,5...@7/d...@0,0 1. c8t1d0 /p...@0,0/pci108e,5...@7/d...@1,0 Specify disk (enter its number): 1 selecting c8t1d0 [disk formatted] Note: capacity in disk label is smaller than the real disk capacity. Select to adjust the label capacity. [..] partition> print Current partition table (original): Total disk sectors available: 781401310 + 16384 (reserved sectors) Part TagFlag First Sector Size Last Sector 0usrwm 256 372.60GB 781401310 1 unassignedwm 0 0 0 2 unassignedwm 0 0 0 3 unassignedwm 0 0 0 4 unassignedwm 0 0 0 5 unassignedwm 0 0 0 6 unassignedwm 0 0 0 8 reservedwm 7814013118.00MB 781417694 Format already tells me that the label doesn't align with the disk size ... should I just do "expand", or should I change the first sectore of partition 0 to be 0? I'd appreciate advice on the above, and on how to avoid this in the future. I just found out that this disk has been EFI-labelled, which I understand isn't what zfs like/expects. what to do now? TIA Michael -- Michael Schuster http://blogs.sun.com/recursion Recursion, n.: see 'Recursion' ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] addendum: zpool UNAVAIL even though disk is online: another label issue?
Michael, ZFS handles EFI labels just fine, but you need an SMI label on the disk that you are booting from. Are you saying that localtank is your root pool? I believe the OSOL install creates a root pool called rpool. I don't remember if its configurable. Changing labels or partitions from beneath a live pool isn't supported and can cause data loss. Can you describe the changes other than the pkg-image-update that lead up to this problem? Cindy On 09/18/09 11:05, michael schuster wrote: michael schuster wrote: All, this morning, I did "pkg image-update" from 118 to 123 (internal repo), and upon reboot all I got was the grub prompt - no menu, nothing. I found a 2009.06 CD, and when I boot that and run "zpool import", I get told localtank UNAVAIL insufficient replicas c8t1d0ONLINE some research showed that disklabel changes sometimes cause this, so I ran format: AVAILABLE DISK SELECTIONS: 0. c8t0d0 /p...@0,0/pci108e,5...@7/d...@0,0 1. c8t1d0 /p...@0,0/pci108e,5...@7/d...@1,0 Specify disk (enter its number): 1 selecting c8t1d0 [disk formatted] Note: capacity in disk label is smaller than the real disk capacity. Select to adjust the label capacity. [..] partition> print Current partition table (original): Total disk sectors available: 781401310 + 16384 (reserved sectors) Part TagFlag First Sector Size Last Sector 0usrwm 256 372.60GB 781401310 1 unassignedwm 0 0 0 2 unassignedwm 0 0 0 3 unassignedwm 0 0 0 4 unassignedwm 0 0 0 5 unassignedwm 0 0 0 6 unassignedwm 0 0 0 8 reservedwm 7814013118.00MB 781417694 Format already tells me that the label doesn't align with the disk size ... should I just do "expand", or should I change the first sectore of partition 0 to be 0? I'd appreciate advice on the above, and on how to avoid this in the future. I just found out that this disk has been EFI-labelled, which I understand isn't what zfs like/expects. what to do now? TIA Michael ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
