 | |
Um... RAID controller/drive problem?
SCSI peripheral devices Discussion of SCSI-based peripheral devices. (comp.periphs.scsi)
 |
| | Thread Tools | Search this Thread | Display Modes |
#11
 
| |||
| |||
|
Re: Um... RAID controller/drive problem? -
05-01-2007
, 10:32 PM
|
"fred" <freaks (AT) nowhereville (DOT) net> wrote Folkert Rienstra wrote: In comp.sys.ibm.pc.hardware.storage fred <freaks (AT) nowhereville (DOT) net> wrote: The Card is an Adaptec 39320 RAID controller. The HDD is a 146Gb Seagate Cheetah (68pin). The message is something like "39320 B slot 3 SCSI configuration error: 02" "Something like" usually doesn't cut it when using Google to find answers. maybe not exactly like that, but that is the gist of it. A.S.K. database search at Adaptec.com though yielded this results with a little help from some of Google's more loose search results: http://adaptec-tic.adaptec.com/cgi-b...?p_faqid=14319 and http://adaptec-tic.adaptec.com/cgi-b...?p_faqid=11116 Unfortunately, though they appear to address the same error message the answers are quite different. (Wrong firmware vs wrong bus type is quite a stretch and appear unrelated). Only thing they have in common is connected peripheral(s), maybe SCSI bus itself. So it could be that your adaptec doesn't like your drive or your SCSI bus topology. I've just put the machine back together again with the card in slot 2 instead of |
"39320 B at slot 02, 01:0a:01 - SCSI controller configuration error: 02"
#12
| ||||||||
| ||||||||
|
|
Folkert Rienstra wrote: The Card is an Adaptec 39320 RAID controller. The HDD is a 146Gb Seagate Cheetah (68pin). NEVER EVER buy or attempt to use any Adaptec SCSI RAID products as they are garbage. You need a good entry level LSI MegaRAID SCSI 320-2X (532) Controller. Yep, both the RAID capability and the Ultra320 bus obviously makes such a lot of sense, for just a single drive. Wotamoron. Sure does, especially when he gets six more drives. |
You mean 7, don't you girl. Or 8 if you include a hot spare.
Quote:
|
You know you just can't stop at one SCSI drive? He does need to scrap the old ribbon cable and go SCA. |
Quote:
|
LSI MegaRAID controllers are very inexpensive and highly reliable. Your choice of the Seagate Cheetah is a very smart one. Use no other drive than Seagate Cheetah. Throw the Adaptec in the trash and grab an LSI. I'm not sure what motherboard you are using, but I'll bet it’s an Intel. Sometimes you can get lucky by swapping the Adaptec controller in a different PCI-X slot. Bwahahah. Shows your lack of actual hands on experience in the real world. Sadly, |
Quote:
|
this cures the problem |
Quote:
|
98.475% of the time. |
What a sad coincidence, eh.
Quote:
|
To cure all of these petty problems you go MegaRAID. |
Results 1 - 10 of about 183,000 for problems+MegaRAID. (0.13 seconds)
Oh dear, dear.
Quote:
|
Now stop playing with yourself and parroting crap you find on the internet and take a course in building an AMD based gaming computer. Don't forget the blue LEDs. |
Quote:
|
Rita |
#13
| |||
| |||
|
|
Folkert Rienstra wrote: "fred" <freaks (AT) nowhereville (DOT) net> wrote Folkert Rienstra wrote: In comp.sys.ibm.pc.hardware.storage fred <freaks (AT) nowhereville (DOT) net> wrote: The Card is an Adaptec 39320 RAID controller. The HDD is a 146Gb Seagate Cheetah (68pin). The message is something like "39320 B slot 3 SCSI configuration error: 02" "Something like" usually doesn't cut it when using Google to find answers. maybe not exactly like that, but that is the gist of it. A.S.K. database search at Adaptec.com though yielded this results with a little help from some of Google's more loose search results: http://adaptec-tic.adaptec.com/cgi-b...?p_faqid=14319 and http://adaptec-tic.adaptec.com/cgi-b...?p_faqid=11116 Unfortunately, though they appear to address the same error message the answers are quite different. (Wrong firmware vs wrong bus type is quite a stretch and appear unrelated). Only thing they have in common is connected peripheral(s), maybe SCSI bus itself. So it could be that your adaptec doesn't like your drive or your SCSI bus topology. I've just put the machine back together again with the card in slot 2 instead of slot 3, and this time I have written the error message - "39320 B at slot 02, 01:0a:01 - SCSI controller configuration error: 02" |
Oops, actually we did, from faq id 11116.
You did bother to read that, right?
So then, how about volunteering some new information. Like your SCSI bus topology.
Or do we have to draw that out of you too.
Did you read the SCSI faq and why not.
One thing it says is to volunteer as much information (relevant to scsi) as you can.
#14
| |||
| |||
|
|
"fred" <freaks (AT) nowhereville (DOT) net> wrote Folkert Rienstra wrote: "fred" <freaks (AT) nowhereville (DOT) net> wrote Folkert Rienstra wrote: In comp.sys.ibm.pc.hardware.storage fred <freaks (AT) nowhereville (DOT) net> wrote: The Card is an Adaptec 39320 RAID controller. The HDD is a 146Gb Seagate Cheetah (68pin). The message is something like "39320 B slot 3 SCSI configuration error: 02" "Something like" usually doesn't cut it when using Google to find answers. maybe not exactly like that, but that is the gist of it. A.S.K. database search at Adaptec.com though yielded this results with a little help from some of Google's more loose search results: http://adaptec-tic.adaptec.com/cgi-b...?p_faqid=14319 and http://adaptec-tic.adaptec.com/cgi-b...?p_faqid=11116 Unfortunately, though they appear to address the same error message the answers are quite different. (Wrong firmware vs wrong bus type is quite a stretch and appear unrelated). Only thing they have in common is connected peripheral(s), maybe SCSI bus itself. So it could be that your adaptec doesn't like your drive or your SCSI bus topology. I've just put the machine back together again with the card in slot 2 instead of slot 3, and this time I have written the error message - "39320 B at slot 02, 01:0a:01 - SCSI controller configuration error: 02" Ooh, that was so helpful. That was information we didn't have yet. Oops, actually we did, from faq id 11116. You did bother to read that, right? If by faq you mean the one at site www.scdifaq.org, then no, I was not aware it |
you are talking about I still have no idea what you mean as there does not
appear to be any faq id system present and id 11116 certainly doesn't show up
anywhere in the site i.e.
http://www.google.com.au/search?as_q...s=&safe=images
Quote:
|
So then, how about volunteering some new information. Like your SCSI bus topology. My what? |
Quote:
|
One thing it says is to volunteer as much information (relevant to scsi) as you can. The mother board is http://support.intel.com/support/mot...s/server/STL2/ |
setup has already been posted in this thread. Oh, and the onboard SCSI
controller has been disabled in the BIOS.
#15
| |||||||||||||
| |||||||||||||
|
|
fred : Help! I'm not yet familiar with all the ins and outs of SCSI drives, and have the following problem - I was wondering if it was possible to run a single SCSI hard disk off a SCSI Which disk drive? Connected internally or externally? |
Quote:
|
RAID Host adapter? Because I connected an Ultra320 hard disk to a RAID Which SCSI controller? |
Quote:
|
controller by itself, and it seems to work for a few weeks without any problem (except for some message about configuration error 02 on channel B, which I can just ignore), then one day, the drive just stops working and cannot be checked Generally error messages should not be ignored. |
Quote:
|
or verified with any utilities - it just becomes totally unreadable one day, and Unaccessible or unreadable? How do you launch the utilities that should check the drive (floppy, cdrom, another disk drive)? Which utilities? On what operating system? |
formatted with gparted or BIOS. I'm using linux.
Quote:
|
the whole drive has to get re-formatted. Then it works fine again for a few weeks. How do you do this, if the drive can not be read (accessed)? In another system? Via the controllers BIOS (then the drive can actually be read/accessed)? I think this recurring problem might have something to do with the fact I'm trying to run a single drive on a RAID setup. Please let me know if this setup I am trying is an impossible configuration, or should I not be experiencing this phenomena with a single drive setup? If it's just a case of me having created an unsupported configuration, then adding a second identical drive will fix it, yes? If you want a qualified answer you should at least post info on your: - Motherboard and BIOS, |
Phoenix BIOS 4.0 release 6
STL20.86B.0022.P01.0105011814
STL2 BIOS release 1.8
Quote:
|
- SCSI controller and BIOS/firmware, |
Quote:
|
- Cable(s)/backplane(s), - Termination, |
unconnected in middle, 1 connect to drive, and 1 terminator (SCSI LVD/SE
Ultra2/Ulta160/Ultra3) on end of cable near drive.
Quote:
|
- SCSI drives attached internally (and externally), |
Quote:
|
- Other devices on the system, |
Video card Nvidia GeForce MX4000 64Mb PCI
A CD-ROM and a DVD-ROM connected to the IDE
A 3.5" floppy drive
A 550W power supply
Quote:
|
- System description (I do like dmesg outputs), |
Quote:
|
- Boot drive, |
Quote:
|
- Operating system, |
version and kernal is at the time.)
Quote:
|
- Detailed problem description (!). The more detail you give, the better you may be helped. |
#16
| |||
| |||
|
|
fred wrote: The Card is an Adaptec 39320 RAID controller. The HDD is a 146Gb Seagate Cheetah (68pin). NEVER EVER buy or attempt to use any Adaptec SCSI RAID products as they are garbage. You need a good entry level LSI MegaRAID SCSI 320-2X (532) Controller. LSI MegaRAID controllers are very inexpensive and highly reliable. Your choice of the Seagate Cheetah is a very smart one. Use no other drive than Seagate Cheetah. |
http://adaptec-tic.adaptec.com/cgi-b...?p_faqid=10047
like with the ST3146807
Quote:
|
Throw the Adaptec in the trash and grab an LSI. I'm not sure what motherboard you are using, but I'll bet it’s an Intel. Sometimes you can get lucky by swapping the Adaptec controller in a different PCI-X slot. Good luck. Rita |
#17
| |||
| |||
|
|
Folkert Rienstra wrote: "fred" <freaks (AT) nowhereville (DOT) net> wrote Folkert Rienstra wrote: "fred" <freaks (AT) nowhereville (DOT) net> wrote Folkert Rienstra wrote: In comp.sys.ibm.pc.hardware.storage fred <freaks (AT) nowhereville (DOT) net> wrote: The Card is an Adaptec 39320 RAID controller. The HDD is a 146Gb Seagate Cheetah (68pin). The message is something like "39320 B slot 3 SCSI configuration error: 02" "Something like" usually doesn't cut it when using Google to find answers. maybe not exactly like that, but that is the gist of it. A.S.K. database search at Adaptec.com though yielded this results with a little help from some of Google's more loose search results: http://adaptec-tic.adaptec.com/cgi-b...?p_faqid=14319 and http://adaptec-tic.adaptec.com/cgi-b...?p_faqid=11116 Unfortunately, though they appear to address the same error message the answers are quite different. (Wrong firmware vs wrong bus type is quite a stretch and appear unrelated). Only thing they have in common is connected peripheral(s), maybe SCSI bus itself. So it could be that your adaptec doesn't like your drive or your SCSI bus topology. I've just put the machine back together again with the card in slot 2 instead of slot 3, and this time I have written the error message - "39320 B at slot 02, 01:0a:01 - SCSI controller configuration error: 02" Ooh, that was so helpful. That was information we didn't have yet. Oops, actually we did, from faq id 11116. You did bother to read that, right? If by faq you mean the one at site www.scdifaq.org, then no, I was not aware it existed until you posted it in this group just recently. However if this is what you are talking about I still have no idea what you mean as there does not appear to be any faq id system present and id 11116 certainly doesn't show up anywhere in the site i.e. http://www.google.com.au/search?as_q...s=&safe=images So then, how about volunteering some new information. Like your SCSI bus topology. My what? One thing it says is to volunteer as much information (relevant to scsi) as you can. The mother board is http://support.intel.com/support/mot...s/server/STL2/ other than that I have no other information. Everything I know about this SCSI setup has already been posted in this thread. Oh, and the onboard SCSI controller has been disabled in the BIOS. |
#18
| |||||||||||
| |||||||||||
|
|
fred wrote: If by faq you mean the one at site www.scdifaq.org, |
Quote:
|
then no, I was not aware it existed until you posted it in this group just recently. |
Quote:
|
However if this is what you are talking about I still have no idea what you mean as there does not appear to be any faq id system present and id 11116 certainly doesn't show up anywhere in the site. |
Right, so you obviously didn't bother to read the A.S.K. FAQ links that I gave you.
One of which was :
http://adaptec-tic.adaptec.com/cgi-b...?p_faqid=11116
Does that number at the end look slightly familiar now?
Quote:
|
Fred, do yourself a favor and take what Folk says with a grain of salt. If you Google his past posts you'll notice he has a track record of being a troublemaker and is the official group idiot. |
Quote:
|
The mother board is http://support.intel.com/support/mot...s/server/STL2/ other than that I have no other information. Everything I know about this SCSI |
Quote:
|
setup has already been posted in this thread. |
Quote:
|
Oh, and the onboard SCSI controller has been disabled in the BIOS. |
suitable for a single Ultra320 drive, or even 4 of them.
Quote:
|
Yes, Intel has a known PCI bridge conflict with this card. |
No such evidence of that here.
Nor here:
http://adaptec-tic.adaptec.com/cgi-b...wers.search_nl
Nor here:
http://mysearch.intel.com/corporate/...archsubmit.y=4
Quote:
|
This is a *KNOWN* problem |
Quote:
|
in the industry. |
Btw, if it actually knew it's stuff and this bridge problem were actually to be true
then it would have advised you to look at the first number in "01:0a:01" of that
error message, which is the SCSI bus number.
Usually Bus #01 means that it is possibly behind a PCI to PCI bridge.
It can also merely mean that Intel just decided to mark the northbridge connected 64-
bit 66 MHz PCI bus as bus #01 and that there is no PCI to PCI bridge involved at all.
These are standard wide PCI slots, not PCI-X. There is no bridge to seperate them.
*If* it actually knew it's stuff about Intel server boards it would have advised you
to put the SCSI adapter in one of the 32-bit slots since the 2 64-bit slots are on
the same bus so changing between those has no effect.
The 32-bit 33 MHz PCI bus is connected to the Southbridge.
The STL2 manual doesn't show a PCI to PCI bridge involved there.
*IF*, *if* that card actually has a problem -as the troll alleges and for which there
is no evidence- with being on PCI bus #1 then you would be looking for a slot that
changes that first number "01" in 01:0a:01, to double zero.
*IF* there is a problem with that card it's likely not to do with PCI to PCI bridges
at all but with the number 01 (or higher) instead of 00. A simple BIOS upgrade would
fix that.
Quote:
|
My suggestion is scrap the Adaptec and use the onboard SCSI controller. Rita |
#19
| ||||
| ||||
|
|
Folkert Rienstra wrote If you Google his past posts you'll notice he has a track record of being a troublemaker and is the official group idiot. Whereas Rita Bigotowitz is a fully respected member of csiphs. Yes I am. |
Quote:
|
I was very instrumental in cleaning up this group |
Quote:
|
and spanking the trolls. |
Quote:
|
It seems you got your corncob lodged in an orifice that is reserved for your head. |
#20
| |||
| |||
|
|
Folkert Rienstra wrote: Whereas Rita Bigotowitz is a fully respected member of csiphs. Yes I am. |
Idiot.
|
« Previous Thread
|
Next Thread »
| Thread Tools | Search this Thread |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.