`<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"> On 24/09/14 15:58, Tom Robinson wrote:<br>
</div>
<blockquote cite="mid:54225D6E.1040906@motec.com.au" type="cite">
<pre wrap="">On 24/09/14 15:47, Tom Robinson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 24/09/14 15:40, Tom Robinson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 24/09/14 15:35, Dan McDonald wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Sep 24, 2014, at 1:33 AM, Tom Robinson <a class="moz-txt-link-rfc2396E" href="mailto:tom.robinson@motec.com.au"><tom.robinson@motec.com.au></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Thanks Dan, I can see where you're going with that idea. Should I pay any attention to:
Partition 0 of the disk has an incorrect offset
Unable to gather device information for /dev/rdsk/c4t3d0s0
</pre>
</blockquote>
<pre wrap="">That is a bit disturbing.
What about the other one in the mirror? c4t2d0s0 ?
</pre>
</blockquote>
<pre wrap="">Nothing reported by beadm. I'm not sure if c4t3d0s0 is first or last according to installgrub. Is
the only way to tell by running installgrub? I get nervous at this point. Also my next maintenance
window will most likely not be until next week.
In theory, installgrub shouldn't have any influence on the currently booted system, right?
</pre>
</blockquote>
<pre wrap="">Ok, since c4t3d0s0 IS failing to accept the installgrub here goes:
# installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c4t3d0s0
Partition 0 of the disk has an incorrect offset
Unable to gather device information for /dev/rdsk/c4t3d0s0
and
# installgrub /mnt/boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c4t3d0s0
Partition 0 of the disk has an incorrect offset
Unable to gather device information for /dev/rdsk/c4t3d0s0
I'm still nervous about running this on my (apparently) only bootable disk... (c4t2d0s0)
</pre>
</blockquote>
<pre wrap="">prtvtoc shows cylinders and accessible cylinders differ by one:
# prtvtoc /dev/rdsk/c4t3d0s0
* /dev/rdsk/c4t3d0s0 partition map
*
* Dimensions:
* 512 bytes/sector
* 56 sectors/track
* 224 tracks/cylinder
* 12544 sectors/cylinder
* 18689 cylinders
* 18687 accessible cylinders
*
* Flags:
* 1: unmountable
* 10: read-only
*
* Unallocated space:
* First Sector Last
* Sector Count Sector
* 0 12544 12543
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 2 00 12544 234384640 234397183
2 5 01 0 234422272 234422271
8 1 01 0 12544 12543
# prtvtoc /dev/rdsk/c4t2d0s0
* /dev/rdsk/c4t2d0s0 partition map
*
* Dimensions:
* 512 bytes/sector
* 56 sectors/track
* 224 tracks/cylinder
* 12544 sectors/cylinder
* 18688 cylinders
* 18686 accessible cylinders
*
* Flags:
* 1: unmountable
* 10: read-only
*
* Unallocated space:
* First Sector Last
* Sector Count Sector
* 0 12544 12543
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 2 00 12544 234384640 234397183
2 5 01 0 234422272 234422271
8 1 01 0 12544 12543
# prtvtoc /dev/rdsk/c4t3d0s0 > /tmp/prtvtoc-c4t3d0s0
# prtvtoc /dev/rdsk/c4t2d0s0 > /tmp/prtvtoc-c4t2d0s0
# diff /tmp/prtvtoc-c4t2d0s0 /tmp/prtvtoc-c4t3d0s0
1c1
< * /dev/rdsk/c4t2d0s0 partition map
---
</pre>
<blockquote type="cite">
<pre wrap="">* /dev/rdsk/c4t3d0s0 partition map
</pre>
</blockquote>
<pre wrap="">8,9c8,9
< * 18688 cylinders
< * 18686 accessible cylinders
---
</pre>
<blockquote type="cite">
<pre wrap="">* 18689 cylinders
* 18687 accessible cylinders
</pre>
</blockquote>
</blockquote>
<br>
Maybe recreating the mirror would work. Not sure what happened but I
could possibly follow this:<br>
<br>
<a class="moz-txt-link-freetext"
href="http://malsserver.blogspot.com.au/2008/08/mirroring-resolved-correct-way.html">http://malsserver.blogspot.com.au/2008/08/mirroring-resolved-correct-way.html</a><br>
<br>
Especially note comments by
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
Malachi de Ælfweald 11/25/2008 8:49 PM<br>
>> before doing the fmthard, you have to do fdisk on the new
drive<br>
<br>
</body>
</html>
`