Turned on the server today. Got this. Its a new hard disc mounted like 2 months back. 

Some immediate help is needed on this guys. 

 

The hard disc is physically running when i tried to sense in my hand, also the warmth while running is there too. Its just not there getting mounted.

 

tower-diagnostics-20191209-1124.zip

Edited December 9, 20196 yr by ThePhotraveller

When a previously working drive shows up as ‘unmountable’ it normally means there is some level of file system corruption.    To fix this restart the array in Maintenance mode and then click on the drive on the Main tab and the resulting dialog has options for checking and repairing the file system on the drive.  
 

Initially this will run a read-only check which merely reports on what the repair process would do without actually changing anything.  To actually fix any reported corruption you need to rerun without the -n (no-modify) flag and if then prompted to do so with the -L flag added.    Assuming the repair completes you should now be able to restart the array in normal mode and the drive should mount OK.

 

if you get any output you do not understand ask again for guidance.

4 hours ago, itimpi said:

When a previously working drive shows up as ‘unmountable’ it normally means there is some level of file system corruption.    To fix this restart the array in Maintenance mode and then click on the drive on the Main tab and the resulting dialog has options for checking and repairing the file system on the drive.  
 

Initially this will run a read-only check which merely reports on what the repair process would do without actually changing anything.  To actually fix any reported corruption you need to rerun without the -n (no-modify) flag and if then prompted to do so with the -L flag added.    Assuming the repair completes you should now be able to restart the array in normal mode and the drive should mount OK.

 

if you get any output you do not understand ask again for guidance.

Done the check. This is what its showing. 

Run again without -n or nothing will be done.

4 hours ago, johnnie.black said:

Run again without -n or nothing will be done.

This now. What do i do after this guys. 

Use -L

Hoo thanks guys. Yay solved it. May i know the reason why it would ve happened. So that i can avoid anything as such in future ? 

Most commonly it can happen after an unclean shutdown.