* FATAL error message
@ 2004-10-10 15:48 Jim McCloskey
2004-10-16 13:39 ` Jim McCloskey
2004-10-16 16:40 ` Kay Sievers
0 siblings, 2 replies; 3+ messages in thread
From: Jim McCloskey @ 2004-10-10 15:48 UTC (permalink / raw)
To: linux-hotplug
Hello. I hope it's OK to ask a help question here rather than a
developer's question.
kernel: 2.6.7
udev: version 0.032 packaged for Debian testing
All was working very well for me. Then I had two hard shutdowns in a
row caused by power-failures. On the second re-boot, I got this message:
FATAL: udev still active on /dev/
And it won't go away after several cycles of clean shutdown followed
by reboot. I can't actually say that anything is broken. Device files
are still created:
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcsa2'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcs4'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcsa4'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcs3'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcs5'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcsa5'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcsa6'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcs6'
Oct 10 08:03:44 lapdog udev: creating device node '/dev/vcsa3'
Oct 10 08:03:45 lapdog udev: creating device node '/dev/vcs2'
I can mount and un-mount usb devices as needed, I can play
sound-files, use alsamixer, and so on. So far, the only source of
worry is the warning message itself. But that big word FATAL all in
capital-letters is not reassuring.
I've looked for the error-message on Google and on various mailing
lists and not found anything. I've gone through the docs in
/usr/share/doc. I've stopped and re-started the udev init-script but
that had no more effect than re-booting and produces the same warning
message (unsurprisingly). I've also removed and re-installed the udev
package. The message persists through all of this.
My suspicion is that there is some temporary file that should have been
deleted in the course of a clean shutdown which has not been, but I
would really appreciate any advice that might be available here.
Thanks to all for a really great utility,
Jim McCloskey
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: FATAL error message
2004-10-10 15:48 FATAL error message Jim McCloskey
@ 2004-10-16 13:39 ` Jim McCloskey
2004-10-16 16:40 ` Kay Sievers
1 sibling, 0 replies; 3+ messages in thread
From: Jim McCloskey @ 2004-10-16 13:39 UTC (permalink / raw)
To: linux-hotplug
I wrote:
|> All was working very well for me. Then I had two hard shutdowns in a
|> row caused by power-failures. On the second re-boot, I got this
|> message:
|>
|> FATAL: udev still active on /dev/
|>
|> And it won't go away after several cycles of clean shutdown followed
|> by reboot.
....
|> My suspicion is that there is some temporary file that should have
|> been deleted in the course of a clean shutdown which has not been, but
|> I would really appreciate any advice that might be available here.
I was able to solve this problem (on the basis of some advice on the
Debian-user mailing list) by deleting .udev.tdb in /dev.
I had tried deleting the file previously, but I suspect that what I
was deleting was a copy in tmpfs. To really delete the file on the
disk, I had to boot with init=/bin/sh, mount / by hand and then rm
/dev/.udev.tdb.
There's a lot I don't understand about what happened here, but the
immediate problem at least seems to have been resolved,
Jim
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: FATAL error message
2004-10-10 15:48 FATAL error message Jim McCloskey
2004-10-16 13:39 ` Jim McCloskey
@ 2004-10-16 16:40 ` Kay Sievers
1 sibling, 0 replies; 3+ messages in thread
From: Kay Sievers @ 2004-10-16 16:40 UTC (permalink / raw)
To: linux-hotplug
On Sat, Oct 16, 2004 at 06:39:33AM -0700, Jim McCloskey wrote:
>
> I wrote:
>
> |> All was working very well for me. Then I had two hard shutdowns in a
> |> row caused by power-failures. On the second re-boot, I got this
> |> message:
> |>
> |> FATAL: udev still active on /dev/
> |>
> |> And it won't go away after several cycles of clean shutdown followed
> |> by reboot.
> ....
This seems like a debian specific issue, as the debian udev refuses to
run udevstart a second time, if it finds a udevdb in /dev. Please file
the bug in the debian bugtracker.
Thanks,
Kay
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-10-16 16:40 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-10 15:48 FATAL error message Jim McCloskey
2004-10-16 13:39 ` Jim McCloskey
2004-10-16 16:40 ` Kay Sievers
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).