Search This Blog

Wednesday 25 March 2009

ERROR: bpgetfile unable to access network - jumpstart

I have recently been installing Solaris 10 on a virtualisaed environment on a Sun T5240

I have noticed with each install, I get a similar error that I can't pass

{0} ok boot net - install
Boot device: /virtual-devices@100/channel-devices@200/network@0 File and args: - install
Requesting Internet Address for 0:14:4f:fb:fb:f3
SunOS Release 5.10 Version Generic_120011-14 64-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
whoami: no domain name
WARNING: ncp0: unable to determine ncp (cpu) binding (ncp)
Configuring devices.
WARNING: ncp0: unable to determine ncp (cpu) binding (ncp)
Using RPC Bootparams for network configuration information.
Attempting to configure interface vnet0...
Configured interface vnet0
ERROR: bpgetfile unable to access network
/sbin/install-discovery: information: not found

The install sits at the # prompt at this point. I typed 'exit' here, expecting it to error out and found it continues the install, I have done two machines this way and both work properly

Wednesday 18 March 2009

Drop sybase devices

I recently installed a virtual machine from a flash archive. This machine had Sybase devices on raw devices which weren't accessible from the virtual machine. I knew I needed to reinstall these which is quite straightforward but because Sybase thought they existed, I couldn't drop them or access them. Below is what I tried.

1> Drop database
2> go

This gave an error saying the database was in use

1> sp_dropdevice
2>

This gave an error as it said the DB needed to be dropped.

1> dbcc dbrepair (DB_name, dropdb)
2> go

This gave a message telling me that I couldn't repair the database as it was not marked suspect. I couldn't mark it suspect as it hadn't initialised at start up time (because the devices weren't present).

I used to be excellent at this stuff but I rarely work on it any more. I knew there was a way to do this but it took some searching, eventually I found:

1> use master
2> go
1> sp_configure 'allow update', 1
2> go
1> begin tran
2> go
1> delete from sysusages where dbid =
2> go
1> commit
2> go
1> begin tran
2> go
1> delete from sysdatabases where dbid=
2> go
1> commit
2> go
1> sp_configure 'allow update', 0
2> go

This is the exact procedure I used and I am now happily reinstalling my databases.