redid the boot loader on 126 and 129. I had a couple of machines earlier in the semester that it happened to, and at the time I considered the possibility that they had gotten corrupted because the bios wasn't locked down. It is now though, so it is either the hardware or the OS corrupting it.
used sysrescue to boot into the os and then manually ran grub2-install, running it through yast does not work.
10/10
121 and 122 also were corrupted, and I need to reset pam.d after fixing grub2
1/22
128 was corrupted and repaired
Wednesday, October 09, 2013
Subscribe to:
Posts (Atom)