Noticed this on boot up the other day, but it doesn't seem to have a negative effect. Everything appears to be running just fine.
"Triggering udev events: /sbin/udevadm trigger --type=failed"
Is this something that needs to be resolved or ignored?
I'm having a bit of a nightmare with my ubuntu hardy server (using hardware raid 1+0). Following a power cut I get the message "udevadm trigger is not permitted while udev is unconfigured" on boot. Before the power cut the server had been up for ~450 days.
I managed to get access to /boot (which was empty) by using the repair option on the alternate cd and mounting /dev/myserver/root. I've installed the packages linux-headers-server, linux-image-server and linux-server. The various 2.6.24-29 files were installed and update-initramfs was automatically run (I noticed others have used update-initramfs to solve this error when upgrading from 8.04 to 10.04 in some posts I've read). No luck with this though - just the same error booting. I've also tried reinstalling udev, but again with no success.
I rebooted and pressed the Esc key to get the boot menu up. Only options were for kernel 2.6.24-26 (rather than the 2.6.24-29 just installed). I ran the recovery option anyway and got "/dev/mapper/myserver-root does not exist".
I use Parallels 5 for Mac (10.6.4). I started my Ubuntu 10.4 virtual machine and it didn't load the Ubuntu Gnome desktop. In stead I did get a command line prompt. I could login with normal username and password, rebooted again, but same result.I tried to update the system with code...
View 4 Replies View RelatedI 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.
I was updating the security updates in my deskptop. It did not executed successfully even after 7 hours. It remain just like hang up. So I switched off the PC and rebooted. Then it is showing the error: "udevadm trigger is not permitted while udev is unconfigured. Gave up waiting for root device."
Now my Lucid Linx is almost dead. There is also no 'Repair' option while booting from Ubuntu 10.04 CD. Pl help to restore it.
I upgraded to the last ubuntu last week and since I get the error: "udevadm trigger is not permitted while udev is unconfigured."I followed different posts on the forums but none helped: [URL]I did the sequence:
"1. Boot liveCD
2. "sudo fdisk -l" to find your boot disk, in my case it is /dev/sda5.
3. "sudo mkdir /media/newroot"
[code]....
Scheduled Tasks is giving me a hard time. I have a command set for 23:00 daily as "gthumb -f ~/Pictures/ScheduledPic.jpg", but when the time rolls around, nothing happens. The strange thing is, it does work when I press "Run scheduled task." I get the same results if I select a different time or change it to "google-chrome ~/Pictures/ScheduledPic.jpg". My other scheduled task, a Perl script, works fine.
View 2 Replies View RelatedI cannot boot my 9.10 system as of this morning. I see these messages:
insserv: warning: script 'dbus' missing LSB tags and overrides
insserv: warning: script 'gdm' missing LSB tags and overrides
insserv: warning: script 'K20acpi-support' missing LSB tags and overrides
insserv: warning: script 's99webmin' missing LSB tags and overrides
/sbin/insserv failed, exit code 1
I then hear 2 or 3 faint clicks and I get a blank screen, with 2 faint lines at the top. I have been searching and trying to figure this out, but to no avail.
We Are Using Centos 5 64Bit with Kernel 2.6.18.92 with Amd Athlon ProcessorThe problem when calling setsockopt it return error errno:22 InvalidargumentThis code run on Macos ,Sunsolaris ,But fail to execute on Centos 5 64bit & The SCTP mailing group told me that this problem belongs to centosexample form ibm webside
/*
server
*/
[code]....
I'm running Slacware current. Ran the updates this morning, including kernel 2.6.33.2. I always get nervous about that since something often goes wrong. Sure enough -
trying to boot I get No kewrnel modules found for Linux 2.6.33.2-smp mount: mounting /dev/sda9 on /mnt failed: No such device ERROR: No /sbin/init found on rootdev ( or not mounted ) and failure to proceed with booting. I got an original warning about the initial ram disk being too big to fit and switched to using generic kernel, and yes I did run lilo afterwards and did add the initrd.gz line. I run Ubuntu on the same laptop and have to boot into that and work as chroot in my Slackware partition to try and fix things.
I haven't updated my centos box for almost about a year, my theory is if it ain't broke don't fix it.These last two weeks I've been replacing hardware, a motherboard, memory, processor, and a hard-disk. Everything worked fine with the current 2.6.18-128.1.10, but I decided that I should upgrade to the latest along with all the new packages. But in doing so I would need to recompile the driver module for the raid controllers, rr1740. So I recompiled them using the 2.6.18-164.1 build while I was in kernel 128. When I was done, I restarted the machine and when it booted to the new 164 kernel, it came back very long error messages but here's what I can remember off the top of my head.
View 14 Replies View RelatedI am running Red Hat Enterprise Server 6.0 I am having issues getting kerberos configured as a client to join a domain. Im getting below error message. "Failed to join domain: failed to connect to AD: KDC has no support for encryption type"
View 9 Replies View RelatedI'm currently trying to setup Slackware 13.7 on a server, using software RAID 1. I'm using the README_RAID.TXT document at the root of the Slackware disc as a reference. Anyway, here's what I have so far.
/dev/md1 -> /boot partition
/dev/md2 -> swap partition
/dev/md3 -> / partition
Code:
[root@raymonde:~] # fdisk -l /dev/sd{a,b}
Disk /dev/sda: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders, total 80293248 sectors
Units = sectors of 1 * 512 = 512 bytes
[code]....
I created an initrd image using mkinitrd -F, added an according stanza to /etc/lilo.conf and ran 'lilo' after that. Now I can boot on the vanilla huge kernel all right. But I can't seem to boot on the generic kernel. Whenever I try to do this, the boot process stops short on the following error message:
Code:
mount: mounting /dev/md3 on /mnt failed: Device or resource busy
ERROR: no /sbin/init found on rootdev
I've recently updated my Slackware 13.1 system to the Slackware current. Although I have created my "initrd" image without specifying the "-u" option to "mkinitrd" it still starts up "udev".
That is causing me some difficulty because I am using "dmraid" to detect my RAID arrays. I had created my own device names such as "/dev/sdr2" for my root partition. With 13.1 I had no problem, since "udev" was not started by the "initrd" unless the "-u" option was provided. The current version seems to start up "udev" even without that option.
Is there a way to disable "udev" in the "initrd", or is there a way to specify custom "udev" rules for an "initrd"? I tried placing a "10-local.rules" file in the "etc/udev/rules.d" directory of the "initrd-tree" but that file had no effect on the device names generated by "udev" during the "initrd".
Here is my script that creates the "initrd".
Code:
ROOTDEVNAME="/dev/sdr2"# Name of root device
LINUXVER="2.6.35.7-smp"# Linux modules version
CLIBVER="2.12.1"# C library version
ROOTDIR="/boot/initrd-tree"# Location of root filesystm
[code]....
It will be helpful for me to understand "udev" issues related to an "initrd" because I will eventually try to use "mdadm" instead of "dmraid". So far I have only been able to get my system to boot from the RAID array using "dmraid" and I often run into new problems when I update Linux. Still, Slackware has proven to have the best support for booting from my RAID array because of the user community, documentation and flexibility.
Are there any prerequisites which much be met in order for udev to create /dev/usb/hiddev* nodes?
I have two Slack 13.0 systems, each connected to a APC UPS via USB, one of which creates a hiddev0 node and the other doesn't. apcupsd can't find the UPS unless this node is present.
The "working" system has been stable in its current configuration for so long that I honestly can't remember if I had to tweak anything in this regard. I've verified that it doesn't use any local udev rules to create this node, and to the best of my knowledge there are no external scripts or processes which would create it either.
The non-working system has a similar configuration - no local rules and/or scripts which touch usb devices or nodes.
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:
Code:
# udev rules for gpsd
# $Id: gpsd.rules 5861 2009-08-03 13:41:01Z bzed $
[code]....
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.
View 14 Replies View RelatedThe value of envar PATH for processes run by the udev system is "/usr/gnu/bin:/usr/local/bin:/bin:/usr/bin:.". If peer review (that's you!) agrees it is a poor choice how can I submit an enhancement request? The man pages do not say anything about bug reporting. Here are reasons why it is a bizarre choice:There is no /gnu/bin directory on as-installed Slackware. /usr/local/bin is empty (or very nearly empty?) on as-installed Slackware. Processes running under udev run as root; having "." in PATH is not good practice when running as root. Processes running under udev are likely to be doing "system" work so executables from the sbin directories are likely to be used. For example, udevadm itself is /sbin/udevadm. Presumably this PATH is set by udevd itself; it is not the PATH in effect when udevd is started by rc.M. AFAIK udevd's PATH is not configurable. The workaround is for processes initiated by udev to set a sane PATH for themselves, perhaps "/usr/sbin:/sbin:/usr/bin:/bin". EDIT: seen on Slackware 13.0 32 bit. EDIT2: rc.udev is run from rc.S, not rc.M as stated above
View 7 Replies View RelatedI just bought a USB hard disk and when I plug it in it gets mounted as owner root and group root. I tried writing a udev rule for it based on the following guide:Nothing seems to work, it always mounts as root. Slackware 13.1, KDE, Dell Optiplex GX280, Western Digital Passport USB 320 gig drive.I am a member of the plugdev group, so it seems to me a rule should not even be necessary.
View 14 Replies View RelatedSome times I boot up, and udev has labelled what is usually eth0 as eth1. Of course, my rc.inet1.conf is configured for seeing internet at eth0, so no connection, quite obviously. Then I reboot and the device label is back to "eth0". Actually I'm still not able to get connected, even at eth0, despite my nameservers being OK, and the default route gateway being all OK. PS. I have a static ip address.
View 3 Replies View RelatedI switched today to slackware-current on one of my desktops to play with it and ran directly into a problem.
Since ages my lilo.conf has two entries for slackware. One for runlevel 3 and one for runlevel 4.
Code:
Since the upgrade this is no more possible because I get a kernel panic as soon as udevadm trigger is called. The stack says something about an unknown boot option. Because that i removed the append lines from my lilo.conf and i was able to boot the system. The crash happens when udev is called from within the ramdisk and afterwards. I tried both.
My question is now. Is this a bug in udev or expected? I have this setup since at least 5 years and had never problems with that. What do I have to do to be able to select the runlevel at boot time?
Let's get clear with all bin and sbin folders(from filesystem hierarchy standard):
So the question is: Why there are so many directories and what are the meanings of /usr/sbin, /usr/local/sbin and /usr/local/bin?
Many programs are distributed through archives and we have to build them from source code. Usually they have makefile so it's quite easy. This process involves creating files in usr/local/lib, usr/local/bin... usr/local/whatever without creating specific folders for a given program.
I think it's not right because if we need to remove the program we have to manually delete every of its files if the program's creator didn't take care of it.
Wasn't sure were to put this go here goes.When I plug in my Canon Powershot Digikam starts up, which is great. But... when I plug in my iPod Touch to recharge Digikam also starts up, how can I put a stop to the latter?
View 2 Replies View RelatedWhen an SD card is inserted before/at boot time, everything works fine, meaning recognized by kernel and mounted to userspace.When an SD card is inserted after boot time, the kernel doesn't 'see' the hardware change not triggered, so no block device /dev/mmcblk0{p1}, so nothing to mount.This behavior is not openSuSE specific, when booting SystemRescueCD-2.0.1, the same behavior is noticed.SD card inserted after booting:
Code:
linux-j60s:~ # hal-device | grep mmc
linux-j60s:~ #
[code]...
I am learning about linux memory and hugepages, and know that hugepages basically is just memory that manages memory. I thought I'd experiment with the subject, and wrote a very small C program [URL] that basically just eats 20 GB of memory. The idea was that I would use this small C program to see how big the page table would get when handling large areas of memory when I'm not using hugepages. After running the program on my RHEL 5 server I was expecting the PageTable to be huge, but found that it was only about 43 MB. The page size on my RHEL box i 4 kB. Why I'm not getting the major PageTable size issue I was expecting?
View 2 Replies View Relatedjust set up a windows server and other windows boxes send alerts to it no problem.Yesterday I configured my linux box (RHEL 5) using /etc/sysconfig/syslog and /etc/syslog.conf so that all alerts would go to the syslog server.There are no external firewalls involved and while the firewall is working on my linux boxI have made sure port 514 TCP/UDP are let through.Ive checked syslogd and klogd are running.I've also applied the '*@10.20.30.40' line in etc/syslog.conf. Basically Id like everything to go to the syslog server.Now if I telnet to the syslog server on port 514 I can type text on the linux box and it comes through on the syslog server. Great - but no syslog alerts seem to come through normally, even when I reboot the box.I've tried *., .*, and * to no avail, ive got an entry in my hosts file for the server 10.20.30.40 and tried using a name instead of an ip address, no luck.
View 1 Replies View RelatedI installed slackware 13.1 x86_64 bit with multilib, and its been about a month already, I'm really enjoying slackware but I am being troubled with my nvidia card, and I need to get my 3D acceleration working. And I've been looking around the net for information and kept on trying to make my nvidia card to work but to no avail. I cant get X to start, once I put in a xorg.conf stating to use the nvidia card. After troubleshooting for almost 2 weeks and now at my wits end, I now come humbly looking for help in linuxquestions slackware community forum.I've installed nvidia 64 bit kernel, drivers from slackbuilds (version 256.44). The laptop model I'm trying to get it working is an -ASUS K52J Intel Core i3 2.40Ghz with 2GB RAM and with an Nvidia Geforce 310M with 1GB dedicated VRAM.
View 14 Replies View RelatedProblem occured yesterday and has added 3 mins to my boot time. all i can say about it is that it occured after a yum update and then a crash while using wine. i navigated to the file but really cant say much about it. however the pci call there makes me wonder if it is related to the post below.
Starting udev:
Wait timeout. Will continue in the background.
I grabbed the new lubuntu 10.10 from [URL] but it turns out I'm having a problem installing it on my netbook (Asus Eee PC 1015PED). While installing, this error pops up:
Quote:
The attempt to mount a file system with type ext4 in SCSI2 (0,0,0), partition #1 (sda) at / failed.You may resume partitioning from the partitioning menu.I'm installing via USB and have selected the option to erase everything and use the full HDD.
Edit: I had Xubuntu installed before.
Unable to install Ubuntu 9.10 on a new internal harddrive. The hardrive contains no operating system. This hardrive is the only drive present in the system.
Whenever the installation trys to mount the ext4 partition the following error appears: The attempt to mount a file system with type ext4 in SCSI1 (0,0,0), partition #1 (sda) at /failed
Iv'e tried over and over to get past this error to no avail.