 |
  |
Page 1 of 1
|
[ 12 posts ] |
|
| Author |
Message |
|
wide_load
Joined: Wed Dec 30, 2009 23:00
Posts: 7
|
 ntfs-3g fakeraid issue hi, I am having some trouble getting my 2TB NTFS partition to mount, i keep getting an error saying that's the partiton is not valid, espite the fact that it is, and mounts find under windows. i think its probably easiest to link to the forum where i originality asked about this, so you can see more details. Code: http://www.linuxquestions.org/questions/linux-newbie-8/dmraid-fakeraid-unequal-volumes-775794/ thanks Jacek
|
| Wed Jan 06, 2010 18:54 |
 |
|
|
jpa
NTFS-3G Lead Developer
Joined: Tue Sep 04, 2007 17:22
Posts: 1013
|
Re: ntfs-3g fakeraid issue Hi, Quote: I am having some trouble getting my 2TB NTFS partition to mount, i keep getting an error saying that's the partiton is not valid, espite the fact that it is, and mounts find under windows. In the forum you referenced, you mention : Quote: Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb41a3d87
Device Boot Start End Blocks Id System
/dev/sdd1 1 243197 1953478878+ 7 HPFS/NTFS Which means the partition sdd1 ends at cylinder 243197 of 121601 (though the block count is probably correct). ntfs-3g will surely refuse to mount a file system overflowing from its partition. Is there an error message in your system log ? You may check the file system parameters from the command (as root) : Code: ntfsinfo -m /dev/sdd1 If the command fails, dump the first 1K bytes of the partition : Code: dd if=/dev/sdd1 of=<some file> bs=1024 count=1 and attach the (gzipped) resulting file to your reply. Regards Jean-Pierre
|
| Wed Jan 06, 2010 20:32 |
|
|
|
wide_load
Joined: Wed Dec 30, 2009 23:00
Posts: 7
|
Re: ntfs-3g fakeraid issue thanks for replying so fast... the output of ntfsinfo -m /dev/mapper/nvidia_afeahbbe1 is as ollows, i dont really understand most of this.  Code: root@jacek-desktop:~# ntfsinfo -m /dev/mapper/nvidia_afeahbbe1
Volume Information
Name of device: /dev/mapper/nvidia_afeahbbe1
Device state: 11
Volume Name: Media
Volume State: 1
Volume Version: 3.1
Sector Size: 512
Cluster Size: 4096
Volume Size in Clusters: 488369719
MFT Information
MFT Record Size: 1024
MFT Zone Multiplier: 1
MFT Data Position: 24
MFT Zone Start: 786432
MFT Zone End: 61832646
MFT Zone Position: 786432
Current Position in First Data Zone: 61832646
Current Position in Second Data Zone: 0
LCN of Data Attribute for FILE_MFT: 786432
FILE_MFTMirr Size: 4
LCN of Data Attribute for File_MFTMirr: 122094975
Size of Attribute Definition Table: 2560
FILE_Bitmap Information
FILE_Bitmap MFT Record Number: 6
State of FILE_Bitmap Inode: 0
Length of Attribute List: 0
Attribute List: (null)
Number of Attached Extent Inodes: 0
FILE_Bitmap Data Attribute Information
Decompressed Runlist: not done yet
Base Inode: 6
Attribute Types: not done yet
Attribute Name Length: 0
Attribute State: 3
Attribute Allocated Size: 61046784
Attribute Data Size: 61046216
Attribute Initialized Size: 61046216
Attribute Compressed Size: 0
Compression Block Size: 0
Compression Block Size Bits: 0
Compression Block Clusters: 0
there is no /dev/sdd1 /dev/sdd is the 1TB disk ntfsinfo -m /dev/sdd Code: Failed to mount '/dev/sdd': Invalid argument.
The device '/dev/sdd' doesn't have a valid NTFS.
the file resulting from dd if=/dev/sdd of=post.gz bs=1024 count=1 is attached, i didnt know what the extension should be so i just guessed.gz thanks for helping. this has been driving me crazy for the best part of a month now
Attachments:
 post.gz [1 KiB]
Downloaded 121 times
|
| Wed Jan 06, 2010 21:08 |
|
|
|
jpa
NTFS-3G Lead Developer
Joined: Tue Sep 04, 2007 17:22
Posts: 1013
|
Re: ntfs-3g fakeraid issue Hi, Quote: the output of ntfsinfo -m /dev/mapper/nvidia_afeahbbe1 is as ollows, i dont really understand most of this. What is the relation (if any) of /dev/mapper/nvidia_afeahbbe1 to /dev/sdd ? Code: Sector Size: 512
Cluster Size: 4096
Volume Size in Clusters: 488369719 This is a header for a ntfs file system whose size is 488369719*4096 or 2TB and ntfs-3g refuses to mount such a file system on a partition smaller than 2TB. Now I guess the partition is a virtual one split among your drives (hence my above question), and you have 2.5TB, but this is a raid mount, so you must have redundancy, and 2TB redundant is more than you have... Quote: there is no /dev/sdd1 /dev/sdd is the 1TB disk But you could post a fdisk display on which it appears... Quote: the file resulting from
dd if=/dev/sdd of=post.gz bs=1024 count=1
is attached, i didnt know what the extension should be so i just guessed.gz This is a partition table, not the ntfs header I was asking for, but you could extract the ntfs data by ntfsinfo, so this dump is not needed. Your situation is similar to the one described in viewtopic.php?f=3&t=1125which the user has apparently solved by changing an option. Regards Jean-Pierre
|
| Wed Jan 06, 2010 22:54 |
|
|
|
wide_load
Joined: Wed Dec 30, 2009 23:00
Posts: 7
|
Re: ntfs-3g fakeraid issue What is the relation (if any) of /dev/mapper/nvidia_afeahbbe1 to /dev/sdd ?
/dev/sdd is one of the disks in the array
/dev/mapper/nvidia_afeahbbe1 is the kind of fake drive that dmraid makes
that is my understanding anyway.
the array is made up of 2 500GB disks and one 1TB, and using windows I was able to use it as a 2TB partition.
ill have a look at the link you suggested.
|
| Wed Jan 06, 2010 23:15 |
|
|
|
jpa
NTFS-3G Lead Developer
Joined: Tue Sep 04, 2007 17:22
Posts: 1013
|
Re: ntfs-3g fakeraid issue Hi, Quote: the array is made up of 2 500GB disks and one 1TB, and using windows I was able to use it as a 2TB partition. So you do not have any redundancy at all (I was imagining 4+1 redundancy). And you were able to get the ntfs header from /dev/mapper/nvidia_afeahbbe1, but what is the error message when trying to mount /dev/mapper/nvidia_afeahbbe1 ? Code: mount -t ntfs-3g -o ro /dev/mapper/nvidia_afeahbbe1 <mountpoint> Regards Jean-Pierre
|
| Wed Jan 06, 2010 23:41 |
|
|
|
wide_load
Joined: Wed Dec 30, 2009 23:00
Posts: 7
|
Re: ntfs-3g fakeraid issue jpa wrote: Hi, Quote: the array is made up of 2 500GB disks and one 1TB, and using windows I was able to use it as a 2TB partition. So you do not have any redundancy at all (I was imagining 4+1 redundancy). And you were able to get the ntfs header from /dev/mapper/nvidia_afeahbbe1, but what is the error message when trying to mount /dev/mapper/nvidia_afeahbbe1 ? Code: mount -t ntfs-3g -o ro /dev/mapper/nvidia_afeahbbe1 <mountpoint> Regards Jean-Pierre omg it mounted ! when i tried before (see forum link) i got the same error about the partition being unreadable. what does the ro option do ? anyway it mounts and shows as 1850GB used - fine 13GB free - fine but when browsing the folder, its empty ... ?? here is ls ... btw ll is just ls -la Code: jacek@jacek-desktop:~$ sudo mount -t ntfs-3g -o ro /dev/mapper/nvidia_afeahbbe1 /media/media
jacek@jacek-desktop:~$ sudo bash
root@jacek-desktop:~# cd /media/media
root@jacek-desktop:/media/media# ls
ls: reading directory .: Input/output error
root@jacek-desktop:/media/media# ll
ls: reading directory .: Input/output error
total 0
root@jacek-desktop:/media/media#
|
| Thu Jan 07, 2010 00:19 |
|
|
|
jpa
NTFS-3G Lead Developer
Joined: Tue Sep 04, 2007 17:22
Posts: 1013
|
Re: ntfs-3g fakeraid issue Hi, Quote: omg it mounted !
when i tried before (see forum link) i got the same error about the partition being unreadable. I did not find this try on the referenced forum. Quote: what does the ro option do ? ro means read-only, this is recommended in unsafe conditions. It also escapes a few checks when mounting. Quote: it mounts and shows as
1850GB used - fine
13GB free - fine Is this the the result of a "df" ? Code: jacek@jacek-desktop:~$ sudo bash
root@jacek-desktop:~# cd /media/media
root@jacek-desktop:/media/media# ls
ls: reading directory .: Input/output error
root@jacek-desktop:/media/media# ll
ls: reading directory .: Input/output error
total 0
root@jacek-desktop:/media/media# For every "Input/output error" you should have an error message in your system log. What is it ? (its location depends on the distribution, on mine it is /var/log/messages). I suspect the root directory is special on that device type. Can you try (with the device unmounted) : Code: sudo ntfsinfo -vi 5 /dev/mapper/nvidia_afeahbbe1 > rootdir.data
gzip rootdir.data And attach the resulting file rootdir.data.gz ? Regards Jean-Pierre
|
| Thu Jan 07, 2010 10:05 |
|
|
|
wide_load
Joined: Wed Dec 30, 2009 23:00
Posts: 7
|
Re: ntfs-3g fakeraid issue Quote: Is this the the result of a "df" ? it was the result of right click > properties from /media/media i figure its the same ? Code: Filesystem Size Used Avail Use% Mounted on
/dev/mapper/nvidia_jbcaafci1
448G 102G 324G 24% /
udev 2.0G 252K 2.0G 1% /dev
none 2.0G 188K 2.0G 1% /dev/shm
none 2.0G 284K 2.0G 1% /var/run
none 2.0G 0 2.0G 0% /var/lock
none 2.0G 0 2.0G 0% /lib/init/rw
/dev/mapper/nvidia_afeahbbe1
1.9T 1.9T 14G 100% /media/media
shows the same anyway. although available 100% is a bit weird. Code: root@jacek-desktop:~# sudo ntfsinfo -vi 5 /dev/mapper/nvidia_afeahbbe1 > rootdir.data
The device /dev/mapper/nvidia_afeahbbe1 doesn't exist
root@jacek-desktop:~# kpartx -a /dev/mapper/nvidia_afeahbbe
root@jacek-desktop:~# sudo ntfsinfo -vi 5 /dev/mapper/nvidia_afeahbbe1 > rootdir.data
Damaged INDX record: Invalid argument.
Damaged INDX record: Invalid argument.
Damaged INDX record: Invalid argument.
Damaged INDX record: Invalid argument.
root@jacek-desktop:~#
ill attach the file anyway the follow shows up in syslog after mounting and trying to open the folder. Code: Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Mounted /dev/mapper/nvidia_afeahbbe1 (Read-Only, label "Media", NTFS 3.1)
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Cmdline options: ro
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Mount options: ro,silent,allow_other,nonempty,relatime,fsname=/dev/mapper/nvidia_afeahbbe1,blkdev,blksize=4096
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0xc7ddf94c size: 4096 usa_ofs: 25496 usa_count: 7270: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0x9604840cb8e2c9ac) of index buffer is different from expected VCN (0x3).
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0xc7ddf94c size: 4096 usa_ofs: 25496 usa_count: 7270: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0x9604840cb8e2c9ac) of index buffer is different from expected VCN (0x3).
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0x9e11626f size: 4096 usa_ofs: 48525 usa_count: 31658: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0xcb32f4f61f9bfe3f) of index buffer is different from expected VCN (0x0) in inode 0x5.
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0x9e11626f size: 4096 usa_ofs: 48525 usa_count: 31658: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0xcb32f4f61f9bfe3f) of index buffer is different from expected VCN (0x0) in inode 0x5.
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0x9e11626f size: 4096 usa_ofs: 48525 usa_count: 31658: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0xcb32f4f61f9bfe3f) of index buffer is different from expected VCN (0x0) in inode 0x5.
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0x9e11626f size: 4096 usa_ofs: 48525 usa_count: 31658: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0xcb32f4f61f9bfe3f) of index buffer is different from expected VCN (0x0) in inode 0x5.
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0x9e11626f size: 4096 usa_ofs: 48525 usa_count: 31658: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0xcb32f4f61f9bfe3f) of index buffer is different from expected VCN (0x0) in inode 0x5.
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0x9e11626f size: 4096 usa_ofs: 48525 usa_count: 31658: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0xcb32f4f61f9bfe3f) of index buffer is different from expected VCN (0x0) in inode 0x5.
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0x9e11626f size: 4096 usa_ofs: 48525 usa_count: 31658: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0xcb32f4f61f9bfe3f) of index buffer is different from expected VCN (0x0) in inode 0x5.
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0x9e11626f size: 4096 usa_ofs: 48525 usa_count: 31658: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0xcb32f4f61f9bfe3f) of index buffer is different from expected VCN (0x0) in inode 0x5.
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0x9e11626f size: 4096 usa_ofs: 48525 usa_count: 31658: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0xcb32f4f61f9bfe3f) of index buffer is different from expected VCN (0x0) in inode 0x5.
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0x9e11626f size: 4096 usa_ofs: 48525 usa_count: 31658: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0xcb32f4f61f9bfe3f) of index buffer is different from expected VCN (0x0) in inode 0x5.
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0x9e11626f size: 4096 usa_ofs: 48525 usa_count: 31658: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0xcb32f4f61f9bfe3f) of index buffer is different from expected VCN (0x0) in inode 0x5.
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0x9e11626f size: 4096 usa_ofs: 48525 usa_count: 31658: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0xcb32f4f61f9bfe3f) of index buffer is different from expected VCN (0x0) in inode 0x5.
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: ntfs_mst_post_read_fixup: magic: 0x9e11626f size: 4096 usa_ofs: 48525 usa_count: 31658: Invalid argument
Jan 7 14:45:36 jacek-desktop ntfs-3g[2929]: Actual VCN (0xcb32f4f61f9bfe3f) of index buffer is different from expected VCN (0x0) in inode 0x5.
|
| Thu Jan 07, 2010 16:48 |
|
|
|
wide_load
Joined: Wed Dec 30, 2009 23:00
Posts: 7
|
Re: ntfs-3g fakeraid issue correction on the above Quote: shows the same anyway. although available 100% is a bit weird. just realied its 100% used makes more sence
|
| Thu Jan 07, 2010 18:46 |
|
|
|
jpa
NTFS-3G Lead Developer
Joined: Tue Sep 04, 2007 17:22
Posts: 1013
|
Re: ntfs-3g fakeraid issue Hi, Quote: ill attach the file anyway Interesting. You can read the root directory and it is (roughly) correct. However you cannot read the index to the file names contained in the root directory, hence the multiple errors you got while reading the index and the directory appearing as void. According to your posted data, the index is located at cluster 0x10692426, and 0x10692426*4096 = 1.127E+12. This means the index is beyond 1TB, the size of your biggest physical drive. The mapping of a virtual cluster to a physical disk is outside ntfs-3g range. I tend to think your raid array is wrongly defined. Read again the similar post I have already mentioned, where the user solved the issue by changing an option -c64 to -c16. I cannot help you in this area, so good luck, and keep me informed of the outcome. Regards Jean-Pierre
|
| Thu Jan 07, 2010 19:02 |
|
|
|
wide_load
Joined: Wed Dec 30, 2009 23:00
Posts: 7
|
Re: ntfs-3g fakeraid issue jpa wrote: Hi, Quote: ill attach the file anyway Interesting. You can read the root directory and it is (roughly) correct. However you cannot read the index to the file names contained in the root directory, hence the multiple errors you got while reading the index and the directory appearing as void. According to your posted data, the index is located at cluster 0x10692426, and 0x10692426*4096 = 1.127E+12. This means the index is beyond 1TB, the size of your biggest physical drive. The mapping of a virtual cluster to a physical disk is outside ntfs-3g range. I tend to think your raid array is wrongly defined. Read again the similar post I have already mentioned, where the user solved the issue by changing an option -c64 to -c16.I cannot help you in this area, so good luck, and keep me informed of the outcome. Regards Jean-Pierre yeh I looked at that, but this is not how I create the array, its done in the BIOS tool, so its not something I can change, the bios tool is pretty terrible all it will allow me to do is add a drive or remove a drive. thanks for your help anyway, ill post again if i find out how get it to work
|
| Thu Jan 07, 2010 19:14 |
|
|
|
|
Page 1 of 1
|
[ 12 posts ] |
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum
|
|
|