Ubuntu

Activity log for bug #74009

Date Who What changed Old value New value Message
2006-12-01 06:04:05 levander bug added bug
2006-12-01 06:06:38 levander description What's going on now with my edgy upgrade from dapper (I did use update-manager) is that when I boot into the recovery mode kernel, it hangs. The last few lines: Begin: Initializing /dev... /init: 76: Syntax error: 0xID=4bd43095-7d5e-4829-95dd-25bb7860664 [4294680.075000] Kernel panic - not syncing : Attempted to kill init! [4294680.075000] I had noticed that when I rebooted, neither my boot nor home partitions were mounted. I guess the kernel was loaded into memory because grub was able to find and load it before the operating system booted. Before I got into this problem, and after I upgraded, /etc/fstab has been converted to some format based on udev, and I'm wondering if this is related to my problem above? The hex numbers in the error message look similar to the ones I saw in /etc/fstab. When I would boot before, if I logged in, I'd get some warning mesage about logging in with $HOME=/. I'd log in and be able to successfully mount boot and home with /dev/hda files. After logging in, I ran "dpkg --configure -a" to try to complete the install. And, later on rebooting, I'm now getting the kernel panic above. What's going on now with my edgy upgrade from dapper (I did use update-manager) is that when I boot into the recovery mode kernel, it hangs. The last few lines: Begin: Initializing /dev... /init: 76: Syntax error: 0xID=4bd43095-7d5e-4829-95dd-25bb7860664 [4294680.075000] Kernel panic - not syncing : Attempted to kill init! [4294680.075000] And here the system just hangs. Not even the power button works. I have to turn power off on the back of the computer. I had noticed that when I rebooted, neither my boot nor home partitions were mounted. I guess the kernel was loaded into memory because grub was able to find and load it before the operating system booted. Before I got into this problem, and after I started trying to upgrade, /etc/fstab has been converted to some format based on udev, and I'm wondering if this is related to my problem above? The hex numbers in the error message look similar to the ones I saw in /etc/fstab. When I would boot before, if I logged in, I'd get some warning mesage about logging in with $HOME=/. I'd log in and be able to successfully mount boot and home with /dev/hda files. After logging in with $HOME back equal to /home/username, I ran "dpkg --configure -a" to try to complete the install. And, later on rebooting, I'm now getting the kernel panic above.
2006-12-01 06:06:55 levander description What's going on now with my edgy upgrade from dapper (I did use update-manager) is that when I boot into the recovery mode kernel, it hangs. The last few lines: Begin: Initializing /dev... /init: 76: Syntax error: 0xID=4bd43095-7d5e-4829-95dd-25bb7860664 [4294680.075000] Kernel panic - not syncing : Attempted to kill init! [4294680.075000] And here the system just hangs. Not even the power button works. I have to turn power off on the back of the computer. I had noticed that when I rebooted, neither my boot nor home partitions were mounted. I guess the kernel was loaded into memory because grub was able to find and load it before the operating system booted. Before I got into this problem, and after I started trying to upgrade, /etc/fstab has been converted to some format based on udev, and I'm wondering if this is related to my problem above? The hex numbers in the error message look similar to the ones I saw in /etc/fstab. When I would boot before, if I logged in, I'd get some warning mesage about logging in with $HOME=/. I'd log in and be able to successfully mount boot and home with /dev/hda files. After logging in with $HOME back equal to /home/username, I ran "dpkg --configure -a" to try to complete the install. And, later on rebooting, I'm now getting the kernel panic above. What's going on now with my edgy upgrade from dapper (I did use update-manager) is that when I boot into the recovery mode kernel, it hangs. The last few lines: Begin: Initializing /dev... /init: 76: Syntax error: 0xID=4bd43095-7d5e-4829-95dd-25bb7860664 [4294680.075000] Kernel panic - not syncing : Attempted to kill init! [4294680.075000] And here the system just hangs. Not even the power button works. I have to turn power off on the back of the computer. Before I got into this problem, and after I started trying to upgrade, /etc/fstab has been converted to some format based on udev, and I'm wondering if this is related to my problem above? The hex numbers in the error message look similar to the ones I saw in /etc/fstab. When I would boot before, if I logged in, I'd get some warning mesage about logging in with $HOME=/. I'd log in and be able to successfully mount boot and home with /dev/hda files. After logging in with $HOME back equal to /home/username, I ran "dpkg --configure -a" to try to complete the install. And, later on rebooting, I'm now getting the kernel panic above.
2006-12-01 06:22:57 towsonu2003 None: statusexplanation
2006-12-01 06:24:06 towsonu2003 title Kernel panic after "Initializing /dev" during startup Kernel panic after "Initializing /dev" during startup after "/init: 76: Syntax error"
2006-12-01 06:27:48 Fabio Massimo Di Nitto linux-source-2.6.17: statusexplanation it looks like grub is passing the wrong root=UUID=$longnumber. Can you please try to see what's in the grub menu and fix it as above? Fabio
2006-12-09 23:15:43 levander grub: statusexplanation it looks like grub is passing the wrong root=UUID=$longnumber. Can you please try to see what's in the grub menu and fix it as above? Fabio
2006-12-12 11:04:13 Scott James Remnant (Canonical) udev: statusexplanation There already are such checks in udev ... This looks far more like a syntax error in the /init shell script in the initramfs!
2008-09-19 00:50:34 Daniel T Chen initramfs-tools: status New Confirmed
2008-09-19 00:50:34 Daniel T Chen initramfs-tools: importance Undecided Medium
2008-09-19 00:50:34 Daniel T Chen initramfs-tools: statusexplanation There already are such checks in udev ... This looks far more like a syntax error in the /init shell script in the initramfs!
2012-10-01 10:57:13 Thomas Hotz bug added subscriber Thomas Hotz
2012-10-01 10:57:15 Thomas Hotz initramfs-tools (Ubuntu): status Confirmed Incomplete
2012-12-01 04:18:15 Launchpad Janitor initramfs-tools (Ubuntu): status Incomplete Expired