>From 14.04.3 LTS,
[2.643930] systemd-udevd[186]: inotify_add_watch(7, /dev/sda1, 10)
failed: No such file or directory
Never fixed doesn't mean invalid.
** Changed in: udev (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubunt
This version is now outdated and no more supported
** Changed in: udev (Ubuntu)
Status: Confirmed => Invalid
** Changed in: dmraid
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I am also affected by this bug. At start up I get the message
"udevd[135] inotify_add_watch (6, /dev/dm-0, 10) no such file or
directory". I have a fake raid which is probably causing the problem. I
also put this in my /etc/rc.local to discover and "activate" my raid
disks: sudo dmraid -r, sudo dm
Hi,
I am also getting the same, on a kvm hypervisor running Ubuntu 12.04 LTS
:
Sep 6 01:19:31 ns5004890 kernel: [188914.076691] EXT4-fs (dm-8): mounted
filesystem with ordered data mode. Opts: (null)
Sep 6 01:19:32 ns5004890 udevd[30252]: inotify_add_watch(6, /dev/dm-8, 10)
failed: No such fi
I don't need cryptsetup on this. ...might be better to provide a fix for
this issue. Ionotify should be working even without cryptsetup : i see
no reason why it should be necessary to install it.
Although it's true : it really fix this issue!
--
You received this bug notification because you ar
Got this while reinstalling the operating system inside a vps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/581566
Title:
udevd inotify_add_watch no such directory error for physical volumes
To ma
I have tried "update-grub", "update-grub2" solutions,
and also Neptune Ning's solution by comment out the line (OPTIONS+="watch")
in "/lib/udev/rules.d/60-persistent-storage-dm.rules" file.
But I still see the line below during bootup:
udevd[254]: inotify_add_watch(6, /dev/dm-0, 10) failed: Inval
I'm using Ubuntu12.04 with updated kernel 3.2.0-34-generic.
The system is installed by Ubuntu-12.04-alternate-amd64 ISO file with LVM
partition:
root@Ubuntu1204:~# uname -a
Linux Ubuntu1204 3.2.0-34-generic #53-Ubuntu SMP Thu Nov 15 10:48:16 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
root@Ubuntu12
Neptune Ning's solution worked for me. Thank you !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/581566
Title:
udevd inotify_add_watch no such directory error for physical volumes
To manage notifi
for the record, I am using udev-175-0ubuntu9.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/581566
Title:
udevd inotify_add_watch no such directory error for physical volumes
To manage notificati
the solution in the previous comment does not work for me...
we are using ubuntu12.04 as xen dom0, and lvm as xen storage. when shutting
down a domU we got these error in the syslog。and I found udev using the lvm LV
device and prevent me from removing it some seconds afterward
---
Same problem and solution as mentioned in the previous comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/581566
Title:
udevd inotify_add_watch no such directory error for physical volumes
To m
I have found this fault too with Ubuntu Server 12.04LTS. I had installed
LVM2 non-raid (it is a VM anyway) for a 2nd drive to be mounted at
'/home'.
The boot-time message I saw was:
udevd[252]: inotify_add_watch(6, /dev/dm-0, 10) failed: Invalid argument
As others have noted, installing cryptsetu
Same here:
$ uname -ra
Linux DELLka 3.2.0-17-generic #27-Ubuntu SMP Fri Feb 24 22:03:50 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
$ sudo fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
One whole year and the bug is still unassigned? Is there nobody in charge of
the udevd module?
I have installed 10.04LTS server lately as a home server with LVM but no Raid
as using Rsync is sufficient for me.
My system says there are no pending updates but nonetheless I do see the
udevd-work bu
Some *possibly* better way to fix this error message :
* What I have done :
- boot from the latest linux kernel version installed on my system
(2.6.32-32)
* The highly probable reason why this fix the error boot message :
- I, previously, upgraded both dmsetup + dmraid + libdmraid and linux
Excume
My english is bad, i have solution for this, in reality this isn't a
bug, the problem comes from bios (i believe this is due from a old pc)
you must go to bios and move from apic to PIC, for me this is impossible
do this, because i have dual boot and windows does not boot if i do
this, if s
My english is bad, i have solution for this, in reality this isn't a
bug, the problem comes from bios (i believe this is due from a old pc)
you must go to bios and move from apic to PIC, for me this is impossible
do this, because i have dual boot and windows does not boot if i do
this, if someone c
I had this issue relating to my LVM volume (I don't have any dmraid
setup).
I tried removing the dmraid package but this didn't help.
I then saw that installing 'cryptsetup' helps -
http://ubuntuforums.org/showthread.php?t=1500937
So I installed 'cryptsetup' and the error went away. No idea why!
So I would not use the dmraid controller then and instead create a software
raid by using the Linux capabilities for that? Did I get that right?
Think I can manage to do that.
But how can I get rid of the dmraid metadata on the disks?
--
You received this bug notification because you are a memb
@bash.vi
The reason that dmraid will halt your system from booting is that the raid
metadata will still be in your disks.
To stop dmraid from recognising your disks as a raid you have to purge this
data from your disks.
Dmraid can only identify disks as in a raid set by this metadata.
I get th
@Mark Wilmoth
Experienced the same. After reading this thread I tried installing 10.10 on the
Revo with 'encrypt home directory' which, obviously, will install cryptsetup
the startup process went one stop further and then hang up while showing the
splash-screen (it didn't show that before).
Sta
oh, also I would like to add this, cuz maybe it could help find the problem or
a solution to anyone who is more skilled than I am:
Installing the dmraid modul on my Ubuntu 10.04 setup (which is installed on the
same computer, but on a 'normal' HDD, and which does NOT touch the SSDs) this
system
I have these error messages with Maverick running on a Sony VGN-AR590E
laptop with Intel Mobile 82801 SATA RAID Controller. The first time I
installed Maverick, it was causing random boot failures. After
installing cryptsetup, it fixed it, but I still experience the error
messages (udevd-work [xx]
** Changed in: dmraid
Status: New => Confirmed
** Changed in: dmraid
Assignee: (unassigned) => ubuntu-dmraid (ubuntu-dmraid)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/581566
Title:
Same as Simon Simon Rodan - I need dmraid since I want to boot from my
(damned expensive) Revodrive X2, which is in fact nothing else but a
dmraid connection 4 Sandforce SSDs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I have similar problems. Since I can't see relevant output in my log
files, I am attaching screenshot which seems to be more verbose.
** Attachment added: "DSC01027_cr.jpg"
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/581566/+attachment/1753383/+files/DSC01027_cr.jpg
--
You received t
I don't think this is a dmraid issue (since I've removed dmraid and the
bug persists). However, since my LVM partitions are generating these
errors I wonder if it could be that certain partition formats (LVM and
dmraid) are unreadable by inotify, hence the error?
--
udevd inotify_add_watch no su
** Also affects: dmraid
Importance: Undecided
Status: New
--
udevd inotify_add_watch no such directory error for physical volumes
https://bugs.launchpad.net/bugs/581566
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
Hey Folks,
This might well be a bug in dmraid, but purge dmraid is not a solution either.
Because I DO use dmraid for a Raid 1 Array and get the Same error.
udevd-work [xx]: inotify_add_watch(6, /dev/dm-0, 10) failed: no such file or
directory
--
udevd inotify_add_watch no such directory error
Thanks Christian for you work.
I quite forgot this issue as it was not really a problem for me.
In my case I never dmraid installed.
When I use "sudo update-grub" now, this error is not displayed anymore.
--
udevd inotify_add_watch no such directory error for physical volumes
https://bugs.launchp
Christian
Many thanks for tracking this down.
The only partitions that generated errors on my system were the LVM
managed extended partitions.
--
udevd inotify_add_watch no such directory error for physical volumes
https://bugs.launchpad.net/bugs/581566
You received this bug notification becaus
WOW...
T.Y. for your work...
(^_^)
now i test it...
Good Work
--
udevd inotify_add_watch no such directory error for physical volumes
https://bugs.launchpad.net/bugs/581566
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
GOOD NEWS EVERYONE!
I did it! I mean track it down ... it IS indeed weird and took me 4
hours... :/
Ultrashort FIX (if not boot disk is affected):
- sudo aptitude purge dmraid
YES! It is the f*ke-Raid module, that causes such headache.is it?
NO! It is the Ubuntu Installer...
Reproduce:
- S
** Description changed:
Binary package hint: udev
-
udevd-work [91]: inotify_add_watch(6, /dev/sda1, 10) no such directory
udevd-work [94]: inotify_add_watch(6, /dev/sdb4, 10) no such directory
udevd-work [95]: inotify_add_watch(6, /dev/sdb5, 10) no such directory
These are the pa
I'm fairly certain that this happens because the kernel device-mapper
removes the devices associated with the partitions that make up the LVM
set *before* udev has an opportunity to process the original event. In
essence, udev is racing.
--
udevd inotify_add_watch no such directory error for phy
I had the same issue, and the solution suggested by tuxfrank worked for me,
too. But I agree with Sic Volo and Brett Slahlman -- the bug remains, we just
covered it for a while by a workaround.
Besides, after this bug appeared, my mother filesystem started acting weird,
announcing severe errors
this bug affected me too and installing cryptsetup fixed the bug. now i
can see my splash :P
--
udevd inotify_add_watch no such directory error for physical volumes
https://bugs.launchpad.net/bugs/581566
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Installing cryptsetup fixed it for me too, but I don't really consider this to
be a fix. I don't need cryptsetup, and don't like the idea that I'm loading
something I don't need upon every boot to mask a bug. I notice this bug is
confirmed but still unassigned. Is it considered low priority? I'v
installing cryptsetup fixed it for me too.
But the bug remains. Now somebody needs to know WHAT cryptsetup is fixing
exactly and have this fix pushed upstream.
--
udevd inotify_add_watch no such directory error for physical volumes
https://bugs.launchpad.net/bugs/581566
You received this bug no
Hi all,
I have not been able to reproduce the error by grub-update as Nico
suggested.
Have followed tuxfrank's advice and - indeed - error disappears after
installing cryptsetup
Cheers
Frank Claessen
--
udevd inotify_add_watch no such directory error for physical volumes
https://bugs.launchpa
I make the Frank test and after installing cryptsetup the problem no longer
occurred for me too.
I think that cryptsetup disables something about udev.
--
udevd inotify_add_watch no such directory error for physical volumes
https://bugs.launchpad.net/bugs/581566
You received this bug notificatio
Same problem here in 3 servers after upgrading from 9.10 to 10.04.
All 3 servers have LVM with multiple physical volumes
--
udevd inotify_add_watch no such directory error for physical volumes
https://bugs.launchpad.net/bugs/581566
You received this bug notification because you are a member of Ub
I had the same problem. After installing cryptsetup the problem no
longer occurred. I assume that the cryptdisks-udev files in the
/etc/init/ and /etc/init.d somehow influence the boot process in a
positive way.
I'm curious to know if this solves the problem for you too...
Greetings,
Fran
To reproduce :
$ sudo update-grub
error: cannot open `/dev/sdb' while attempting to get disk size.
error: cannot open `/dev/sdb' while attempting to get disk size.
Generating grub.cfg ...
error: cannot open `/dev/sdb' while attempting to get disk size.
error: cannot open `/dev/sdb' while attemptin
I recently update from 8.04LTS up to date to the new 10.04LTS.
Same problem for me when rebooting after doing a grub update.
udevd-work [XXX]: inotify_add_watch(x /dev/sda7, x) failed: no such file or
directory
/dev/sda7 is my main lvm partition :
Périphérique . IdSystème
/dev/sda7
Same problem here. During the boot process, before the Ubuntu boot logo
appears, the following message appears:
udevd-work [XXX]: inotify_add_watch(6, /dev/sdb9, 10) failed: no such
file or directory
(Where XXX might be a process pid number, its value varies). Sometimes a
second message appears a
sorry, my pc as crashed... is death definitelly...
now i can buy a new pc
new pc= news bug
this bug is not confirmed a in to the new pc...
good work friends...
hem, sorry for my english...
--
udevd inotify_add_watch no such directory error for physical volumes
https://bugs.launchpad.net/bugs
Same problem on a fresh kubuntu lucid install. The messages seem to
randomly oscilate between real devices (not partitions) though, /dev/sda
/dev/sdf /dev/sde etc. Makes the boot look ugly and somewhat slower but
does not seem to cause other issues
** Changed in: udev (Ubuntu)
Status: New =
This bug makes my boot-process stop for about 10-15 seconds, so it is
really "bugging" me - what can be done to improve the situation?
--
udevd inotify_add_watch no such directory error for physical volumes
https://bugs.launchpad.net/bugs/581566
You received this bug notification because you are
** Tags added: boot
--
udevd inotify_add_watch no such directory error for physical volumes
https://bugs.launchpad.net/bugs/581566
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
bug 441367 could be related, although it does not seem to be a real
duplicate
--
udevd inotify_add_watch no such directory error for physical volumes
https://bugs.launchpad.net/bugs/581566
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirming this bug, similar situation here with multiple partitions
defined as LVM physical volumes belonging to a volume group.
> sudo fdisk -l /dev/sda
>
> Disk /dev/sda: 320.1 GB, 320072933376 bytes
> 255 heads, 63 sectors/track, 38913 cylinders
> Units = cylinders of 16065 * 512 = 8225280 by
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/48586370/BootDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/48586371/Dependencies.txt
** Attachment added: "Lspci.txt"
http://launchpadlibrarian.net/48586372/Lspci.txt
** Attachment adde
54 matches
Mail list logo
