Hello,

Today I wanted to "move" the file directly form my 1.5TB cache disk to it's destination.

So I'm gone through the forum to see where the hell is that button "Move Now" about people are talking about.

Not found

 

But my Syslog was all red :

Mar 30 05:33:38 Tower ntfs-3g[11418]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error

Mar 30 05:33:38 Tower ntfs-3g[11418]: Failed to read of MFT, mft=5 count=1 br=-1: Input/output error

all the 3000 lines are alike.

 

Then I stopped the array (stop button on the Main screen), and Restart after a while.

The same red message appears now somewhere in the syslog.

 

Where have I to look at?

 

Is there somewhere where I can found an error table?

 

Thanks

 

 

 

Hello,

Today I wanted to "move" the file directly form my 1.5TB cache disk to it's destination.

So I'm gone through the forum to see where the hell is that button "Move Now" about people are talking about.

Not found

 

But my Syslog was all red :

Mar 30 05:33:38 Tower ntfs-3g[11418]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error

Mar 30 05:33:38 Tower ntfs-3g[11418]: Failed to read of MFT, mft=5 count=1 br=-1: Input/output error

all the 3000 lines are alike.

 

Then I stopped the array (stop button on the Main screen), and Restart after a while.

The same red message appears now somewhere in the syslog.

 

Where have I to look at?

 

Is there somewhere where I can found an error table?

 

Thanks

I'm a bit confused.

 

The "Move" of files from your cache disk to the protected data disks has absolutely nothing to do with ntfs-3g.

 

So.  Answer to first question.  The "Move" button is on the unRAID web-interface.    (I don't use a cache drive, so I can't tell you specifically which one)

 

Lines in the syslog are colored "red" by unMENU's syslog viewer if they contain the word "error" anywhere in them.  The error itself can usually be looked up via a google search.

 

In this case, it appears as if you have mounted an ntfs drive.  From the google search, it also appears as if it was not cleanly un-mounted in the window's environment and might need to have checkdisk run against it in windows.

 

For any more help you'll need to zip up a copy of your syslog and attach it to your next post and describe a bit more detail about what you're doing on your server with the ntfs formatted drive.

 

See this link I found on google.  It might give you some ideas: http://serverfault.com/questions/34895/usb-drive-changes-name-from-dev-sdb-to-dev-sdc-and-back-again-when-copying

The 'move now' button is on the 'Shares' page of the unRAID web interface.

The 'move now' button is on the 'Shares' page of the unRAID web interface.

 

OK, thanks.

 

 

 

I'm a bit confused.

 

The "Move" of files from your cache disk to the protected data disks has absolutely nothing to do with ntfs-3g.

 

It was simply because I was searching this , and by the way I discover my syslog all red.

 

Lines in the syslog are colored "red" by unMENU's syslog viewer if they contain the word "error" anywhere in them.  The error itself can usually be looked up via a google search.

 

In this case, it appears as if you have mounted an ntfs drive.  From the google search, it also appears as if it was not cleanly un-mounted in the window's environment and might need to have checkdisk run against it in windows.

 

For any more help you'll need to zip up a copy of your syslog and attach it to your next post and describe a bit more detail about what you're doing on your server with the ntfs formatted drive.

 

See this link I found on google.  It might give you some ideas: http://serverfault.com/questions/34895/usb-drive-changes-name-from-dev-sdb-to-dev-sdc-and-back-again-when-copying

 

Eventually, I remember I've mounted a friend HDD, to copy some files easily directly from the unRAID server.

It was weeks ago.

And, after all, It was just after the second successful parity check I've made in the unRAID complete life.

So, and because looking at the syslog is not my cup of tea, there are chances that those errors were there running since a long time.

 

Looking at this today : no problem since the last restart on march 30th.

Thanks again.

 

-------------

 

BTW, is there a simple way to correctly stop the unRAID server just after a start?

 

My GO file :

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/emhttp &

cp /boot/config/samba/smb.conf /etc/samba

smbcontrol smbd reload-config

installpkg /boot/packages/ntfs-3g-2009.3.8-i486-1.tgz

/boot/packages/cache_dirs -B -w

/boot/unmenu/uu

 

Since I've added the cache_dirs, my unRAID fly when navigating in the directories.

Then I don't want to remove it.

But, after a start, and during a long time, there is no way to correctly stop the server, even after using "cache_dirs -q"

The best solution, after all, would be that the stop button (on the web interface) and the power button (physical) would launch this command "cache_dirs -q", but if it's not THE solution.....?

 

Any clue?