Hey guys,

 

Last week i posted a question, but no one seems to know the answer to it:

( http://lime-technology.com/forum/index.php?topic=9450.0 )

 

I can now be more specific, so maybe there is someone who can solve this puzzle for me..

 

The problem is that i can not delete, remove or rename files on disk6. I CAN move files to it.

It seems to me that disk6 is a read-only file system? In my syslog you can see unRAID plots a line which says that.

The picture is not that important, but shows the message i get when trying to rename a file (in dutch).

("you have to be authorized by TOWER/root to change anything to this file", says Windows..)

I'm a complete newbie with servers, unRAID & Linux, so probably it's something obvious and simple, but i can't manage to get this going.

 

History:

My server is running for two weeks now, and i have had this problem from the beginning.

First i thought it had something to do with Dune Explorer, which scans my server for new movies, but it has nothing to do with that.

A few days ago i had a lot of errors on disk6, even after 2 parity checks. So i bought myself a new parity drive and replaced disk6 with my old parity drive.

After the data rebuild i did a parity check again which returned no errors, which you can see in my syslog.

The problem is still there, so i guess i didn't had to buy a new disk after all ..

 

Does anyone understand why i have this problem? I'm really frustrated with this problem, please help!

syslog.txt

Hey guys,

 

Last week i posted a question, but no one seems to know the answer to it:

( http://lime-technology.com/forum/index.php?topic=9450.0 )

 

I can now be more specific, so maybe there is someone who can solve this puzzle for me..

 

The problem is that i can not delete, remove or rename files on disk6. I CAN move files to it.

It seems to me that disk6 is a read-only file system? In my syslog you can see unRAID plots a line which says that.

The picture is not that important, but shows the message i get when trying to rename a file (in dutch).

("you have to be authorized from TOWER/root to change anything to this file", says Windows..)

I'm a complete newbie with servers, unRAID & Linux, so probably it's something obvious and simple, but i can't manage to get this going.

 

History:

My server is running for two weeks now, and i have had this problem from the beginning.

First i thought it had something to do with Dune Explorer, which scans my server for new movies, but it has nothing to do with that.

A few days ago i had a lot of errors on disk6, even after 2 parity checks. So i bought myself a new parity drive and replaced disk6 with my old parity drive.

After the data rebuild i did a parity check again which returned no errors, which you can see in my syslog.

The problem is still there, so i guess i didn't had to buy a new disk after all ..

 

Does anyone understand why i have this problem? I'm really frustrated with this problem, please help!

Last week you did not mention the line in your syslog. nor did you post one for anybody to discover it on your behalf.

 

The line in your syslog indicates that unRAID's OS has mounted the file system as read-only to prevent further corruption to it.  This is because it detected file-system corruption.

 

The fix is fairly straight-forward.  It is to run the equivalent of checkdisk in windows on the file-system.

 

The procedure to do that is well documented in the wiki here:

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

 

To help others like yourself in the future I also added an item in the FAQ

http://lime-technology.com/wiki/index.php?title=FAQ&action=submit#Why_is_my_disk_being_marked_as_Read-Only

 

Joe L.

Thank you very much !

 

I'm gonna try this now.

From now on, when i have a question, i'll post my syslog.

Last week i didn't even know how to do that..

 

Grtngz,

 

Bart

Ok,

 

It said i had to use the "--rebuild-tree"-command, so i did.

It's now busy (for a very long time i suppose).

 

When its ready, i will post the result.

 

Grtngz,

 

Bart

The time it takes is dependent on how many files and directories you have on the disk, in combination with the size of the disk.

 

Good luck.  at least it should fix the problem.

 

 

It's finished.

 

Everything seems to work just fine now!!

 

Thanx for the very good advice!

 

Grtngz,

 

Bart