DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My Debian etch system (kernel 2.6.15-1-686-smp) stalls indefinitely during boot. I can press control-c to end the stall. A lot of udevd_event messages flood the screen before and during the stall.
I've tried booting the kernel in recovery mode, but it still hangs at the same point.
Nothing out of the ordinary is logged in dmesg or /var/log/messages.
Why is it not an option? What's your alternative? What's the use of a system with the "latest and greatest" software that doesn't boot? Well, this is Linux: it's your choise!
Did it boot correctly before or does this problem occur from the first reboot after installation?
Tons of Fun,
My network info hasn't changed. The network configuration happens after the stall, and without problems.
Dutch Master,
Because it's not possible to go from testing to stable without reinstalling the system. And since Etch is scheduled to go to stable in a couple of months, it doesn't seem like it's worth the trouble to completely reinstall my system.
...but I can't be sure since I leave my computer running for so long between reboots. Is there any indication of what's wrong from looking at the bootchart?
DutchMaster is a very smart guy, but he's hung up on Sarge as a distro that people should be using. I think Etch is much more satisfactory for most people.
Did you upgrade from Sarge to Etch or do a fresh install?
Did you install udev as part of that tutorial you were following, or was it installed by Etch?
What Kernel are you using?
Ok, I see your point. But, as Etch still takes a few months to become stable you're stuck with an unusable system during that time. As I see it, you have three options:
a) re-install everything (either Sarge or Etch) and forget about udev for the moment
b) uninstall udev from your system, but that might be a PITA (pain in the *ss ) and might take you more time then re-installing the lot
c) use a rescue CD like Knoppix to try to get rid of udev, but I doubt if that will work: dunno if apt/dpkg/aptitude will accept a different target, i.e. your harddrive, to it's own system. AFAIK it won't...
I'm afraid that dmesg won't be of any help, it's data is lost/overwritten with every reboot and I'm not sure you can redirect it's output to a file during the bootprocess. I don't know enough about udev to be of any help there I'm afraid... One more question though: did you set up the automount stuff on udev from the last article you've mentioned? Or did udev go nuts right after you've installed it?
<edit>Rickh: you might be right. But Etch is still in Testing, which means that it can and at some time will be broken! It's less likely to happen comparing with Sid/Unstable, but the stable branch provides, well, just that: a stable distro. But maybe I'm biased as I've got an unusable Etch system before when using an older net-install CD...</edit>
Last edited by Dutch Master; 09-12-2006 at 06:17 PM.
I did a fresh install of Etch. (I actually meant to install Sarge, but I grabbed the wrong net-install disc. I decided to stay with Etch after seeing how stable it was.)
I installed udev manually.
I'm using kernel 2.6.15-1-686-smp.
Dutch Master,
I'm very against your first suggestion, to reinstall everything. It's my personal preference to figure out the cause of problems, rather than reinstall as a Windows user would.
I installed udev and automount several months ago, so it's possible that before I manually installed udev, the Etch kernel supported devfs, but now it doesn't.
Code:
# apt-get remove -s udev
Reading package lists... Done
Building dependency tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:
The following packages have unmet dependencies.
linux-image-2.6.15-1-686-smp: Depends: initramfs-tools but it is not going to be installedor
yaird but it is not going to be installedor
linux-initramfs-tool
E: Broken packages
Quote:
did you set up the automount stuff on udev from the last article you've mentioned? Or did udev go nuts right after you've installed it?
I did set up automount from that article. I'm not sure exactly when udev went nuts, because I leave my system running for so long between reboots.
Also it probably wouldn't hurt you to get a newer kernel. Udev was still giving intermittent problems until sometime in the 2.6.16 series. Do the above first, tho
I understand your view on re-installing an OS and frankly, I agree! But at some point you must be pragmatic about it: how much time does it take to re-install your system compared to solving the problem by re-tracing your steps (especially as you have such long intervals between reboots) and studying man-pages and such. Ok, I admit that rolling your system back helps you learn a lot on how things work, but is that the purpose of a work-station? (I presume you actually use that machine to do something other then playing Patience )
IMHO a computer is an aid for a human to help him/her to do certain tasks more efficiently or without human intervention, not to spend weeks of tinkering and still it doesn't do what you want it to do... But that's just my
Dutch Master,
I was reluctant to say it, because I knew I'd be scolded for not using Debian stable, but this is a server. So reinstalling isn't an option. I'd have a LOT to reconfigure if I reinstalled this system.
rickh,
I tried your suggestion, and I still have the same exact problem.
I was really surprised that I didn't need hotplug. Does udev replace it?
I don't know what to say. I would still try upgrading the kernel. With any kind of luck the kernel image reconfigure might have cleared up whatever problem you were having there, and it would probably also upgrade udev.
If that doesn't work, a reinstall is quick if you have your /home on a separate partition. While partitioning, just don't reformat /home. You'll get a few warnings about new users being assigned to groups they don't own, but it's insignifficant and irons itself out quickly. I break mine pretty regularly, probably wind up reinstalling every 6 months or so, but it's a 45 minute process to get it running again. Keeps you busy tweaking for a while, but that's the fun part.
here's what finally fixed my problem (this is from a #debian irc bot):
Code:
<dpkg> extra, extra, read all about it, fresh udev config is when upgrading to
a new major release of udev it is often beneficial to get fresh udev
config files: dpkg -P --force-depends udev && apt-get install udev
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.