"Unable to migrate to dependency-based boot system..."
in [Setup]
|
From: Ant on 1 Mar 2010 07:33 Hello. I just ran apt-get update and apt-get upgrade on my very old Debian box (from 9/24/2004; Kernel v2.6.30-2-686 #1 SMP Fri Dec 4 00:53:20 UTC 2009 i686 GNU/Linux) and ran into this: # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: akregator amor ark blinken dpkg gcj-jre-headless gij indi juk k3b k3b-data kaddressbook kalarm kalzium kalzium-data kamera kanagram kappfinder kate katomic kbattleship kblackbox kbounce kbruch kcalc kcharselect kcron kdeaccessibility kdeadmin kdeartwork kdeartwork-style kdebase kdebase-bin kdebase-data kdeedu kdegames kdegraphics kdelirc kdemultimedia kdemultimedia-kio-plugins kdenetwork kdepasswd kdepim kdepim-kresources kdepim-wizards kdessh kdetoys kdeutils kdewebdev kdf kfilereplace kfind kfloppy kgamma kgeography kgeography-data kget kgoldrunner kgpg khangman kig kimagemapeditor kiten kjots kjumpingcube kleopatra klettres klettres-data klines klinkstatus klipper kmag kmahjongg kmail kmines kmix kmousetool kmouth kmplot knetwalk knetworkconf knode knotes kolf kommander konq-plugins konqueror konqueror-nsplugins konquest konsole konsolekalendar kontact kopete korganizer kpackage kpat kpilot kppp krdc kreversi krfb kruler ksame kscd kscreensaver kshisen ksnapshot kspaceduel kstars kstars-data ksysguard ksysguardd kteatime ktimer ktouch ktron kttsd ktuberling kturtle ktux kuser kwalletmanager kweather kwordquiz kxsldbg linux-image-2.6-686 lskat ┌──────────────────────────────────Configuring sysv-rc────────────────────────────────────┐─ │ Unable to migrate to dependency-based boot system │ │ │ │ Tests have determined that problems in the boot system exist which prevent migration │ │ to dependency-based boot sequencing: │ │ │ │ package wifi-radar left obsolete init.d script behind, package and removed but not │ │ purged, package apache2.2-common removed but not purged, package at removed but not │ │ purged, package console-common removed but not purged, package console-tools removed │ │ but not purged, package cpufreqd removed but not purged, package libdevmapper1.02 � Package configuration ┌──────────────────────────────────Configuring sysv-rc────────────────────────────────────┐─ │ Unable to migrate to dependency-based boot system │ │ │ │ Tests have determined that problems in the boot system exist which prevent migration │ │ to dependency-based boot sequencing: │ │ │ │ package wifi-radar left obsolete init.d script behind, package and removed but not │ │ purged, package apache2.2-common removed but not purged, package at removed but not │ │ purged, package console-common removed but not purged, package console-tools removed │ │ but not purged, package cpufreqd removed but not purged, package libdevmapper1.02 │ │ removed but not purged, package nfs-common removed but not purged, package │ │ openbsd-inetd removed but not purged, package pcscd removed but not purged, package │ │ policykit removed but not purged, package portmap removed but not purged, package │ │ powernowd removed but not purged, package virtualbox-2.0 removed but not purged, │ │ package wifi-radar removed but not purged, package yum removed but not purged, │ │ package zope2.10 removed but not purged, package zope2.9 removed but not purged, │ │ package zope3 removed but not purged, insserv: warning: script 'K20ntop' missing LSB │ │ tags and overrides, insserv: warning: script 'S25libdevmapper1.02' missing LSB tags │ │ and overrides, insserv: warning: script 'ntop' missing LSB tags and overrides, │ │ insserv: script zope2.10: service zope2.9 already provided!, insserv: warning: │ │ script 'libdevmapper1.02' missing LSB tags and overrides, │ │ │ │ If the reported problem is a local modification, it needs to be fixed manually. If │ │ it's a bug in the package, it should be reported to the BTS and fixed in the │ │ package. See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for more │ │ information about how to fix the problems preventing migration. │ │ │ │ To reattempt the migration process a< EXIT > │ └─────────────────────────────────────────────────────────────────────────────────────────┘ My formattings and texts seems to be cropped off due to old SecureCRT v3.4.8's SSH2 terminal program. I looked at http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot and was confused on if I need to deal with this or not. So I continued to see what happens: Package configuration ─────────────────────────────────────────────────────────────────────────────────────────── ┌────────────────────────────────Configuring libpam0g───────────────────────────────────┐ │ Most services that use PAM need to be restarted to use modules built for this new │ │ version of libpam. Please review the following space-separated list of init.d │ │ scripts for services to be restarted< OK > │ └───────────────────────────────────────────────────────────────────────────────────────┘ │ ┌───────────────────────────────────────────────────────────────────────────────────┐ │ │ │vsftpd samba gdm exim4 cups cron │ │ �─└───────────────────────────────────────────────────────────────────────────────────┘─┤ │ Restarting services possibly affected by the upgrade: vsftpd: stopping...starting...done. samba: stopping...starting...done. gdm: reloading...done. exim4: stopping...starting...done. cups: stopping...starting...done. cron: stopping...starting...done. Services restarted successfully. (Reading database ... 158112 files and directories currently installed.) Preparing to replace python-dbus 0.83.0-1+b1 (using ..../python-dbus_0.83.1-1_i386.deb) ... Unpacking replacement python-dbus ... Processing triggers for python-support ... Setting up python-dbus (0.83.1-1) ... Processing triggers for python-support ... localepurge: Disk space freed in /usr/share/locale: 596 KiB localepurge: Disk space freed in /usr/share/man: 0 KiB localepurge: Disk space freed in /usr/share/gnome/help: 0 KiB localepurge: Disk space freed in /usr/share/omf: 0 KiB localepurge: Disk space freed in /usr/share/doc/kde/HTML: 0 KiB Total disk space freed by localepurge: 596 KiB I checked some of those restarted services (gpm, vsftpd, and Smaba), and they seemed fine. I looked at http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot to find out more details about my migration issue and tried a command with a package as an example: # dpkg-query -W -f='${Conffiles}\n' apache2.2-common /etc/logrotate.d/apache2 82c68e66df6fc09029813440bf8988dc /etc/apache2/conf.d/security 5368b38550a2dfcff71b292f81dc31f3 /etc/apache2/conf.d/localized-error-pages 563909621007197d4f0480e3460ef818 /etc/apache2/conf.d/charset e6fbb8adf631932851d6cc522c1e48d7 /etc/apache2/envvars f0bc087e1c57fd0ac8606f8d9739eea6 /etc/apache2/magic a6d370833a02f53db6a0a30800704994 /etc/apache2/sites-available/default-ssl 9ab3b2fdb39675bfab20552f37f0efba /etc/apache2/sites-available/default b9d4b0be5f66e4507cf9ada37acd9ef2 /etc/apache2/ports.conf 0ff791f4df9b71e024c658c7d07a5f31 /etc/apache2/mods-available/speling.load 095570b0cb18ebdfc357a2241c6932ea /etc/apache2/mods-available/autoindex.conf 77ea294b47d8d2e4dc68107907da8311 /etc/apache2/mods-available/include.load 427760ab8396c2a3af8dfa25ed62c92c /etc/apache2/mods-available/authn_dbm.load 4e37546871dbcba8550a0d781f6fbfa8 /etc/apache2/mods-available/log_forensic.load 7177e2427eb7c78f1ab10c034a809793 /etc/apache2/mods-available/cgid.load c3ee2eac02c248b5a39fb1a7afee4cb9 /etc/apache2/mods-available/proxy.load 3d3719c88d01152e817f74fc2fd6ce9e /etc/apache2/mods-available/status.conf 2db2247ae37ae1e2bf9bf35413c14ab7 /etc/apache2/mods-available/actions.conf e496c26d829f0186e46a87eace8a42f6 /etc/apache2/mods-available/disk_cache.conf fe06d97d8cb000ef4b60ba2a7cff92e9 /etc/apache2/mods-available/info.load c1faffe40b8bed9f2b817b9dc0503bb6 /etc/apache2/mods-available/dbd.load f03fe275174a5ed97b0f5f5726ccea60 /etc/apache2/mods-available/authn_default.load a54d861749157cc576744d50d8d2d773 /etc/apache2/mods-available/authnz_ldap.load d65845f053d08b82da239c73c9094c35 /etc/apache2/mods-available/rewrite.load 55e18fb7df64c8f390904b972637c17d /etc/apache2/mods-available/proxy_scgi.load cb11d685e60db26bbdad456263bf63b7 /etc/apache2/mods-available/userdir.load c034025405561ea48fbcb67fd1998f4d /etc/apache2/mods-available/usertrack.load 8400042dd4374fad5eedf33ffb3c68f0 /etc/apache2/mods-available/cgi.load 32a1c48f0e29feb415c9460378728d82 /etc/apache2/mods-available/alias.conf c0579b22a661c4e37bb019a97eadb0a8 /etc/apache2/mods-available/proxy_ajp.load e058e03c1d4f9e4d8e2c439ed75cc501 /etc/apache2/mods-available/ident.load 51ba623a8a2bd71c512f847d02e0934f /etc/apache2/mods-available/dav_fs.load 17f662fd023dbaaab9d89f9a11ae58c1 /etc/apache2/mods-available/ldap.load 735ac5f246738e11a53f6c515b8dfc48 /etc/apache2/mods-available/mime.conf 324e56ffc681fc38d663ebc1105652c5 /etc/apache2/mods-available/filter.load 8df0170e37a8925238860657d6c60fe5 /etc/apache2/mods-available/mime_magic.conf 0174ea31061cbf1d73e48c89f30b802e /etc/apache2/mods-available/unique_id.load 6c13959015fb35276572070b44e63380 /etc/apache2/mods-available/autoindex.load b9f9d364f1b4c96c45b6db353180aa15 /etc/apache2/mods-available/authz_user.load 69150f8246499e0135580d8cc16eaeab /etc/apache2/mods-available/info.conf 8a36e9a5542c8e24df6170052a31b62b /etc/apache2/mods-available/authz_default.load 26209bfbb5e230e3b33bbe10febae72d /etc/apache2/mods-available/setenvif.conf 90bff5e63e61b18dc77aad8bfd9d13c1 /etc/apache2/mods-available/authn_file.load ecdeeab8cfec4a9dd0c065a4d6948c31 /etc/apache2/mods-available/mem_cache.load 282139ee986076295f97a67987e2554b /etc/apache2/mods-available/mem_cache.conf 9f18d50ca7613b9c694de9ef4545d6c5 /etc/apache2/mods-available/disk_cache.load 4a523a67fa6f1b4f5966a4d583f8f433 /etc/apache2/mods-available/version.load 3d76c5c51100f9c28ae1a66b56e01764 /etc/apache2/mods-available/deflate.load ac4540dd672556b07f900425751f745c /etc/apache2/mods-available/dav.load ed469867552a1145b8c3ffa5780ff83e /etc/apache2/mods-available/deflate.conf 8c13524d3a4955810e6434ff388c3168 /etc/apache2/mods-available/proxy_connect.load 6bc4b5de977f70a0b6ae98ab04383c0c /etc/apache2/mods-available/cern_meta.load 2c2d9adcb273f934304e7dfb5775f7b9 /etc/apache2/mods-available/dir.conf b6882491a6d2b823da960f19a50b132f /etc/apache2/mods-available/actions.load 95dcfd2efdd41666de5f31dd72e01e41 /etc/apache2/mods-available/authz_owner.load 9ed1ea15654bb594453438154b642539 /etc/apache2/mods-available/dump_io.load 8231c51ef692e0766625ece087484fe4 /etc/apache2/mods-available/setenvif.load 6f670fad5b6f6b14fa72c9cd3058469b /etc/apache2/mods-available/file_cache.load f097659127628ec6f9c6a558d0baf566 It looks like I have tons of packages to fix/repair. Do I need to worry about this issue? Thank you in advance. :) -- At length, when they came to a (lowly) valley of ants, one of the ants said: "O ye ants, get into your habitations, lest Solomon and his hosts crush you (under foot) without knowing it." --Surah 27. The Ant, The Ants, line 18 /\___/\ / /\ /\ \ Phil./Ant @ http://antfarm.ma.cx (Personal Web Site) | |o o| | Ant's Quality Foraged Links: http://aqfl.net \ _ / Nuke ANT from e-mail address: philpi(a)earthlink.netANT ( ) or ANTant(a)zimage.com Ant is currently not listening to any songs on his home computer.
From: J G Miller on 1 Mar 2010 08:03 On Mon, 01 Mar 2010 04:33:13 -0800, Ant wrote: > The following packages have been kept back: apt-get does not automagically upgrade these because the upgrade also either a) pulls in other packages which have not previously been installed or b) replaces installed packages of type A with new packages of type B If you do an explicit apt-get install akregator for example, it will then commence the operation and show you all of the changes necessary. If you did the upgrade via dselect, as far as I recall, it would just summarize all the changes, ask you if you were sure, and then go ahead. > Tests have determined that problems in the boot system exist which > prevent migration This means that something is out of synchronization in the boot system -- I seem to recall you were trying to update the kernel but were failing because of problems of disk space. Did you resolve that issue? > It looks like I have tons of packages to fix/repair. Yes because you have not bothered to keep your system up to date. > Do I need to worry about this issue? Yes you should be extremely worried and be prepared to lose a lot of sleep at night. Of course, it is probably an awful lot easier if you were just to wipe++ the system and do a fresh install. ++ AFTER backing up all your configuration and personal and customization files from /etc, /var, /home etc as necessary of course.
From: ANTant on 1 Mar 2010 20:11 >> Tests have determined that problems in the boot system exist which >> prevent migration > > This means that something is out of synchronization in the > boot system -- I seem to recall you were trying to update > the kernel but were failing because of problems of disk space. > > Did you resolve that issue? Not yet. >> It looks like I have tons of packages to fix/repair. > > Yes because you have not bothered to keep your system up to date. Ah. I was trying to avoid upgrading my KDE v3.5.10 to v4. Is that the cause of this problem? >> Do I need to worry about this issue? > > Yes you should be extremely worried and be prepared to > lose a lot of sleep at night. > > Of course, it is probably an awful lot easier if you > were just to wipe++ the system and do a fresh install. Yeah, I might have to do that since I messed up with the partitions hence the low disk space with / and /boot. :( -- "We are anthill men upon an anthill world." --Ray Bradbury /\___/\ / /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site) | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / Please remove ANT if replying by e-mail. ( )
From: J G Miller on 1 Mar 2010 21:03 On Mon, 01 Mar 2010 19:11:50 -0600, ANTant wrote: > Not yet. That is probably the cause of the problem of "unable to migrate to dependency-based boot system". > I was trying to avoid upgrading my KDE v3.5.10 to v4. Is that the > cause of this problem? No. The current stable version of Debian is still KDE 3.5 and not KDE 4.0. > Yeah, I might have to do that since I messed up with the partitions > hence the low disk space with / and /boot. Well it is entirely up to you -- if you want to put in the effort, it should be possible to overcome the difficulties, but it all depends on how much customization you have done. Otherwise it will be quicker and a lot less painful to do a fresh install on a better partitioned (as in appropriate sizes) system. With regard to the error message though, have you had a look at <http://forums.debian.NET/viewtopic.php?f=5&t=45626> and do you have any of your own init.d scripts added to the system? And have you read the information about what the Debian "dependency based boot system" is at <http://wiki.debian.ORG/LSBInitScripts/DependencyBasedBoot>
From: philo on 1 Mar 2010 21:19
ANTant(a)zimage.com wrote: >>> Tests have determined that problems in the boot system exist which >>> prevent migration >> This means that something is out of synchronization in the >> boot system -- I seem to recall you were trying to update >> the kernel but were failing because of problems of disk space. >> >> Did you resolve that issue? > > Not yet. > > >>> It looks like I have tons of packages to fix/repair. >> Yes because you have not bothered to keep your system up to date. > > Ah. I was trying to avoid upgrading my KDE v3.5.10 to v4. Is that the > cause of this problem? > > >>> Do I need to worry about this issue? >> Yes you should be extremely worried and be prepared to >> lose a lot of sleep at night. >> >> Of course, it is probably an awful lot easier if you >> were just to wipe++ the system and do a fresh install. > > Yeah, I might have to do that since I messed up with the partitions > hence the low disk space with / and /boot. :( In the time you've been fooling with your system you could have easily backed up your data and have done a clean install... and started out with a rational partitioning scheme quit trying to beat a dead horse |