Um... RAID controller/drive problem?

[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
RAID Host adapter? Because I connected an Ultra320 hard disk to a RAID
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
or verified with any utilities - it just becomes totally unreadable one day, and
the whole drive has to get re-formatted. Then it works fine again for a few weeks.

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?

 

[Arno Wagner]

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
RAID Host adapter? Because I connected an Ultra320 hard disk to a RAID
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
or verified with any utilities - it just becomes totally unreadable one day, and
the whole drive has to get re-formatted. Then it works fine again for a few weeks.

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?

A well-designed controller should either support this reliably or not at
all. Both are valid possibilities. I would advise you to throw away this
junk-controller and get something more reliable.

Arno

 

[Folkert Rienstra]

But you are on Raid controllers, obviously.

and have the following problem -

A well-designed controller should either support this reliably or not at
all. Both are valid possibilities. I would advise you to throw away this
junk-controller and get something more reliable.

Typical clueless babblebot.
Doesn't even ask what controller, whether there are BIOS/driver updates
or even what the error message was.

 

[fred]

But you are on Raid controllers, obviously.



Typical clueless babblebot.
Doesn't even ask what controller, whether there are BIOS/driver updates
or even what the error message was.

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"
maybe not exactly like that, but that is the gist of it.

 

[Eric Gisin]

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" maybe not exactly
like that, but that is the gist of it.

This is a SCSI card with optional RAID. Ultra 320 is overkill for a single disk.

 

[Arno Wagner]

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"
maybe not exactly like that, but that is the gist of it.

Well,unfortunately Adaptec is high-proced trash. The first disk I lost
with their controllers was an ESDI disk way back. They had a problem
they did not admit to then. The last thing I bought was an exceedingly
unreliable 8-way SATA RAID controller. It kept dropping disks without
good reason.

This fool-you-into-thinking-it-works behaviour just means they think
their name is good enough and they do not have to actually care about
their customers data. I would advise you to move to something worth
its money, e.g. 3ware.


Arno

 

[Odie Ferrous]

But you are on Raid controllers, obviously.



Typical clueless babblebot.
Doesn't even ask what controller, whether there are BIOS/driver updates
or even what the error message was.

And your solution is????

Twat. Please go away. No-one likes you. Myself included.


OD

 

[Folkert Rienstra]

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-bin/adaptec_tic.cfg/php/enduser/std_adp.php?p_faqid=14319
and
http://adaptec-tic.adaptec.com/cgi-bin/adaptec_tic.cfg/php/enduser/std_adp.php?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.

 

[Folkert Rienstra]

Well,unfortunately Adaptec is high-proced trash.

Babblebot on his 100.000th brainfarct.

The first disk I lost with their controllers was an ESDI disk way back.
They had a problem they did not admit to then.

The last thing I bought was an exceedingly
unreliable 8-way SATA RAID controller.
It kept dropping disks without good reason.

This fool-you-into-thinking-it-works behaviour just means they think
their name is good enough and they do not have to actually care about
their customers data.
Gibberish.

I would advise you to move to something worth its money, e.g. 3ware.

Very good, moron babblebot.
3ware are renowned for their SCSI controllers and Non-RAID controllers.
For not having any of them, that is.

 

[=?Windows-1252?Q?Rita_=C4_Berkowitz?=]

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. 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

 

[Folkert Rienstra]

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.

 

[=?Windows-1252?Q?Rita_=C4_Berkowitz?=]

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 know you just can't
stop at one SCSI drive? He does need to scrap the old ribbon cable and go
SCA.

Bwahahah.

Shows your lack of actual hands on experience in the real world. Sadly,
this cures the problem 98.475% of the time. To cure all of these petty
problems you go MegaRAID. 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.






Rita

 

[fred]

"Something like" usually doesn't cut it when using Google to find answers.


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-bin/adaptec_tic.cfg/php/enduser/std_adp.php?p_faqid=14319
and
http://adaptec-tic.adaptec.com/cgi-bin/adaptec_tic.cfg/php/enduser/std_adp.php?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"

 

[Folkert Rienstra]

Sure does, especially when he gets six more drives.

Ah, the magic number 6.
You mean 7, don't you girl. Or 8 if you include a hot spare.

You know you just can't stop at one SCSI drive?
He does need to scrap the old ribbon cable and go SCA.

Corse he does. (clueless)

Shows your lack of actual hands on experience in the real world.

Sadly,

As in: you're a sad excuse of a bullshit artist, girl?

this cures the problem

Not the SCSI bus related ones, dear.

98.475% of the time.

Poster must be in that remaining 1.525% then, dear.
What a sad coincidence, eh.

To cure all of these petty problems you go MegaRAID.

http://64.233.183.104/search?hl=en&q=problems+MegaRAID&btnG=Google+Search
Results 1 - 10 of about 183,000 for problems+MegaRAID. (0.13 seconds)

Oh dear, dear.

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.

Like the one featuring in your shop window prominently, dear?

 

[Folkert Rienstra]

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?

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.

 

[fred]

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_...search=www.scdifaq.org&as_rights=&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/motherboards/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.

 

[=?Windows-1252?Q?Rita_=C4_Berkowitz?=]

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

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.

The mother board is
http://support.intel.com/support/motherboards/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.

Yes, Intel has a known PCI bridge conflict with this card. This is a
*KNOWN* problem in the industry. My suggestion is scrap the Adaptec and use
the onboard SCSI controller.







Rita

 

[=?Windows-1252?Q?Rita_=C4_Berkowitz?=]

Ah, the magic number 6.
You mean 7, don't you girl. Or 8 if you include a hot spare.

Or a baker's dozen.

Corse he does. (clueless)

LOL! Who uses cables anymore to connect drives? Backplanes are where it is
at.

As in: you're a sad excuse of a bullshit artist, girl?

LOL! You are a funny man. Have you ever held a SCSI drive?

Not the SCSI bus related ones, dear.

And you are sure it's a SCSI bus related problem? It really aint, but I'll
let you make the usual fool of yourself.

Poster must be in that remaining 1.525% then, dear.
What a sad coincidence, eh.

He didn't tell us what motherboard he's using. But, the other 1.525% is
reserved for AMD based crap.

http://64.233.183.104/search?hl=en&q=problems+MegaRAID&btnG=Google+Search
Results 1 - 10 of about 183,000 for problems+MegaRAID. (0.13 seconds)

Oh dear, dear.

Yep! And you'll notice on the very first page these idiots are using the
wrong OS. They created these problems by not using Windows.

Like the one featuring in your shop window prominently, dear?

Sorry, all AMD products that come in on sight unseen lots get stripped down
and sold for parts on eBay. There's no money in AMD.







Rita

 

[=?Windows-1252?Q?Rita_=C4_Berkowitz?=]

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?

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.

Why don't you stop pissing around at making a total fool of yourself and
either help the man or not respond to him? If you knew what you were doing
you would have solved his problem. I don't know why this person wasted his
time with your clueless bullshit?







Rita

 

[Michael Giegerich]

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?

RAID Host adapter? Because I connected an Ultra320 hard disk to a RAID

Which SCSI controller?

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.

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?

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,
- SCSI controller and BIOS/firmware,
- Cable(s)/backplane(s),
- Termination,
- SCSI drives attached internally (and externally),
- Other devices on the system,
- System description (I do like dmesg outputs),
- Boot drive,
- Operating system,
- Detailed problem description (!).

The more detail you give, the better you may
be helped.

A not really helpful answer to your question
may be:
the system I'm writing this message on, has
a non raided scsi device attached to a raid
controller working flawlessly since years.

Much more information (still not really
answering your problem is the dmesg output
of the system, which tells you that it has a
tape drive attached to an Adaptec 3200S raid
controller):

Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.11-RELEASE-p26 #68: Sun Dec 10 18:30:18 CET 2006
(e-mail address removed):/usr/obj/usr/src/sys/LOCAL
Timecounter "i8254" frequency 1193182 Hz
CPU: Intel Pentium III (799.62-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x686 Stepping = 6
Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory = 2147471360 (2097140K bytes)
avail memory = 2087194624 (2038276K bytes)
APIC_IO: MP table broken: 8259->APIC entry missing!
Programming 16 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
Programming 16 pins in IOAPIC #1
FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs
cpu0 (BSP): apic id: 3, version: 0x00040011, at 0xfee00000
cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000
io0 (APIC): apic id: 14, version: 0x000f0011, at 0xfec00000
io1 (APIC): apic id: 13, version: 0x000f0011, at 0xfec01000
Preloaded elf kernel "kernel" at 0xc0450000.
ccd0-3: Concatenated disk drivers
netsmb_dev: loaded
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <ServerWorks NB6635 3.0LE host to PCI bridge> on motherboard
IOAPIC #1 intpin 11 -> irq 2
IOAPIC #1 intpin 0 -> irq 5
IOAPIC #1 intpin 2 -> irq 9
pci0: <PCI bus> on pcib0
pci0: <S3 Savage 4 graphics accelerator> at 1.0
fxp0: <Intel 82559 Pro/100 Ethernet> port 0x2000-0x203f mem 0xfea00000-0xfeafffff,0xfeb7f000-0xfeb7ffff irq 2 at device 2.0 on pci0
fxp0: Disabling dynamic standby mode in EEPROM
fxp0: New EEPROM ID: 0x4080
fxp0: EEPROM checksum @ 0x3f: 0xd1f8 -> 0xd1f8
fxp0: Ethernet address 00:06:29:13:7a:18
inphy0: <i82555 10/100 media interface> on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: <Intel 82558 Pro/100 Ethernet> port 0x2040-0x205f mem 0xfe900000-0xfe9fffff,0xfcfff000-0xfcffffff irq 5 at device 9.0 on pci0
fxp1: Ethernet address 00:08:c7:9b:33:91
inphy1: <i82555 10/100 media interface> on miibus1
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
atapci0: <Promise TX2 ATA133 controller> port 0x2080-0x208f,0x206c-0x206f,0x2070-0x2077,0x2068-0x206b,0x2060-0x2067 mem 0xfeb78000-0xfeb7bfff irq 9 at device 10.0 on pci0
ata2: at 0x2060 on atapci0
ata3: at 0x2070 on atapci0
isab0: <ServerWorks IB6566 PCI to ISA bridge> at device 15.0 on pci0
isa0: <ISA bus> on isab0
atapci1: <ServerWorks ROSB4 ATA33 controller> port 0x700-0x70f at device 15.1 on pci0
ata0: at 0x1f0 irq 14 on atapci1
ata1: at 0x170 irq 15 on atapci1
ohci0: <OHCI (generic) USB controller> mem 0xfeb7e000-0xfeb7efff irq 10 at device 15.2 on pci0
usb0: OHCI version 1.0, legacy support
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 4 ports with 4 removable, self powered
pcib1: <ServerWorks NB6635 3.0LE host to PCI bridge> on motherboard
IOAPIC #1 intpin 6 -> irq 11
pci1: <PCI bus> on pcib1
pcib2: <PCI to PCI bridge (vendor=1044 device=a500)> at device 6.0 on pci1
pci2: <PCI bus> on pcib2
asr0: <Adaptec Caching SCSI RAID> mem 0xec000000-0xedffffff irq 11 at device 6.1 on pci1
asr0: major=154
asr0: ADAPTEC 3200S FW Rev. 370F, 2 channel, 256 CCBs, Protocol I2O
orm0: <Option ROMs> at iomem 0xc0000-0xc9fff,0xca000-0xca7ff,0xca800-0xccfff,0xcd000-0xd2fff on isa0
pmtimer0 on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2
APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0
IPsec: Initialized Security Association Processing.
SMP: AP CPU #1 Launched!
ad4: 156334MB <Maxtor 6Y160P0> [317632/16/63] at ata2-master UDMA133
acd0: CD-RW <HL-DT-ST RW/DVD GCC-4480B> at ata0-master PIO4
sa0 at asr0 bus 0 target 4 lun 0
sa0: <TANDBERG SLR100 0550> Removable Sequential Access SCSI-2 device
da0 at asr0 bus 0 target 2 lun 0
da0: <ADAPTEC RAID-1 370F> Fixed Direct Access SCSI-2 device
da0: Tagged Queueing Enabled
da0: 35003MB (71686144 512 byte sectors: 255H 63S/T 4462C)
cd0 at ata0 bus 0 target 0 lun 0
cd0: <HL-DT-ST RW/DVD GCC-4480B 1.06> Removable CD-ROM SCSI-0 device
cd0: 16.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present
Mounting root from ufs:/dev/da0s2a