Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] Server won't boot kernel. initramfs problem?



My understanding is that ECC RAM merely makes a server crash on a memory
error, not detect the error and alert the sysadmin. Is that not the case?

And no, I'm not looking to implement this in the near future, I just prefer
automating routine sysadmin chores and relying on Nagios for routine system
health monitoring, and memtest86 is a useful tool that I'm unable to
automate.

It's hard to justify taking down a production server to run memtest86 just
for the sake of running it, so running it manually on a production server
will never be routine.



On Sun, Feb 24, 2013 at 7:19 PM, Rich Pieri <richard.pieri at gmail.com> wrote:

> On Sun, 24 Feb 2013 19:13:21 -0500
> John Abreau <abreauj at gmail.com> wrote:
>
> > I wonder if it could be automated? Perhaps a weekly or monthly cron
> > job that temporarily sets grub to default to the memtest config, then
> > reboots, runs the memtest and logs the results, and finally sets grub
> > back to its previous config?
>
> If you are seriously considering this then you should be using ECC RAM.
>
> --
> Rich P.
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>



-- 
John Abreau / Executive Director, Boston Linux & Unix
PGP KeyID: 32A492D8 / Email: abreauj at gmail.com
PGP FP: 7834 AEC2 EFA3 565C A4B6  9BA4 0ACB AD85 32A4 92D8



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org