Unable to start the problem after MongoDB is not properly shut down

Some time ago accidentally closed MongoDB, ready to restart but found no, error message is as follows:   Tue Apr 11:13:30  www.2cto.com   Tue Apr 11:13:30 War Ning:32-bit servers don ' t has journaling enabled by default. Please use the--journal if you want durability. Tue Apr 11:13:30 Tue Apr 11:13:30 [initandlisten] MongoDB starting:pid=7128 port=27017 Dbpath=d:\programs\mo Ngodb204\db 32-bit host=falcon Tue Apr 11:13:30 [initandlisten] Tue Apr 11:13:30 [initandlisten] * * note:when Using MongoDB + bit, you is limited to about 2 gigabytes of data Tue APR 11:13:30 [initandlisten] * *   &NBSP ;   See http://blog.mongodb.org/post/137788967/32-bit-limitations Tue Apr 11:13:30 [initandlisten] * *   &NB Sp   with--journal, the limit is lower Tue Apr 11:13:30 [initandlisten] Tue Apr 11:13:30 [Initandlisten] db Version v2.0.4, pdfile version 4.5  www.2cto.com   Tue APR 11:13:30 [Initandlisten] git version:329f3c47 Fe8136c03392c8f0e548506cb21f8ebfTue APR 11:13:30 [Initandlisten] Build info:  windows sys.getwindowsversion (major=6, minor=0, build=6002 , platform=2, service_pack= ' Service Pack 2 ') boost_lib_version=1_42 Tue Apr 11:13:30 [Initandlisten] options: {Dbpat H: "D:\Programs\mongodb204\db"} ************** unclean shutdown detected. Visit Http://dochub.mongodb.org/core/repair for recovery instructions. ************* Tue APR 11:13:30 [Initandlisten] exception in initandlisten:12596 old lock file, terminating Tu E Apr 11:13:30 dbexit:20 Tue Apr 11:13:30 [Initandlisten] shutdown:going to close listening sockets ... Tue APR 11:13:30 [Initandlisten] shutdown:going to flush diaglog ... Tue APR 11:13:30 [Initandlisten] shutdown:going to close sockets ...  www.2cto.com   Tue APR 11:13:30 [Initandlisten] shutdown:waiting for FS preallocator ... Tue APR 11:13:30 [Initandlisten] shutdown:closing All Files ... Tue APR 11:13:30 [Initandlisten] Closeallfiles () finished Tue Apr 11:13:30 dbexit:really exiting now   Workaround:   1, delete the. Loc under%mongo_home%/db K file   2, input command Mongod--repair   3, restart MongoDB       Author in the cloud-see the world changing