Ubuntu Installation :: Ureadahead Requires /var On Root Filesystem
May 11, 2010
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 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]....
I downloaded a driver for my printer today and I opened it in the terminal. Then a window popped up saying "This opporation requires root (administrative) privileges. Please enter the administrative password below:" I typed in the same password that I use when authorizing the installation of programs from the Ubuntu Software Center and I tried it multiple times. Each time, it rejects the password. I even tried downloading something else from the software center, just to make sure the password was correct, but the system had no problem with the password when downloading from the software center. So, is my software center password different from my administrator password?
When I try to boot to OpenSUSE I get the following error during boot-up: unknown filesystem type 'reiserfs' could not mount root filesystem - exiting to /bin/sh$
This only started happening quite recently - before this I could boot to Linux quite happily.
i made a live usb stick with a original live iso image of f10 following carefully instructions of fedora support comunity once i finished i had tested it and i had the same problem (warning can not find root filesystem create symlink /dev/root and then exit this shell to continue the boot sequence, bash: no job control in this shell) of the following person:
I'm having trouble installing it on a "new" computer that I found at Goodwill for $60 with no operating system on it. When I go to edit the partitions, it won't let me do anything due to an apparent lack of a root filesystem. (I know this issue has been brought up and resolved in the past, but the usual solution (going into the validation.py file) isn't working for me, as there is no line in this one that says "if not root".)
I decided to try to do the 3 distro upgrade stretch from 8.04 to 10.04 this weekend and now I am hung on 9.04 to 9.10.. The upgrade went swimmingly, but I hit a wall upon boot. When I try to load kernel 2.6.31-22 I am greeted with the following error:
Code:
[ 20.879845] ACPI: I/O resource vt596_smbus [0x400-0$407] conflicts with ACPI region SMOV [0x400-0x406] Mount of root filesystem failed.
A maintenance shell will now be started ... After doing some digging I found this thread which appears to be similar in the inability to mount the filesystem. However, it does not mention the ACPI error. I tried everything in that thread; verifying device ID's, editing fstab options; running a filesystem check, and flipping the UTC option in the rcS file but nothing worked. The OP of that thread eventually did a fresh install of Karmic; but I would rather not have to go that far.
Have been running 11.1 on a generic notebook (eRacks) just fine until a few days ago when CUPS couldn't be reached. Rather than futz more with 11.1, I decided to install 11.2 (which has been on my desktop). Using the same CD, which continues to check ok, the install has failed many times at about the same point: 87% through "copying root filesystem" in yast2. Specs: Intel P4 2.4 GHz, 1.5 GB RAM, ATI radeon PV250Lf
The HD was partitioned into /, swap, /home, and an extended partition of /opt, /var, /usr. Only / was ext4 and the rest were ext3. Tried various options: * no apic * no acpi * "noapic acpi=off" entered manually * Vesa instead of 1024x768
Each time had to edit partition table to mount the extended partitions. Always formatted /. At first didn't format the extended patitions, later formated all but /home. Then set yast2 to format / as ext3, to match the other partitions. In the sysinfo page the / partition is now shown as /mnt containing 723.6 MB out of 7 GB, still formatted as ext4. On rescan by yast2 partition manager, / shows as ext3. The install halts every time with an error while "copying root filesystem." Tried booting from the CD direct to install and to the Live OS followed by install--same result. So, hours later, went back to 11.1--which installed in minutes.
I have been having a small problem since I upgraded from Jaunty to Karmic, whenever I shutdown or restart, root password is required due to multiple users being logged-in.
I have run ck-list-sessions, however I can not trace where (or what) session 5 is.
Code:
Since I have MythTV installed and there was a similar bug, I tried the following solution without any success: [url].
I have the script below that I want to run when my sister logs into her account. But the problem is that `ifconfig up` or `ifconfig down` requires root privileges. How do I initiate the program when she logs in and have root the the runner of the program.
Code:
#!/bin/bash while true do elevenpm=`date +%s --date "2300"`
I've upgraded my squeeze box to linux kernel 2.6.32-5. But it shows mounting "here is the uuid of / " on /root failed: Device or resource busy while booting.Here is the menuentry of linux kernel 2.6.32-5.
I am running Fedora 10 new install. lsdvd gives an error when trying to access the dvd. If I issue chmod 766 /dev/dvd then it works fine. Is there a way to set this a boot so access to the dvd does not require root password?
One of my machines running 10.04 recently began requiring the root password in order to carry out privileged operations in update-manager. I found this bug in launchpad. It's similar, but related to 10.10. If I create a root password, then I can use it to carry out privileged operations in update-manager, but I prefer not to add a root password just for this purpose.
My linux distro is CentOS 5.3. Today I edited /etc/sysconfig/readonly-root and set "READONLY" to yes, now my /etc/sysconfig/readonly-root file is like this:
# Set to 'yes' to mount the system filesystems read-only. READONLY=yes # Set to 'yes' to mount various temporary state as either tmpfs
I've been running 11.3 on a net book for several weeks and have not had this happen on that computer. On a different computer, which was upgraded from 11.2 to 11.3, now requires a root password to shut down the computer.
Since i installed KDE 4.* Whenever I go to shutdown, I get the shutdown dialogue, I hit shutdown, it logs me off, shows some text on shutdown screen, and then opens up the GUI again, bringing up a small window, where It asks for the root password, in order to shutdown. If i don't give it the root password, it goes to the login screen.
I cannot, any way, command line, GUI, or anything, shutdown without providing a root password.
If I use the command shutdown now, as root, it logs me off and goes through an endless cycle of logging off, and then asking for root to shut down, and not shutting down (All on the CLI), and everytime i give it the password, it cancels shutdown and goes back to the prompt. I eventually have to pull the battery to kill it in that case..
I have tried chmoding the shutdown scripts to make it work, it doesn't.
I have an HP Pavilion notebook running Ubuntu 9.04 and it has a lightscribe enabled DVD burner. Whenever I try to print a label using the LaCie Lightscribe Simple Labeler the program starts, I create the label but when I tell it to print I get an error message saying " Printing requires root privileges". I have tried starting the program with the icon, from a terminal using both "sudo" and "gksudo" and from a root terminal.
I have a second hard disk which has windows and C and D drives partitions. When I boot fedora 13, fedora automatically mounts them as 53 Gb Filessytem and 200 GB Filessytem. But when i try to browse to these filesystem, fedora ask me root password. How I can configure fedora so that it does not ask me root password and this change should be permanent ( surving computer shutdown and restart) ? I want these windows partitions to be reachable by me as the non-root user.Also given /dev/sdb (the windows disk) what is the command line to find out the filesytem path to which various paritions on /dev/sdb are mapped to?
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 have a custom Ubuntu distro that run both from a CD and PXE boot. The problem I have is that I need to boot in an environment that has to be routed through a router that can't forward NFS (the protocol doesn't use a standard port) I found that the Ubuntu based Clonezilla Live CD has a option like "fetch tftp://server/folder/filesystem.squashfs" I can borrow the kernel and initrd and it works, but how do I add this feature myself? Is there a package I need to install or a initrd option I need to add?
Lately however my root filesystem is getting filled up every night-- I come in in the morning and have notices that I have 0 bytes remaining. There's tons of room on the disk, but the root is full. Here's what it looks like with a df -h:
ive been recently experiencing some problems with my ubuntu studio 9.10 setup, with the filesystem failing to mount. after deciding to try a new hard drive and cable, as well as clean install ubuntu, fedora and now mint, im still finding no filesystem.im using a live cd created for mint (like it ). having clicked install to hard drive, all is well until the partition manager, where all the boxes are greyed out. clicking forward produces a box saying "no root filesystem defined". i see there are a few on here from a few years back and having read through them, cannot find a fix for myself.
Using Ubuntu 10.10, 64-bit, installing after LiveCD testing.sda3 can't really be erased due to its contents, something I can't exactly get back or transfer.
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.
I have a local computer (local), and remote computer (remote) behind of remote server (server). Also, I have user access to all of these 3 machines. Now, I want mount some directory, located at remote, to my local mount-point via sshfs. How should I setup my local sshfs and what should be done on server to make this mounting?
I'm stuck with ssh tunneling because the default method for tunneling requires root access while WinSCP somehow could do this with only user access (the tunnel server could be configured there in 'tunnel' panel).
I have a dual booting newly installed 64 bit Ubuntu 9.10 on my machine. It was all fine until today. Now when I boot into Ubuntu, I see the error Failed to mount root filesystem. I cant remember any significant changes during the last session. One thing I remember is I upgraded the system using the update manager which asked me to choose an option for grub boot loader. I opted for its upgradation. After the upgrade, I was able to work with Ubuntu for a few more sessions. Windows XP works very fine.I checked other threads which suggested running fsck, but it did not help. fsck does not report any errors.
