Hardware :: Boot Fails (after "udev") While Doing Filesystem Checks?
Aug 28, 2009
On a Sun Ultra10 333MHz, 512M, 9gB HDD. Booting Fedora-9. Silo v1.4.14 into kernel 2.6.27 64bit (vmlinuz-2.6.27.12-78.2.9fc9.sparc64). This is a brand-new installation.Although it's running on a Sparc it makes v.litte difference so far as this bootprocess, teh way Linux runs, where everything is - is concerned. That's why I've cross posted this query here.Booting merrily, in the interactive startup section just past "Starting udev", "Setting hostname", at "Checking filesystems" I get:
/: clean, 155284/557056 files, 920932/2225412 blocks
fsck.ext2: Device or resource busy while trying to open /dev/sda
Filesystem mounted or opened exclusively by another program? [FAILED]
*** An error occured during the filesystem check
*** Dropping you to a shell, the system will reboot
*** when you leave the shell
*** Warning --SELinux is active
My Ubuntu Linux system was switched off at the mains without being properly shut down. When it was restarted again, the file system checks failed and I was presented with the maintenance console command prompt. How do I check what is wrong with the file system. Is there any sort of generic repair command that checks the disk and fixes errors?
I'm having some trouble with udev, in that it won't create me a symlink for the infrared device which is part of my Hauppauge Nova-TD-500 TV card.I've got the card installed, and for the most part working, but I want to have the infrared device on /dev/ir.I've created a rule in /etc/udev/rules.d/ called 55-dvb_usb_dib0700-ir.rules which contains this:
Code: SUBSYSTEM=="input", ATTR{name}=="IR-receiver inside an USB DVB receiver", RUN="/bin/date > /home/xbmc/foo", SYMLINK+="ir"
Ever since my upgrade from 9.10 to 10.4, every time I reboot the system it does a full disk check. /var/log/boot.log tells me that fsck thinks that the file systems contain errors or that it wasn't cleanly unmounted. And yet, it doesn't seem to actually find errors, and a clean reboot starts another check (again with it thinking something is dirty). I dual-boot with Windows, and reboot from there with the same problem.Again, all of this is new with 10.4 and was not happening with 9.10.Is there a way to find out when/how/why the disks are not being unmounted cleanly?
These days I see the disk check that is popping up when my Ubuntu is booting up quite frequently. It says 'press C to cancel' but C (or Shift C or CTRL C or CTRL ALT C) does not have any effect. Pressing CTRL+ALT+DELETE reboots but again ends up in the vicious loop of disk check. How to bypass it? When I need to critically enter the desktop for an urgent pressing info waiting for 20 to 25 minutes disk check is kind of difficult.
I've been an Ubuntu 10.04 64 bit user for one year. My Ubuntu distro is installed on an ext2 file system. Occasionally, I experience disk checks during boot without any system freeze or power loss.Sometimes, once reboot, the system works fine but Evolution Mail requests a new account, as if it was used for the very first time.Does anyone know how to fix this problem?
I rsync-ed root fs as a whole to another hard drive. In grub.conf I changed kernel option
root=/dev/sda1 ---> root=/dev/sdb
After kernel mounted root filesystem on the new hdd and all services started I successfully got prompt to enter login and password. However after login I immediatelly logout automatically. Here is /var/log/secure output:
Quote:
May 20 23:53:18 localhost login: pam_unix(login:session): session opened for user alex by alex(uid=0) May 20 23:53:18 localhost login: LOGIN ON tty2 BY alex May 20 23:53:18 localhost login: pam_unix(login:session): session closed for user alex
What is printed before this:
Quote:
May 20 23:50:47 localhost pam: gdm-password[1469]: gkr-pam: couldn't run gnome-keyring-daemon: Access denied May 20 23:50:47 localhost pam: gdm-password[1455]: gkr-pam: gnome-keyring-daemon didn't start properly properly
Neither of these quotes appears if the initial file system (not rsync-ed) is used as root fs. I guess that pam might use information of hard drive, for example, its serial number, and login is tied to a disk. Please, give me a suggestion how to get rid of automatic logout.
I recently made a custom spin of fedora on 29th August 2009. It initially failed to go past the slash screen but a solution was found here on fedora forum. It included adding the following to kernel line in grub.
enforcing=0
I later checked SElinux and found the option to do a filesystem relabel at next boot was enabled. I rebooted the system without adding the above words "enforcing=o" and it got stuck after the the splash screen (the blue screen with a fedora bubble). I then did some more research on SElinux and filesystem relabelling. There were several comments that said that a notice is given in the event of a filesystem relabel. I went to the konsole and as root I wrote the following commands:
touch /.autorelabel reboot
I gave my pc 20Hrs 48min and nothing happened. My HDD is 80GB but it only had 7.5GB of data. There were no messages that indicated that the filesystem relabel was in progress or even if it had started. I also tried the following command but failed:
make relabel
I have now had to edit grub.conf and added the words "enforcing=0" as it is the only way the system will go passed the splash screen.
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.
During the boot process the machine (Fujitsu Celsius M470) hangs about 4 min at udev:loading drivers. After that it continues and I can work with the OpenSuse 11.2 system without problems.I activated the debug log in /etc/udev/udev.confthen I see that it is doing a lot in that time, at the end I see the message:udevadm settle timeout queue contains: a long list of pci/usb entries (no entries in any log for this)
in the logfile I find:udevd-work[1071]: '/sbin/modprobe' (stderr) 'FATAL: Error inserting ipmi_si (/lib/modules/2.6.31.12-0.1-desktop/kernel/drivers/char/ipmi/ipmi_si.ko): No such device'there is no ipmi. how can I deactivate the loading of this module?
udevd-work[412]: '/sbin/modprobe' (stderr) 'FATAL: Module input:b0019v0000p0001e0000_e0,1,k74,ramlsfw not found.' Mar 17 11:35:36 mira udevd-work[418]: '/sbin/modprobe' (stderr) 'FATAL: Module
In Ubuntu 910 on my Asus EEE-PC1005HA, I notice that during boot, when the screen is dark between the plain Ubuntu logo and the animated purple screen, there is a brief message:udev[488] cannot read file (rest of message goes by too fast for me)This doesn't seem to hurt anything. My system has been working just fine for a long time. I don't know how long the message has been there. Perhaps it merely lengthens boot time? Should I care? If I should care, where might the message be logged (so that I don't have to photograph the screen)?
I'm writing for my brother who was running Karmic on a Microtel desktop.He'd been having trouble with blank cds (data cds and dvds didn't cause this problem) crashing his box so he uninstalled and then installed udev package.Now when he tries to boot the box goes into a memory test and then reboots into the memory test over and over. He tried to check the installed kernels to choose one that might boot but there are none listed (he pressed "esc" to see the list-it's empty).He tried booting from a live cd and that won't work either. The cd drive spins but nothing else.
This morning I had the courage to run an apt-get autoremove which took some 275 packages off my hard drive, and now I am experiencing a delay of about 40 seconds at boot, after grub, before the plymouth splash appears. The cursor blinks on a black screen while the hard drive churns away. Finally two error messages appear too quickly to be read, and then the bootsplash kicks in. I can find the instant in the dmesg where the delay happens, but can't locate the cause. Here's what my dmesg looks like:
[Code]....
The laptop is an Acer Timeline X 3820TG, with the dual GPU "switchable graphics." These dual graphics cards have given me enough trouble in the past that I wouldn't be surprised if they were the problem. But the hard drive action sounds like a 'fsck,' and seems to be contemporaneous with the dmesg notice that the root partition is mounted.
Incidentally, my boot wasn't all that fast before; I would not be surprised if this delay was preexisting, but used to happen after the plymouth boot screen was already on screen. Still, if I can get rid of this one ugly delay, I can have a fast (c. 10 secs) boot time.
I am trying to make gentoo boot faster and in my searching I came across this article http://lwn.net/Articles/299483/. One of the things they did was revert to a "persistent, old-school /dev directory so that boot doesn't depend on udev". I would like to know how to do this, but when I searched for disabling udev all the forums say that its a bad idea. All I want to know is how to make a static /dev directory.
I've been having problems with start_udev on my machine post kernel 2.6.18-162 on my CentOS machine. A previous install would work on the old kernelut not the newer ones. I recently did a completely fresh install of CentOS 5.5o see if maybe there was a orruption in my install when it upgraded,t I still have the problem of udev hanging on startup.Using the rescue option on the disk, I've managed to track the problem down to the 50-udev.rules file. Through trial and error, I moved all the .rules files out of the rules.d directory, and added them back one at a time to see which one(s) caused the system to hang, and which ones it carried on booting as normal with. The only one that causes it to hang is the 50-udev.rules.
From what I can tell, this rules file is responsible for letting udev check various pieces of hardware. I think that it is failing whent runs modprobe on a pci device address.Only problem is I don't understand the rules file syntax, so I don't know if I can simply comment out or change a line in this file to skip the device that its looking for.Can anybody help me track down the specific device/line that is doing this?(I've kept the file out of the folder for now and my system appears to continue operating, but I get the occasional problem that for all I know could be due to udev not having a complete start up).
I have done a fresh text-only installation of Fedora 10 on a Dell Dimension E521 for the purpose of setting up a server. After installation I ran yum update to bring the system up to date. After the update, I rebooted the computer, but the boot process froze. I recycled power and pressed "I" after the Dell BIOS screen and the GRUB bootloader appeared. I selected the most current version, edited the kernel line by deleting "rhgb quiet" and replacing it with "3." After making this change, I continued with the boot and the computer stopped at "Starting udev:" I have two fedora 10 revisions showing in the GRUB bootloader, the original installation and the update after running yum.
I repeatedly tried rebooting both versions and, after about 30 attempts, the computer finished booting and got me to the command prompt. Reading through the forums indicated there might be some issue with my nVidia GeForce 6150 onboard video and fedora 10. So, when I got to the command prompt, I followed the instructions in the forums [URL] to load the rpmfusion drivers. This appeared to be successful and when I looked at /etc/X11/xorg.conf it appeared to be correct for the new nVidia drivers. After loading these new drivers I tried rebooting. Unfortunately, I have been trying now over and over to get back to the command prompt, but simply can't get past "Starting udev."
i'm heaving the following message at boot time: "Starting udev: udevd[114]: unknown key 'DEVTYPE' in /etc/udev/rules.d/70-cups-libusb.rules:6", i guess it's something about usb printing support but i am not sure, and i don't know how to fix it, does any of you guys know what this exactly means and how to fix it
I'm trying to configure gpsd 2.96 to start automatically from udev rule on a Slack 13.37 box.1. I've compiled and installed gpsd from sources and made sure it starts manually.2. I've copied the /lib/udev/gpsd.hotplug and /lib/udev/gpsd.hotplug.wrapper scripts in their places from the source tree and made them executable.3. I've copied the gpsd.rules file from sources into /etc/udev/rules.d4. I renamed it 99-persistent-gpsd.rules to run late in the bootup process.5. I've copied the /etc/default/gpsd file from sources and made sure it has the right settings inside.
Now, for the results. If I plug the gps usb dongle in while the system runs, it starts gpsd if it is not started, and it connects to it just as it should. But if I start the system with the dongle in, gpsd doesn't get started during boot. I can't find any relevant message in /var/log/syslog or /var/log/messages for boot time. There is stuff there from when I plug the dongle in while the system is running though. It's like udev ignores the rules for it at boot time.Is there something in the Slackware boot scripts that would prevent running those scriptssd.hotplug.wrapper which in turn runs /lib/udev/gpsd.hotplug which is a Python script)?Here is the contents of 99-persistent-gpsd.rules (ignore the comments referring to Debian, it was meant for a Debian box). My usb gps adapter is the first one - the Prolific chipset one:
I have just installed slack-13.1 on an acer aspire one netbook from a usb stick by booting the install kernel with noudev. I was able to do a complete install including lilo but upon rebooting my boot hangs when encountering my webcam.I see enough info to note the id as 0c45:62c0. This is a microdia webcam which I may be able to do something about later but in the first instance I'd like to be able to boot my system. The bios is very basic and there is no way to disable devices.
Have just installed 5.4 64 bit on an AMD64 x2 system with 4 GB ram running ESXi4.Text based install went fine, but on reboot starting up it gets as far as 'Starting udev' and just hangs. Checking the performance in ESXi it appears to be using 100% cpu.I have left it for half an hour and it does not progress and the only thing to do is to power cycle the VM.I have searched and found a few suggestions for kernel parameters but they did not make any difference. I can't even get in to a command line as it doesn't boot up far enough.I have reinstalled it several times and also checked the MD5 of the downloaded file and all appears Ok.
I'm hoping someone knows about this one... I'm running the latest CentOS 5.4 with kernel 2.6.18-164.15.1.el5 (x86_64).When I boot the machine, it gets to the udev starting bit, hangs for like 5 minutes, then prints a message "Failed, will continue in the background." Then it boots OK after that.I tried booting again with the kernel option (from grub) "udevdebug", and what I saw when it tried again was a million messages saying it was waiting for "/sbin/pam_console_apply" to return, but I guess it wasn't returning... ;) Again, after 5 minutes, it gave up and finished booting.Now, this host is an LDAP client.
I figured that may have something to do with it as it is likely that pam_console_apply tries to make an LDAP lookup, which is wrong, because networking hasn't even started yet. If I disable LDAP (by removing ldap lookups in nsswitch.conf), I get no pam_console_apply errors from udev and it boots quickly. But that's a bummer, I need LDAP on this box, and I don't want my boot time to be 7-8 minutes. ;)Presumably before, when LDAP was enabled and it waited 5 minutes and then notified me that it will "continue in the background", that it was eventually successful after networking started. LDAP otherwise works fine on this box, just like all the other servers we have.This is new behavior, I've not seen it with CentOS 5.3 and below. Has anyone seen this? Any hints on what I can do to avoid it? It seems like a pam bug or something, but I don't know for sure.
Fedora 12 randomly crashes after a fresh install.Everything is left at its default during the installation except I install KDE and not Gnome.When I try to boot I hit esc at the splash screen to see where it hangs, but it never hangs at the same spot twice. Sometimes it hangs and sometimes it restarts. Its crashed everywhere from starting udev to the login screen.
I've been using kubuntu for the past year because I have the same problem with F10 and F11. I dual boot with Windows 7 for games.
System specs: Motherboard: MSI P45 Platinum Processor: Intel Core 2 Duo E8500 Video Card: Radeon HD4850 Memory: 4GB (2x2GB) Patriot HDD: Main: 250GB SATA Western Digital code....
I just performed an update thru the Update Manager, & on re-boot got this message: ( Ubuntu 10.04.1 LTS, kernel 2.6.32-24-386 ) udevadm trigger is not permitted while udev is unconfigured. Gave up waiting for root device. Common problems :
- Boot args ( cat /proc/cmdline ) - Check root delay= ( did the system wait long enough? ) - Check root= ( did the system wait for the right device? ) - missing modules ( cat /proc/modules; ls /dev )
ALERT! /dev/disk/by-uuid/df0200e3-e6e9-439a-922f-100d92af0c58 does not exist. Dropping to a shell!. BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) built in shell (ash) (initramfs)_ Info: I can boot into older version: Ubuntu 10.04.1 LTS, kernel 2.6.32-23-386. The Update Manager does not seem to want to show any updates that are available.
