Public bug reported: Binary package hint: plymouth
2010 Apr 12 09:24:43 <al-maisan> A laptop of mine (running lucid) gets stuck after a post-boot file system check, I don't see any hard disk activity (the hard disk LED is not lighting up) and typing 'C' will not abort the fsck; I have to hold the power button to turn off the machine. 2010 Apr 12 09:24:59 <al-maisan> A part of the drive is encrypted FWIW 2010 Apr 12 09:25:05 <al-maisan> Is this a known issue? 2010 Apr 12 09:29:38 <mdke> how does one get the ability to accept bug nominations for particular releases? [..] 2010 Apr 12 09:34:47 <slangasek> al-maisan: have seen bug reports describing this, but they're as-yet-untriaged - can you try a few things for me? 2010 Apr 12 09:35:09 <al-maisan> slangasek: yes, of course. 2010 Apr 12 09:35:13 <pitti> tkamppeter: can he please say so in that bug? 2010 Apr 12 09:35:32 <slangasek> al-maisan: 1) are the dots under the logo still scrolling, or have they stopped? 2010 Apr 12 09:35:41 <slangasek> (tells us whether plymouth is still running) 2010 Apr 12 09:35:52 <pitti> tkamppeter: oh, there is a confirmation already 2010 Apr 12 09:36:09 <al-maisan> slangasek: I believe they have stopped. 2010 Apr 12 09:36:38 <slangasek> al-maisan: ok - Alt+F1 doesn't switch VTs? 2010 Apr 12 09:36:52 <al-maisan> slangasek: nope, I tried that. 2010 Apr 12 09:36:58 <slangasek> al-maisan: Alt+SysRq+K? 2010 Apr 12 09:37:08 <al-maisan> didn't try that 2010 Apr 12 09:37:23 <al-maisan> how can I mark a partition to be fsck'ed? 2010 Apr 12 09:37:43 <al-maisan> I'd like to do that and reboot in order to try Alt+SysRq+K [..] 2010 Apr 12 09:38:27 »» al-maisan looks for a 'SysRq' key on his keyboard 2010 Apr 12 09:39:13 <slangasek> al-maisan: you can set the mount count manually on the filesystem with tune2fs -C <device>; or to force a rootfs check, touch /forcefsck 2010 Apr 12 09:39:21 <slangasek> SysRq is the printscreen key 2010 Apr 12 09:39:31 <al-maisan> slangasek: right 2010 Apr 12 09:42:26 <mvo> al-maisan: probably not helpful for your use-case, but the recovery mode has a filesystemcheck option too 2010 Apr 12 09:42:55 <al-maisan> mvo: just did a "sudo tune2fs -l /dev/mapper/ul-h" 2010 Apr 12 09:42:59 <al-maisan> rebooting.. [..] 2010 Apr 12 10:03:48 <al-maisan> slangasek: after pressing Alt+SysRq+K I see a black screen for a second, there was an error message related to getpwuid or something similar bit I do not know whether it's pertinent to the fsck problem 2010 Apr 12 10:04:00 <nigelb> didrocks, ok. will get you a debdiff in a few :) 2010 Apr 12 10:04:07 <slangasek> al-maisan: do you have an external monitor plugged in? [..] 2010 Apr 12 10:04:31 <al-maisan> slangasek: sorry, I don't. 2010 Apr 12 10:05:06 <slangasek> al-maisan: darn, was hoping this was bug #533135 again - that would've made things simpler [..] 2010 Apr 12 10:05:37 <slangasek> al-maisan: ok, next question is whether it's reproducible when booting without 'splash' 2010 Apr 12 10:06:01 <al-maisan> slangasek: I will try that. [..] 2010 Apr 12 10:23:03 .:al-maisan:. slangasek: booting w/o splash makes no difference i.e. the file system is checked and the boot-strapping is stuck [..] 2010 Apr 12 10:23:54 <slangasek> al-maisan: excellent, that makes it much easier to debug ;-) Try booting without quiet, without splash, and with --verbose [..] 2010 Apr 12 10:24:24 .:al-maisan:. slangasek: will do. [..] 2010 Apr 12 10:30:32 .:al-maisan:. slangasek: hmm .. ok .. I have a console full of log statements, is there anything in particular you'd like to know? [..] 2010 Apr 12 10:31:19 .:al-maisan:. slangasek: btw, the last line reads: "plymouth-log state changed from pre-start to spawned" 2010 Apr 12 10:31:28 <slangasek> al-maisan: the last four or five lines are probably the place to start; maybe easier to take a photo? [..] 2010 Apr 12 10:31:47 .:al-maisan:. slangasek: let me do that .. just a minute 2010 Apr 12 10:31:52 <slangasek> al-maisan: ah, that job only runs once the 'filesystem' event is emitted 2010 Apr 12 10:31:57 .:slangasek:. so that tells us something [..] 2010 Apr 12 10:32:55 .:slangasek:. tsk, plymouth-log.conf calls a plymouth command not documented in plymouth --help [..] 2010 Apr 12 10:49:22 .:al-maisan:. slangasek: here's the screen shot: https://devpad.canonical.com/~muharem/IMG_4284.JPG [..] 2010 Apr 12 10:52:43 <slangasek> al-maisan: very odd; I don't see anything here that tells me why it stopped where it did [..] 2010 Apr 12 10:53:19 <slangasek> al-maisan: I guess it's most likely to be a bug in plymouth, then 2010 Apr 12 10:53:29 <slangasek> al-maisan: since plymouth is responsible for console redirection at boot time 2010 Apr 12 10:54:56 .:al-maisan:. slangasek: yeah .. I was scrolling up a bit and did not see any error message that would stand out either [..] 2010 Apr 12 11:00:44 .:al-maisan:. slangasek: so, after pressing Alt+SysRq+K I see one more error message, it reads: "General error mounting filesystems." 2010 Apr 12 11:01:12 .:al-maisan:. "A maintenance shell will now be started." 2010 Apr 12 11:02:01 .:al-maisan:. "Control-D will terminate this shell and reboot the system" [..] 2010 Apr 12 11:03:10 .:al-maisan:. slangasek: the boot continues and gdm comes up, after "sudo /etc/init.d/gdm stop" I can do Ctrl+Alt+F7 and the maintenance shell still seems to be there [..] 2010 Apr 12 11:12:15 <slangasek> al-maisan: ok, so mountall was still running when you hit Alt+SysRq+K, probably waiting for the processing of the 'filesystem' signal to finish; that gives us a small clue, but I still don't know where the bug lies. Can you file a bug on the plymouth package with this information? It's best if Keybuk can take a look at it 2 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: plymouth 0.8.1-4ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-20-generic x86_64 Architecture: amd64 Date: Mon Apr 12 11:13:15 2010 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: LENOVO 8895WFJ PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-20-generic root=UUID=c25a9613-2615-4f97-acf0-f0680e9702a8 ro --verbose ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth dmi.bios.date: 07/01/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC1WW (2.21 ) dmi.board.name: 8895WFJ dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC1WW(2.21):bd07/01/2008:svnLENOVO:pn8895WFJ:pvrThinkPadT61:rvnLENOVO:rn8895WFJ:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 8895WFJ dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- fcsk hangs up the boot-strapping process https://bugs.launchpad.net/bugs/561312 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
