PDA

View Full Version : Did NTFS-3G mess up my files?

Waggoneer
6th April 2009, 05:25 AM
This is bad. I think ntfs-36 is screwing up my files on my raid partition. I am getting lots of errors in my log.

I am posting this here, since it occured while I was testing the beta. This occurred on a RAID drive.

Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 33556 has no FILE magic (0x0)
Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 34130 has no FILE magic (0x0)
Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 39490 has no FILE magic (0x0)
Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 39245 has no FILE magic (0x0)
Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 39247 has no FILE magic (0x0)
Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 39481 has no FILE magic (0x0)
Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0xd16be2be size: 4096 usa_ofs: 16261 usa_count: 9840: Invalid argument
Apr 5 18:47:36 LinPC ntfs-3g[1811]: Actual VCN (0xfccfb1645c7c5118) of index buffer is different from expected VCN (0x0) in inode 0x8359.
Apr 5 18:47:39 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:39 LinPC ntfs-3g[1811]: Record 39245 has no FILE magic (0x0)
Apr 5 18:47:39 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:39 LinPC ntfs-3g[1811]: Record 39247 has no FILE magic (0x0)
Apr 5 18:47:39 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:39 LinPC ntfs-3g[1811]: Record 33848 has no FILE magic (0x0)
Apr 5 18:47:39 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:39 LinPC ntfs-3g[1811]: Record 33556 has no FILE magic (0x0)
Apr 5 18:47:39 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:39 LinPC ntfs-3g[1811]: Record 34130 has no FILE magic (0x0)
Apr 5 18:47:39 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:39 LinPC ntfs-3g[1811]: Record 39490 has no FILE magic (0x0)
Apr 5 18:47:42 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:42 LinPC ntfs-3g[1811]: Record 33848 has no FILE magic (0x0)
Apr 5 18:47:43 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:43 LinPC ntfs-3g[1811]: Record 33994 has no FILE magic (0x0)
Apr 5 18:47:43 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:43 LinPC ntfs-3g[1811]: Record 39245 has no FILE magic (0x0)
Apr 5 18:47:43 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:43 LinPC ntfs-3g[1811]: Record 39247 has no FILE magic (0x0)
Apr 5 18:47:43 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:43 LinPC ntfs-3g[1811]: Record 41988 has no FILE magic (0x0)
Apr 5 18:47:43 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:43 LinPC ntfs-3g[1811]: Record 41989 has no FILE magic (0x0)
Apr 5 18:47:46 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:46 LinPC ntfs-3g[1811]: Record 34050 has no FILE magic (0x0)
Apr 5 18:47:46 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:46 LinPC ntfs-3g[1811]: Record 39230 has no FILE magic (0x0)
Apr 5 18:47:46 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:46 LinPC ntfs-3g[1811]: Record 34007 has no FILE magic (0x0)
Apr 5 18:47:46 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:46 LinPC ntfs-3g[1811]: Record 41311 has no FILE magic (0x0)
Apr 5 18:47:47 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:47 LinPC ntfs-3g[1811]: Record 39451 has no FILE magic (0x0)
(...)
Apr 5 18:47:52 LinPC ntfs-3g[1811]: Index root attribute missing in directory inode 33699: Input/output error
Apr 5 18:47:52 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:52 LinPC ntfs-3g[1811]: Record 33208 has no FILE magic (0x0)
(...)
Apr 5 18:52:15 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:52:15 LinPC ntfs-3g[1811]: Record 39490 has no FILE magic (0x0)
Apr 5 18:52:15 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:52:15 LinPC ntfs-3g[1811]: Record 39538 has no FILE magic (0x0)
Apr 5 18:52:15 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:52:15 LinPC ntfs-3g[1811]: Record 33556 has no FILE magic (0x0)
Apr 5 18:52:15 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:52:15 LinPC ntfs-3g[1811]: Record 34130 has no FILE magic (0x0)


I can't open several of the folders because they have become corrupted.
RahulSundaram
6th April 2009, 01:26 PM
Hi

Can you file a bug report in http://bugzilla.redhat.com with the log, version information and it will reach the maintainer. upstream developers who can look into the issue.
Waggoneer
6th April 2009, 03:41 PM

Bug filed,
https://bugzilla.redhat.com/show_bug.cgi?id=494356
Waggoneer
6th April 2009, 10:41 PM
In the mean time, does Fedora have any good file-repair tools?
Hlingler
6th April 2009, 10:49 PM
yum install testdisk

TestDisk web site: http://www.cgsecurity.org/wiki/TestDisk

Good Luck,
V
SlowJet
6th April 2009, 11:12 PM
ntfs-3g 4.4.1 was released today as stable in F10, and on the 4th for rawhide.
Are you using 4.4.1 version? coz that is suppose to fix nasty stuff like you are getting.

See logs in https/::admin.fedoraproject.og/updates/F10/FEDORA-2009-3394


SJ
Waggoneer
7th April 2009, 02:33 AM
I logged into my computer in single-user mode and commented out my ntfs drive
to prevent any possible further corruption.
I checked the version of ntfs-3g and it was ntfs-3g-2:2009.4.4-1.fc11 (x86_64).
I am fairly certain that this version caused my problems. After I did the
initial install of Fedora 11 Beta I did a full update before mounting my ntfs
drives via fstab.
Should I wait for the next ntfs-3g update before I start using it again?
Hlingler
7th April 2009, 02:39 AM
I would think that data recovery (if needed, and if possible) takes precedence over gettings ntfs-3g working.

2¢
V
SlowJet
7th April 2009, 04:51 AM
I logged into my computer in single-user mode and commented out my ntfs drive
to prevent any possible further corruption.
I checked the version of ntfs-3g and it was ntfs-3g-2:2009.4.4-1.fc11 (x86_64).
I am fairly certain that this version caused my problems. After I did the
initial install of Fedora 11 Beta I did a full update before mounting my ntfs
drives via fstab.
Should I wait for the next ntfs-3g update before I start using it again?

I think the ntfs was already screwed and the new version is finding the errors.
But someone will need to test a new NTFS with the new version from the get go with 2009-4.4.1

You will need Windows Xp or Vista to do a an ntfsck in either case.
It will restore the ntfs structure but not the data affected.

SJ
SlowJet
7th April 2009, 05:14 AM
There is an ntfs mount error fix in the 30 kernel
kernel-2.6.29-git14
So it may have been a kernel error all along
but since there is not enough detail in the logs
one can not discern which version or kernel did what.
So the only thing that can be done for now is a series of tests to find out what works and what does not work.

SJ
szaka
7th April 2009, 11:39 AM
This is bad. I think ntfs-36 is screwing up my files on my raid partition.
It seems you have only one problem: one segment of the NTFS superblock is invalid (uninitialized, empty space) between file numbers 33,000-42,000. There can be several reasons for this:

1. One lower layer is temporarily or permanently broken (device driver, disk):
2. If the relevant NTFS info is at the end of the NTFS superblock then the volume was not safely unmounted (i.e. the data was not written to the disk).
3. The issue could be also not NTFS but RAID related. Sometimes they are doing funny things.

You should check your logs not only for NTFS but all kind of disk, I/O,RAID errors in the past: http://ntfs-3g.org/support.html#ioerror
Waggoneer
8th April 2009, 02:15 AM
Is there any way to recover that section of the NTFS superblock?

Here is some more of the errors I found. I truncated it somewhat. There haven't been any errors since the 5th, when I stopped mounting my RAID device. There is lots to read in the logs, as a lot of debugging is enabled in Beta.


Apr 5 18:47:33 LinPC gnome-keyring-daemon[2516]: removing removable location: volume_uuid_647E_9BA5
Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 33556 has no FILE magic (0x0)
Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
(...)
Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 39245 has no FILE magic (0x0)
Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 39247 has no FILE magic (0x0)
Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 39481 has no FILE magic (0x0)
Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0xd16be2be size: 4096 usa_ofs: 16261 usa_count: 9840: Invalid argument
Apr 5 18:47:36 LinPC ntfs-3g[1811]: Actual VCN (0xfccfb1645c7c5118) of index buffer is different from expected VCN (0x0) in inode 0x8359.
(...)
Apr 5 18:47:52 LinPC ntfs-3g[1811]: Record 33708 has no FILE magic (0x0)
Apr 5 18:47:52 LinPC ntfs-3g[1811]: Inode is corrupt (33699): Input/output error
Apr 5 18:47:52 LinPC ntfs-3g[1811]: Index root attribute missing in directory inode 33699: Input/output error
Apr 5 18:47:52 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:52 LinPC ntfs-3g[1811]: Record 33208 has no FILE magic (0x0)
Apr 5 18:47:52 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:52 LinPC ntfs-3g[1811]: Record 33216 has no FILE magic (0x0)
Apr 5 18:47:52 LinPC ntfs-3g[1811]: Inode is corrupt (33205): Input/output error
Apr 5 18:47:52 LinPC ntfs-3g[1811]: Index root attribute missing in directory inode 33205: Input/output error
Apr 5 18:47:52 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 5 18:47:52 LinPC ntfs-3g[1811]: Record 39271 has no FILE magic (0x0)
Apr 5 18:47:52 LinPC ntfs-3g[1811]: Inode is corrupt (32662): Input/output error
Apr 5 18:47:52 LinPC ntfs-3g[1811]: Index root attribute missing in directory inode 32662: Input/output error
(...)
Apr 5 18:52:15 LinPC ntfs-3g[1811]: Record 34130 has no FILE magic (0x0)
Apr 5 19:03:06 LinPC console-kit-daemon[2122]: GLib-GObject-WARNING: IA__g_object_get_valist: value location for `gchararray' passed as NULL
Apr 5 19:03:06 LinPC gnome-keyring-daemon[2516]: dbus failure unregistering from session: Connection was disconnected before a reply was received
szaka
8th April 2009, 11:49 AM
Is there any way to recover that section of the NTFS superblock?
If the metadata was never written to disk, or the RAID remapped the relevant disk sectors because they became physically unreadable then you can not recover them.

It also could be that you had only some bad sectors and CHKDSK lost the other 10k files. It's known to have such problems and always a good idea to make a full backup before running CHKDSK.

If the metadata was ever written to the disk then you could try some recovery software.

Here is some more of the errors I found. I truncated it somewhat. There haven't been any errors since the 5th, when I stopped mounting my RAID device.
These logs are not useful. They say the same, that something lost an important part of the NTFS superblock EARLIER. You must look for earlier errors for the reason, not later for the symptoms. Maybe improperly stopping the RAID killed the files.
szaka
8th April 2009, 11:57 AM
Apr 5 18:47:33 LinPC gnome-keyring-daemon[2516]: removing removable location: volume_uuid_647E_9BA5
I just noticed, maybe this log line is useful. If gnome or something else unexpectedly removed (one of) your devices storing some part of NTFS then the NTFS error messages are the expected ones. Of course the kernel should I/O errors, not zero filled buffers. But sometimes these happen with buggy kernel device drivers.

Your symptom is exactly like if the device would have been unsafely removed and some file system parts are still cached in the kernel page cache.
Waggoneer
8th April 2009, 06:41 PM
So then it wasn't NTFS-3G, but Gnome or something else.

That makes sense. Also, yesterday when I was running a yum update of my computer a random error message popped up in my GUI saying that a one of the NTFS partitions was unexpectedly disconnected. I had never seen that error occur before. However, it could have happened, because sometimes I start an update then wander off.
Waggoneer
11th April 2009, 07:42 PM
The problem for me is persisting. I wonder, do I need to just reformat the drive?


Apr 11 10:17:50 LinPC ntfs-3g[1937]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 11 10:17:50 LinPC ntfs-3g[1937]: Record 40852 has no FILE magic (0x0)
Apr 11 10:17:50 LinPC ntfs-3g[1937]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 11 10:17:50 LinPC ntfs-3g[1937]: Record 39490 has no FILE magic (0x0)
Apr 11 10:17:50 LinPC ntfs-3g[1937]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 11 10:17:50 LinPC ntfs-3g[1937]: Record 39538 has no FILE magic (0x0)
Apr 11 10:17:50 LinPC ntfs-3g[1937]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 11 10:17:50 LinPC ntfs-3g[1937]: Record 33556 has no FILE magic (0x0)
Apr 11 10:17:50 LinPC ntfs-3g[1937]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 11 10:17:50 LinPC ntfs-3g[1937]: Record 34130 has no FILE magic (0x0)
Apr 11 10:19:34 LinPC ntfs-3g[1937]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 11 10:19:34 LinPC ntfs-3g[1937]: Record 40852 has no FILE magic (0x0)
Apr 11 10:19:34 LinPC ntfs-3g[1937]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 11 10:19:34 LinPC ntfs-3g[1937]: Record 39490 has no FILE magic (0x0)
Apr 11 10:19:34 LinPC ntfs-3g[1937]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 11 10:19:34 LinPC ntfs-3g[1937]: Record 39538 has no FILE magic (0x0)
Apr 11 10:19:34 LinPC ntfs-3g[1937]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 11 10:19:34 LinPC ntfs-3g[1937]: Record 33556 has no FILE magic (0x0)
Apr 11 10:19:34 LinPC ntfs-3g[1937]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument
Apr 11 10:19:34 LinPC ntfs-3g[1937]: Record 34130 has no FILE magic (0x0)


When I boot into linux with my RAID mounted, and browse the directory structure these errors start occurring. Then when I switch back, windows automaticly launches into check disk. Once I am back at the desktop the video game I have installed on the RAID is corrupted and I have to restore it. Then when I switch again, linux can't seem to understand the restored directory.
If I browse the directory with nautilus some of the files don't appear. If I run an ls - l I can see the folders but not access them. The folder (x86) has the video game Left 4 Dead.


[Jason@LinPC my_raid]$ ls -l
ls: cannot access BU: Input/output error
ls: cannot access Mozilla Firefox 3.1 Beta 2: Input/output error
ls: cannot access MSOCache: Input/output error
ls: cannot access Office: Input/output error
ls: cannot access Rosetta Stone: Input/output error
ls: cannot access temp: Input/output error
total 3236
drwxrwxrwx 1 root root 0 2009-01-15 17:02 Adobe
-rwxrwxrwx 1 root root 3019119 2009-03-28 12:23 $AVG8.VAULT$
d????????? ? ? ? ? ? BU
drwxrwxrwx 1 root root 0 2009-01-19 18:21 Garmin
drwxrwxrwx 1 root root 16384 2008-10-07 20:01 Jason
drwxrwxrwx 1 root root 4096 2009-02-18 18:29 KeePass Password Safe
drwxrwxrwx 1 root root 4096 2009-04-05 17:46 Kuma
-rwxrwxrwx 2 root root 147864 2007-11-20 17:49 lighthouse.jpg
drwxrwxrwx 1 root root 0 2008-10-13 09:58 LookB4Deleting
-rwxrwxrwx 2 root root 35880 2008-10-17 22:46 M_bookmark.htm
d????????? ? ? ? ? ? Mozilla Firefox 3.1 Beta 2
d????????? ? ? ? ? ? MSOCache
-rwxrwxrwx 1 root root 54784 2002-01-05 03:38 msvci70.dll
drwxrwxrwx 1 root root 0 2009-01-12 22:27 NVIDIA
d????????? ? ? ? ? ? Office
drwxrwxrwx 1 root root 4096 2009-01-11 21:53 Picasa3
drwxrwxrwx 1 root root 4096 2007-11-21 13:10 $RECYCLE.BIN
d????????? ? ? ? ? ? Rosetta Stone
drwxrwxrwx 1 root root 0 2009-03-20 20:46 Sony Ericsson
drwxrwxrwx 1 root root 0 2007-11-02 18:18 System Volume Information
d????????? ? ? ? ? ? temp
-rwxrwxrwx 1 root root 9216 2008-05-29 19:59 Thumbs.db
drwxrwxrwx 1 root root 0 2009-03-08 16:50 (x86)


If windows thinks the drive is formatted correctly, why does fedora have a hard time viewing it?

Here is my fstab. I changed it to read-only in the hopes that it would protect it from being messed up again.

# /etc/fstab
# Created by anaconda on Fri Apr 3 19:02:32 2009
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or vol_id(8) for more info
#
UUID=ba129a42-b580-4964-ba61-cfcc5dfe45f6 /boot ext3 defaults 1 2
/dev/mapper/vg_linpc-lv_root / ext4 defaults 1 1
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts defaults 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/mapper/nvidia_adiadhfdp1 /mnt/my_raid ntfs-3g ro,auto,user,noexec 0 0
#/swapfile swap swap defaults 0 0