Main DC not recoverable - next step?

Hello
We had a domain with 2 DCs, one of these (the first one) was irreperably damaged, with no backups. I am having problems with various things and it seems that it is because of the FSMO roles that are still held by the dead server. I have added a new DC to bring the number of DCs up to 2, and running dcdiag shows some problems (I have cut out the tests that passed to save space):
#NEWSERVER - the DC I just promoted
#OLDSERVER - the dead, irreperable server
#server2 - the second DC, unchanged

Starting test: KnowsOfRoleHolders
         [OLDSERVER] DsBindWithSpnEx() failed with error 1722,
         Win32 Error 1722.
         Warning: OLDSERVER is the Schema Owner, but is not responding to DS RPC Bind.
         [OLDSERVER] LDAP search failed with error 58,
         Win32 Error 58.
         Warning: OLDSERVER is the Schema Owner, but is not responding to LDAP Bind.
         Warning: OLDSERVER is the Domain Owner, but is not responding to DS RPC Bind.
         Warning: OLDSERVER is the Domain Owner, but is not responding to LDAP Bind.
         Warning: OLDSERVER is the PDC Owner, but is not responding to DS RPC Bind
.
         Warning: OLDSERVER is the PDC Owner, but is not responding to LDAP Bind.          Warning: OLDSERVER is the Rid Owner, but is not responding to DS RPC Bind.
         Warning: OLDSERVER is the Rid Owner, but is not responding to LDAP Bind.
         Warning: OLDSERVER is the Infrastructure Update Owner, but is not respond
ing to DS RPC Bind.
         Warning: OLDSERVER is the Infrastructure Update Owner, but is not respond
ing to LDAP Bind.
         ......................... NEWSERVER failed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... NEWSERVER failed test RidManager
[snip]
      Starting test: frsevent
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
         Group Policy problems.
[snip]
      Starting test: FsmoCheck
         Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
         A Global Catalog Server could not be located - All GC's are down.
         Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
         A Primary Domain Controller could not be located.
         The server holding the PDC role is down.
         ......................... domain.mydomain.net failed test FsmoCheck

So I now try to "sieze" the roles with the older, non-failing server. I understand that this will effectively cause the old dead server to need to be formatted if it needs to get rejoined to the network:

C:\>ntdsutil
ntdsutil: roles
fsmo maintenance: connections
server connections: connect to server server2
Binding to server2 ...
Connected to microlinkt using credentials of locally logged on user.
server connections: q
fsmo maintenance: sieze pdc
Error 80070057 parsing input - illegal syntax?
fsmo maintenance: Sieze PDC
Error 80070057 parsing input - illegal syntax?
fsmo maintenance:

Is there something else I should do? The error suggests improper syntax, but I have copied directly from the microsoft support page.
I am running a samba domain member, and this is failing because it cannot find a PDC, obviously because the PDC role server is offline. Any ideas how to get the roles transferred to the "living" servers?
Thanks