20 Most Recent IBM eserver xSeries 232 8668 Questions & Answers

hi,
which material have you ? : CD
which server ? xseries xxx model type ?
If this is the unique SCSI adapter in your system
or the unique seen, you must:

0) download
90p2772.iso 505,085,952 IBM ServeRAID support CD v6.10
or use what you have.

1) Boot from cd (linux) to configure RAID , before install W2K Server

2) run 23k4684.exe (previous site) in another pc and make a floppy

3) boot from W2k CD and press F6 when proposed

4) insert floppy previously made

5) when OS is installed, or from CD or using 23k4687.exe,
install "IBM ServeRAID Manager", to see activity.

Interesting....have you preformed a low level format on the destination HDD? The one receiving the clone? With linux previously being on that HDD its MBR may not be viable by windows. Windows doesn't like to play with others. Although its MBR shouldn't matter in a clone, some software may react differently. I would try a low level format on the destination driver before continuing threw the clone.

Assuming that this is resolved as it appears to be an old, time-sensitive issue. Although I would say that what you're asking would have been a design choice on IBM's part. The BMC would dictate fan curve and if one of the fans is not spinning at the minimal RPM - as specified in that fan curve - then it would obviously shut the system down to protect it from heat damage. You may be able to adjust this using various commands in the BMC but I am not familiar with IBM's hardware. (Which is likely different in the same way that Dell's iDRAC differs from HP's iLO, etc.) I'd say it's unlikely either way.

bad net Connection or netcard

I would check the firmware/bios as these had a known issue. Check with IBM for the latest firmware and BIOS. Update me if this does not resolve the problem.

Hi, Server is model is not mentioned. You can clear logs by this way.. 1: Get into BIOS and there you could see server logs. Clear those logs 2: Get into IMM and you can find logs there. Clear those logs (This is applicable to servers with IMM and Uefi firmwares) 3: Get into BIOS and find out IPMI logs. Its under Advanced settings. Clear those (This is applicable for older x series machines with BIOS firmwares) Thanks

Guide events have changed the identification protocol and a refreshment of the input data to the Event ID structure will fix the problem. This must be done within 24 hours of the last formal event or else the system will crash and no longer be salvable.

go into bios and change start up type from uefi to legacy if you don't have the option update the bios

Well it usally means the fan is bad it may work and keep your CPU cool but it can still send the code just replace the fan

you need to install a "server OS" either (server 2000 or 2003, 2008) windows xp will not work on the sever machine

Depending on version you have the should numerous boot options, like power off / on, ctrl alt del, and so on. You may also require admin rights. Some accounts only have read only.