Announcement

**Qqmike** · Jan 22, 2009, 08:06 AM

Re: Cannot access ntfs-volume. Ownership problems?

In 8.10:

kdesudo dolphin
kdesudo konqueror

**arochester** · Jan 22, 2009, 08:08 AM

Re: Cannot access ntfs-volume. Ownership problems?

Is ntfs-3g installed?

**NexusHumanis** · Jan 22, 2009, 11:57 AM

Re: Cannot access ntfs-volume. Ownership problems?

Originally posted by Qqmike

In 8.10:

kdesudo dolphin
kdesudo konqueror

>> I tried both, but konqueror did not show a trace of the volume, while dolphin showed the volume in the menu on the left, but gave no access.
kdesudo dolphin gave the following error messages in konsole:
"/usr/bin/dolphin(6247)" Error in thread 3051923664 : "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files"
"/usr/bin/dolphin(6247)" Error in thread 3051923664 : "QLocalSocket::connectToServer: Invalid name"
dolphin(6247) <unnamed>::GlobalModelContainer::init: Failed to connect to Nepomuk server via local socket "/root/.kde/share/apps/nepomuk/socket"
Object::connect: No such signal DolphinView::redirection(KUrl,KUrl)
Object::connect: No such signal DolphinView::redirection(KUrl,KUrl)
"/usr/bin/dolphin(6247)" Error in thread 3051923664 : "org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files"

Dolphin nevertheless opened, and trying to open the ntfs volume now gave an error message suggesting I had something called softraid/fakeraid, or that something is wrong with ntfs. Tried posting the output, but cannot find a way to post the screendump.

ntfs-3g is installed.

**Detonate** · Jan 22, 2009, 06:48 PM

Re: Cannot access ntfs-volume. Ownership problems?

Sounds like another "dirty bit" problem. Which means Windows was not correctly shut down the last time that disk was used. We've been through this before here on the forum. A search on "dirty bit" should turn up the thread. Basically, you have to reboot into Windows, under disk tools you need to select the option to run scan disk and fix any errors found. Then it will probably tell you that it will run it the next time you boot windows. So reboot into windows again, and it should run scandisk /f on the drive. Then shut down windows using the proper shutdown procedure, then reboot into Kubuntu and you should be able to mount the drive.

**NexusHumanis** · Jan 22, 2009, 11:07 PM

Re: Cannot access ntfs-volume. Ownership problems?

Originally posted by Detonate

Sounds like another "dirty bit" problem. Which means Windows was not correctly shut down the last time that disk was used. We've been through this before here on the forum. A search on "dirty bit" should turn up the thread. Basically, you have to reboot into Windows, under disk tools you need to select the option to run scan disk and fix any errors found. Then it will probably tell you that it will run it the next time you boot windows. So reboot into windows again, and it should run scandisk /f on the drive. Then shut down windows using the proper shutdown procedure, then reboot into Kubuntu and you should be able to mount the drive.

>>Yeah..I figured that might have something to do with it... Problem is, the reason I was allowed to install kubuntu at all, was that the windows installation was shot to h***. I cannot boot into windows, and the installation cd we used seems to be damaged. Getting another one just like it is impossible, as the version was not....well...enterely kosher..... Is it still possible to download the windows 7 beta?

**Detonate** · Jan 23, 2009, 08:54 AM

Re: Cannot access ntfs-volume. Ownership problems?

The other poster that had the same problem took the drive out of his computer and took it to a friend's house and put the drive in his windows computer where he was able to run scandisk /f on the drive. There is a mount option called "force" that is supposed to make the drive mountable, but I have never been able to get it to work on a drive with this problem.

**NexusHumanis** · Jan 23, 2009, 01:55 PM

Re: Cannot access ntfs-volume. Ownership problems?

Originally posted by Detonate

The other poster that had the same problem took the drive out of his computer and took it to a friend's house and put the drive in his windows computer where he was able to run scandisk /f on the drive. There is a mount option called "force" that is supposed to make the drive mountable, but I have never been able to get it to work on a drive with this problem.

>> Thanks for the tip, but I was luckily(?) able to reinstall windows. So now I have access to the windows partition as well. The data storage partition remains unavailable though. Is "scandisk" different from "chkdsk"? The Xp install is only sp1 for now, would that make any difference at all? It has nevertheless been a fruitful day, as I managed to figure out how to reinstall Grub..... A good thing to know. :-)

**Detonate** · Jan 23, 2009, 04:24 PM

Re: Cannot access ntfs-volume. Ownership problems?

Scandisk is what us old guys call it, but I believe it was changed to chkdisk in XP. Doesn't matter. to run the program:

1. Click on Start and then My Computer.
2. Right click on disk you wish to scan and then click on properties.
3. Click on Tools tab at top of window.
4. Click on Check Now in the Error Checking section.
5. Click on boxes to automatically fix file system errors and scan for and attempt recovery of bad sectors.
6. Click on Start button.
It can't scan the disk it is running from, so a window will pop up asking if you want to schedule the scan for the next time Windows is started. Answer yes, the restart windows. If you are trying to scan a NTFS disk other than the one the windows install is on it should go ahead and run. And just to make things work better, after you've run the scandisk or chkdisk program, go ahead and defrag the drive. If you ever want to change the size of this drive to make room for another partition, Gparted will balk if the drive is fragmented.

It won't matter whether you only have SP1. It should run anyway.

**NexusHumanis** · Jan 29, 2009, 07:31 AM

Re: Cannot access ntfs-volume. Ownership problems?

Originally posted by Detonate

Scandisk is what us old guys call it, but I believe it was changed to chkdisk in XP. Doesn't matter. to run the program:

1. Click on Start and then My Computer.
2. Right click on disk you wish to scan and then click on properties.
3. Click on Tools tab at top of window.
4. Click on Check Now in the Error Checking section.
5. Click on boxes to automatically fix file system errors and scan for and attempt recovery of bad sectors.
6. Click on Start button.
It can't scan the disk it is running from, so a window will pop up asking if you want to schedule the scan for the next time Windows is started. Answer yes, the restart windows. If you are trying to scan a NTFS disk other than the one the windows install is on it should go ahead and run. And just to make things work better, after you've run the scandisk or chkdisk program, go ahead and defrag the drive. If you ever want to change the size of this drive to make room for another partition, Gparted will balk if the drive is fragmented.

It won't matter whether you only have SP1. It should run anyway.

>> Well......I have cheched both ntfs-partitions, with half(and pretty useless) success. I can now access the windows system-partition.(C

, but still cannot get access to the storage-partition. It shows up, and asks for password, but then nothing.

**Detonate** · Jan 29, 2009, 07:42 AM

Re: Cannot access ntfs-volume. Ownership problems?

Post the command you are using to mount it please.

Do you have an entry in fstab for it? Post the output of

cat /etc/fstab

**NexusHumanis** · Jan 30, 2009, 02:31 PM

Re: Cannot access ntfs-volume. Ownership problems?

I have not used any commands as such, only tried to click on the drive in dolphin and konqueror. In normal mode the marker just jump back to the last place entered, and when I open with kdesudo I get a pink error message telling me I cannot get access. It suggests the chkdsk /f in windows as a possible solution, and something about SoftRaid/ FakeRaid hardware mounting. I dont know what that is, but I recently changed the graphics card on the computer. Could that have something to do with it?

etc/fstab output: # /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda2
UUID=08696d5d-f25b-4e61-990f-0599ab75352b / ext3 relatime,errors=remount-ro 0 1
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

**Detonate** · Jan 30, 2009, 04:45 PM

Re: Cannot access ntfs-volume. Ownership problems?

Originally posted by NexusHumanis

It suggests the chkdsk /f in windows as a possible solution, and something about SoftRaid/ FakeRaid hardware mounting.

That's not good. We have had several posters lately with this problem. What it means is, that this disk was not cloed out properly the last time windows was shut down. When this happens, from an improper windows shutdown, the disk is basically unusable until chkdisk /f is run on it to correct any errors caused by the improper shutdown. Before we can work further with helping you get that disk mounted, you need to do this. Boot up in Windows, open My Computer, right click on the disk in question, open properties, and under Disk Tools ( I think that's it, working from memory here) you can select to scan the disk for errors and fix any errors found. After selecting that, it will probably ask if you want to schdule chkdisk for the next tiem windows starts, click yes, then restart windows. After chkdsk finishes running and your system boots into windows, shut down windows correctly using the proper windows shutdown procedure. Then we can help you get that disk mounted in Kubuntu. I know you already tried to do this, but you were alittle vague about your success. Try it again on all hard disks you have in windows.

**NexusHumanis** · Jan 31, 2009, 05:30 AM

Re: Cannot access ntfs-volume. Ownership problems?

So....I have now done chkdsk on both ntfs-partitions on the computer, and logged back into windows TWICE( as spesified in the pink error message in dolphin), and I still cannot get the D:/sda3 partition mounted. I guess then, that the terminal might come to my rescue.....again.

I am still not certain there is not an ownership problem, but I guess I should try the simpler solutions first.

You should know that the drive shows up in the places-list on the left of the dolphin window. It is not visible in the /media folder. The C:/sda1-partition is, and that one I have access to. The sda3-partition is the one I need access to, at the moment.

**NexusHumanis** · Jan 31, 2009, 06:16 AM

Re: Cannot access ntfs-volume. Ownership problems?

I have read up on mounting, and here is what my efforts produced:

cecilie@Cecilie:~$ sudo fdisk -l

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000001

Device Boot Start End Blocks Id System
/dev/sda1 * 1 2615 21004956 7 HPFS/NTFS
/dev/sda2 2616 5171 20531070 83 Linux
/dev/sda3 5172 30401 202659975 7 HPFS/NTFS
cecilie@Cecilie:~$ sudo mount -t ntfs /dev/sda3 media
$MFTMirr does not match $MFT (record 0).
Failed to mount '/dev/sda3': Input/output error
NTFS is either inconsistent, or you have hardware faults, or you have a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows TWICE. The usage of the /f parameter is very
important! If you have SoftRAID/FakeRAID then first you must activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for the details.

The last part is identical to what I get when trying to access the partition with Dolphin. The partition is easily accessible in windows.

Announcement

Cannot access ntfs-volume. Ownership problems?

Cannot access ntfs-volume. Ownership problems?

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment