Skip to main content

Intel's SSD migration tool & TrueCrypt - big gotcha

TL;DR: If you must help someone migrate from HDD to SSD, uninstall/disable any drive encryption before even starting this process.

If you are going to use Intel's SSD migration software (Acronis-based) to 'help someone out', be VERY VERY VERY VERY certain that the drive is not encrypted before starting.  In retrospect a pretty noob mistake, but it does highlight something that I haven't had much exposure to (disk encryption).

What happens is that the clone software modifies the MBR or something like that so you boot into the clone software rather than the OS.  TrueCrypt goes bananas and the Intel/Acronis software throws "MBR ERROR #3" and/or #2/#1.

No prob, right?  Just do a bootrec fixmbr/fixboot off a Windows recovery disk and you're back to normal!  Nuh uh.  Drive is nuked.  I would note that at this point NO CLONING HAS BEEN DONE.  Simply installing the software, starting the clone wizard, and rebooting has broken the drive.

The only way to recover it is using your TrueCrypt recovery disk.  You do have this, right?


Right?


I had hoped that simply mounting the drive in another computer running TrueCrypt and entering the boot password would fix it...not the case. (or maybe the TrueCrypt versions were off)  The only relevant Google hit I got mentioned mounting the drive using 'advanced' options.

Anyways, if you can't find that disk, just give up now.  Intel, please update your documentation to include a disclaimer about encryption.

Bonus:  I would assume that you could use something like Clonezilla to do a block-level clone of the drive, but then you have to deal with the fact that the partitions don't line up, because most commodity laptop drives these days are 500GB, and the affordable SSDs are 100-200GB.  If there is a bulletproof and easy (and free) way of dealing with that issue, I'm all ears.

Comments

  1. You can still recover the data. Hook it up to another machine, and then do this in TrueCrypt:

    * Click Select Device, and pick the drive or partition
    * Click System > Mount without pre-boot authentication
    * Enter the password and it should mount the encrypted volume

    I've had to do this many a times in the past, when I didn't have access to the recovery disk :)

    ReplyDelete
  2. No foolin', that (mount without pre-boot authentication) works!! At least we can recover the data now. Thanks, Keith!

    ReplyDelete
  3. VeraCrypt offers includes that are same as seen in Truecrypt yet includes security improvements. It permits production of encoded holders on hard drives. It likewise permits plate allotment or hard drives including framework parcel encryption.

    ReplyDelete

Post a Comment

Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:


You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\user.name\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):
MSSQLSVC/tor-sql-01.domain.local:1433

If you use a user object to auth (such as a service account, or admin account):
MSSQLSVC/username:1433

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/server1.company.local:1433 is registered on these accounts:
CN=SERVER1,OU=servers,OU=resources,DC=company,DC=local
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get going...so here's a config and brain dump...

Why?
You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

How?
ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
OMD
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…