Unsolved
1 Rookie
•
2 Posts
0
297
April 19th, 2024 11:54
R630 can't boot (sec 0033)
Hello,
I have a R630 that refuses to start up with the message sec 0033 Intrusion detected check chasis cover appearing (once).
The startup attempt lasts 10sec, then the server shuts down and tries, in a loop, to start up.
LCD in front doesn't start most of the time eather and when it's showing something, it's just the name.
So far I've done the following:
- changed the chasis cover: without success
- Changed the PCI card where the contactor is located: without success.
- Changed both PSU : without success.
I'm left with a black screen, no loading and a looping reboot, so there's no way of reaching the BIOS or IDRAC.
Is it possible that it could be one or both processors?
Can the RAM fail too?
Thanks in advance for any help you can provide :)


DELL-Chris H
7 Practitioner
•
9.7K Posts
•
48K Points
1
April 19th, 2024 16:29
Melvira,
I would start with taking the R630 to its minimum to post configuration, which is removing everything from the server internally and externally but the following
One processor (CPU) in socket processor 1
● One memory module (DIMM) in socket A1
● One power supply unit
● Left control panel with cable (for power button functionality)
● System board
Try powering up and see if the server posts correctly, if it does then individually add te removed devices back until the issue reappears, identifying the problem device, or until everything is reinstalled.
Now if you can't post under that configuration then the culprit is likely one of the devices listed above, where my thoughts would be motherboard.
Let me know what you seem and if this helps.
Melvira
1 Rookie
•
2 Posts
0
April 20th, 2024 12:22
Hello Chris,
Thanks for your reply, I wasn't sure if sec 0033 could appear with other components at fault.
I'll try this and post the results to help the community (you never know).
Regards
PortalNET2
1 Rookie
•
72 Posts
0
January 13th, 2025 23:28
Hi guys..
Funny enough i have a Dell R630 with the exact same issue here..
i can power the server , and login to idrac server has BIOS 1.0.4 and idrac 2.02.xxx
so far i have managed to upgrade idrac couple of times with lower idrac versions.. managed to upgrade up to 2.86.xx last version..
tried updating bios to next 1.1.4 but soon as the idrac sends de reboot command.. server boots up i can hear fans spinning for about 7 seconds then stops and restarts again , obviously the bios does not update..
i have removed back pci-e cards, removed raid controller h730, removed cpu2 just left cpu 1 with ram slot a1, removed psu2, i am using cpu e52630v3 on slot 1 ..
server simply doest not start it stuck after 7 seconds is cuts power and reboots again.. in a loop cycle..
any ideas on what could be? i have already tried NVRAM_CLR jumpers also..
running out of ideas .. if i put back the pci-e adapter, and the lower slot pci-e card on the chassi put the 2 psu with the 2 cables plugged on the energy and close the cage.. when i plug both cables form PSU with green light.. server does not start.. i wait around 30 seconds.. and the idrac blue light comes on.. i can login to the idrac remotely.. and i can try to search for any diferent errors from cage open.. psu removed..etc.. but no other error shows up.. , when i press the power button on the server it powers up for around 7 to 8 seconds then fans stop spinning , after another 2 to 3 seconds it powers up the server again..
we have some spare R630 laying around.. so we tested the cpus on the other servers, we have tested the psu, the PCI-e nics.. and all working fine.. now starting to wonder if could be corrupted BIOS.. or some hardware issue on the motherboard preventing if from booting completely?
and no VGA of course because server does not boot at all.. black screen.. no BIOS menu..
(edited)
DELL-Young E
Moderator
•
5.4K Posts
•
37 Points
0
January 14th, 2025 11:04
Hello, I Believe what DELL-Chris H posted stands correct: I'd do minimum to post and go from there.
If it does not post with that config, need to source all parts required for min to post and get theme replaced.
And from your writing I think you may have already figured it out- The answer is simple: if you tested all parts on other servers you need to replace what is not tested and starting point will be the motherboard.
Respectfully,