[Bug 165154] Re: NTFS-3G does not mount external disc in kernel 2.6.22

2007-11-27 Thread Yeuclid
*** This bug is a duplicate of bug 115616 *** https://bugs.launchpad.net/bugs/115616 Fixed ! I removed evms as suggested in BUG 115616 and I now have my External drives back. Also Kernel 2.6.22 is OK now. Thanks -- NTFS-3G does not mount external disc in kernel 2.6.22 https://bugs.laun

[Bug 165154] Re: NTFS-3G does not mount external disc in kernel 2.6.22

2007-11-26 Thread Szabolcs Szakacsits
*** This bug is a duplicate of bug 115616 *** https://bugs.launchpad.net/bugs/115616 I can tell you that the issue has really absolutely nothing to do with ntfs-3g. It's the kernel how it (incorrectly?) started to setup raid, dm, ldm, etc. The "device busy" always means that something already

[Bug 165154] Re: NTFS-3G does not mount external disc in kernel 2.6.22

2007-11-26 Thread fishor
*** This bug is a duplicate of bug 115616 *** https://bugs.launchpad.net/bugs/115616 ** This bug has been marked a duplicate of bug 115616 Device-mapper errors: dm-linear, lookup failed -- NTFS-3G does not mount external disc in kernel 2.6.22 https://bugs.launchpad.net/bugs/165154 You rec

[Bug 165154] Re: NTFS-3G does not mount external disc in kernel 2.6.22

2007-11-26 Thread Yeuclid
Yes, certainly Find attachment and Grep result here: dpkg -l | grep ntfs ii libntfs-3g12 1:1.913-2ubuntu1 ntfs-3g filesystem in userspace (FUSE) libra rc libntfs-gnomevfs 1.13.1-6 NTFS GNOME virt

[Bug 165154] Re: NTFS-3G does not mount external disc in kernel 2.6.22

2007-11-26 Thread fishor
Please include the following additional information: 1. Please run the command "dmesg > dmesg.log" after enabling you external USB HDD and attach the resulting file "dmesg.log" to this bug report. 2. Please run the command "dpkg -l | grep ntfs" and post the result here. -- NTFS-3G does not mou

[Bug 165154] Re: NTFS-3G does not mount external disc in kernel 2.6.22

2007-11-26 Thread fishor
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW] https://wiki.ubuntu.co