Gin and Tonic
When combined, Gin and tonic makes a highball cocktail where right now I think I could use a stiff one. I never resort to numbness but it’s been too long a day to find that your Linux server crashed and doesn’t reboot and fsck fails.
For some reason the x-server died when starting up Evolution. I had to kill the email client twice and eventually reboot the server. The reboot hung will one of the CPUs “got stuck” so the power had to be yanked.
The last time the server rebooted was about 4 months ago when we had a power failure at three in the morning and the time between reboots triggered a forced fsck.
I sorta hold my breath when I reboot servers or even my workstation. You never know when it the computer may not come up clean so I just leave them running 24/7. But this time, the server did not come up clean.
When fsck fails in the bootup script you simply run fsck on the device in question, or /dev/sda1 and the problem goes away after the scan finishes and corrects the errors.
Somehow fsck kept failing over and over which brings me to the title of this post “Gin and Tonic.”
At work we have two servers “gin” and of course “tonic”. Tonic’s been a very reliable server but for some reason we have to reboot it several times a week. In our geekiness, gin was the next server we added to support software development.
But all I could think after all these reboots of my dedicated server was poor old tonic and it’s root problem which has yet been located. I digress.
After a few more reboots and a fsck on “/” instead of /dev/sda1 seemed to resolve the problem. Who knows. I just hope my server doesn’t become a Gin and Tonic problem.

Just fooling around with 




