Unix Technical Forum

No Root Disk Controller

This is a discussion on No Root Disk Controller within the Sco Unix forums, part of the Unix Operating Systems category; --> Hello Everyone, I just installed a new SCSI tape with an Adaptec ad160 controller. I originally have an Adaptec ...


Go Back   Unix Technical Forum > Unix Operating Systems > Sco Unix

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 02-15-2008, 12:21 PM
bernie
 
Posts: n/a
Default No Root Disk Controller

Hello Everyone,

I just installed a new SCSI tape with an Adaptec ad160 controller. I
originally have an Adaptec raid controller for my 2 SCSI hard drive
(MIRROR). After installing the ad160 controller driver and relinked the
kernel and rebooted the machine. During boot up I can see tape and
everything but then I get this ERROR

WARNING: hd: no root disk controller was found

PANIC: srmountfun - Error 19 mounting rootdev

and then I have reboot. That's as far as I can get to.

Any help with how to get both my hard drive and tape working will be much
appreciated. Thanks


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 02-15-2008, 12:22 PM
Bela Lubkin
 
Posts: n/a
Default Re: No Root Disk Controller

bernie wrote:

> I just installed a new SCSI tape with an Adaptec ad160 controller. I
> originally have an Adaptec raid controller for my 2 SCSI hard drive
> (MIRROR). After installing the ad160 controller driver and relinked the
> kernel and rebooted the machine. During boot up I can see tape and
> everything but then I get this ERROR
>
> WARNING: hd: no root disk controller was found
>
> PANIC: srmountfun - Error 19 mounting rootdev
>
> and then I have reboot. That's as far as I can get to.
>
> Any help with how to get both my hard drive and tape working will be much
> appreciated. Thanks


Start by booting from unix.old:

Boot
: unix.old

Hopefully that will boot and see your hard drive (but not the tape). Go
to single-user mode and preserve that kernel immediately!

# btmnt -w
# cp /stand/unix.old /stand/unix.good

Now you can boot with "unix.good", and it won't be overwritten by the
next kernel link.

Next, run these commands and post the results here:

# hwconfig -h name=adapter
# hwconfig -h name=sk
# cat /etc/conf/cf.d/mscsi

>Bela<

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 02-15-2008, 12:23 PM
bernie
 
Posts: n/a
Default Re: No Root Disk Controller

Hi,

Here are the results after running these commands:

First Command: # hwconfig -h name=adapter

device address vec dma comment
adapter 0x170-0x117 15 -- type IDE ctlr =
secondary dvr = wd
adapter 0xf400-0xf4ff 10 -- type-dpti ha=0
id=7, PCI v1.12

Second Command: # hwconfig -h name=sk

disk -- -- type=S ha=0 id=0 lun=0 bus=0 ht=dpti
Sdsk -- -- cycls=2231 hds=255 sec=63

Third Command: # cat /etc/conf/cf.d/mscsi

ha attach number ID lun bus

wd Srom 1 0 0 0
dpti Sdsk 0 0 0 0


What do I do next. Thanks.

Bernie









"Bela Lubkin" <belal@sco.com> wrote in message
news:20031122013238.GF19731@sco.com...
> bernie wrote:
>
> > I just installed a new SCSI tape with an Adaptec ad160 controller. I
> > originally have an Adaptec raid controller for my 2 SCSI hard drive
> > (MIRROR). After installing the ad160 controller driver and relinked the
> > kernel and rebooted the machine. During boot up I can see tape and
> > everything but then I get this ERROR
> >
> > WARNING: hd: no root disk controller was found
> >
> > PANIC: srmountfun - Error 19 mounting rootdev
> >
> > and then I have reboot. That's as far as I can get to.
> >
> > Any help with how to get both my hard drive and tape working will be

much
> > appreciated. Thanks

>
> Start by booting from unix.old:
>
> Boot
> : unix.old
>
> Hopefully that will boot and see your hard drive (but not the tape). Go
> to single-user mode and preserve that kernel immediately!
>
> # btmnt -w
> # cp /stand/unix.old /stand/unix.good
>
> Now you can boot with "unix.good", and it won't be overwritten by the
> next kernel link.
>
> Next, run these commands and post the results here:
>
> >
> >Bela<



Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 02-15-2008, 12:23 PM
Bela Lubkin
 
Posts: n/a
Default Re: No Root Disk Controller

bernie wrote:

> > > I just installed a new SCSI tape with an Adaptec ad160 controller. I
> > > originally have an Adaptec raid controller for my 2 SCSI hard drive
> > > (MIRROR). After installing the ad160 controller driver and relinked the
> > > kernel and rebooted the machine. During boot up I can see tape and
> > > everything but then I get this ERROR
> > >
> > > WARNING: hd: no root disk controller was found
> > >
> > > PANIC: srmountfun - Error 19 mounting rootdev
> > >
> > > and then I have reboot. That's as far as I can get to.


> Here are the results after running these commands:
>
> First Command: # hwconfig -h name=adapter
> Second Command: # hwconfig -h name=sk
>
> device address vec dma comment
> ====== ======= === === =======
> adapter 0x170-0x117 15 - type=IDE ctlr=secondary dvr=wd
> adapter 0xf400-0xf4ff 10 - type=dpti ha=0 id=7, PCI v1.12
> disk - - - type=S ha=0 id=0 lun=0 bus=0 ht=dpti
> Sdsk - - - cycls=2231 hds=255 sec=63
>
> Third Command: # cat /etc/conf/cf.d/mscsi
>
> *ha attach number ID lun bus
>
> wd Srom 1 0 0 0
> dpti Sdsk 0 0 0 0
>
> What do I do next. Thanks.


Ok. The mscsi file shows no evidence of your having added the tape
drive. Meanwhile, the new kernel does not seem to recognize the host
adapter that's supposed to be running the hard disk.

Which adapter(s) does the new/bad kernel recognize? You should still
have that kernel as /unix, so just hitting <Enter> at the boot prompt
will load it. Do that and write down any "%adapter" lines it shows in
the laundry list. Post them here. (It will go on to panic; hopefully
you can see and write down the "%adapter" lines before the panic scrolls
too much off the screen...)

After writing down the "%adapter" lines from the bad kernel, try this:

Boot
: defbootstr disable=ad160

This loads the bad kernel, but tells it to disable the 29160 driver.
Doing this will tell us whether this kernel fails to see your "dpti"
board because something is wrong with that driver; or because it's
conflicting with the actions of the "ad160" driver.

>Bela<

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 11:47 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.2.0
www.UnixAdminTalk.com