[Bug 545536] Re: Not able to boot
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/545536 Title: Not able to boot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545536] Re: Not able to boot
http://ubuntuforums.org/showpost.php?p=9094227&postcount=11 After adding nomodeset to /etc/default/grub and running update-grub is the problem fixed after finding the machine booted successfully if I unplugged the HDMI cable. Still funny how it worked with modesetting after I kill those 2 processes. -- Not able to boot https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: Not able to boot
I've just encountered this problem also. Luckily I can still SSH in to my machine and browse all my mounts. The following works for me 1. SSH in to machine 2. Kill both Plymouthd and upstart-udev-bridge 3. Alt-Ctl-Del to reboot Upon reboot you should boot up successfully however it should need to be done at every boot up. -- Not able to boot https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: not able to boot
I would like to add that this problem may occur if the system fails to mount a partition that is in fstab. Due to an apparent bug in upstart the mount problem handling does only kick in every n-th boot, and n may be >10 if you are out of luck. Otherwise only the above mentioned ureadahed error mesage is visible and the rest of the screen stays black which is a very unfortunate situation. -- Not able to boot https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: Not able to boot
Jaromir, In most times you don't have to reinstall the whole system. Try to boot from Ubuntu LiveCD, then open your root partition in the file manager (Places - Computer), then 'etc' folder, then edit 'fstab' file there. Comment out lines referring to /proc/bus/usb and your FireWire drive (by inserting # sign at the beginning of these lines). Save the file, reboot Live CD session and boot from your hard drive to see if the boot goes any further. If it does, boot from LiveCD again and edit the same etc/fstab file, uncommenting the line referring to your FireWire drive. Save it and reboot again from your HDD. Tell us here if things still go wrong after your actions. -- Not able to boot https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: Not able to boot
I didn't get any further .. I probably will reinstall the whole system after, the final version is out, or wait for new pc with next ubuntu. -- Not able to boot https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: Not able to boot
Confirmed. I had this same issue. Ctrl alt del gave it the kick that it needed to complete boot. -- Not able to boot https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: Not able to boot
I tried today to get the log, but with little success. I am not able to get to the terminal session - the system is stuck with the message about "... status 4". I tried all possible combinations of keyboard shortcuts like ctrl c, ctrl break, c-esc, esc, ctrl backspace ... and it just writes the command and does not get me to a root terminal but when I left the PC running for some time, on Alt-F1 and F7 I found something that might be of a importance: [ 41.202693] sd 6:0:0:0: rejecting I/O to offline device .. and many similar messages with different end numbers starting 41. 57.058007 ieee1394: sbp2: scsi_add_device failed ... and I have my WD MyBook connected through FireWire .. But even if I turn the drive off, the system will lock up the same and will not boot to x-windows. I was trying to get to terminal on both available kernel versions - last was 2.6.31.20 -- Not able to boot https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: Not able to boot
I figured out my issue: I wasn't using the current kernel. When I updated my kernel I choose to "keep my old menu.lst". This was the source of many problems. I upgraded to Grub2, which automatically grabbed my latest kernel, and my system seems to be working great now. I was using 2.6.24, and now I'm using 2.6.31. -- Not able to boot https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: Not able to boot
Hello, I will try the commands //I'm in win now// later. I was trying some steps in the morning - was able to upgrade new packages, which didn't help, but in recovery mode on the current kernel, I left the pc running for a long time and a screen came through with the message same as before with added: "your disc drives need to be checked for errors. this may take some time" which led me to a conclusion - one of my drives recently broke and had to be reformatted, windows see it as good now, but ubuntu is still reporting "broken drive". the other thing is, that my WD MyBook external drive will lock-up with the message :... status 4: and has to be disconnected from power, to get it running again .. no encrypted drives in the system hope this helps. I plan to restart and try the things in terminal -- Not able to boot https://bugs.launchpad.net/bugs/545536 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
Re: [Bug 545536] Re: Not able to boot
I thought I had solved; however, today it represented in the form of forcing me to Ctrl+Alt+Del it 5 or 6 times before having my system booted. It always sticks at Waiting for /home [SM] I'm updating now, and plymouth is one of the provided updates, so it _may_ be fixed now, but I don't really know and I don't want to reboot as I have a working system... This said, I'll reboot as soon as I finish doing my stuff and then I can tell if it was fixed or not On Sat, Mar 27, 2010 at 05:32, goldfish2 wrote: > Claudio Moretti, even if the original poster doesn't have encrypted > volumes, I have encrypted volumes and am having this errror... what is > the solution that you found? Thanks. > > -- > Not able to boot > https://bugs.launchpad.net/bugs/545536 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Ubuntu: Incomplete > > Bug description: > I upgraded to current beta version of ubuntu 10.4. today. all went fine in > the ugprade process, but when I tried to boot, the system will hang up in > the same position. Tried this with all kernel versions and (recovery) boot > options. > > the system will start to boot and than report: > init: ureadahead - other main process (891)terminated with status 4 > init: ureadahead - other main process (896) terminated with status 4 > init: ureadahead - other main process (901)terminated with status 4 > init: ureadahead - other main process (904)terminated with status 4 > > and below somethink like > waiting for WD My Book > > no matter what you press, the system will not continue. I managed to get to > a command line, and was able to run some basic commands. > > I am currently in Windows and are not able to get any data from Ubuntu with > some logs. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+bug/545536/+subscribe > -- Not able to boot https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: Not able to boot
Claudio Moretti, even if the original poster doesn't have encrypted volumes, I have encrypted volumes and am having this errror... what is the solution that you found? Thanks. -- Not able to boot https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: Not able to boot
This leads me to a question: do you use encrypted volumes? I had the same problem (even if it's now solved) -- Not able to boot https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: Not able to boot
The ureadahead message is not relevant to your problems ** Summary changed: - Not able to boot - ureadahead other main process terminated with status 4 + Not able to boot ** Package changed: ureadahead (Ubuntu) => ubuntu -- Not able to boot https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: Not able to boot - ureadahead other main process terminated with status 4
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 545536 This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. Thanks in advance! When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: ureadahead (Ubuntu) Status: New => Incomplete -- Not able to boot - ureadahead other main process terminated with status 4 https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: Not able to boot - ureadahead other main process terminated with status 4
** Package changed: ubuntu => ureadahead (Ubuntu) -- Not able to boot - ureadahead other main process terminated with status 4 https://bugs.launchpad.net/bugs/545536 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
[Bug 545536] Re: Not able to boot - ureadahead other main process terminated with status 4
I am not particulary strong with terminal, but If you tell me what I should do, I could try some steps to get around this, or get some logs. I have 2 internal driver + 1 external - Western Digital My Book. -- Not able to boot - ureadahead other main process terminated with status 4 https://bugs.launchpad.net/bugs/545536 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
