Re: alad init on bootup causes panic...
- From: "Bob Bailin" <72027.3605@xxxxxxxxxxxxxx>
- Date: Tue, 29 Jul 2008 20:54:30 -0400
"scooter" <sullmann@xxxxxxxxxxxxxxxx> wrote in message news:200b50c4-52ac-4749-861d-4a54ab19615c@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am trying to resurrect an OpenServer 5.0.5 server that has the
following configuration...
It's on an old Dell PoweEdge server....so it has the 2 embedded SCSI
controllers (7890 & 7860 I believe). Those use the blad driver as I
understand.
There are 2 mirrored drives that have the OS (mirrored with SCO VDM).
There is also an Adaptec 2940UW that has 3 drives attached to it.
(This contains /dev/dsk/vdisk4 - a RAID 5 array that is also RAID'ed
with SCO VDM)
THIS is where I need some data - on the /u filesystem that is on
these 3 disks.
So, I pull it out of the closet....boot it up.....presto...get a boot
prompt.
I hit enter and when it gets to aladinit in the boot up sequence, I
get a double panic.
So, I reboot.........and at the boot prompt I enter defbootstr
disable=alad
and the system boots up just fine.
To job my memory, I go look at /etc/conf/cf.d/mscsi - it shows my 3
disks that are supposed to be on the Adaptec 2940 (all are listed as
host adapter 0, bus 0, lun 0 and ID's of 0, 1 & 2 - perfect)
It lists the 2 mirrored OS drives as blad (host adapter 0, bus 0, lun
0 and ID's of 0 & 1 - perfect)
Now, this server did use to have a tape drive, so I see it in there as
well, only it shows to be on alad host adapter 1, bus 0, lun 0 and ID
of 3 --- uh, okay....
Also, it shows the cd-rom drive on alad host adapter 2, bus 0, lun 0
and ID of 5.
So, this tells me this sytem once upon a time had 3 alad-based SCSI
controllers at one time, right??
I look in the PCI slots and there is one PCI slot where the rear cover
is missing, so you can see to the outside of the case....so, I'm
guessing someone took a PCI device out of this server at some
point....?
Sorry for the long post, but I'm trying to be thorough........
So, I did mkdev .scsi and removed the tape drive and cd-rom from the
configuation because I don't need them.....relinked the kernely,
rebooted and still get double panic...
My question is this.........what would cause a double panic when
initializing the adaptec controller? I tried removing the drives from
the controller, but still panics.....
I changed the cable, same error..........
This server isn't on a network so I can't post the exact double panic
message, but is ends with 0x0000000E at the end....
If it's absolutely necessary, I can post the full panic message if
that helps anyone with some insight.....
Is it possible the kernel is looking for multiple alad based
controllers and panics when it can only find one??
HELP!! I would appreciate any insight....I really need to get some
data off the /u filesystem and this is my last resort.....
The 0x0E fault is a generic hardware problem. It could very well
be caused by the missing alad device. It's also possible that by
removing the 2nd alad adapter, the BIOS has rearranged the IRQ
assignments and the remaining alad adapter is sharing its IRQ with
another, non-alad device when it wasn't before.
Assuming it's the 1st case, boot up the system with disable=alad
and go into single-user mode. Go to /etc/conf/sdevice.d and edit
the alad file. Change the "Y" to "N" on the second line to remove
the second alad device from the kernel. Relink the kernel and
reboot normally without the disable=alad boot string. It should
work now.
If it doesn't, check the scsi bus on the other alad adapter and make
sure there's an active terminator on the end of the bus. If not, it's
possible that the last drive on the bus is jumpered to provide
active termination and term power.
You can also hit ctrl-A when the 2940UW appears during boot
to go into its setup mode and check that on board termination
is enabled there, too.
Bob
.
- Follow-Ups:
- Re: alad init on bootup causes panic...
- From: scooter
- Re: alad init on bootup causes panic...
- References:
- alad init on bootup causes panic...
- From: scooter
- alad init on bootup causes panic...
- Prev by Date: Does 5.0.7 run well on modern hardware?
- Next by Date: Re: Does 5.0.7 run well on modern hardware?
- Previous by thread: alad init on bootup causes panic...
- Next by thread: Re: alad init on bootup causes panic...
- Index(es):
Relevant Pages
|