Posts

Showing posts from April, 2009

Upgrade from kubuntu 8.10 to 9.04 with raid disk : no block devices found

Image
Well... I could have waited 15 more days to have the stable version of Ubuntu 9.04 available for upgrade... but no... It seems I wasn't aware i've so much time to loose. So I've upgraded my kubuntu 8.10 (64bit) to the 9.04 version. All went smoothly until I reboot where I get this nice message : no block devices found (4 times) Gave up waiting for root device. ALERT! /dev/md3 does not exist. dropping to a shell! Apparently the raid configuration has been dropped during the upgrade. I've filled a bug here : https://bugs.launchpad.net/ubuntu/+bug/358054 I don't know exactly what in my setup causes this, but it seems that it's a bug of the last kernel. Probably my raid setup. My computer is made of : P5N32-E Sli plus motherboard C2D 6250 4GB of RAM 2x 250GB SATA, RAID1 software for linux (sdc, sdd) 2x150GB Raptor SATA Raid0 for windows (fake raid from motherboard) (sda, sdb) To get my system back on line I just need to do this in the busybox shell : mdadm -As exit...

Send mail through gmail smtp server with Exim4 - What to do when gmail account has been disabled

Image
To send mail from a machine using gmail smtp server see this tutorial : http://www.manu-j.com/blog/wordpress-exim4-ubuntu-gmail-smtp/75/ I've just ran into a problem with this config. I've created a gmail account just for this purpose because you need to set the gmail account password in exim4 configuration file on each machine. I didn't want to use my personnal gmail account for obvious reasons. As it's a technical account, I never log into it through http://gmail.com web interface. Which lead to the account beeing disabled by gmail. As a result, all mail that exim4 tryed to send gives this warning message in /var/log/exim4/mainlog : R=send_via_gmail T=gmail_smtp defer (-53): retry time not reached for any host To solve this issue, you need to Login to http://gmail.com with the account you use with exim4. It will ask you to login a second time with a captcha... do so login on all of your machine that use this technique and issue the following command : sudo exim -qff ...