 |
|
Page 1 of 1
|
[ 11 posts ] |
|
Author |
Message |
pingo
Joined: Tue Feb 27, 2007 19:35 Posts: 1 Location: India
|
 NTFS signature missing
hi ,
I was trying with a linux distribution, Fuji Linux on a machine having windows xp only.I though it was a live distribution and tried browing through the cd and unknowing kickstarted an installation. Releasing my folly, I aborted the installation.In the process windows got corrupted.I have not deleted any data further to it.I tried booting through knoppix 5.1 live cd and could see my windows drive on mounting i.e.
mount /dev/hda2 /mnt/windows , though the file names folders appear in cryptic codes
I then tried with the ntfs-3g ( 1.0 stable release with fuse 2.6)
mount -t ntfs-3g /dev/hda2 /mnt/windows
and the outputs is
NTFS signature is missing.
Failed to startup volume: Invalid argument
Failed to mount '/dev/hda2': Invalid argument
The device '/dev/hda2' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?
and the ouput of fdisk -lu is as
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 63 1044224 522081 82 Linux swap / Solaris
/dev/hda2 * 1044225 156296384 77626080 87 NTFS volume set
Do I stand a chance to get back my windows data, with ntfs-3g ?
|
Thu Mar 08, 2007 21:16 |
|
 |
szaka
Tuxera CTO
Joined: Tue Nov 21, 2006 23:15 Posts: 1648
|
 NTFS signature missing
Hi,
It seems Fuji Linux (Turbolinux?) overwrote your Windows installation. You
may try a Windows recovery software, ntfs-3g can not help.
|
Thu Mar 08, 2007 23:19 |
|
 |
mifritscher
Joined: Thu Jan 11, 2007 21:34 Posts: 77
|
hmm, the filesystem id 87 isn't normal for a ntfs-partition...
Is that a raidx system? If it is a raid1 there are changes that the other HDD is ok. Else you should backup the partition with a low level program like dd and then try to use chkdsk from a windows-CD.
if it is a raid0 or 5 you should try to assemble the raid again, perhaps LVM from linux or again the repairconsole from a windows-cd helps.
|
Fri Mar 09, 2007 01:44 |
|
 |
szaka
Tuxera CTO
Joined: Tue Nov 21, 2006 23:15 Posts: 1648
|
 NTFS signature missing
On Fri, 9 Mar 2007, mifritscher wrote:
Quote: hmm, the filesystem id 87 isn't normal for a ntfs-partition...
It's a hidden NTFS but that means __nothing__. The filesystem type can be
freely changed, independently of the real file system. What is sure is that
no NTFS on the partition. Probably the installer formatted to ext3 (type
82) then a boot loader or something else changed it to hidden NTFS for some
reason.
I think the 'mount /dev/hda2 /mnt' worked because no filesystem type was
specified and in such cases the kernel autodetects the type, completely
independently what the partition type is in the partition table.
|
Fri Mar 09, 2007 01:53 |
|
 |
anuu
Joined: Tue Jul 22, 2008 14:46 Posts: 3 Location: LTU
|
Hello, my ntfs encountered same problem - system cant mount, I cant mount it,(after heavy r/w usage with ..home power failure). Partition contains files that i planed to backup, (and i will get a 2nd hd soon, i planing reformat ntfs, it is left after old windowsxp install..).
NTFS signature is missing : on sda1 partition.
Notice: sda4 mounts as usually w/o problems
(/dev/sda4 /mnt/sda4 ntfs-3g defaults,auto,nonempty,force,locale=en_US.utf8,users 0 0)
Code: Disk Drive: /dev/sda Size: 80026361856 bytes, 80.0 GB Heads: 255 Sectors per Track: 63 Cylinders: 9729
Name Flags Part Type FS Type [Label] Size (MB) ------------------------------------------------------------------------------------ sda1 Primary NTFS [PMS=MTAT+C] 26139.94 sda2 Primary Linux JFS 1110.42 sda4 Primary NTFS 3717.83 sda5 Logical W95 FAT32 (LBA) 45378.87 sda6 Boot Logical Linux JFS 3018.68 sda7 Logical Linux JFS 658.03
fstab: /dev/sda1 /mnt/windows_C ntfs-3g defaults,auto,nonempty,force,locale=en_US.utf8,users 0 0 manually: mount -t ntfs-3g /dev/sda1 /mnt/windows_C
NTFS signature is missing. Failed to mount '/dev/sda1': Invalid argument The device '/dev/sda1' doesn't have a valid NTFS. Maybe you selected the wrong device? Or the whole disk instead of a partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?
root@# fdisk -l
Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 3178 25527253+ 7 HPFS/NTFS /dev/sda2 3179 3313 1084387+ 83 Linux /dev/sda3 3766 9729 47905830 f W95 Ext'd (LBA) /dev/sda4 3314 3765 3630690 7 HPFS/NTFS /dev/sda5 3766 9282 44315271 c W95 FAT32 (LBA) /dev/sda6 * 9283 9649 2947896 83 Linux /dev/sda7 9650 9729 642568+ 83 Linux Partition table entries are not in disk order
software:
libntfs-3g31 Version 1.2531 (May 29, 2008)
ntfs-3g (1:1.2531-1)
lntfsprogs (2.0.0-1)
ntfsinfo v2.0.0 (libntfs 10:0:0)
Wish someone help me :?
..i have a lot of photos on that nts.
|
Tue Jul 22, 2008 15:46 |
|
 |
szaka
Tuxera CTO
Joined: Tue Nov 21, 2006 23:15 Posts: 1648
|
Try a partition/data recovery software. NTFS-3G doesn't include built-in recovery yet.
|
Tue Jul 22, 2008 15:51 |
|
 |
anuu
Joined: Tue Jul 22, 2008 14:46 Posts: 3 Location: LTU
|
Can You plz, suggest some free tool/s ?
I'm willing to fix partition..
(hmn i think i have somewhere ultimate boot cd)
Code: ntfsfix /dev/sda1 Mounting volume... Failed to startup volume: Invalid argument. FAILED Attempting to correct errors... FAILED Failed to startup volume: Invalid argument. Volume is corrupt. You should run chkdsk.
chkdsk... I don't have windows to do that..
_________________ http://www.elivecd.org/
Debian based/Enlightenment powered
|
Tue Jul 22, 2008 16:46 |
|
 |
anuu
Joined: Tue Jul 22, 2008 14:46 Posts: 3 Location: LTU
|
 Hello,
me again, PROBLEM SOLVED:
Code: dmesg | tail --- NTFS-fs error (device sda5): read_ntfs_boot_sector(): Primary boot sector is invalid. NTFS-fs error (device sda5): read_ntfs_boot_sector(): Mount option errors=recovery not used. Aborting without trying to recover. NTFS-fs error (device sda5): ntfs_fill_super(): Not an NTFS volume
so searched my repos for any kind of tools and found testdisk ,
searched on www about boot sector.. found those:
http://www.xtralogic.com/testdisk_rebui ... ctor.shtml
http://ubuntuforums.org/showthread.php?t=61340
Still.. i cant believe that power failure did that coruption..
G.L. ALL my patition is mountable as it was before.
_________________ http://www.elivecd.org/
Debian based/Enlightenment powered
|
Wed Jul 23, 2008 15:44 |
|
 |
szaka
Tuxera CTO
Joined: Tue Nov 21, 2006 23:15 Posts: 1648
|
 Re: Hello,
anuu wrote: i cant believe that power failure did that coruption. Power failure can cause any kind of harm, even permanent hardware destruction. You don't need to believe it, it's only a scientific and engineering fact.
|
Wed Jul 23, 2008 22:40 |
|
 |
john4499
Joined: Fri Dec 19, 2008 19:07 Posts: 1
|
 Similiar mounting problem
I have a similar problem in a partition installed for virtual windows.
(1) installed a fedora core in sda5
(2) installed window xp on partition sda2, which is working.
I cannot mount using ntfs-3g, get similar error
When I used fdisk to view the file system. sda2 is 95 vfat, So I changed its fs id to 7. I was still unable to mount after rebooted.
Then, I rebooted my virtual XP, IT STILL WORKS! The FS in partition sda2 must be OK.
In my case, it is not file corruption, but some compatibility issue although corruption is a possibility in other reported cases. I asked NTFS-3G staff to look into possible compatibility issues. Thanks.
|
Fri Dec 19, 2008 19:23 |
|
 |
szaka
Tuxera CTO
Joined: Tue Nov 21, 2006 23:15 Posts: 1648
|
If the partition was marked as FAT by Windows then it is FAT.
If Windows shows it as NTFS then either the Linux partition detection code or the block device setup code is not correct, or the NTFS bootsector was corrupted by a virus, partitioner, boot loader, etc. Please see http://www.ntfs-3g.org/support.html#mbr.
This is not an NTFS level issue. Either repair NTFS or set the block device up properly, so it can be accessed by the NTFS-3G driver. NTFS-3G is neither a volume manager, nor a repair/recovery tool ;-)
|
Fri Dec 19, 2008 19:31 |
|
|
|
Page 1 of 1
|
[ 11 posts ] |
|
Who is online |
Users browsing this forum: No registered users and 4 guests |
|
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
|
|
 |