MySQL Bugs: #8987: mysql fails to start after reboot

Bug #8987	mysql fails to start after reboot
Submitted:	6 Mar 2005 0:40	Modified:	8 Apr 2005 1:18
Reporter:	Dave Dyer	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	4.0.22	OS:	Windows (windows 2000)
Assigned to:		CPU Architecture:	Any

Description:
My mysql has developed a disease where the service always 
fails to start after a reboot, but fortunately then always 
succeeds in starting when launched manually.   The mysql
error log records this sequence of messages on every
shutdown/reboot sequence.

Version: '4.0.22-debug-log'  socket: ''  port: 3306  Source distribution
050303 12:04:14 MySQL: Normal shutdown

050305 16:17:13  InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 44118
InnoDB: Doing recovery: scanned up to log sequence number 0 44118
050305 16:17:13  InnoDB: Flushing modified pages from the buffer pool...
050305 16:17:13  InnoDB: Started
MySQL: ready for connections.
Version: '4.0.22-debug-log'  socket: ''  port: 3306  Source distribution

and the windows even viewer reports this for every reboot:
The MySQL service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 0 milliseconds: No action.

How to repeat:
reboot my system.

I guess this isn't InnoDB issue, its start message error happens because
the server eventually has crashed.
Could you please test the below:

Remove the service of the debug version server from a DOS prompt:

mysqld-nt --remove

and install the service for the release server:

mysqld-nt --install

and test if continues the same issue.

Thanks in advance.

this made no difference

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

I suspect this problem is related to using a UNC path as 
the mysql log address in my.conf