I can't create a directory

pan64 · 07-01-2017, 09:09 AM

if that was a corrupted filesystem you could find something related in /var/log/messages (or next to it)

EdN · 07-01-2017, 10:58 PM

Unfortunately I'm having a problem with my Windows 10 not being able to boot up. I'm working on that separately. But I will try ntfsfix.

Quote:

Originally Posted by rknichols

Well, this time you did not get the "Read-only filesystem" message, but something else seems to have prevented creating the file. This smells like a damaged NTFS filesystem. Have you connected it to a Windows system and run chkdsk on it? You could try the Linux ntfsfix utility (part of the ntfsprogs package), but it has only very limited repair capability.

EdN · 07-02-2017, 10:04 PM

My Windows 10 is not working right now. So until I get it fixed let's try ntfsfix

[enowak@localhost ~]$ sudo ntfsfix /dev/sda3
Mounting volume... The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
FAILED
Attempting to correct errors...
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sda3 was processed successfully.
[enowak@localhost ~]$

I still have the same problem. I still get the error message "bash: dummyfile: No such file or directory"
I guess I'll have to wait until I get my Windows 10 up and running.

Quote:

Originally Posted by rknichols

Well, this time you did not get the "Read-only filesystem" message, but something else seems to have prevented creating the file. This smells like a damaged NTFS filesystem. Have you connected it to a Windows system and run chkdsk on it? You could try the Linux ntfsfix utility (part of the ntfsprogs package), but it has only very limited repair capability.

rknichols · 07-02-2017, 10:24 PM

One other thing you can do is look at the system error log for messages that came at the time the filesystem changed to read-only. There should be some message about what caused the kernel to protect the filesystem. There's probably nothing related to the latest "dummyfile: No such file or directory" message, but there should be something preceding the "Read-only filesystem" errors.

EdN · 07-03-2017, 01:32 AM

My Windows 10 is not working now so I decided to try what you suggested and I ran ntfsfix as follows:

[enowak@localhost ~]$ sudo ntfsfix /dev/sda3
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sda3 was processed successfully.

I mounted Seagate_2TB-1 via nautilus (Files). I then did the following:

[enowak@localhost ~]$ cd /run/media/enowak/Seagate_2TB-1/Miscellaneous
[enowak@localhost Miscellaneous]$ df .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 1953279996 1756982640 196297356 90% /run/media/enowak/Seagate_2TB-1
[enowak@localhost Miscellaneous]$ echo This is a test >dummyfile
[enowak@localhost Miscellaneous]$ ls -l dummyfile
-rwxrwxrwx. 1 enowak enowak 15 Jul 2 23:21 dummyfile
[enowak@localhost Miscellaneous]$

Wow! It worked! The odd thing is the permissions for dummyfile -> rwxrwxrwx
I would have expected something like rw-r--r--
Otherwise everything looks fine.
Thanks for your help and for hanging in there with me.

Quote:

Originally Posted by rknichols

Well, this time you did not get the "Read-only filesystem" message, but something else seems to have prevented creating the file. This smells like a damaged NTFS filesystem. Have you connected it to a Windows system and run chkdsk on it? You could try the Linux ntfsfix utility (part of the ntfsprogs package), but it has only very limited repair capability.

EdN · 07-03-2017, 08:48 PM

My Windows 10 is not working right now so I did what you suggested and tried ntfsfix as follows:

[enowak@localhost ~]$ sudo ntfsfix /dev/sda3
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sda3 was processed successfully.

I then mounted /dev/sda3 using nautilus, and did the following:

[enowak@localhost ~]$ cd /run/media/enowak/Seagate_2TB-1/Miscellaneous
[enowak@localhost Miscellaneous]$ df .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 1953279996 1756986512 196293484 90% /run/media/enowak/Seagate_2TB-1
[enowak@localhost Miscellaneous]$ echo This is a test >dummyfile
[enowak@localhost Miscellaneous]$ ls -l dummyfile
-rwxrwxrwx. 1 enowak enowak 15 Jul 3 18:38 dummyfile
[enowak@localhost Miscellaneous]$

Wow! It works! The odd thing is the permissions for dummyfile ---> rwxrwxrwx
I would expect something like rw-r--r--
Otherwise everythings seems OK now.
Thanks for your help and for hanging in there with me.

Quote:

Originally Posted by rknichols

Well, this time you did not get the "Read-only filesystem" message, but something else seems to have prevented creating the file. This smells like a damaged NTFS filesystem. Have you connected it to a Windows system and run chkdsk on it? You could try the Linux ntfsfix utility (part of the ntfsprogs package), but it has only very limited repair capability.

EdN · 07-03-2017, 09:02 PM

I did as you suggested and ran ntfsfix on /dev/sda3 before mounting it with nautilus.
Everything seems to work now. I tried to create the file dummyfile as before and it worked. The odd thing is the permissions for dummyfile are rwxrwxrwx. I would have expected rw-r--r--.
Otherwise everything is fine.
Thanks for your help and for hanging in there with me.
Ed

Quote:

Originally Posted by rknichols

Well, this time you did not get the "Read-only filesystem" message, but something else seems to have prevented creating the file. This smells like a damaged NTFS filesystem. Have you connected it to a Windows system and run chkdsk on it? You could try the Linux ntfsfix utility (part of the ntfsprogs package), but it has only very limited repair capability.

rknichols · 07-04-2017, 07:50 AM

I would rather have seen ntfsfix report that it had fixed something, but whatever.

Those permissions are normal. Windows filesysems don't support all the Linux permissions bits, so those permissions are simulated by mount options for the entire filesystem. Take a look at the ntfs-3g manpage, in particular the umask, fmask, and dmask options.

EdN · 07-05-2017, 03:56 AM

Actually there was a report that said something was fixed but I forgot to copy it before I shut down. Of course the next time I ran ntfsfix everthing was OK.
As for the permissions, I forgot that this is a Windows, not a Linux, filesystem. I believe in Linux rx-r--r-- would be normal for a file.
Again, many thanks.

Quote:

Originally Posted by rknichols

I would rather have seen ntfsfix report that it had fixed something, but whatever.

Those permissions are normal. Windows filesysems don't support all the Linux permissions bits, so those permissions are simulated by mount options for the entire filesystem. Take a look at the ntfs-3g manpage, in particular the umask, fmask, and dmask options.

pan64 · 07-05-2017, 04:04 AM

ntfsfix is not really reliable, you need fix ntfs on windows. otherwise you may run into the same/similar problems again.