Ubuntu :: Boot.log Ureadahead - Ureadahead-other Main Process (759) Terminated With Status 4
Sep 10, 2010
i had a couple of things popping up during bootup and checked my boot.log and found this
Code:
fsck from util-linux-ng 2.17.2
fsck from util-linux-ng 2.17.2
udevd[416]: can not read '/etc/udev/rules.d/z80_user.rules'
fsck from util-linux-ng 2.17.2
fsck from util-linux-ng 2.17.2
[Code]....
Last night i have upgraded my 9.10 to 10.04. After rebooting the system i couldnt boot linux.I got the following message:Starting up ...mount: mounting none on /dev failed: No such deviceinit: ureadahead main process (20 terminated with status 5After that message some 10.04 check disk started, but nothing good came out of it.
I have Ubuntu 10.10 installed. When I boot, this error message appeared "init: ureadahead main process 388 terminated with status 5" After that, another error message appear saying " *ERROR* render ring head not reset to zero"
Code: init: ureadahead main process (423) terminated with status 5 Ubuntu 10.10 lorentz tty1
lorentz login: The first line of the above shows up during boot before the display goes graphical. I can see it again (all of the above) when I Ctrl+Alt+F1 to access the first text console. Anyone know what is causing this, what problems can happen as a result, and what should be done about it? I moved from 9.10 on one machine to 10.10 on a new machine, so I don't know if it's a hardware problem or software. I am running 64-bit. I am not really seeing any problems happening besides the few scattered application and GUI glitches that are common with a new/migrated setup.
I installed Lucid Lynx on my laptop a couple of months ago and for the most part everything was working fine. However, just recently the computer doesn't seem to be booting up at all. I start up the machine and then a black screen appears with the text: init: ureadahead main process (306) terminated with status 5 the (#) is different in some boot-ups
And the computer just hangs there. typing anything doesn't seem to help at all. I press enter and a new line just appears. I've left it there for hours and still no login screen.
Quote: init: ureadahead main process (274) terminated with status 59 Starting up... There is a blinking cursor under the 'S' in Starting. It doesn't boot or respond to any escape combinations that I know. Several retries have yielded the same screen. I read the original post and a few comments here about ureadahead, but did not find anything related to my problem.
So when I boot before the boot slpash this shows:ureadahead-other main process (320) terminated with status 5. It started happening completely randomly, is this anything I should be worried about and can I fix it?When I try and run ureadahead I get this:
brandon@brandon-laptop:~$ sudo ureadahead -v /var/lib/ureadahead/pack: No such file or directory ureadahead: Error while tracing: No such file or directory
I have an Acer 9410Z laptop that I believe is running the Maverick Meerkat version of Ubuntu Studio. I just did an upgrade using Synaptic. I get to GRUB, but When I try to boot 2.6.35-22 (or the recovery mode or a real time kernel I had installed )I get the error:
INIT: Failed to spawn ureadahead main process. No such file or directory I then get the Ubuntu Studio splash screen for 2 seconds but then instead of a normal boot I end up in the terminal.
I keep getting this message as the first thing I see when I boot up. Afterwards, it displays the ubuntu logo and dots under it and then the screen blacks out, but the display lights act like its OK (wireless ETC). should I use a boot CD or something? The hard drive is fine and this happened after the computer blacked out during updates. i scanned the hard drive and its OK, according to the little scan thing you can do before booting up. I have a Compaq Presario V200. For specs, thats all I know.
My ubuntu server was working normally but it suddenly failed to start, stopping after the following message: init: ureadahead-other main process (587) terminated with status 4 after this message, the system halts and does not finish the start up processes.
If I start the server in recovery mode, I get: init: ureadahead-other main process (587) terminated with status 4 [ 21.892940] ACPI: I/O resource w83627hf [0x295-0x296] conflicts with ACPI region HWMI [0x295-0x296] the system also halts and does not start. Right now, I can not use the server at all.
When i boot my pc there is a black screen and then a message appears (initlymouth-splash main process(856) terminated with status 1) Some other times only this appears '' _ '' blinking (i don't remember how it is called in english,sorry) I hold Ctrl+Alt+Delete and then the screen where i choose profile comes up. I have 10.04 since they came out,and didn't have any problem except one issue with my belkin adaptor,but now i can't sync my iphone with rhythmbox or detect any flash sticks.
I tried a dist upgrade from 10.10 and come across the below errors:
init: udevtrigger main process (352) terminated with status 1 init: udevtrigger post-stop process 357terminated with staus 1 init: udevmonitor main process (351) killed by erm signal
When I restart my computer the following messages come up: __________________________________________________ _ init: usplash post-start process (2221) terminated with status 1 * Stopping ClamAV virus database updater freshclan
I have upgraded my ubuntu to the latest version a few days ago. Prior to the update I played a little with my partitions (transferred about 15GB from my windows partition to ubuntu partition).Up until yesterday everything worked. For some reason ubuntu will not load up now. After selecting ubuntu on grub i get the following msg: init: mountall main fsck process (574) terminated with status 3 mount of filesystem failed one or more of the mounts
Can't seem to get past this error Doing a google search resulted with no good answers that pertained to this issue. Not sure what's halting the system from starting up, but it just sits and hangs at this forever. Only able to view the error when booting into single user mode - normal boot hangs after "enabling /etc/fstab swaps: [OK]"
I installed slackware 12.1 from files i downloaded and converted to cd (images). There are six "disks" i downloaded from the slackware site and converted to images via a homemade .cmd in windows xp and then burned using imgburn.
I partitioned my hd (canibalized from an acquaintance's emachine and connected it to my desktop (1G ram, 2Ghz processor). Booted from disk 1 and fomatted the 80G HD for 2 partitions of linuxswapable at 2G apeice and 2 partitions of bootable linux. (Because i want to try another distro later). I ran the setup installing most everything and all seemed to go well. After i exited setup and restarted, it identifed the cd/hd as normal and then went into some sort of recovery mode with the emachine logo call pcangel, after which it tells me.
STOP: c0000021a (fatal system error) The session manager initialization system process terminated unexpectedly with a status of 0xc000003a (0x00000000 0x00000000). the system has been shut down. So, is this indeed an xp error message, and if so, why am i getting it after formatting everything?
On Launchpad there is the following thread on ureadahead:
[URL]
Is it sensible to remove "ureadahead" until this is fixed or is there no harm done? As a normal user ... (yes still I have /var in a separate partition, because I want to be on the safe side with my databases located in /var when reinstalling or upgrading the system ... - by the way: does this make sense or is it better to just have /home separate and use a backup of /var folders?) ... as a normal user I feel a bit lost with bugs like this. It would be nice to get some information somewhere. Something like:
"Don't worry, just wait for an update with a bugfix!" or "To avoid further problems just remove 'ureadahead' until it's fixed!"
I recently tried to upgrade my graphics card. I had an Intel GMA 950, and upgraded to a PNY Nvidia GEForce 8400GS with 512 DDR I installed the card, and was unsuccessful in getting it to work, but while using the onboard graphics I updated the drivers in ubuntu to use the Nvidia proprietary drivers. I went into a cycle of rebooting and fiddling. booting into Ubuntu was successful with the onboard card, however I only got a command line. I used nano to change my xorg.conf from saying
Driver "nvidia". I simply deleted this portion in the hope that X11 would simply think on its feet. Onboard graphics wouldn't deliver any X session after that. I eventually got the card to work after futzing with the BIOS settings, however once I tried to boot, I got the error "init : ureadahead main process (264) terminated with status 5" after numerous upgrades, my GRUB menu has several kernels, however none of them would boot properly, including recovery sessions.
I decided to boot into a livecd to edit my xorg.conf in a Live environment, but I was unsuccessful, the LiveCD (simply Maverick Meerkat, after trying Karmic Koala) got stuck in a loop of not being able to detect media in /dev/sr0, which is very puzzling. So now I'm stuck with a computer with a functioning video card and nothing else.
First off I am aware ureadahead isn't in the repos, but thought this forum would fit the best regardless. I installed upstart, then the deb package on packages.ubuntu.com and rebooted. The /var/lib/ureadahead folder exists but there are no .pack files in that folder. I tried running "service ureadahead start" but it said "Service failed to start". Anyone used ureadahead on Debian?
boot fails with the following message:/etc/default/locale: 5: d_fmt: not found init: mountall main process (234) terminated with status 127
if I boot to Recovery, is there any way to edit this locale file or to delete it and replace it with a default one? How can I edit the Locale file to fix this problem without being able to boot?
I was running ubuntu 9.4 previously and a few days ago i upgraded to 10.04. everything appears to be perfect.
However i ran df -h and was surprised that i had 3.7G remaining on the / i went to my home directory and moved out 15Gig and executed df -h again the result is the same 3.7G remaining.
I went to "/var/lib/ureadahead/debugfs" only to find nothing in there and at one level up "/var/lib/ureadahead" there is a file called "pack" which is 768.6Kb in size.
After moving files from the home directory i did a property check on it and the home folder is 3.8Gg used
Im confused as to 1, what is eating my HDD space ? 2, is "/var/lib/ureadahead/debugfs" misleading the sytem 3, is this a bug ?
Im using ubuntu 10.04 but up till a few days ago it has been 9.4 so im guessing this problem didn't suddenly appear since the installation of 10.04
I booted up my laptop and the boot sequence got stuck at the boot splash screen (plymouth). I did an esc and I saw a failure message, the error I remember in my panic mode is: fsck terminated with status 8
I rebooted, got the same message. Rebooted again and this time, to my relief, it worked.
1) What happened, should I be concerned? Not sure why it worked after 2 reboots.
2) Is there a possibility this could happen again?
3) Are there any boot log files I could look at?
4) Is there anything I can do to fix this? Or a check of some sort?
I'm using Ubuntu 10.04 on a Dell Studio 1535 laptop. No dual boot. The disk is partitioned and I've got my /home folder on the other partition for situations like this.
My desktop using Ubuntu 10.4 (I recently ungraded from 9.04) crashed. That is Ubuntu is not loading. At first I get a Ubuntu icon and count % of cheeking system and before it reaches 50% a linux screen comes up with error messages: Last six lines: Code: mountall: fsck / (9290) terminated with status 4 mountall: Filesystem has errors: / init: mountall main process (9289) terminated with status 3 Mount of filesystem failed. Maintenance shell will now be started. CONTROL-D will termainae this shell and re-try. roo@computername-desktop:"# _ How to revive Ubuntu?
I am currently running this off my laptop with the issue using a bootable flash version of 11.04. hwclock keeps terminating with status 127 on boot everytime tried anything i could come across, and still nothing checked the hard drive as well.