accessing ntfs drives?

[umar001]

How do I access my windows drive?

Apparently there is a problem with "mount"


I have suse linux version 8.0

I can see the partition using the partition information desplayer or YaST partitioner

I can even make the hard drive icon on my desktop and associate with the correct partition


but when i click on the icon the error comes up... when i get home, i will post the error,, but it has to do with "mount ... something or other"

[umar001]

The followng is the error i get when trying to access the drive using the icons i made despite i can see the information in YaST partitioner of \dev\hda1 as being /windows/D


Could not mount device.
The reported error was:
mount: mount point /windows/D does not exist

[mdwatts]

Does /windows and /windows/D exist?

[umar001]

as a partition they do exist..

and the YaST partitioner shows them as follows:

device mount point fstype

dev/hda1 /windows/C ntfs
dev/hdb1 /windows/D ntfs



The Partitions exist physically, but I don't know, how I can make them accessible,, as errors come up (explained earlier)

[bwkaz]

From a root shell, do a mkdir -p /windows/D. The error is saying that the /windows/D directory does not exist, and it has to in order to mount anything there.

You're also going to want to mkdir /windows/C before trying to mount hdc1, but you may have already done that.

[umar001]

hey thanks that worked great....

but i have a tiny weeny problem,,, it actually arose from resizing partition using boot commander (with partition commander),, it deleted some files of window system...

to fix it i need access to the D: drive....


unfortunately, i can access C drive now, but not D drive,, it gives me error saying following


Could not mount device.
The reported error was:
mount: wrong fs type, bad option, bad superblock on /dev/hdb1,
or too many mounted file systems

[bwkaz]

If you're sure hdb1 was the right partition (first partition on the primary slave drive, right?), and you're sure you formatted it with ntfs, then it would appear that your partitioning utility is not to be trusted anymore.

If both of the above are true (it's the right partition and was formatted ntfs), then it's likely that the filesystem header information (if it was a vfat-formatted drive, this would be the actual file allocation table) has been corrupted.

Sometimes there are backups on ntfs drives. I'm pretty sure I saw a "how to fix your ntfs filesystem by restoring a backup filesystem header" article on MSKB last summer, that might be worth a shot. Go to search.microsoft.com and start typing stuff in until you get something that tells you where on the disk your backup FS header information is (I think it's called the MFT on ntfs).