I tried to install the 184.108.40.206 kernel (as suggested for security reasons) twice, and each time, I got a BIG mess up of the installation.
Here is the story (I’ll try to keep it short):
The installation of the kernel was not a problem, it went fine both time (I just had to reorganize Grub entries a bit). At first, all was running normal.
Suddenly, after having left the computer idle for a moment, I was faced with a black screen (blanker probably) and I could not wake up the system: no mouse, no keyboard, all seemed to be frozen and I had to press the reset button.
After the reboot, and as soon as the desktop was loaded, I got an error message saying that /var has 0 bytes left !
The nightmare began…
The first time that happened, I tried to find what was wrong in /var and /var/log , but found nothing abnormal. The info given by the Diskinfo tool were strange, sometimes showing /var as 100% full, sometimes it was /home that was 100% full and some other times it was /.
I tried to fall back to kernel 220.127.116.11 using Yast, but it failed at the middle of the process.
At this point I realized that the system was very unstable.
I then booted the Install HD and run the repair mode. Some errors were found and corrected, but in the end, the system was not repaired; and worst, Grub lost all entries except the floppy one. (Hopefully, I knew how to boot the Install HD from Grub’s command line).
I tweaked again and again, and finally got my system up again with kernel 18.104.22.168 (don’t remind all the steps).
Recently, as the kernel update was still suggested, as there were other updates in the meantime (like mkinitrd), and as haven read anyone else complaining about 22.214.171.124, I decided to give a try again.
And again, a couple of days later, same symptoms: black frozen screen, no space left in /var.
As I knew the system was unstable, I immediately booted the Install HD. Tried the repair mode and it failed (just mess Grub again). Tried to (update) install kernel 126.96.36.199 from there and it also failed.
I then started the rescue mode and tried to delete some big files in /var (again I did not found any monstrous thing in there), then tried again the repair and update process with no better results.
From rescue mode, I finally deleted everything in /var (that was not a good idea as I also deleted some NEEDED files)…
Got the system to boot, but only to the text login: nscd failed because of missing files in /var, starx failed because no X server found, …
Fed up, I lastly decided to “update” all system base RPM, the Gnome and KDE desktop environment from the 11.2 install HD, then update everything again with Yast Online Update. This took HOURS !
My 11.2 installation is now up again.
How can I, from command line, find the biggest files nested somewhere in /var ? (Is it possible that the kernel is writing a log that cannot be seen ?)
From Yast Online Update, I have now two packages waiting: the kernel (188.8.131.52) which I have banned, and gnome_2_28_2 which fail to install (the progress only show “Suppressing libsoup-2_4-1”)
From Yast Install/suppress Software, when I select the installed libsoup, I immediately receive the following error:
y2base: /usr/include/boost/smart_ptr/intrusive_ptr.hpp :149 : T* boost::intrusive_ptr<T>::operator->() const [with T = const zypp::target::rpm::RpmHeader]: L’assertion « px != 0 » a échoué.
YaST got signal 6 at YCP file PackagesUI.ycp:280
/sbin/yast2: line 454: 23597 Abandon $ybindir/y2base $module “$@” “$SELECTED_GUI” $Y2_GEOMETRY $Y2UI_ARGS
Any idea how to solve this ?