OK the penny may have dropped somewhat at my end but I can only propose the basic theory, no idea how to proceed if this is feasibly the reason I am having difficulties accessing these partitions...

At xmas I added a new 160GB hard drive, and copied various (the ntfs and fat32 data ones) partitions between drives, my old smaller second hard drive going to another machine, the new one becoming hda, the old hda going to hdb. After the annual XP reinstall I needed to reinstall grub to be able to boot into SuSE again.

Could this perhaps be what is causing the difficulty getting to that partition? Can I force a refresh or recreation of the process of creating the fstab file that is created during a linux install?

(Not ready to give up yet)
Roger



Hi, I am wanting to copy a file from an ntfs formatted drive on my suse
box to a windows box. I can do this from the hdb1 ntfs partition ok,
but if I try to look at the hda6 drive (also ntfs) in konqueror I get
the following error from "kio_devices_mounthelper":
mount: wrong fs type, bad option, bad superblock on /dev/hda6, or too
many mounted file systems. Please check that the disk is entered
correctly.


The lines in fstab look the same, yet the mount command shows that hda6
in NOT mounted. What do I need to do to view the files on hda6? I can
browse all the other partitions OK.

[snip]



/dev/hda5 /windows/E vfat
users,gid=users,umask=0002,iocharset=utf 8 0 0

[snip]

Have you tried mounting the partition by hand?
I have an XP partition which mounts with a command like this one:-
mount -t ntfs -o ro,users,gid=users,umask=0002 /dev/hda6 /windows/F
Note that I haven't put in the nls=utf8 phrase because it causes the error message you mention. ( The nls=utf8 bit is not mentioned in the man page as an option for ntfs either - hint )


Also check that the /windows/F mount point exists.

--
C. S.



Hi Chris, yes /windows/F exists. When trying to manually mount with your suggested command I get almost the same error:

SuSEbox:/home/roger # mount -t ntfs -o ro,users,gid=users,umask=0002 /dev/hda6 /windows/F
mount: wrong fs type, bad option, bad superblock on /dev/hda6,
or too many mounted file systems


Does this provide any clarity on what's happening (or not happening?) The other partition that is ntfs doesn't have this problem in linux. The commands in fstab are simply the ones created during the suse install. Booting into windows shows all ntfs drives appearing to function as I would expect. Roger



Reply via email to