Red led at SCSI drive# 2 and 5

First off, a main board will never cause a backlight issue like this, the main either turns them on or it doesn't. The inverter for the backlights on this and a few other LG sets have the current tolerance extremely sensitive, there are 2 supplies driving the backlights, one supply for 4 strips the other for 6 and each is independent where one can work and the other not work. Where did you buy the LED lights? Were they some off brand knock off lamp strips or did you get them from a reputable place like shopjimmy? A gut feeling is you have bad lamps, the power board seldom gives issues on this model, if you get them from shopjimmy have them send you another set. Also it's possible for the lamps to work on a LED tester but not work in the TV, I've seen it many times.

Larry the Computer Guy, posted up there ^^^^ instead of here.

• Larry Ng Jan 19, 2021NO PC told no maker no model
  no UW SCSI card told, at all. (Adaptec?)_
  SCSI can run HDD, or tape and many things
  what does yours run? IDK.
  
  we run ultra for years, back when.
  why are you doing old UW SCSI.?
  tell what tool means,. ive no idea at all
  a metal tool , software what?
  tell what the tool does? and we now can communicate.
  only very very old full blown workstations
  had a UW SCsi HDD, non told yet.
  
  what does not responding mean./
  1: PC dead silent..
  2: all fans dead.
  3: power on LED dead or acts odd now.?
  4; BIOS screens dead./ all ? this is goal #1
  5: hdd boot files not found error on screen.
  6: any beep codes, any LED blink codes.
  id have to ask like 100 question more
  with you not telling make of PC , model of PC and where is this SCSI port, show 1 photo of
  the inside of PC left side and AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
• 
  Anonymous Jan 19, 2021
  pure raw wild guess.
  the PC is 20 year old
  the HDD died 15 years ago
  and found this rig for $1 at a garage sale
  DOA.
  Ultra-320 SCSI ? from year 2003?
  
  remove it and put in SSD 2.5" solid state drive (SATA) and boot from that.
  end story, join the modern world?
  SCSI is now dead, tech. as in fully retired.
  we use SAS or fast SSD. now.
• 
  Larry Ng Jan 19, 2021
  if the HDD is dead say so.
  post symptoms and ask for help,ok?
  that is why this forum exists to diagnose problems.
  test #1 on PC that seems to have power and does with BIOS screens working
  the HDD must be heard to spin. (and all fans)
  
  
  ask how. (i own a 5$ stethoscope a TOOL)
  no spin ,no joy, possible.
  it has motor inside, the hdd controller
  sends a command to the hDD to spin up
  turned on, in magical SCSI land
  we can even sequence say 5 HDD drives to spin up 1 at a time to not overload the PSu.
  
  
  that is all controlled via the SCSI card
  own Bios screens. prompted at power on in fact.
  the SCSI card has its own menus inside its own ROM.firmware. we go there and check the drive out. (might show HDD dead in fact)
  
  
  NO PC told no scsi card told.
  
  here is mine spinning up now.https://pcdied.com/HDD-SDD/spoolupjet.mp...
  
  if HDD click like mad , the HDD is bad.
  like this.
  https://pcdied.com/HDD-SDD/WD-bad-heads-...*****.mp3
  
  post of photo or left side inside this PC.
  lid off PC pulled off. (then add a photo)
  then we can talk turkey. (to brass tacks)
• 
  Anonymous Jan 19, 2021
  have scsi now
  or dreaming of 2003 old dead parts to buy cheap. tell the story fully dude. we can not guess what is up there.
  did i nail this?
• 
  Anonymous Jan 19, 2021
  post a problem, and ask for help
  please.
  what PC
  what OS
  and what fails. tell all that.
  even tell what works good too?
• 
  Anonymous Jan 19, 2021
  the reason nobody talks SCSI now is that it is now retired. (eol)
  yes some very very old PCs workstations had this, OOBE day1. sure. have one in my attic full of thick dust. old and slow.
  and for sure servers. old.
  

Hi , I suggest try testing single memory modules , one at a time to isolate a faulty module if that is the issue
Another idea is running a Linux live distro os like Ubuntu from bootable disk or flash drive in live/try mode which run from a virtual partition on the ram memory
If Linux runs ok - then likely a Windows related driver / software issue but if same crash issues are observed then most likely a hardware device issue ie faulty memory module , but as varies when crashes i am thinking more the psu - high boot current load demands due to twin SCSI drives , video card etc - old psu - after a few years the power current rating reduces I recall -25% typical , discrete components not so resistant to heat - try to test with a known good high performance psu or just replace , at release date 2002 definitely due for a replacement new psu

SCSI Hard Drive Activity LED Connector
The SCSI hard drive activity LED connector is a 1 x 2-pin connector that allows an add-in SCSI controller to use the same LED as the on-board IDE controller. For proper operation, this connector should be wired to the LED output of the add-in SCSI controller. The LED indicates when data is being read from, or written to, both the add-in SCSI controller and the IDE controller.

Test the 2 pins using a multi-meter to determine which is + and which is -. Nowhere in the manual does it say which is which.

I’m happy to help further over the phone at https://www.6ya.com/expert/jeremy_69f3cc28d95bf514

There are two ways of retrieving data from a SCSI hard drive.
1. Connect the SCSI hard drive to a different SCSI connector on the same data cable, make sure this hard drive has a different SCSI ID from the first hard drive or other SCSI devices in your system. When you boot up your MAC you should see the second SCSI hard drive, You can then copy off your data or remove the redundant files and keep the old hard drive in your system as a 2nd hard drive.
2. Connect the old SCSI hard drive to a SCSI USB hard drive adapter. Then connect it to the USB port on the MAC and you should see this as an external hard drive.

Are you sure the new motherboard was of the same revision as the old one? Dell shipped 400FSB boards during the beginning of the 1600SC line and shipped 533Mhz boards during the end of the run. I would check the revision level of the motherboard to make sure it is compatible. If it's the same revision, I would start small and connect just one CPU and put the system at 512mb ram and see if that works. If this works, you can begin to add additional components as needed.

Good luck

$3$ WolF ILia $3$ :):):)

If the Bios did not detect the third drive, try switching it to a known working slot and see if you have a bad drive, or something wrong with the cage or cabling. The 3000 were shipped with either a 68 pin drive cage or a 80 pin drive cage. The 68 pin drives and the 80 pin drives are not interchangeable. To make matter worse, the drive cage would be configured as simplex or duplex. For duplex mode, you will need to connect two SCSI cables to the cage.

When you get the red ring, these things can happen. But u should get a error message or something. 
The specific type of hardware failure can be determined by a "hidden" error code

• Turn the xbox 360 on, and wait till the 3 red lights are flashing.
• Press and hold the sync up button (the small white one), while holding that button press the eject button.
• The LEDs will now blink the first number in the code (as described below).
• Release the eject button and press it again.
• The LEDs will now blink the second number of the code.
• Release the eject button and press it again.
• The LEDs will now blink the third number of the code.
• Release the eject button and press it again.
• The LEDs will now blink the forth number of the code.
• Release the eject button and press it again.
• The LEDs will go back to the 3 red flashing lights.

You should be able to determine the difference between the 3 flashing lights and the error code lights by the rate in which they flash.

Here is how you interpret the LEDs to get the code number:

• All four lights flashing - 0
• One light flashing - 1
• Two Lights flashing - 2
• Three lights flashing - 3

0001 power supply problem
0002 Network Interface problem
0003 Power problem could be the PSU could be the GPU/CPU, somehow the console isn't getting clean power from the power supply.
0010 There is a problem with the Southbridge Chip usually dealing with how it connects to the mainboard (cold solder joint/bridged solder joints)
0011 CPU over heating - If you are receiving this error after disassembling your console make sure to all 8 of the heatsinc screws are tightened securely to the board/heatsink holes.
0012 GPU over heating
0013 RAM over heating
0020 (Not yet known, possibly overheating)
0021 This can be caused by two completely different things either: 
A. DVD Drive Time out - Can be caused by problems with a firmware flash. This is also speculated to sometime be caused by a problem with the southbridge chipset on the motherboard based on how it connects to the DVD drive.
B. GPU error, generally caused by a poor connection to the mainboard (cold solder joints/bridged solder joints) See error 102 for more information
0022 CPU error, generally caused by a poor connection to the mainboard (cold solder joints/bridged solder joints). This can also be triggered by an error with the TSOP.
0023 (not yet known)
0030 Problem with temperature control
0031 (not yet known)
0032 (not yet known)
0033 (not yet known)
0100 (not yet known)
0101 (not yet known)
0102 Error in the "Digital Backbone" (CPU/GPU/RAM), this is usually caused by a cold solder joint between the GPU and the mainboard.
There are two theories to fixing this one deals with the "X" clamps that hold down the chips. The other involvesre-Heating the chips. DO NOT attempt either of these if your console is still under warranty. If your console is still under warranty return it to the store where it was purchased or call MS to have it replaced. 
[/list]0103 GPU Error this is usually caused by bridged solder points where the GPU connects to the mainboard. see error 0102 for more detailed information
0110 Ram error, this is caused by a cold or bridged solder joint on one of the Ram chips.
...
0200 (not yet known)
...
1000 Kernel can't be launched/signature in NAND Flash chip is broken! It could be possible after bad update.http://forums.xbox-scene.com/index.php?sho...p;#entry4156375 This might also be caused by a bad SATA cable.
1001 DVD Drive Error, either incorrect firmware or DVD Time out.
1002 DVD Drive Error, likely a firmware error, drive can eject, read, and write under windows but errors on console, replacing original firmware should fix issue.
1003 Hard Drive Error... It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it
1010 Hard Drive Error, Can be caused buy a corrupt or missing eProm. See also E68 above
1011 (not yet known)
1012 (not yet known)
1013 (not yet known) possibly a dashboard update error
1020 (not yet known)
1021 (not yet known)
1022 There is high chance it's a scaler chip problem (the "ANA" or "HANA" chip near the AV cable connection) it can also be caused by a faulty AV cable so check that first. In some cases it is a problem with the GPU and may be repairable by doing the x-clamp replacement (see error 0102)
1023 DVD drive not connected, connect DVD drive to boot
1030 This error deals with the Ethernet port's controller chip, a dead chip may not cause the error but removing the Ethernet controller chip does, it may also be caused by other Ethernet related problems.
1031 (not yet known)
1032 (not yet known)
1033 it could be cpu/gpu related or it could be psu related, not much info is known for sure.
...
1444 and up There is no "4" in the error codes four lights is a "0" go back and check your code again.


That should help That should help./

I had the same problem.
There is a cd that came with the server called "IBM RAID Support" that is a must have to reconfigure the hard drives.
It took me a week to find the ISO image.
I will upload the cd via FTP and send you the link.