Bug 355454 - can't mount ntfs disk last my last update from factory
Summary: can't mount ntfs disk last my last update from factory
Status: RESOLVED DUPLICATE of bug 354113
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Other (show other bugs)
Version: Alpha 1
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: John Jolly
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-22 21:24 UTC by Chema Ollés
Modified: 2008-02-06 12:17 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
hwinfo information (550.38 KB, text/plain)
2008-01-28 21:22 UTC, Chema Ollés 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chema Ollés 2008-01-22 21:24:21 UTC 
Hi all:
Now I have last update from factory with:
ntfs-3g-1.913-19
ntfsprogs-2.0.0-4
packages and now,each time I try mount a ntfs device I see:
Failed to read $MFTMirr: Error de entrada/salida
Failed to mount '/dev/sda1': Error de entrada/salida
NTFS is either inconsistent, or you have hardware faults, or you have a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows TWICE. The usage of the /f parameter is very
important! If you have SoftRAID/FakeRAID then first you must activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for the details.

I check this partition and I not found any error.I try mount again under linux and see the same message again.

I use openSUSE 11.0 (i586) Alpha1 with kernel-2.6.24-rc8-git1-2-default
Regards
Comment 1 Rastislav Krupansky 2008-01-23 13:21:28 UTC 
This bug sounds like bug 354903.
Comment 2 Chema Ollés 2008-01-28 21:20:42 UTC 
Now I use openSUSE 11.0 (i586) Alpha1 with kernel-2.6.24-rc8-git2-3-default.
This problem continues.
I add an attachment with hwinfo.log
Regards
Comment 3 Chema Ollés 2008-01-28 21:22:52 UTC 
Created attachment 192051 [details]
hwinfo information
Comment 4 Hans-Peter Holler 2008-02-06 12:17:58 UTC 

*** This bug has been marked as a duplicate of bug 354113 ***