Windows partitions not accessible

[Robert]

Binary package hint: linux-source-2.6.22

When I look via System Settings/Disk & Filesystem I notice that my windows partitions are disabled. When I try to enable them I get the following error :

An error occurred while enabling /media/hda5
The system reported: fuse: mount failed: Device or resource busy
FUSE mount point creation failed
Unmounting /dev/sda5 (Gegevens)
 When I click Details I get the following additional info :
Return code from mount was 10
"system error (out of memory, cannot fork, no more loop devices)"
"user interrupt"

I checked when running kernel 2.6.20. There all my windows partitions are accessible.

[Greg Copenhaver (greg-gcopenhaver)]

Confirming this bug.

This is what I get when I try mounting my windows ntfs partition:

$ sudo mount /media/sda2
fuse: mount failed: Device or resource busy
FUSE mount point creation failed
Unmounting /dev/sda2 ()

I am currently running kernel version 2.6.22-13-386...last time I used 2.6.20 I had no problems mounting the windows partition.

[Bin (guobinb)]

same here, my system was upgraded from 5.10-6.06... 7.10
I have two windows partitions, fat format, and they are both unaccessable at boot up, but it seems my /etc/fstab file
is fine.
And I couldn't mount it by hand either

[Robert (robertvanreij)]

Problem is resolved.

I tried to change /etc/evns.conf and put in "*" in the sysfs_devices section of /etc/evms.conf. It worked for me. See this bugs for more detail:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/115616

[Ethan Bissett (draimus-deactivatedaccount)]

This problem occurs on my system. At first when I upgraded from 7.04 to 7.10 mounting my windows disk worked (just double clicked on the drive icon in nautilus). However now it does not work. I do not have evms installed so it can't be related to that.

What's worse is the way NTFS-3g is integrated in 7.10, manually performing a "mount -t ntfs /dev/sdb1 /mnt" doesn't allow me to use the old read-only kernel driver.

[Szabolcs Szakacsits (szaka)]

The relevant device is already locked by probably the device mapper, LDM or md.

Look for mountable devices under /dev/mapper. kpartx -a /dev/mapper/brand_blabla may be needed to create the mountable partitions under /dev/mapper.

In the other two cases follow the relevant instructions how to create a mountable device or what to mount.

[Brian Murray (brian-murray)]

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Przemek K. (azrael)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The version of Ubuntu that you were using has reached its End Of Life. Please test the latest Ubuntu version (9.10) and report a new bug if necessary.
https://help.ubuntu.com/community/ReportingBugs