Video Screencast Help

BMR restore failing with err boot: cannot open kernel/sparcv9/unix

Created: 26 Sep 2012 • Updated: 27 Sep 2012 | 7 comments
This issue has been solved. See solution.

Hi I am attempting to restore a Solaris 9 machine from a Solaris 10 boot server. I have created the Solaris 9 SRTs and everything was fine.

Now I have the issue where when I boot client it performs the initial handshake fine but then i get this error. 

boot: cannot open kernel/sparcv9/unix

>> From a snoop of the transaction between boot server and client I get this output.

 

 

10:17:58.87653 client_restore -> boot_server MOUNT1 C Mount /export/srt/Solaris9sparc/Solaris_9/Tools/Boot
          80: 000d 6265 7465 2d77 7777 2d62 7570 3100    ..client_restore.
10:17:58.87717 boot_server -> client_restore MOUNT1 R Mount OK FH=0D80
10:17:58.87790 client_restore -> boot_server NFS C LOOKUP2 FH=0D80 platform
          80: 000d 6265 7465 2d77 7777 2d62 7570 3100    ..client_restore.
10:17:58.87920 boot_server -> client_restore NFS R LOOKUP2 OK FH=161F
10:17:58.87990 client_restore -> boot_server NFS C LOOKUP2 FH=161F SUNW,Sun-Fire-V240
          80: 000d 6265 7465 2d77 7777 2d62 7570 3100    ..client_restore.
10:17:58.88003 boot_server -> client_restore NFS R LOOKUP2 No such file or directory
10:17:58.88077 client_restore -> boot_server NFS C LOOKUP2 FH=161F sun4u
          80: 000d 6265 7465 2d77 7777 2d62 7570 3100    ..client_restore.
10:17:58.88083 boot_server -> client_restore NFS R LOOKUP2 OK FH=E24A
10:17:58.88152 client_restore -> boot_server NFS C LOOKUP2 FH=E24A kernel
          80: 000d 6265 7465 2d77 7777 2d62 7570 3100    ..client_restore.
10:17:58.88158 boot_server -> client_restore NFS R LOOKUP2 OK FH=CC68
10:17:58.88227 client_restore -> boot_server NFS C LOOKUP2 FH=CC68 sparcv9
          80: 000d 6265 7465 2d77 7777 2d62 7570 3100    ..client_restore.
10:17:58.88232 boot_server -> client_restore NFS R LOOKUP2 OK FH=1287
10:17:58.88302 client_restore -> boot_server NFS C LOOKUP2 FH=1287 unix
          80: 000d 6265 7465 2d77 7777 2d62 7570 3100    ..client_restore.
10:17:58.88307 boot_server -> client_restore NFS R LOOKUP2 OK FH=3E05
10:17:58.88839 client_restore -> boot_server NFS C LOOKUP2 FH=161F SUNW,Sun-Fire-V240
          80: 000d 6265 7465 2d77 7777 2d62 7570 3100    ..client_restore.
10:17:58.88846 boot_server -> client_restore NFS R LOOKUP2 No such file or directory

Comments 7 CommentsJump to latest comment

manmountain's picture

>> So when the host attempts to look for this info from the BMR 

NFS C LOOKUP2 FH=161F SUNW,Sun-Fire-V240

>> Response is received 

NFS R LOOKUP2 No such file or directory

Both the Client and the boot server should have the same hardware.

Any ideas?? Would it be related in any way to 'Prepare to Discover'?

mandar_khanolkar's picture

I believe you have boot server and client both of SPARC family. In this case boot server can be solaris sparc 10 and it can recovery solaris sparc 9 client using sparc 9 based srt.

Looks to me this is NFS server configuration issue rather than BMR problem. Please check if your NFS server on boot server is functioning correctly. It seems you are doing NW based BMR recovery where BMR restore method tries to mount SRT on bmr boot server using NFS protocol. This mounting has some issue due to NFS service problem on BMR Boot server. Try re-starting your Boot server or NFS daemon and re-try.

No need to do prepare to discover.

thanks.

mandar

manmountain's picture

This issue was due to missing Patches in the SRT for Solaris 9.

The SRT did not have the patch loaded which allowed enrty for v240 in usr/platform.

I had to download recommended patches for Solaris 9 and install a multidude from here so that there was an entry for /usr/platform/SUNW,Sun-Fire-V240

SOLUTION
susindran.suruli's picture

Hi Manmountain,

Me too receiving same error.I have downloaded entire solaris 9 recommanded patch set.WHich one we need to apply???

manmountain's picture

I added these patches to resolve issue I was having. SRT scripts may prompt you to add in other patches which these have dependencies on.

SUNWpiclu, SUNWfruip, SUNWkvm and SUNWhea

susindran.suruli's picture

Ok Thanks Manmountain...SRT script??Could you please explain how to check logs..Actually i am booting from cd-based SRT and after disimiler disk restore steps and have inserted iso image CD..Given ok boot cdrom and getting this error..Which log we can tarce which patch exactly required??

manmountain's picture

SRT script

I was talking here about the script /usr/openv/netbackup/bin/bmrsrtadm

I did a boot from boot server over the network and did a snoop where I could see issues. Didn't specifically say what patches were missing. Just seen that some hardware platforms were missing from directory /usr/platform.

To get logs you can create directory /usr/openv/logs/bmrsrt and set debug level to 6 as follows.

 

bmrsrt log on the boot server.
 
This is a vx (unified) log, with oid number 125
 
To create the log:
 
vxlogcfg -a -p 51216 -o 125 -s DebugLevel=6 -s DiagnosticLevel=6
 
 
To view the log ...
 
vxlogview -p 51216 -o 125 -d all -t 01:00:00  (this would give the last 1 hr of the log, relative to when the command is run).