... or change the place AD looks for edb.log?
I can't start my server 2008 foundation because AD can't access adb.log etc on virtual drive D, which I deleted to extend the partition used as C: so I could install SQL Server 2012.
Short history - Physical drive partitioned in to C and D: with C the OS drive, and D labelled as DATAPART.
C too small, so copied everything off D; to another physical drive in server, deleted the DATAPART partition assigned as D:, and extended the OS/C: partition,
Server won't restart as it can't find edb.log on D:,
Now I can only get to a command prompt. To make it worse, this reassigns the drives as C: - RECOVERY and the OS drive as D, (formerly C), and I can't see how use DISKPART to assign a drive letter to the extended partition on the OS volume, and make it persist.
Using DISKPART I tried to re assign the other physical disk, (G) as D, so it would appear correctly at restart, but it seems DISKPART is only valid for the current session, and at restart the original settings were restored., so D: went back to being G:
I've also tried creating an autoexec.bat file with SUBST G:\D_DRIVE D: but I guess autoexec is obsolete now, because it didn't work.
The alternative is to change the location that AD looks for the edb.log, but with only a command prompt, I guess that's tricky.
Any help in plain English greatly appreciated - I'm a SQL Server developer. and not a hardware builder!