** Description changed:
Since my upgrade to Karmic, my system fails to boot about 80% of the time.
One of several possibilities will happen:
- many of the boot processes will terminate (status 1, 4, or 5) in the
console log. The system will hang at some point in the boot process (the last
output being either about sysfs or about Timidity)
- the system will boot to a console login. however, trying to login crashes
the shell with SEGV each time.
- the system will boot to a console login where I can actually login.
Manually starting gdm ("sudo service gdm start") crashes gdm with SEGV.
- the system will boot to X, where I can log in. However, one or several
partitions are not mounted, so I need to run "sudo mount -a" manually.
- the system will boot normally
If the system fails to boot, it is not possible to use Ctrl+Alt+Del to
reboot the system - the key combination will be mostly ignored (short
disk activity, no relevant console output). The only way to cleanly
reboot the system each time until it finally boots properly is
SysRq+RSEIUB.
About my Xubuntu/xfce4 system:
The only thing that is probably unusual is that /usr, /home, and /var/lib are
sitting on a different partition, due to a small root partition. My disk setup
has become a bit strange over the ages. I have 3 physical disks with several
partitions each.
/dev/sda3 - /
/dev/sda2 - swap
/dev/sdb6 - /mnt/hdf6; /usr, /home, and /var/lib are here, all softlinked on
the root-fs (this has never caused any problems at all)
/dev/sda4, /dev/sdb5, /dev/sdc1 - non-essential vfat filesystems
From what I can see from the console messages is that device and/or
partition detection seems to fail at random during the boot phase
(upstart/mountall). Depending on which partition(s) are not recognized
(or if for example /dev/sdb6 is recognized/mounted too late, so that
/usr is unavailable), the system will fail to boot at certain points.
But this is just a guess, since I am not familiar with the methodology
of upstart.
If the system does boot and fails to mount some of the vfat partitions,
the ones which are not mounted appear to be random - sometimes sdb5,
sometimes sdc1, sometimes both. However, the one vfat that is *always*
mounted correctly is sda4, sitting on the boot disk and the same disk as
the root-fs.
I only now removed the "quiet" and "splash" options from grub, so
hopefully I'll get some error logs I can attach next time.
- #rant on
- Probably not really related to this bug, but I feel the need to rant about it
anyways: This pretty annoying problem, in addition to *several* other
bugs/problems introduced since my upgrade to Karmic (on different machines)
make 9.10 the worst Ubuntu experience ever, making me thinking about switching
distros altogether. Out of the top of my head I can recount about 7 heavy
regression bugs I did not have before the 9.10-upgrades, most of them
*severely* impeding productive work :-(
- #rant off
+ Unfortunately, this very annoying problem, together with several other
+ work-impeding regressions, make Karmic the worst Ubuntu experience ever
+ for me :-(
I found bug #434395, describing very similar symptoms; however, the
reported no longer appears to have this problem and set his report to
"Invalid".
ProblemType: Bug
.etc.asound.conf:
pcm.!default front:Live
ctl.!default front:Live
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'CMI8738'/'C-Media CMI8738 (model 55) at 0xb800, irq 21'
Mixer name : 'CMedia PCI'
Components : ''
Controls : 41
Simple ctrls : 22
Card1.Amixer.info:
Card hw:1 'Live'/'SB PCI512 [CT4790] (rev.7, serial:0x80231102) at 0xb400,
irq 23'
Mixer name : 'TriTech TR28602'
Components : 'AC97a:54524123'
Controls : 216
Simple ctrls : 38
Date: Thu Jan 7 14:45:43 2010
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=5076dfbc-cbb2-4d4d-a580-c54561478fb7
IwConfig:
lo no wireless extensions.
eth2 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System Manufacturer System Name
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-17-generic 2.6.31-17.54
ProcCmdLine: root=UUID=88c5a1d5-4940-4c63-8d7f-fec9a32cc6b8 ro quiet splash
ProcEnviron:
LC_COLLATE=C
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/tcsh
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
RelatedPackageVersions:
linux-backports-modules-2.6.31-17-generic N/A
linux-firmware 1.25
RfKill:
SourcePackage: linux
Uname: Linux 2.6.31-17-generic i686
WpaSupplicantLog:
XsessionErrors: (polkit-gnome-authentication-agent-1:3836): GLib-CRITICAL **:
g_once_init_leave: assertion `initialization_value != 0' failed
dmi.bios.date: 02/21/2003
dmi.bios.vendor: Award Software, Inc.
dmi.bios.version: ASUS P4B533 ACPI BIOS Revision 1014
dmi.board.name: P4B533
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: REV 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 7
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAwardSoftware,Inc.:bvrASUSP4B533ACPIBIOSRevision1014:bd02/21/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4B533:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion:
dmi.product.name: System Name
dmi.product.version: System Version
dmi.sys.vendor: System Manufacturer
--
system fails to boot most of the time since Karmic upgrade
https://bugs.launchpad.net/bugs/504258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
