An expert who has achieved level 2 by getting 100 points
An expert that got 5 achievements.
An expert who has posted more than 50 answers, of which 90% or more were rated as helpful.
An expert whose answer got voted for 20 times.
Re: BOOT FAIL: PCF8584: I2C ERROR
According to the message you received on the screen there's might be something wrong with your RAM module(s). Take a look inside and see if everything's alright with RAM. Replace it to another slot if there are empty.
Download and use a program like MemTest to see if RAM is properly working.
If you have another computer which is compatible with your RAM, try it inserting then in to PC and see if everyhting's alright.
If nothing helps, then purchase a new RAM module
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Then, if compatible, check the IDE/SATA setting. Change the hard drive controller settings from IDE to AHCI or vice versa to see if the OS kernel panics on boot. If that does not work, please reply with your OS version and motherboard model.
Welcome to Fixya
The problem is with the raid controller . Either the controller is faulty or it is due to dust or happen some shake. To rectify this issue do the following
1: Switch off the server
2: Remove the Raid controller from the server and clean the dust . ( Please Don't touch with hand just blow air )
3: Clean the Controller slot
4: Refix the Controller and power on the server .
5: Check whether the controller is booting or not .
6: If you gets same problem then replace the controller
dear sir in my server IBM X3400 has a problem due to RAM it might be corrupted or out of order bcause system gives continues beep when i change the RAM with HCL 1 GB DDR2 (Previous RAM was also 1 GB) it gives error: waiting for controller to start FATAL ERROR: controller kernel self test failed << press any key to continue>> please solve the problem
Some common reasons for a delayed-write failure are:
1. Problems with a device driver, especially a SCSI or RAID device driver.
Some RAID device drivers are known to issue spurious "Delayed Write
Failed". Most manufacturers have been
alerted to this, so check to make sure the disk drivers are up-to-date.
2. Cabling problems. A faulty or broken cable
-- especially for an external USB or Firewire enclosure—can generate
this error. It can also happen if the cable is too long, or if it is
hooked up through a hub that isn't up to spec. Another possible culprit
is if you have a UDMA drive that requires an 80-pin cable, and you are
using a 40-pin cable.
3. SCSI termination errors. This has become less likely with the advent of self-terminating SCSI hardware, but it shouldn't be counted out.
4. Media errors. This is the worst possible
scenario -- essentially, drive failure. If you can garner statistics on
the drive via SMART (such as SMART & Simple (http://www.beyondlogic.org/solutions/smart/smart.html), you may be able to determine if there's a mechanical failure in the offing. Gibson Research's SpinRite tool (http://grc.com/) is also useful for assessing media errors, but be warned: It may take a long time to do a thorough test.
5. BIOS settings on the computer are forcing faster UDMA modes than the drive controller can handle.
This is unlikely, especially with newer hardware (which can support
UDMA far more flexibly), but it can usually be fixed with a BIOS
upgrade, or by resetting the BIOS entries for the hard drives to
auto-detect settings. Devices set to UDMA Mode 6 that produce this
error, for instance, might need to be set to Mode 5.
6. Controller issues. I've observed that USB
controllers that contend strongly with other hardware can produce this
error. In systems that have both "long" and "short" PCI slots (i.e.,
64-bit and 32-bit), try moving the USB controller to the long slot.
Older PCI cards will not fit in such a slot.
7. Memory parity issues. If the problem
appears after installing new memory, the memory in question may be
faulty or not of the correct type for the motherboard in question.
(This may go hand-in-hand with other problems such as random lockups,
8. The LargeSystemCache Registry tweak and ATI video adapters.
One peculiar set of circumstances that has been observed on multiple
machines with ATI video adapters and more than 512MB of memory involves
the LargeSystemCache Registry setting, a DWORD entry found in HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession
This setting governs the amount of memory set aside by the system for
certain kernel processes. If it's set to 1 (which allegedly improves
performance on systems with more than 512MB of memory), it can cause
data corruption on some systems, and produce the "Delayed Write Failed"
error. Try resetting it to 0 if it's been set.