Heretic Posted February 18, 2011 Share Posted February 18, 2011 for a couple of days now i was suddenly having a 2 tone alarm beep now and then. this morning I send an mail to supermicro asking about the meaning of it. it must have been the quickest response i ever got on an email. This means: "CPU overheat" Can you check IPMI logfiles for related message? i sent related ipmi logs and a printout for the cpu readout fro unmenu (the temps seemed fine 45 c for all cores) in the response that followed there was an instruction to update the ipmi firmware and update the firmware with the attached file. strangely enough (well to me at least) provided was the firmware for X8SIU0. I installed the firmware and when i boot now is listed Supermicro X8SIU(-F) here is a link for reference and x8sil-f I'm a little surprised since the layout is different but then again I dont really know that much about these things any thoughts? Quote Link to comment
Ford Prefect Posted February 18, 2011 Share Posted February 18, 2011 in the response that followed there was an instruction to update the ipmi firmware and update the firmware with the attached file. strangely enough (well to me at least) provided was the firmware for X8SIU0. I installed the firmware and when i boot now is listed Supermicro X8SIU(-F) ...just to clarify things a bit... ...you updated the IPMI firmware and the mobo model changed in the BIOS ? Did you reset the IPMI device and powered down the box completely...including disconnecting mains? ...looks like a glitch to me but definitely not a normal operational state. I'd return to SM with that info and ask what they can make of off it. Quote Link to comment
Heretic Posted February 18, 2011 Author Share Posted February 18, 2011 to clarify Please update IPMI firmware Temporary download link: xxxxxxxxx If possible please uncheck the option “preserve configuration” which forces a complete firmware update Note: this will reset all IPMI settings including IP address After firmware update it is also highly recommended to remove all power from system for 30 seconds At next power up IPMI will re-initialize with the new firmware Before connecting to IPMI please clear all browser cache and JAVA cache You can upgrade the IPMI firmware by web interface trough menu function; Maintenance -> Firmware Update Also please update to latest bios (attached) suplied bios was X8SIU0_C10 so first did an update with new ipmi firmware through web interface then flashed bios firmware from a bootable flash drive Quote Link to comment
Ford Prefect Posted February 18, 2011 Share Posted February 18, 2011 to clarify suplied bios was X8SIU0_C10 Ah, ok...thanks for that piece of the story Well, since you were able to successfully cross-flash the BIOS I don't see much of a problem. Both boards are based on the same main chipset(s). What I can see, they differ in the Super-I/O mentioned in the specs. But obviously it accepted the IPMI FW as well. ..did you find any new or changed items inside the BIOS (i.e. Super-I/O)?? ...again, I'd ask SM whether this move was intentional. Quote Link to comment
Heretic Posted February 18, 2011 Author Share Posted February 18, 2011 my intend is to double check if this firmware was supplied as intended. bios seemed mostly the same some minor differences unfortunately i don't have photographic memory strangely and maybe completely unrelated i'm no longer able to login to the server other than by ip address its a bit annoying for unmenu. also on boot unraid started an parity check although I'm pretty sure the data is correct (did an parity check this morning) I'm reluctant to stop it since it must be doing it for a reason, no? this seemed different to me but maybe i'm mistaken a small update: the bios updates did not solve the alarms going off it seems to be some errors with fan speeds on free fan pins only fan pin that actualy is in use is pin1 for the cpu the connection problems were gone when all equipment was powercycled, dont think it was related to the bios update. update from supermicro will probably not come before monday. Quote Link to comment
Ford Prefect Posted February 19, 2011 Share Posted February 19, 2011 ...here's the shot from mine... Looks like you've lost the floppy controller and gained some more setups for the sata-ports. BTW: you can take the shots from IPMI remote console..no need to grab a cam ...my sensors report OK. Quote Link to comment
Heretic Posted February 19, 2011 Author Share Posted February 19, 2011 thanks for the tip and the comparison shots. they are definitely easier on the eyes . out of curiosity what fans do you have connected to the motherboard? Quote Link to comment
Ford Prefect Posted February 19, 2011 Share Posted February 19, 2011 out of curiosity what fans do you have connected to the motherboard? Fan1 is the stock Intel boxed for my L3426 For the others, I went for cheap (around 5USD each) PWM capable ones. I ended up with Xilence Redwing models (Fan2 is the 120 and Fan4/5 are the 92mm variants) The BIOS health / fan-control is set to lowest level. The CPU boxed cooler/fan is the noisiest of the bunch The case is a yeong-yang cube YY-0221 Quote Link to comment
Heretic Posted February 20, 2011 Author Share Posted February 20, 2011 ah thanks, that brand is new to me. it claims to have up to 15 drive bays i only see 6 . i can see how you can make that 10 wit drive cages were are the other 5? this morning the state of the errors changed to this everything else seems fine I really wonder what is causing it. Could it theoretically be caused by software? Quote Link to comment
Ford Prefect Posted February 20, 2011 Share Posted February 20, 2011 ah thanks, that brand is new to me. it claims to have up to 15 drive bays i only see 6 . i can see how you can make that 10 wit drive cages were are the other 5? There's a link to a PDF that shows the structure and links to reviews with some photos. The case has actually two compartments, one for the mobo and one for the drives. There are 6x 5.25 bays in the front side of the drive compartment and 7x 3.5 bays in the back (might cover 10x but airflow might be tight for three of the disks). Along with 2x 5-in-3 cages you can have 17(save) - 20(tight) drives in your unRAID box. (I am not using it for unRAID...yet). everything else seems fine I really wonder what is causing it. Could it theoretically be caused by software? I really cannot tell...haven't seen it on my SM boards so far. Quote Link to comment
Heretic Posted February 21, 2011 Author Share Posted February 21, 2011 I had a look at the pdf's, definitely an interesting case. Got to say their drive cages look good as well, the fan in the center and control over fan speeds. no update form SM so far what did happen as sudden as the alarms came they went away i did unplug the power once more (already did twice to clear the cmos) and uninstalled 2 addons, iStat and bwm-ng. maybe one of those was somehow causing it. everything seems to run fine now, lets hope it will remain that way Quote Link to comment
Heretic Posted February 22, 2011 Author Share Posted February 22, 2011 got an update from SM today. the move was unintentional and they apologized. Also send me another firmware for the x8sil, which seems to share the same firmware between the x8sil-f x8sil and x8sil-v models will flash back as soon as the system is done preclearing Quote Link to comment
Ford Prefect Posted February 22, 2011 Share Posted February 22, 2011 got an update from SM today. the move was unintentional and they apologized. Also send me another firmware for the x8sil, which seems to share the same firmware between the x8sil-f x8sil and x8sil-v models will flash back as soon as the system is done preclearing Ah, thanks for the update. By "firmware" you mean BIOS, IPMI or both? May I ask you to provide the version number(s) as soon as you managed to apply it/them? Did it/they come with a changelog (probably not...haven't seen such a thing from SM) Quote Link to comment
Heretic Posted February 22, 2011 Author Share Posted February 22, 2011 i meant to say bios ipmi was version 2.22 and included in the first mail Bios was sent today. named X8Sil_tA270. when the files is dated at 27-10-10 the "normal" bios named x8sil0.527 on the site is dated 27-5-10 there are no change logs supplied. Quote Link to comment
Ford Prefect Posted February 22, 2011 Share Posted February 22, 2011 i meant to say bios ipmi was version 2.22 and included in the first mail Bios was sent today. named X8Sil_tA270. when the files is dated at 27-10-10 the "normal" bios named x8sil0.527 on the site is dated 27-5-10 there are no change logs supplied. Ok, so the newer IPMI FW was supplied for that mobo by SM? Sorry for being somewhat annoying, but I was under the assumption that both, IPMI-FW and BIOS image must match the mobo. I own a couple of different models of SM boards and BIOS+IPMI combinations seem to be individually advertised/maintained on the SM site. Your IPMI-FW seems to be the newest of all, being v2.22. Quote Link to comment
Heretic Posted February 22, 2011 Author Share Posted February 22, 2011 no wories I dont think you're annoying. this is in the textfile suplied with the ipmi firmware IPMI Firmware Release Note ---------------------------- Filename: SMT_222.bin ver2.22 Date: 02-09-2011 1. Correct ID for new motherboard support X8SIL-SIOM 2. Fix cpu temp "Overheat" logged when the reading reports "High" Description: CPU temp Overheat should be logged as the reading reaches "Overheat" 3. For security issue, set the privilege of user ID1(Anonymous) with no access Validation: 1. open IPMI web, 2. click Configuration->Users, and 3. check the privilege of user shows Reserved ====================================================================================== Filename: SMT_221.bin ver2.21 Date: 02-01-2011 1. Add new motherboard support X8SIL-SIOM 2. Add new motherboard support H8DCL ====================================================================================== Filename: SMT_V220.bin ver2.20 Date: 01-11-2011 1. H8DGG: Add slot 4 M1060/M2050/M2070/M2070Q GPU support (fan speed control, shutdown and slowdown) 2. Fix KVM slight flashes of white space while screen resolustion is below 800*640 ====================================================================================== Filename: SMT_V219.bin ver2.19 Date: 12-31-2010 1. H8DCT: remove VRD1 & VRD2 sensor items. 2. Fix uninstalled fans report lower threshold events while doing system reset 3. Fix lan1 lost connection issue while doing ipmi cold reset ====================================================================================== Filename: SMT_218.bin ver2.18 Date: 12-17-2010 1. X9SCL/X9SCM: modify Fan5 to FanA 2. X7SPT/X7SPA/X7SPE: fix wrong CPU Temp reading ====================================================================================== Filename: SMT_217.bin ver2.17 Date: 12-10-2010 1. H8SCM: Removed Fan6 sensor entry ====================================================================================== Filename: SMT_216.bin ver2.16 Date: 12-06-2010 1. Add new motherboard X7SPT support ====================================================================================== Filename: SMT_215.bin ver2.15 Date: 11-24-2010 1. Bug fix on Lan1 issue ====================================================================================== Filename: SMT_213.bin ver2.13 Date: 11-10-2010 1. Add new SSID for X9SCM 2. Fix incorrect sensor readings ====================================================================================== Filename: SMT_212.bin ver2.12 Date: 10-25-2010 1. Add new motherboard X9SCL/X9SCM support 2. H8DCT: Bug fix Fan3 speed is monitored ====================================================================================== Filename: SMT_211.bin ver2.11 Date: 10-19-2010 1. Fixed Virtual Media can't mount hidden files Description: VM should be able to mount hidden files with a dollar sign in the share like "\share$\dvdimage.iso" ====================================================================================== Filename: SMT_210.bin ver2.10 Date: 10-13-2010 ***CPU clock fixed at 180MHz*** 1. CPU clock fixed at 180MHz 2. X8DGG: Added device ID for GPU models, M2070 & M2070Q Description: GPU temperature are readable for new models. ====================================================================================== Filename: SMT_208.bin ver2.08 Date: 09-29-2010 1. Update on ECC error event logs 2. Add support for the BIOS to set different ACPI state (S0: system on, S1: sleep, S3: hypernate and S5: system off) 3. H8DGU(Appro): change lower thresholds of CPU Vcore & CPU DIMM VTT to fix the problem when 1.35v 8GB memory installed. Note: CPU Vcore: 0.736(NR), 0.744(CT), 0.752(NC) and CPU DIMM VTT: 0.584(NR), 0.592(CT), 0.6(NC). 4. Correct entity IDs in SDR 5. H8DGT/H8SGL/H8SCM/H8DGU-LN4: modify upper thresholds of NB Temp to 90(NC), 100(CT) and 110(NR) degree c 6. H8DGG: Remove sensors of GPU3 & GPU4 temp 7. Add new motherboard H8DCT support ====================================================================================== Filename: SMT_207.bin ver2.07 Date: 09-15-2010 For X8SIL/X8SIE/X8SII/X8SIA/X8SIU: 1. Adjust lower thresholds of fan speed to 215, 400 and 585(rpm) 2. Adjust upper thretholds of -12v to -10.934, -10.74 and -10.546(volts) ====================================================================================== Filename: SMT2_206.bin ver2.06 Date: 09-08-2010 Bug fixes: 1. CPU clock follows hardware strapping (to fix BMC crash by DDR using Winbond instead of Hynix chip) ====================================================================================== Filename: SMT_206.bin ver2.06 Date: 09-03-2010 Bug fixes: 1. X8SIT: Fix event log cannot catch CPU thermal trip event log (issueID=24349) and modify sensor system temperature to read from RT1: Bank 2, Reg.50 2. H8DGU-LN4+: Fix sensor CPU temperature does not show medium/high (IssueID=24950) 3. H8DGT-HF: Modify bootloader to fix memory corrupted at production (Ferrari Project) ====================================================================================== Filename: SMT_205.bin ver2.05 Date: 08-27-2010 Bug fixes: 1. X7SPA: Modify sensor name "Vnbcore" to "Vichcore" 2. H8DG6-F: Fix CPU temperature reports 'Low' eventhough CPU is overheating (issueID=24719) 3. Fix SSH login with user/password: ADMIN/C0rbisSMAdmin ====================================================================================== Filename: SMT_204.bin ver2.04 Date: 08-13-2010 Bug fixes: 1. X8SIL/X8SIE/X8SIA/X8SIU: Modify system temperature to read from RT1: Bank 2, Reg.50 (issueID=24254) 2. Add Daylight Saving Time in web gui: Configuration->Date & Time 3. H8DGG-QF: Support Fermi GPU M2050 which can slowdown and shutdown GPU when overheat ====================================================================================== Filename: SMT_203_0805.bin ver2.03 Date: 08-05-2010 Bug fixes: 1. X8DTU-6F+: Add 100ms delay for sensor polling to fix issue wrong sensor readings on SD3 client after overnight stress test (issueID=23803) ====================================================================================== Filename: SMT_203_0803.bin ver2.03 Date: 08-03-2010 Bug fixes: 1. H8DG6: Remove GPU from sensor readings (issueID=24521) 2. X7SPE-HF-D525: Modify +12V sensor calculation ===================================================================================== Filename: SMT_202_0727.bin ver2.02 Date: 07-27-2010 Bug fixes: 1. H8DGU-LN4F: set GPIO34 to high to fix BIOS hangs with post code '3E' or 'E1' (IssueID=24461) 2. Add SMTP sender's email (Web gui: Configuration -> SMTP) ===================================================================================== Filename: SMT_201_0721.bin ver2.01 Date: 07-21-2010 Bug fixes: 1. Fix Lan1 issue for all motherboards with Hartwell (82574) LAN chip Description: Cannot connect to BMC use onboard LAN1 after upgrade to new FW. Validation: With default setting "failover" or default for non-dedicate LAN MB, BMC connect with LAN1, SUT in OS (WS2008R2, RH5.4, or RH5.5). Please upgrade FW from previous release version to this new version using web GUI and check whether BMC can connect again after FW flashing. ===================================================================================== Filename: SMT_200_0720.bin ver2.00 Date: 07-20-2010 Bug fixes: 1. X8DTU-LN4F+: Add +1.1V sensor (issueID=24334) 2. X8DTU-F: Add sensor CPU1 DIMM and CPU2 DIMM (issueID=24269) 3. X7SPA/X7SPE: Rename sensor name "1.05V" to "Vnbcore" to sync with BIOS (issueID=23092) I can only speculate here, the links on the ipmi firmware page all seem to be a different url suggesting its different firmwares. seeing the release notes however seem to suggest otherwise a lot of different MB's are named. the first mail I got gave the 2.22 ipmi firmware and the wrong bios. If ipmi firmware is bound to the motherboard I have the wrong one installed. maybe it would be interesting to physically compare 2. Quote Link to comment
Heretic Posted February 22, 2011 Author Share Posted February 22, 2011 ok I downloaded and unpacked the SMT_201_0721 firmware for x8siu-f and x8sil-f created and sfv file for one and compared both files. they matched. Quote Link to comment
Ford Prefect Posted February 22, 2011 Share Posted February 22, 2011 Good job! I think IPMI FW is only bound to the BMC used. Interestingly, not all mobos listed in the txt file of yours, are maintained at the SM ftp site for IPMI-FW, like the H8DCT. However, the individually advertised link for this mobo's FW points indeed to v2.19. Also the FW for the X7SPA-HF is still advertised as 2.02, while in your txt a newer version is available. Looks like SM is saving a lot of regression testing and is only handing out newer versions individually and only if the customer files a bug with them. BTW: I have two identical SM boards/models, with same BIOS and IPMI-FW but board no. A reports three more sensors than board no. B it its health status. Quote Link to comment
Heretic Posted February 23, 2011 Author Share Posted February 23, 2011 Today was a lil nerv-wrecking. I finally ended up with the latest firmware for the X8sil-F installed. at first neither the new or old firmware wanted to flash and when it finally did it stopped midway. only option was a bios recovery to the old x8sil0.527 firmware. The recovery succeeded but it had to be re-flashed to get rid of the cmos checksum error. again it didn't want to flash this time it gave: error: bios does not support ME ignition Firmware update then i tried flashing the newer bios and it actualy worked altho again an checksum error. flashing a second time it again stopped like in the first pic. another recovery this time using the new firwarebios and like magic it suddenly worked. damn i get tired reading that the moral of this story: beware upgrading your bios! SM's help has been great during the whole process great support lets hope i never have to touch this bios again Quote Link to comment
01111000 Posted February 24, 2011 Share Posted February 24, 2011 Wow, small world. http://lime-technology.com/forum/index.php?topic=11160.0 I have a SUPERMICRO MBD-X7SPE-HF-D525-O. At 45 C I get the same alarm. Very annoying. So I'm assuming you fixed it by upgrading the IPMI BIOS? This topic is a bit hard to follow. Quote Link to comment
Heretic Posted February 24, 2011 Author Share Posted February 24, 2011 The error i got was for failed fans on a fan header without any fan. It seems it was some monitor software that caused it. After I uninstalled 2 addons, iStat and bwm-ng. I got no more Alarms. It is probably only one of those i assume istat but i haven't tested. I'm a little reluctant to reinstall it . Did you read out your ipmi events? If it is your cpu is your alarm threshold accidentally set to low? Quote Link to comment
01111000 Posted February 24, 2011 Share Posted February 24, 2011 I too have iStat installed. I just disabled it, let's see if it happens again. I cannot change the cpu threshold. I noticed that every time it gets to 45C it happens. I'm guessing the board attempts to cool the CPU down, and since there are no fans connected, it throws the fan fail error. I guess it wasn't the CPU alarm after all, just the fan error like yours. Other than this problem, everything has been smooth sailing. Quote Link to comment
Heretic Posted February 24, 2011 Author Share Posted February 24, 2011 it wil be interesting to know if we can isolate istat as the culprit Quote Link to comment
christuf Posted March 12, 2011 Share Posted March 12, 2011 Hi, I have exactly the same issue with a X8SIL-F-O motherboard. Keep getting two-tone beeping warning noises which are giving me the creeps! I disabled both the iStat and bwm-ng addins, restarted, but am still getting critical warnings for fans (2-5) which are not installed on my system. I have not upgraded the stock BIOS, but from reading below, it seems that didn't help fix anything. Very grateful for any assistance! Chris Quote Link to comment
Heretic Posted March 14, 2011 Author Share Posted March 14, 2011 do you have ipmi events? try pulling the power plug for 1 min so ipmi can reset otherwise maybe try updating the ipmi firmware I hear a little beep now and then but believe that is when the network lease "refreshes" it doesn't register events Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.