Request help in un-hosing my botched NTFS read-write config attempts [SOLVED]

[Guest]

Hi, I've tried a few things to get my 3 NTFS partitions R/W-accessible via dolphin. I think I've probably hosed things up pretty good. I'm looking for any assistance in getting them unscrewed. I've got the latest ntfs-3g and ntfs-config installed. However, I continue to run into mounting/write permission errors. Here's all the info pasted below.


from sudo fdisk -l

eagle@eagle-desktop:~$ sudo fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00048c6f

Device Boot Start End Blocks Id System
/dev/sda1 * 1 18662 149902483+ 83 Linux
/dev/sda2 18663 19457 6385837+ 5 Extended
/dev/sda5 18663 19457 6385806 82 Linux swap / Solaris

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xf6dbf6db

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 10199 81923436 7 HPFS/NTFS
/dev/sdb2 10200 60800 406452532+ f W95 Ext'd (LBA)
/dev/sdb5 10200 22947 102398278+ 7 HPFS/NTFS
/dev/sdb6 22948 60800 304054191 7 HPFS/NTFS

================================================== =====================

from sudo cat /etc/fstab

eagle@eagle-desktop:~$ sudo cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=ce5b2a0f-5ffd-44a5-8fe1-21264ec371db / ext3 relatime,errors=remount-ro 0 1
# /dev/sda5
UUID=30289cf7-0334-48a7-976f-7d22c19a1691 none swap sw 0 0
/dev/scd1 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
/dev/sdb1 /media/sdb1 ntfs nls=iso8859-1,users,umask=000,gid=users,user,owner 0 0

================================================== ==================================================

This is the backed-up fstab.

I tried using ntfs-config and mounting /dev/sdb5 to /media/sdb5 and it said it was "already in use." If I try unmounting everything, it says that sdb5 is not mounted.

Basically I'm looking for help in cleaning out all the disk settings and starting fresh.

For disk management applications, I seem to have ntfs-config and a program called Disk Manager. Perhaps the two settings could be interfering?

Here's an error message I get from ntfs-config when I try to set it to 'enable read-write':

===Begin error message===
Mounting /media/sdb1 failed.

$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sdb1': Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:

Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.

Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:

mount -t ntfs-3g /dev/sdb1 /media/sdb1 -o force

Or add the option to the relevant row in the /etc/fstab file:

/dev/sdb1 /media/sdb1 ntfs-3g force 0 0

===End error message===

I have FUSE:

eagle@eagle-desktop:~$ sudo modinfo fuse
filename: /lib/modules/2.6.27-9-generic/kernel/fs/fuse/fuse.ko
alias: char-major-10-229
license: GPL
description: Filesystem in Userspace
author: Miklos Szeredi <miklos@szeredi.hu>
srcversion: F894F76B6931D141D3D433B
depends:
vermagic: 2.6.27-9-generic SMP mod_unload modversions 586



I'm trying out KDE 4.2 (Kubuntu 8.10)


Thanks for any help!

[dibl]

Re: Request help in un-hosing my botched NTFS read-write config attempts

Here's how it worked the last time I needed to do that:

http://kubuntuforums.net/forums/inde...opic=3084679.0

You can obviously skip the part about installing the ntfs-3g package. I think the mount command now uses "ntfs" rather than "ntfs-3g" as the filesystem type, but I may be mistaken since I don't use NTFS any more.

[muzicman0]

Re: Request help in un-hosing my botched NTFS read-write config attempts

I admit that I didn't read through everything you posted, but it looks like you had an unclean shutdown on the ntfs drive, so it won't mount. do you still have windows installed? If so, reboot into windows, and then do a shutdown, this will clear the 'dirty' flag.

I had this issue once also, and didn't have a windows partition at the time, and did some googling and found a linux command line utility to clear the drive.

At any rate, as long as the drive is listed with an unclean shutdown, you will not be able to mount it in linux.

mm0

[Guest]

Re: Request help in un-hosing my botched NTFS read-write config attempts

muzicman0 - thanks! i booted into windows, shut down properly, restarted everything and sudo ntfs-config - and the drives mount properly now with r/w access!

dibl - thanks also for your suggestion and i'll be sure to bookmark it if i run into mounting issues in the future. from what i've seen on the forums it's not uncommon to experience random unmounting/un-auto-mounting of drives...

[muzicman0]

Re: Request help in un-hosing my botched NTFS read-write config attempts [SOLVED]

Glad I could help you out!
mm0