How to Fix DELL PowerEdge Memory/battery issues were
identified Error? On
the off chance that you are dealing with a DELL PowerEdge server, you might've
seen the accompanying mistake message on the support during framework startup.
This will occur during
the PERC RAID Controller check.
For the most part, when
you press any key and proceed with the startup procedure, your framework will
boot-up and keep on working.
PERC Controller Battery
On the off chance that
the issue simply happens to be with PERC battery, at that point when the framework is running, it will attempt to charge the PERC battery. On the of the chance that it succeeds, next time when you reboot the machine, you most likely
probably won't see that blunder message once more.
In the event that this
is an old DELL Power Edge server, you may confront this issue. Or on the other
hand, if the framework was down for some time, and in the event that you are
attempting to begin it, the PERC controller battery might've lost its charge,
and you may see that blunder message.
For that, a situation
the PERC battery will energize when the framework is fully operational.
Be that as it may, at
times, the PERC battery itself may be dead. In this way, you may need to
supplant it with another battery.
Filesystem Error on
Console
On the off chance that
it's anything but a PERC controller battery related issues, at that point you
may see some other unusual issues.
Here and there on the off chance that you've disregarded the "Memory/battery issues were
distinguished" message and kept on beginning the framework, it may
boot-up.
Be that as it may, on
the off chance that you are running Linux on this DELL server when it is ready
for action, here and there you may see the accompanying mistake message on the
reassure. "unfit to peruse inode square".
fsck Error on Console
When you see the above
blunder message, one of the prompts the response is that something isn't right
with the filesystem.
In the event that it is
non-root filesystem, you can play out an fsck and see what occurs.
For this situation, to
perform it on the root filesystem, we ought to go to single client mode from
grub as demonstrated as follows.
Auto fsck during Reboot
When you keep on
rebooting the framework, it will complete a programmed fsck on the filesystem
as demonstrated as follows.
Here, wherever it
prompts for "Fix?", feel free to state "yes".
Be that as it may, this
still says "Filesystem still has blunders"
Respawning too quick
Error
When you keep on
rebooting the machine, after the auto-fsck, you may see the accompanying
mistake message, where it is unfit to execute mingetty.
Change PERC Controller
Memory
Presently, on the off the chance that you reboot the machine once more, despite everything, you'll get
the accompanying mistake message on the screen during the PERC controller
check.
At this stage, you've
changed the PERC battery, and you realize it isn't the battery issue.
In any case, in the event that you keep on rebooting by disregarding the message, you may, in any
case, be getting a wide range of unusual blunders identified with the file the system has appeared.
In this way, at this
stage, it is fundamental that you don't disregard the above memory/battery
issue and proceed with any further.
Change your PERC
controller memory, and reboot the machine.
Much of the time, this
ought to take care of the issue, and you shouldn't see the "Memory/battery
issues were recognized" blunder message.
This ought to likewise
quit giving each one of those peculiar file system related to blunder messages.
In this model situation, we got each one of those blunder messages on
Hope this the article
has helped you in solving the issue of Dell Computer contact Dell Customer Service toll-free number
which is available at your service 24*7 +1-855-729-6682
Comments
Post a Comment