parameter 3608 errors

sql2000 build 818
i was using kb article 224071 to move model and msdb to a new drive.
after i add the parameter -T3608 and restart the server, the server will
die with the error, 2004-06-09 18:16:44.61 spid52 WARNING: problem
activating all tempdb files. See previous errors. Restart server with
-f to correct the situation.
the log says it's only recovering master, but it dies at random points.
sometimes it will die after it starts up the first user db. sometimes
it gets all the user db's started before it dies with that error.
what causes this error? this has happened to me on two servers so far.
i have to try to sneak in the detach and attach commands before sql
server decides to quit working while 3608 is enabled. once i get model
and msdb detached, moved to new location, reattached, and then restart
the server without 3608 enabled, everything is fine.My guess is that tempdb cannot be created and the first access to tempdb mak
es SQL Server "bomb". Did you try
starting using -f, as the error message say? Or using 3809?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ch" <ch@.dontemailme.com> wrote in message news:40C8580F.8D08149F@.dontemailme.com...eagreen">
> sql2000 build 818
> i was using kb article 224071 to move model and msdb to a new drive.
> after i add the parameter -T3608 and restart the server, the server will
> die with the error, 2004-06-09 18:16:44.61 spid52 WARNING: problem
> activating all tempdb files. See previous errors. Restart server with
> -f to correct the situation.
> the log says it's only recovering master, but it dies at random points.
> sometimes it will die after it starts up the first user db. sometimes
> it gets all the user db's started before it dies with that error.
> what causes this error? this has happened to me on two servers so far.
> i have to try to sneak in the detach and attach commands before sql
> server decides to quit working while 3608 is enabled. once i get model
> and msdb detached, moved to new location, reattached, and then restart
> the server without 3608 enabled, everything is fine.