*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803
It turned out to a kind of mystery. No files are left open for writing but device is busy and can not be cleanly remounted readonly. Moreover it is not clear how to reproduce the issue. Concerning the formalities, since the issue addressed in the last comments have nothing with bug lp: #1124803 "NetworkManager doesn't respond to SIGTERM in daemon mode", the link to that bug might be removed. On the other hand original description of this bug fitted quite well to bug lp: #1124803 and it has nothing common with removing of network-manager, plymouth, etc. In my opinion the case with no bunch of packages should be filed as a dedicated bug with clear statements concerning conditions and ruled out hypotheses. Alexander, actually I can not figure out which way debug scripts can block umount, but since they provide no useful info, it is interesting what would happen if you completely remove debug scripts and temporally set HALT=halt in /etc/default/halt to have time to inspect last messages without writing them to a file. Have you tried memtest on that box? Have you experienced kernel panic or Oops due to kernel modules or hangs due to e.g. graphics card driver? Concerning the bug lp: #1124803, there are tails of modem-manager and so network-manager again. I can not comment on plymouth hangs since removing of "quiet" and "splash" from GRUB_CMDLINE_LINUX_DEFAULT works like a charm for me. (Actually I have tried an upstart task with "/bin/plymouth hide-splash" command before.) To obtain more debug info I would suggest to run sudo initctl log-priority info before shutdown (perhaps 'sudo sysctl kernel.printk="7 4 1 7"' to see the messages on the screen as well) and add dmesg > /upstart-messages.log to /etc/init.d/umountroot There is an issue with network manager proliferated to plenty of bugs, but it can be easily fixed. The problem with busy / when no processes are left and no files are open is very strange. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 Status in Upstart: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Triaged Status in “upstart” package in Ubuntu: Confirmed Bug description: 1. Format and label a target Ext4 partion using Ubuntu 12.04 2. Install 64bit 12.10 OS using that target without reformatting it 3. Shut down 4. Boot an alternate copy of Ubuntu 5. Restart selecting the newly installed OS 6. Login then shutdown 6. Boot an alternate copy of Ubuntu 7.Fsck the newly installed OS allowing corrections to be made Each time the the newly installed OS is executed and then shutdown, even if execution only consists of logging on, a subsequent fsck will FAIL. I used Acronis True Image Home 2013 to create an image of the newly installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4 filesystem corruption 100% of the time by restoring from the image, booting, logging on and shutting down. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: aguru 1871 F.... pulseaudio /dev/snd/controlC0: aguru 1871 F.... pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 22:24:54 2012 HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lo no wireless extensions. MachineType: System manufacturer P5Q-E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware 1.95 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp