I've run into my first one of these checks when I pressed the power button on the server, expecting Linux to pick up on this, and shut down the system correctly like other Linux's do, but in NanoNAS's case, this is obviously not the case, and the machine shut off immediately.(at least I know not to do this again!
![Razz :P](./images/smilies/icon_razz.gif)
)
It took 27 minutes to check the filesystem on the single 500GB drive in the server so far(and that drive is only half-full), and I have totally lost my patience - Even with Windoze, I'd have the server up and running again inside 3 minutes - even with an illegal shutdown...
I don't consider this filesystem check thing a very clever idea, as with modern drives of several hundred GB each, it is not really practical to have the server offline for eternity while the system checks the disks...
The idea of a server, is to have it up and running again ASAP if there is a power failure or other problem. If NanoNAS needs to run disk scanning, should it not be done AFTER the server is back on line?(such as running Scandisk or CHKDSK /F in XP after XP has restarted) This could be run as a seperate background process after the server is online again...
QUESTION: How do I turn this auto-checking off completely - once I add more drives, I don't want to have to deal with this delay. Once I have 4 drives in there, if NanoNAS has to check each one after an unclean dismount, this would take 1.8 hours to do(based on the 27 minute check-time of the first one), and once I have all 8 drives in place, this would potentially increase to 3.6 hours which is totally ludicrous. If all 8 drives are full to capacity, this could represent 7.2 hours worth of checking time - totally unacceptable for a server.
If I can't totally turn off the auto-checking, I will delete NanoNAS and go back to a Windows 2000-based Server.
In some ways, I hope I have got my maths wrong with respect to the time taken to check(say) 4x 500GB drives as being 1.8 hours, but if I am actually correct, then this is not satisfactory as this is far too long to wait.
Perhaps someone here can give me some pointers?