1) Problem appears on different hardware. I mean totally different (except for my usb hdd, from which the system boots). 2) I run memtest about a year ago... But I don't see any oops-es, hangs or kernel panics. So the problem is not related with (broken) hardware. 3) How I've removed plymouth? I read about plymouth in comments to #556372. People suggest to install plymouth-dummy package (which has no mountall dependency) so after that plymouth can be easily removed. I have neither plymouth nor network-manager nor modemmanager nor wicd installed. Just plain /etc/network/inerfaces. +guessnet. 4) I'm bringing network interface up manually from /etc/rc.local. Because 'ifup -a' called from init-scrips doesn't work correctly (bug). 5) The harder I'm trying to debug this bug, the less it appears (he knows that I'm hunting on him! haha). 6) I can speak russian, если что. 7) currently I can't set HALT=halt in /etc/default/halt. Because most of the time shutdown is scheduled and done automatically (and I can be far away from computer at that moment). But I'll do that soon. 8) Problem doesn't appear 100% of the time (at least for me). And also not related with any of my debug scripts. 9) Both root and swap partitions are on my usb harddrive. So, maybe it's somehow related to usb? Or swap? I don't know is it important... but root and swap are mounted from fstab by label: LABEL=root / ext4 errors=remount-ro 0 1 LABEL=swap none swap sw 0 0 10) I'm also using autofs daemon. Maybe it's somehow related to it? 11) Now I've removed all my debug parts from umountroot. And added two scripts:
/etc/rc0.d/S59-before-umountroot: #!/bin/bash /sbin/sysctl kernel.printk="7 4 1 7" /bin/dmesg > /upstart-messages-1-before-ro-`date +%s`.log /etc/rc0.d/S75-before-halt: #!/bin/bash /bin/dmesg > /upstart-messages-2-after-ro-`date +%s`.log (also added symlinks to rc6.d) But, I've got nothing interesting: ... [22482.298335] init: smbd main process (1057) killed by TERM signal [22482.299101] init: tty4 main process (1246) killed by TERM signal [22482.299659] init: tty5 main process (1255) killed by TERM signal [22482.300259] init: tty2 main process (1293) killed by TERM signal [22482.304610] init: tty3 main process (1294) killed by TERM signal [22482.305310] init: tty6 main process (1299) killed by TERM signal [22482.315235] init: irqbalance main process (1327) killed by TERM signal [22482.315828] init: cron main process (1339) killed by TERM signal [22482.318599] init: tty1 main process (2165) killed by TERM signal [22484.047088] init: Disconnected from system bus [22484.190023] tg3 0000:10:00.0: wake-up capability enabled by ACPI Both logs are the same. 12) cat /proc/cmdline root=LABEL=root ro ipv6.disable=1 -- 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
