Is this the same hardware?
Are the disk(s) partitioned EXACTLY the same as before?

Kurt Jensen wrote:

>Hi,
>
>After having trashed a Compaq Win2K SP3 server and then used the IDR recovery
>cd to get the system up again - Everything seems to work fine, I then rename
>the server to the right name, reboot and still it boots up fine...
>
>Then I restore the latest backup from our backup, through ethernet, and the
>backup restores fine as well.. After a reboot I get the INACCESSIBLE_BOOT_DEVICE
>blue screen.. After consulting the Veritas Technical Support the describe
>it as a basic vs dynimic disks problem...
>
>That I don't understand.. I am 1000000% sure that the disk was basic before
>the backup and the disk is still basic after I used the IDR cd.
>
>Any ideas?
>
>The server is a Compaq Proliant DL380 with a Compaq Smart Array 5i controller
>and two 18GB SCSI disks running RAID 1 (mirror)
>
>

Hi Ken,

Yes, it's the same hardware... But I'm not sure that the disks are partitioned
EXACTLY the same size ...

I will try once again, first thing monday morning... If the problem still
exists after that I will contact you again.

/Kurt

Ken Putnam wrote:
>Is this the same hardware?
>Are the disk(s) partitioned EXACTLY the same as before?
>
>Kurt Jensen wrote:
>
>>Hi,
>>
>>After having trashed a Compaq Win2K SP3 server and then used the IDR recovery
>>cd to get the system up again - Everything seems to work fine, I then rename
>>the server to the right name, reboot and still it boots up fine...
>>
>>Then I restore the latest backup from our backup, through ethernet, and
the
>>backup restores fine as well.. After a reboot I get the INACCESSIBLE_BOOT_DEVICE
>>blue screen.. After consulting the Veritas Technical Support the describe
>>it as a basic vs dynimic disks problem...
>>
>>That I don't understand.. I am 1000000% sure that the disk was basic before
>>the backup and the disk is still basic after I used the IDR cd.
>>
>>Any ideas?
>>
>>The server is a Compaq Proliant DL380 with a Compaq Smart Array 5i controller
>>and two 18GB SCSI disks running RAID 1 (mirror)
>>
>>
>

Size isn't as important as the right number of partitions. The Compaq
diagnostics partition by default is the first partition with the OS
(C on the second. If you don't have the Compaq partition defined, the
boot.ini will point to the first data partition (D (or to a partition
that doesn't exist!) and won't find any boot files.

Kurt Jensen wrote:

>Hi Ken,
>
>Yes, it's the same hardware... But I'm not sure that the disks are partitioned
>EXACTLY the same size ...
>
>I will try once again, first thing monday morning... If the problem still
>exists after that I will contact you again.
>
>/Kurt
>
>Ken Putnam wrote:
>
>
>>Is this the same hardware?
>>Are the disk(s) partitioned EXACTLY the same as before?
>>
>>Kurt Jensen wrote:
>>
>>
>>
>>>Hi,
>>>
>>>After having trashed a Compaq Win2K SP3 server and then used the IDR recovery
>>>cd to get the system up again - Everything seems to work fine, I then rename
>>>the server to the right name, reboot and still it boots up fine...
>>>
>>>Then I restore the latest backup from our backup, through ethernet, and
>>>
>>>
>the
>
>
>>>backup restores fine as well.. After a reboot I get the INACCESSIBLE_BOOT_DEVICE
>>>blue screen.. After consulting the Veritas Technical Support the describe
>>>it as a basic vs dynimic disks problem...
>>>
>>>That I don't understand.. I am 1000000% sure that the disk was basic before
>>>the backup and the disk is still basic after I used the IDR cd.
>>>
>>>Any ideas?
>>>
>>>The server is a Compaq Proliant DL380 with a Compaq Smart Array 5i controller
>>>and two 18GB SCSI disks running RAID 1 (mirror)
>>>
>>>
>>>
>>>
>
>
>

Hi Ken,
Then I can say that there are, and were, the exactly samt number of partitions.

There is no problem with BOOT.INI, the server boots fine, but about 60-70%
in booting Windows Server up, the blue screen of death comes with the INACCESSIBLE_BOOT_DEVICE
failure.

After rereading my first post, I can see that I forgot to mention that it
boots up fine until the error comes.

After consulting the Veritas Technical Support the describe it as a basic
vs dynamic disks problem... But the disk was basic before the backup and
the disk is still basic after I used the IDR cd.

/Kurt


Ken Putnam wrote:
>Size isn't as important as the right number of partitions. The Compaq
> diagnostics partition by default is the first partition with the OS
>(C on the second. If you don't have the Compaq partition defined, the

>boot.ini will point to the first data partition (D (or to a partition

>that doesn't exist!) and won't find any boot files.
>
>Kurt Jensen wrote:
>
>>Hi Ken,
>>
>>Yes, it's the same hardware... But I'm not sure that the disks are partitioned
>>EXACTLY the same size ...
>>
>>I will try once again, first thing monday morning... If the problem still
>>exists after that I will contact you again.
>>
>>/Kurt
>>
>>Ken Putnam wrote:
>>
>>
>>>Is this the same hardware?
>>>Are the disk(s) partitioned EXACTLY the same as before?
>>>
>>>Kurt Jensen wrote:
>>>
>>>
>>>
>>>>Hi,
>>>>
>>>>After having trashed a Compaq Win2K SP3 server and then used the IDR
recovery
>>>>cd to get the system up again - Everything seems to work fine, I then
rename
>>>>the server to the right name, reboot and still it boots up fine...
>>>>
>>>>Then I restore the latest backup from our backup, through ethernet, and
>>>>
>>>>
>>the
>>
>>
>>>>backup restores fine as well.. After a reboot I get the INACCESSIBLE_BOOT_DEVICE
>>>>blue screen.. After consulting the Veritas Technical Support the describe
>>>>it as a basic vs dynimic disks problem...
>>>>
>>>>That I don't understand.. I am 1000000% sure that the disk was basic
before
>>>>the backup and the disk is still basic after I used the IDR cd.
>>>>
>>>>Any ideas?
>>>>
>>>>The server is a Compaq Proliant DL380 with a Compaq Smart Array 5i controller
>>>>and two 18GB SCSI disks running RAID 1 (mirror)
>>>>
>>>>
>>>>
>>>>
>>
>>
>>
>

Kurt,

Veritas support gave me the following reference:

http://seer.support.veritas.com/docs/237174.htm

It mentions that '"use currently installed drivers" was not selected during
disk creation' but I can't find where to select this when creating the IDR
CD. Does anyone know?

Aloha,
McGarrett

"Kurt Jensen" wrote:
>
>Hi Ken,
>Then I can say that there are, and were, the exactly samt number of partitions.
>
>There is no problem with BOOT.INI, the server boots fine, but about 60-70%
>in booting Windows Server up, the blue screen of death comes with the INACCESSIBLE_BOOT_DEVICE
>failure.
>
>After rereading my first post, I can see that I forgot to mention that it
>boots up fine until the error comes.
>
>After consulting the Veritas Technical Support the describe it as a basic
>vs dynamic disks problem... But the disk was basic before the backup and
>the disk is still basic after I used the IDR cd.
>
>/Kurt
>
>
>Ken Putnam wrote:
>>Size isn't as important as the right number of partitions. The Compaq

>> diagnostics partition by default is the first partition with the OS
>>(C on the second. If you don't have the Compaq partition defined, the
>
>>boot.ini will point to the first data partition (D (or to a partition
>
>>that doesn't exist!) and won't find any boot files.
>>
>>Kurt Jensen wrote:
>>
>>>Hi Ken,
>>>
>>>Yes, it's the same hardware... But I'm not sure that the disks are partitioned
>>>EXACTLY the same size ...
>>>
>>>I will try once again, first thing monday morning... If the problem still
>>>exists after that I will contact you again.
>>>
>>>/Kurt
>>>
>>>Ken Putnam wrote:
>>>
>>>
>>>>Is this the same hardware?
>>>>Are the disk(s) partitioned EXACTLY the same as before?
>>>>
>>>>Kurt Jensen wrote:
>>>>
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>After having trashed a Compaq Win2K SP3 server and then used the IDR
>recovery
>>>>>cd to get the system up again - Everything seems to work fine, I then
>rename
>>>>>the server to the right name, reboot and still it boots up fine...
>>>>>
>>>>>Then I restore the latest backup from our backup, through ethernet,
and
>>>>>
>>>>>
>>>the
>>>
>>>
>>>>>backup restores fine as well.. After a reboot I get the INACCESSIBLE_BOOT_DEVICE
>>>>>blue screen.. After consulting the Veritas Technical Support the describe
>>>>>it as a basic vs dynimic disks problem...
>>>>>
>>>>>That I don't understand.. I am 1000000% sure that the disk was basic
>before
>>>>>the backup and the disk is still basic after I used the IDR cd.
>>>>>
>>>>>Any ideas?
>>>>>
>>>>>The server is a Compaq Proliant DL380 with a Compaq Smart Array 5i controller
>>>>>and two 18GB SCSI disks running RAID 1 (mirror)
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>
>

Admittedly it's a bandaid, but if you have a diskette with the RAID drivers,
on it, as soon as you see the blue screen, press F6 several times and you'll
go into a dialog to load drivers.



"Steve McGarrett" wrote:
>
>Kurt,
>
>Veritas support gave me the following reference:
>
>http://seer.support.veritas.com/docs/237174.htm
>
>It mentions that '"use currently installed drivers" was not selected during
>disk creation' but I can't find where to select this when creating the IDR
>CD. Does anyone know?
>
>Aloha,
>McGarrett
>

Hi again,

Maybe I'm not explaning it correct -

I made a IDR rescue cd, trashed the server (Win2K SP3)
Booted on the cd, and it did everything correct - at the end I restored the
server from a backup - (yes, I did remember the thing about overwriting existing
files) - And the restore, that didnt come up with any errors. After the restore,
I rebooted the server and its began to start windows. Just about where I
would be able to log in to Windows it crashed with the blue screen.

And everytime I tried since it crashed the same place.....

"Ken Putnam" wrote:
>
>Admittedly it's a bandaid, but if you have a diskette with the RAID drivers,
>on it, as soon as you see the blue screen, press F6 several times and you'll
>go into a dialog to load drivers.
>
>
>
>"Steve McGarrett" wrote:
>>
>>Kurt,
>>
>>Veritas support gave me the following reference:
>>
>>http://seer.support.veritas.com/docs/237174.htm
>>
>>It mentions that '"use currently installed drivers" was not selected during
>>disk creation' but I can't find where to select this when creating the
IDR
>>CD. Does anyone know?
>>
>>Aloha,
>>McGarrett
>>
>

Ken,

Thenks but no dice for me. The RAID drivers were about the only thing IDR
*was* intelligent enough to add to the generic installation procedure. I
saw them go by at the bottom of the screen during text setup.

I started over and tried the F6 thing anyway. It took the new drivers just
fine, but on the final reboot after IDR had restored from the tape I still
got the INACCESSIBLE_BOOT_DEVICE error.

(BTW, you only need to press F6 once, when requested. You may think the install
procedure is ignoring you, but it just has to load a number of other drivers
before it can load the extra ones you want.)

So, has anybody seen the mysterious "use currently installed drivers" selection
in IDR? It doesn't seem to be mentioned anywhere else on Veritas' web site
or documentation.

Aloha,
McGarrett

"Ken Putnam" wrote:
>
>Admittedly it's a bandaid, but if you have a diskette with the RAID drivers,
>on it, as soon as you see the blue screen, press F6 several times and you'll
>go into a dialog to load drivers.

Hi again,

Maybe I'm not explaning it correct -

I made a IDR rescue cd, trashed the server (Win2K SP3)
Booted on the cd, and it did everything correct - at the end I restored the
server from a backup - (yes, I did remember the thing about overwriting existing
files) - And the restore, that didnt come up with any errors. After the restore,
I rebooted the server and its began to start windows. Just about where I
would be able to log in to Windows it crashed with the blue screen.

And everytime I tried since it crashed the same place.....

"Ken Putnam" wrote:
>
>Admittedly it's a bandaid, but if you have a diskette with the RAID drivers,
>on it, as soon as you see the blue screen, press F6 several times and you'll
>go into a dialog to load drivers.

We went thru the same story and ended upwith reinstalling the whole ****ing
server, users, profiles, .... Took us two weeks. Terrible. AFAICS a
*restore* may succeed if it goes to the same disk - not only same geometry,
there is soemthing with the driver signatures wich cause the inaccessible
boot device if they change. On a workstation you can superseed this by
editing the registry but not on a server.

Restoring to different hardware is a *move* and not covered by IDR. Do a
search with "inaccessible boot device" and you will see that there are far
more problems than solutions.

What we have now is a redundant server system, both with RAID system.

Cheers
Bernd

"Kurt Jensen" schrieb im Newsbeitrag
news:3df6e08c$1@hronntp01....
>
> Hi again,
>
> Maybe I'm not explaning it correct -
>
> I made a IDR rescue cd, trashed the server (Win2K SP3)
> Booted on the cd, and it did everything correct - at the end I restored
the
> server from a backup - (yes, I did remember the thing about overwriting
existing
> files) - And the restore, that didnt come up with any errors. After the
restore,
> I rebooted the server and its began to start windows. Just about where I
> would be able to log in to Windows it crashed with the blue screen.
>
> And everytime I tried since it crashed the same place.....
>
> "Ken Putnam" wrote:
> >
> >Admittedly it's a bandaid, but if you have a diskette with the RAID
drivers,
> >on it, as soon as you see the blue screen, press F6 several times and
you'll
> >go into a dialog to load drivers.
>
>

Hi there,

There is a known problem with SP3 and compaq hardware. I think what ken has
suggested is right. You can start the IDR process again and during the initial
setup, press F6 and load the correct driver for your hardware.

Did you try this with SP2? if you did, i guess you will not have many problems
restoring.

sa

"Kurt Jensen" wrote:
>
>Hi again,
>
>Maybe I'm not explaning it correct -
>
>I made a IDR rescue cd, trashed the server (Win2K SP3)
>Booted on the cd, and it did everything correct - at the end I restored
the
>server from a backup - (yes, I did remember the thing about overwriting
existing
>files) - And the restore, that didnt come up with any errors. After the
restore,
>I rebooted the server and its began to start windows. Just about where I
>would be able to log in to Windows it crashed with the blue screen.
>
>And everytime I tried since it crashed the same place.....
>
>"Ken Putnam" wrote:
>>
>>Admittedly it's a bandaid, but if you have a diskette with the RAID drivers,
>>on it, as soon as you see the blue screen, press F6 several times and you'll
>>go into a dialog to load drivers.
>
>

Hi,

we did. We had SP 2 and *no* comapq hardware. If there is anybody who can
show me how to use IDR to restore a domain server to a replaced harddisk,
I´d be glad to learn how this can be done.

Bernd
"sa" schrieb im Newsbeitrag news:3df6f40a$1@hronntp01....
>
> Hi there,
>
> There is a known problem with SP3 and compaq hardware. I think what ken
has
> suggested is right. You can start the IDR process again and during the
initial
> setup, press F6 and load the correct driver for your hardware.
>
> Did you try this with SP2? if you did, i guess you will not have many
problems
> restoring.
>
> sa
>
> "Kurt Jensen" wrote:
> >
> >Hi again,
> >
> >Maybe I'm not explaning it correct -
> >
> >I made a IDR rescue cd, trashed the server (Win2K SP3)
> >Booted on the cd, and it did everything correct - at the end I restored
> the
> >server from a backup - (yes, I did remember the thing about overwriting
> existing
> >files) - And the restore, that didnt come up with any errors. After the
> restore,
> >I rebooted the server and its began to start windows. Just about where I
> >would be able to log in to Windows it crashed with the blue screen.
> >
> >And everytime I tried since it crashed the same place.....
> >
> >"Ken Putnam" wrote:
> >>
> >>Admittedly it's a bandaid, but if you have a diskette with the RAID
drivers,
> >>on it, as soon as you see the blue screen, press F6 several times and
you'll
> >>go into a dialog to load drivers.
> >
> >
>

I'm not sure where on the veritas website I read about it, but, if I remember
it correctly, the option "use currently installed drivers" is only available
when creating IDR-diskettes and maybe it was only present in earlier versions
of BE. It's definitely not available when creating CD-images with version
8.6.



"Steve McGarrett" wrote:
>
>Ken,
>
>Thenks but no dice for me. The RAID drivers were about the only thing IDR
>*was* intelligent enough to add to the generic installation procedure. I
>saw them go by at the bottom of the screen during text setup.
>
>I started over and tried the F6 thing anyway. It took the new drivers just
>fine, but on the final reboot after IDR had restored from the tape I still
>got the INACCESSIBLE_BOOT_DEVICE error.
>
>(BTW, you only need to press F6 once, when requested. You may think the
install
>procedure is ignoring you, but it just has to load a number of other drivers
>before it can load the extra ones you want.)
>
>So, has anybody seen the mysterious "use currently installed drivers" selection
>in IDR? It doesn't seem to be mentioned anywhere else on Veritas' web site
>or documentation.
>
>Aloha,
>McGarrett
>
>"Ken Putnam" wrote:
>>
>>Admittedly it's a bandaid, but if you have a diskette with the RAID drivers,
>>on it, as soon as you see the blue screen, press F6 several times and you'll
>>go into a dialog to load drivers.
>