Re: Latest update borks

[hvw59601 <hvw59601@care2.com>]

hvw59601 wrote:
> Frank McCormick wrote:
> > On 05/03/12 08:58 AM, Claudius Hubig wrote:
> > > Hello Frank,
> > >
> > > Frank McCormick<debianlist@videotron.ca>  wrote:
> > > > sid:/home/frank# aptitude full-upgrade
> > > > The following packages will be upgraded:
> > > >     gir1.2-javascriptcoregtk-3.0 gir1.2-webkit-3.0
> > > > libjavascriptcoregtk-1.0-0
> > > >     libjavascriptcoregtk-3.0-0 libwebkitgtk-1.0-0 
> > > > libwebkitgtk-1.0-common
> > > > libwebkitgtk-3.0-0
> > > >     libwebkitgtk-3.0-common linux-libc-dev linux-tools-3.2 ntfs-3g
> > > > xserver-common xserver-xephyr
> > > >     xserver-xorg-core
> > >
> > > The only thing remotely related to this is linux-tools-3.2. Maybe
> > > this package then tries to build the initrd for the 2.6.38 kernel and
> > > fails for some reason? On the other hand, this appears rather
> > > unlikely, as it claims to only contain a ‘perf’ tool for performance
> > > analysis…
> >
> >
> >
> >   Looking through the packages that were updated, it **appears** as 
> > though the culprit is ntfs-3g. It's the one that calls the update of 
> > initrd.img .
> >
> >
> >
> > > It looks a little bit as if there was not enough space on /var/tmp,
> > > but I am not sure…
> > >
> > > What do
> > >
> > > # df -hP
> > >
> > > and
> > >
> > > # df -hPi
> > >
> > > say?
> >
> > Looks like there's enough room.
> >
> > sid:/boot# df -hP
> > Filesystem                                              Size  Used 
> > Avail Use% Mounted on
> > rootfs                                                   14G  6.4G  
> > 6.5G  50% /
> > udev                                                    492M     0  
> > 492M   0% /dev
> > tmpfs                                                   100M  344K  
> > 100M   1% /run
> > /dev/disk/by-uuid/e27e5d70-6d89-407c-a7c0-078ae4a0e704   14G  6.4G  
> > 6.5G  50% /
> > tmpfs                                                   5.0M     0  
> > 5.0M   0% /run/lock
> > tmpfs                                                   199M   96K  
> > 199M   1% /tmp
> > tmpfs                                                   199M  248K  
> > 199M   1% /run/shm
> > /dev/sda3                                                14G  6.1G  
> > 6.8G  48% /media/sda3
> > /dev/sdb1                                               3.8G  2.0G  
> > 1.9G  52% /media/FlashDrive
> > /dev/sda5                                               216G  4.3G  
> > 201G   3% /media/sda5
> > sid:/boot#
> >
> >
> > > Does the initrd get generated at all? (# ls -la /boot)
> >
> >
> >   Well, it's there, but I am unsure whether it's a valid file because 
> > of the FATAL warnings when it was generated.
>
> I got that too:
>
> ...
> update-initramfs: Generating /boot/initrd.img-3.2.0-1-amd64
> FATAL: Module xhci not found.
> FATAL: Module ext4dev not found.
> FATAL: Module zfcp not found.
> FATAL: Module pata_hpt366 not found.
> FATAL: Module pata_hpt37x not found.
> FATAL: Module pata_ninja32 not found.
> FATAL: Module dasd_diag_mod not found.
> FATAL: Module dasd_eckd_mod not found.
> FATAL: Module dasd_fba_mod not found.
> WARNING: could not open 
> /var/tmp/mkinitramfs_lup5qo/lib/modules/3.2.0-1-amd64/modules.builtin: 
> No such file or directory
> ...
>
> But it appears to have no effect on reboot. AFAICT.
> But what's worse, it deleted konsole because the dependent kdepart 
> package does not exist...
Sorry, that's 'katepart' :-(