|
Bugzilla – Full Text Bug Listing |
| Summary: | Mounting NTFS partitions as part of Filesystem creation fails | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Andrew Wafaa <awafaa> |
| Component: | Installation | Assignee: | E-mail List <bnc-team-screening> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | k.e.wagner, liz, mmeeks, peterhead |
| Version: | Alpha 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
The mount command prepends "/mnt" to the mount point, causing the failure. ---- Mounting /dev/sda1 to /windows/C mount -r -t ntfs -ousers,gid=users,fmask=133,dmask=022 /dev/sda1 /mnt/windows/C: ---- Should be: mount -r -t ntfs -ousers,gid=users,fmask=133,dmask=022 /dev/sda1 /windows/C: *** Bug 360440 has been marked as a duplicate of this bug. *** *** Bug 359667 has been marked as a duplicate of this bug. *** *** Bug 356195 has been marked as a duplicate of this bug. *** Bug 360566 includes a workaround for users and a summary of the problem with further links and a reference to bug 354113 where the issue is being analazed for ntfs-3g. Indicated in this bug is also that the kernel ntfs filesystem might have problems as well, it is also discussed in bug 360566. *** This bug has been marked as a duplicate of bug 360566 *** *** Bug 364546 has been marked as a duplicate of this bug. *** |
After formatting ext3 partitions system fails to mount NTFS partitions with the following error: Failure occurred during following action: Mounting /dev/sda1 to /windows System error code was: -3003 mount -r -t ntfs -ousers,gid=users,fmask=133,dmask=022/dev/sda1 /mnt/windows: mount: wrong fs type, bad option, bad superblock on /dev/sda1. missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Unfortunately checking kernel messages after accepting the failure shows no errors.