Re: Help with replacing the boot drive with Solstice DiskSuite
From: Germano (gsilva3891_at_yahoo.com)
Date: 02/07/04
- Next message: Gary L. Burnore: "Re: Printing system in Solaris9"
- Previous message: Joerg Schilling: "Re: getopt_long on Solaris 9 x86"
- In reply to: Darren Dunham: "Re: Help with replacing the boot drive with Solstice DiskSuite"
- Next in thread: Shivakanth Mundru: "Re: Help with replacing the boot drive with Solstice DiskSuite"
- Reply: Shivakanth Mundru: "Re: Help with replacing the boot drive with Solstice DiskSuite"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 7 Feb 2004 09:57:30 -0500
At the OK prompt, if I force it to boot from the new disk, the server boots
fine, but I need to configure the server to automatically boot to the right
drive when the power is turned on, since I'm not even at the same site where
the server is located. I'm only a couple of miles away, but I can't expet to
have for example a night operator to force a boot from a specific disk.
How do I set the device-string?
I assume it can be done at the OK prompt, but I haven't done anything at the
OK prompt for years and I don't remember what the syntax is.
"Darren Dunham" <ddunham@redwood.taos.com> wrote in message
news:wmXUb.21059$cM6.5213@newssvr27.news.prodigy.com...
> Germano <gsilva3891@yahoo.com> wrote:
> > Old configuration
> > -----------------
> > d2: Mirror
> > Submirror 0: d0
> > State: Needs maintenance
> > Submirror 1: d1
> > State: Okay
> > Pass: 1
> > Read option: roundrobin (default)
> > Write option: parallel (default)
> > Size: 524880 blocks
> [snip]
> > New configuration
> > -----------------
> > d2: Mirror
> > Submirror 0: d0
> > State: Okay
> > Submirror 1: d1
> > State: Okay
> > Pass: 1
> > Read option: roundrobin (default)
> > Write option: parallel (default)
> > Size: 524880 blocks
>
> > d0: Submirror of d2
> > State: Okay
> > Size: 524880 blocks
> > Stripe 0:
> > Device Start Block Dbase State Hot Spare
> > c1t2d0s0 0 No Okay
>
> > d1: Submirror of d2
> > State: Okay
> > Size: 524880 blocks
> > Stripe 0:
> > Device Start Block Dbase State Hot Spare
> > c2t2d0s0 0 No Okay
>
> > Here's my situation:
>
> > I was having disk problems on c1t0d0 which was a sub-mirror as shown
below.
> > This happened to also be the boot device, with root, /usr, /var, etc.,
so I
> > used the following procedure to fix it.
>
> > I got a new drive, plugged it on target 2, partioned it the same as
c1t0d0
> > and used metareplace to move all slices (metareplace d0 c1t2dos0,
> > etc.),because it seemed at the time the easiest way to replace the drive
> > going bad.
>
> > The problem I have now is that the server (E3000) does not boot when I
> > remove c1t0d I get a "The file just loaded does not appear to be
executable"
> > and I end up at the OK prompt. There's nothing on vfstab that points to
> > c1t0, but I still can't boot the system unless I put the drive on the
> > server, which I need to send back to Sun.
>
> How are you trying to boot it? You can't just type 'boot' unless your
> boot-device string contains one of your root disks. You need to point
> at the new disk.
>
> The boot blocks should already be moved over by the mirror, but you
> could try to install the boot blocks on the new disk with installboot.
> It shouldn't be necessary.
> --
> Darren Dunham ddunham@taos.com
> Senior Technical Consultant TAOS http://www.taos.com/
> Got some Dr Pepper? San Francisco, CA bay area
> < This line left intentionally blank to confuse you. >
- Next message: Gary L. Burnore: "Re: Printing system in Solaris9"
- Previous message: Joerg Schilling: "Re: getopt_long on Solaris 9 x86"
- In reply to: Darren Dunham: "Re: Help with replacing the boot drive with Solstice DiskSuite"
- Next in thread: Shivakanth Mundru: "Re: Help with replacing the boot drive with Solstice DiskSuite"
- Reply: Shivakanth Mundru: "Re: Help with replacing the boot drive with Solstice DiskSuite"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
