about img
blogger img

Corys posts image

buchos posts img

UnderPaidLoveMonkis posts img

scotts posts image


My Ubuntu Gutsy borked!

UnderpaidLoveMonki @ 11:01 pm February 12th, 2008

Over the weekend, I wiped out my RAID 1 partition that was running off of the motherboard SATA Raid controller. This controller is also known as “Fake RAID.” Instead of using this, I configured a software RAID 1 using open source tools, notably mdadm.

Monday morning before work, I rebooted my box to check for good measures. Everything booted OK and the graphical login screen appeared normally. Then I proceeded to login, authenticated successfully, and then my desktop was all black. Against the black background was my gkrellm, configured to load after login, blinking like crazy in various colors of green, orange and yellow. Since my box is a dual core AMD, one of the cores was spinning at near 100% CPU usage and then CPU usage spinning alternated between the two cores. After watching this madness, I restarted the X server and the graphical login displayed normally. I logged in again and the same horror continues. I decided it’s time to reboot the box to observe what’s going on by clicking on the Options button on the bottom left hand side in the graphical login screen. Lo and behold, clicking that button redirects me to the login screen without popping up a menu for me to select “Reboot.” My Ubuntu Gutsy box is b0rked!

Pressing Ctrl-Alt-F2 brought me to the console and I logged in. I digged around the log files in /var/log and discovered there were many gnomegreeter crashing and other gnome related applications error messages. I’ve never encountered these problems before and I’ve used Ubuntu since it first debuted. Here’s what I found in the daemon.log and syslog:


Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Could not access configuration key
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Using compiled in value for
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Could not access configuration key
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Using compiled in value for
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Could not access configuration key
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Using compiled in value for
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Could not access configuration key
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Using compiled in value for
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Could not access configuration key
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Using compiled in value for
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Could not access configuration key
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Using compiled in value for
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Could not access configuration key
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Using compiled in value <> for
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Could not access configuration key
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Using compiled in value for
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Could not access configuration key
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Using compiled in value for
Feb 11 22:45:51 localhost gdmgreeter[9549]: CRITICAL: Could not access configuration key

More interesting logfiles in /var/crash:

root@localhost:/var/crash# ls -l
total 9592
-rw——- 1 bonehead bonehead 660103 2008-02-11 22:39 _usr_bin_gnome-panel.1000.crash
-rw——- 1 gdm gdm 1661031 2008-02-11 21:58 _usr_lib_gdm_gdmgreeter.108.crash

I was about to give up since it was a long day, typical of Mondays. Suddenly a lightbulb lit up. I decided to reinstall the gdm package:

$ sudo apt-get –reinstall install gdm

Viola! It worked! My b0rked Ubuntu box has been unb0rked! Hot damn, everything went back to situation normal. Oh well, what an adventurous Monday. Shit happens.

Leave a Reply

Subscribe without commenting