hello.

 

disk went disabled after a series of warnings - none about the HDD condition !

 

Invalid folder cache-65cbf03a98f1 contained within /mnt	
Invalid folder cache-8124ae6239d2 contained within /mnt	
Invalid folder cache-8ceef825acdd contained within /mnt	
Invalid folder cache-Tower contained within /mnt	
Invalid folder share contained within /mnt	
Invalid folder socket-65cbf03a98f1 contained within /mnt
Invalid folder socket-8124ae6239d2 contained within /mnt
Invalid folder socket-8ceef825acdd contained within /mnt
Invalid folder socket-Tower contained within /mnt
Invalid folder tmp-65cbf03a98f1 contained within /mnt
Invalid folder tmp-8124ae6239d2 contained within /mnt
Invalid folder tmp-8ceef825acdd contained within /mnt
Invalid folder tmp-Tower contained within /mnt

so how can i re-enable the HDD without the need of rebuilding it ?

 

cheers

You should provide the full diagnostics (Tools->Diagnostics) not just a log snippet.  The events leading up to the problem are typically more important than the final messages.

 

the messages you did post suggest that a lot of spurious folders have been created under /mnt.    Any idea what caused this?    A common reason would be something like a misconfigured docker.

As itimpi said.

 

Go to Tools - Diagnostics and post the complete zip.

 

And you definitely have something misconfigured. Only the system should create folders in /mnt. That is where it mounts the disks and user shares. Any folders you create there will actually be in RAM taking up memory, and will not survive a reboot.

 

1 hour ago, ahab666 said:

so how can i re-enable the HDD without the need of rebuilding it ?

 

Usually rebuilding is what you DO want to do, since the contents of the disabled disk are invalid and no longer consistent with parity. It is either rebuild data or rebuild parity, and data is the one that is wrong in this case.

 

Get us that diagnostic.

@trurl

okay here is my diagnostic file .... and btw. the array disk is still disabled, all user shares as well as disk shared appear to be unprotected  ....

@itimpi

there are only 2 docker apps i use krusader and ubuntu-libreoffice ....

 

cheers

tower-diagnostics-20170408-0908.zip

SMART for that disk looks OK. Since you rebooted before getting the diagnostic we can't tell what happened that caused it. Anytime you have a problem you should always get a diagnostic before rebooting if possible.

 

The most common cause of disk disabled is connection issues. Check all connections. You can rebuild the disk to itself

 

Stop array.

Unassign disk.

Start array so disk shows as missing.

Stop array.

Reassign disk.

Start array to begin rebuild.

 

You have Transmission running as a plugin. You should consider using a docker instead. Can't tell whether it is the cause of your invalid folders or not. Could also be misconfigured dockers as we said.

 

After you get the disk rebuilt we can investigate further.

@trurl:

 

did the rebuild and everything seems to be fine for now .... anyway please send me a not about wich files you need for further investigations ....

 

cheers and thx for your support

2 hours ago, ahab666 said:

@trurl:

 

did the rebuild and everything seems to be fine for now .... anyway please send me a not about wich files you need for further investigations ....

 

cheers and thx for your support

 

Do you have any VMs?

 

Do you know how to get to the command line?

 

hello again,

 

no I have no VMs installed

 

command line on the server itself or via an SSL client I guess right ?

 

need to find one that works in W10 though

Putty works with Win10

To investigate the folders that are being created in /mnt:

 

Set all dockers to NOT autostart.

 

Boot in SAFE mode.

 

From the command line, post the result of this:

ls -lah /mnt

If you're using puTTY it has a menu button at the left on the title bar. I think we used to call this the system button on Windows 3 but most people probably don't pay it much attention these days. It is the button that is found on most windows that has selections to minimize/maximize, close, or move/size the window using the arrow keys. puTTY has added some additional functionality to that button, one of which is "Copy All to Clipboard". That is a good way to get your results into something that you can then edit to just give the part needed.

2 hours ago, trurl said:

To investigate the folders that are being created in /mnt:

 

Set all dockers to NOT autostart.

 

Boot in SAFE mode.

 

From the command line, post the result of this:

ls -lah /mnt

If you're using puTTY it has a menu button at the left on the title bar. I think we used to call this the system button on Windows 3 but most people probably don't pay it much attention these days. It is the button that is found on most windows that has selections to minimize/maximize, close, or move/size the window using the arrow keys. puTTY has added some additional functionality to that button, one of which is "Copy All to Clipboard". That is a good way to get your results into something that you can then edit to just give the part needed.

 

here is the output :

 

Linux 4.9.19-unRAID.
Last login: Thu Apr 13 17:02:02 +0200 2017 on /dev/pts/0 from 192.168.0.11.
root@Tower:~# ls -lah /mnt
total 32K
drwxr-xr-x 17 root   root  340 Apr 13 11:17 ./
drwxr-xr-x 18 root   root  400 Apr 13 11:17 ../
drwxrwxrwx  1 nobody users 290 Apr 13 17:30 cache/
drwxrwxrwx 10 nobody users 181 Apr 13 17:30 disk1/
drwxrwxrwx  4 nobody users  46 Apr 13 17:30 disk10/
drwxrwxrwx  4 nobody users  59 Apr 13 17:30 disk11/
drwxrwxrwx  3 nobody users  19 Apr 13 17:30 disk2/
drwxrwxrwx  3 nobody users  19 Apr 13 17:30 disk3/
drwxrwxrwx  3 nobody users  26 Apr 13 17:30 disk4/
drwxrwxrwx  3 nobody users  19 Apr 13 17:30 disk5/
drwxrwxrwx  3 nobody users  97 Apr 13 17:30 disk6/
drwxrwxrwx  3 nobody users  26 Apr 13 17:30 disk7/
drwxrwxrwx  3 nobody users  34 Apr 13 17:30 disk8/
drwxrwxrwx  4 nobody users  46 Apr 13 17:30 disk9/
drwxrwxrwx  2 nobody users  40 Apr 13 11:17 disks/
drwxrwxrwx  1 nobody users 290 Apr 13 17:30 user/
drwxrwxrwx  1 nobody users 181 Apr 13 17:30 user0/
root@Tower:~#

 

those nasty folders are gone …. 

So if you followed my instructions you aren't running any plugins or dockers, and

1 hour ago, ahab666 said:

those nasty folders are gone …. 

That would seem to indicate they were being created by plugins or dockers. So you could try enabling one docker at a time and see if any of those create the folders. Same for plugins.