SCO defbootstr question for filePro server

[James Flanagan]

You do not specify the make and model of the replacement motherboard.  Assuming that you replaced the fried mobo with an identical model, it should work transparently, as long as all bios settings have been replicated.  

If you instead, have replace the motherboard with something new and modern, all bets are off using a OS so old.  your best bet would be to eBay an identical board to get the server back up.  

Good luck, 

James Flanagan

> On Apr 11, 2016, at 7:57 AM, Larry Hoover via Filepro-list <filepro-list at lists.celestial.com> wrote:
> 
> This is more of a SCO Openserver question, but the continued existence of a filePro application depends on this server, and this forum has a lot of knowledge in SCO.
> 
> I have a customer running SCO Openserver 5.0.7 who has a fried motherboard, an Intel Server Board G7ESZ with two on-board SCSI channels, one a ultra160 and the other regular SCSI.  There is a cage with two IBM drives in RAID.  I replaced the mother board and it boots, but crashes when it tries to load SCO.  It gets to the host adapter part of the boot and reports an error:
> 
> "no root disk controller was found.  A boottime loadable driver may be required.  dpti: HA0  Channel 0:  ID 1 2 3 4 ..   Panic Srmountfun error 19 mounting rootdir 1/42"
> 
> I think the new motherboard is not compatible somehow with the SCSI drivers built into the boot string.  Channel A (ultra160) does not even find the operating system.  Channel B (regular SCSI) attempts to load but reports the error above.  The SCSI channels use different interrupts than the old one did, but there is no way to change this.
> 
> Any ideas such as defboostr's to try?
> 
> Thanks in advance,
> Larry Hoover
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20160411/a0d111c1/attachment.html>