• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1920
  • Last Modified:

After reboot we can’t get it to boot to root mirror - Sun-Fire-280R

Hi Experts,

After reboot we can’t get it to boot to rootmirror since it says it’s not executable.  We are able to access disk from boot cdrom. We installed new boot block but this isn’t working. So for this we need to have servers root drives in the mirrored state. I have not used SVM before. Could some one help me with the commands step by step ? your help is highly appreciated experts.

this started happening in the process of patching. We have the same type of server which we applied the patches But did not had any impact. so does in the process of detaching the mirrors it happens that the boot priority may change. b'se I was simply doing # init 0 & then at ok prompt boot -s and was able to apply the core patch. But later when I had to implement the Misc patch I did init 0 and at ok prompt boot -s it started throwing errors as follows.

panic[cpu0]/thread=180e000: consconfig: unable to find wc device

000000000180b7b0 consconfig_dacf:cons_build_upper_layer+210 (60010d11740, 7bb5c800, ffffffffffffffff, 190dc00, 3, 7bb5c800)
  %l0-3: 00000000018cec00 000000000125fc00 00000300000bdc28 0000000000000000
  %l4-7: 0000000000000000 00000000018c9c00 000000000190dc00 00000000018c2800
000000000180b890 consconfig_dacf:dynamic_console_config+68 (18c2800, ffffffffffffffff, 0, 60010d11740, 1870000, 1870000)
  %l0-3: 00000000018475a8 0000030000c28000 00000000018ca000 00000000018c9800
  %l4-7: 00000000018ca000 00000000018c9c00 00000000018c9c00 00000000018c2800
000000000180b940 unix:stubs_common_code+70 (1527b9d098, c27b8, c8000000, 0, 142d00, 0)
  %l0-3: 000000000180b209 000000000180b2e1 00000000ff000000 0000000000000001
  %l4-7: 0000000000000000 0000000001818ac0 0000000000000000 0000060010ccf1c0
000000000180ba10 genunix:main+13c (18c70e8, 18c2c00, 18397b0, 1879800, 181b578, 1815000)
  %l0-3: 0000000001015400 0000000000000001 0000000070002000 0000000000000002
  %l4-7: 00000000018ca340 00000000018ca000 00000000018c70f8 00000000018c7000

syncing file systems... done
skipping system dump - no dump device configured
rebooting...

Resetting ...

After this for a while we booted from ok prompt with - ok boot disk0 -s it worked and thats how we applied the core patch But after init 0 & ok boot disk0 -s
did not work & corrupted the FS which we repaired with fsck successfully But now it won't boot with ok boot disk0 -s :-(

And we did ok boot disk1 -s it worked ! But since we had applied the patch on disk0, How on the earth we can boot the system from disk0 ? So looks like we have lost the mirroing and we need to mirror disk1 to disk0 back. We can boot from the cdrom - ok boot cdrom -s. Please advise.....  Thanks a lot in advance.

Below are some of the system commands to understand the disk structure.

# uname -a

SunOS  5.10 Generic_144488-14 sun4u sparc SUNW,Sun-Fire-280R

Open in new window


# iostat -en
  ---- errors ---
  s/w h/w trn tot device
    0   0   0   0 ramdisk1
    5   0   0   5 c0t6d0
    0   0   0   0 c1t0d0
    0   0   0   0 c1t1d0


------------------------------

Open in new window



# format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cfa664b9,0
       1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
          /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w21000004cfa66d5f,0
Specify disk (enter its number): ^C
# fsck /dev/rdsk/c1t0d0s0
** /dev/rdsk/c1t0d0s0
** Last Mounted on /
** Phase 1 - Check Blocks and Sizes



SunOS Release 5.10 Version Generic_142900-11 64-bit

Open in new window


rsc> showenvironment


=============== Environmental Status ===============


System Temperatures (Celsius):
------------------------------
      CPU0    52
      CPU1    48
       RSC    27

=================================

RSC Power Status:
-----------------

RSC is running on Normal System Power

RSC Battery Voltage: 4.25V


=================================

Front Status Panel:
-------------------

Keyswitch position is in On mode.


=================================

System LED Status: GENERAL ERROR    POWER
                      [OFF]         [ ON]

Disk LED Status:    OK = GREEN  ERROR = YELLOW
        DISK  1:    [OK]
        DISK  0:    [OK]

=================================


Fan Bank :
----------

Bank      Speed     Status
         (0-255)
----      -----     ------
 SYS       255        OK

=================================


Power Supplies:
---------------

Supply     Status
------     ------
  0          OK: 560w
  1          OK: 560w

=================================

Open in new window

0
rajsolaris
Asked:
rajsolaris
  • 4
1 Solution
 
rajsolarisAuthor Commented:
from ok prompt - boot cdrom -s
I keep getting following: Virtual address already used

Tried this next, but failed:
rsc> break
rsc> console

{0} ok boot
Boot device: rootdisk File and args: read failed

The file just loaded does not appear to be executable.
See if this helps in the diagnosis:
{0} ok printenv 
Variable Name Value Default Value 

test-args 
diag-passes 1 1 
pcia-probe-list 4,1 4,1 
pcib-probe-list 5,6,1,2,3,4 5,6,1,2,3,4 
local-mac-address? false false 
fcode-debug? false false 
silent-mode? false false 
scsi-initiator-id 7 7 
oem-logo No default 
oem-logo? false false 
oem-banner No default 
oem-banner? false false 
ansi-terminal? true true 
screen-#columns 80 80 
screen-#rows 34 34 
ttyb-rts-dtr-off false false 
ttyb-ignore-cd true true 
ttya-rts-dtr-off false false 
ttya-ignore-cd true true 
ttyb-mode 9600,8,n,1,- 9600,8,n,1,- 
ttya-mode 9600,8,n,1,- 9600,8,n,1,- 
output-device rsc-console screen 
input-device rsc-console keyboard 
load-base 16384 16384 
auto-boot? false true 
boot-command boot boot 
diag-file 
diag-device disk net 
boot-file 
boot-device rootdisk rootmirror net disk net 
use-nvramrc? true false 
nvramrc devalias rootdisk /pci@8 ... 
security-mode none No default 
security-password No default 
security-#badlogins 0 No default 
diag-out-console true false 
#power-cycles 61 No default 
diag-script none none 
diag-level min min 
diag-switch? false false 
error-reset-recovery boot boot

Open in new window


Or this:
-bash-3.00$ iostat -En 
c4t2d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: EQLOGIC Product: 100E-00 Revision: 5.0 Serial No: 
Size: 53.70GB <53697576960 bytes> 
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 0 Predictive Failure Analysis: 0 
c4t3d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: EQLOGIC Product: 100E-00 Revision: 5.0 Serial No: 
Size: 107.38GB <107379425280 bytes> 
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 0 Predictive Failure Analysis: 0 
c4t4d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: EQLOGIC Product: 100E-00 Revision: 5.0 Serial No: 
Size: 107.38GB <107379425280 bytes> 
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 0 Predictive Failure Analysis: 0 
c4t5d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: EQLOGIC Product: 100E-00 Revision: 5.0 Serial No: 
Size: 214.76GB <214758850560 bytes> 
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 0 Predictive Failure Analysis: 0 
c0t6d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: TOSHIBA Product: DVD-ROM SD-M1401 Revision: 1009 Serial No: 
Size: 2.66GB <2661416960 bytes> 
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 4 Predictive Failure Analysis: 0 
c2t0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: SEAGATE Product: ST373405FSUN72G Revision: 0638 Serial No: 0227K1WX9R 
Size: 73.41GB <73407865856 bytes> 
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 1 Predictive Failure Analysis: 0 
c2t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
Vendor: SEAGATE Product: ST373405FSUN72G Revision: 0638 Serial No: 0227K1X0TT 
Size: 73.41GB <73407865856 bytes> 
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
Illegal Request: 2 Predictive Failure Analysis: 0

Open in new window


It seems like current issue is at d1:
bash-3.00# metastat -c 
d4 m 21GB d40 d41 
d40 s 21GB c2t0d0s3 
d41 s 21GB c2t1d0s3 
d3 m 14GB d30 d31 
d30 s 14GB c2t0d0s4 
d31 s 14GB c2t1d0s4 
d1 m 23GB d10 (maint) d11 (maint) 
d10 s 23GB c2t0d0s0 (last-erred) 
d11 s 23GB c2t1d0s0 

Open in new window



How to rectify the d1 now ? Any help pls ?

Thanks.
0
 
ej2bonnerCommented:
have you tried metareplace -e d1 c2t0d0s0
0
 
rajsolarisAuthor Commented:
I get :

bash-3.00# metareplace -e d1 c2t0d0s0
metareplace: rodevdb010: c2t0d0s0: is mounted on /


Thanks.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
AnacreoCommented:
I'm not sure I understand exactly what is at error here, but you may need to just start over with SVM.  This involves changing the /etc/system to unmirror root.  Perform your patches then simply remirror the whole kit...

If you look at this link:
http://www.unix.com/solaris/96019-unmirror-remirror-solaris-10-a.html

You'll find the steps to unmirror the root system, Kumarmani's steps are sound so I'll repost them, full credit to him (I'd probably skip the ufsdump, assuming you have backups).
 
kumarmani  
Registered User
 	

Join Date: Sep 2008
Posts: 413
Thanks: 0
Thanked 2 Times in 2 Posts
We follow following steps , I am sure there must be better way to do the same thing and my steps can be also verified/purified by Gurus 


Detach the metadevices for root file system. if you have swap, var and opt mounted on different volumes then detach them also. 

Mount the secondary disk on some mount point and modify the <mountpoint>/etc/vfstab and change the root file system to mount from slices instead of volumes. Some thing like below 
Quote:
mount /dev/dsk/c1t1d0s0 /mnt
vi /mnt/etc/system
# remove the rootdev entry and any refeences to “md”
vi /mnt/etc/vfstab
# adjust entries for root, swap & opt to use slices on the rootmirror disk



Shutdown the system and boot from the rootmirror like below 

Quote:
shutdown -y -g0 -i0
boot rootmirror -s

once system is booted check the ‘/’, var, opt fliesystem are clean some thing like below 

Quote:
fsck -n /dev/rdsk/c1t0d0s0
fsck -n /dev/rdsk/c1t0d0s3


ufsdump the original( primary) root, opt, and var filesystems to some other system. May be you can use other server and dump 

Once you have successfully dumped the again shutdown the system and reboot the system from primary disk i.e. 

Quote:
init 0
boot -s


do the installation/ patching once you are over with that reboot the system i.e. reboot 

if no problem has been reported, re-attached the secondary disk.

Open in new window


Reboot on the non-mirrored system, make sure system boots ok, then apply patches if still necessary.

I'd go the extra step of removing the metadbs:
metadb -d cXtXdXsX

Then recreate it all.  It may also be worth doing:
devfsadm -C

After the patch, then "reboot -- -rs"...

Then go into the process of re-metadb, re-metainit, metaroot.  Take care of initializing and changing mount points for the other file systems, reboot once more and attach all the mirrors, and you should be good for production.

Sorry this is a shortcut post, may be able to fill in the steps later.
0
 
rajsolarisAuthor Commented:
Please close this question as I have fixed it on my own. The system was booted from the cdrom in the single user mode the FS monted on /a and then running the fsck and booted the system from ok prompt with
# boot disk -s

patched the system and metaattached the mirrors. System is now good.

BTW, Thanks Anacreo:
0
 
rajsolarisAuthor Commented:
Please close this question as I have fixed it on my own. The system was booted from the cdrom in the single user mode the FS monted on /a and then running the fsck and booted the system from ok prompt with
# boot disk -s

patched the system and metaattached the mirrors. System is now good.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now