Can not boot after double space 2

For all your technical questions and concerns.

Can not boot after double space 2

Postby Tbarran » Fri Jun 12, 2015 12:18 am

I have a thinkpad X1 carbon 3rd gen with a 500gb SSD, after running doublespace 2 without errors, compressing and rebooting, I enter a system recovery reboot loop.

When I boot into a recovery partition, trying to access the main boot partition gives me an error that the file system is unrecognized.

Guidance please?

Windows 8.1, 64bit
T
Tbarran
 
Posts: 4
Joined: Fri Jun 12, 2015 12:06 am

Re: Can not boot after double space 2

Postby Tbarran » Fri Jun 12, 2015 1:58 pm

Here's the BCDEDIT dump:


Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {bootmgr}
{4236c441-c755-11e4-a477-806e6f6e6963}
{4236c442-c755-11e4-a477-806e6f6e6963}
{4236c443-c755-11e4-a477-806e6f6e6963}
{4236c444-c755-11e4-a477-806e6f6e6963}
{4236c445-c755-11e4-a477-806e6f6e6963}
{4236c446-c755-11e4-a477-806e6f6e6963}
{4236c447-c755-11e4-a477-806e6f6e6963}
timeout 0

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {default}
resumeobject {34ec8baa-c6ce-11e4-a843-605718e36c69}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 5

Firmware Application (101fffff)
-------------------------------
identifier {4236c43a-c755-11e4-a477-806e6f6e6963}
description Setup

Firmware Application (101fffff)
-------------------------------
identifier {4236c43b-c755-11e4-a477-806e6f6e6963}
description Boot Menu

Firmware Application (101fffff)
-------------------------------
identifier {4236c43c-c755-11e4-a477-806e6f6e6963}
description Diagnostic Splash Screen

Firmware Application (101fffff)
-------------------------------
identifier {4236c43d-c755-11e4-a477-806e6f6e6963}
description Lenovo Diagnostics

Firmware Application (101fffff)
-------------------------------
identifier {4236c43e-c755-11e4-a477-806e6f6e6963}
description Startup Interrupt Menu

Firmware Application (101fffff)
-------------------------------
identifier {4236c43f-c755-11e4-a477-806e6f6e6963}
description Rescue and Recovery

Firmware Application (101fffff)
-------------------------------
identifier {4236c440-c755-11e4-a477-806e6f6e6963}
description MEBx Hot Key

Firmware Application (101fffff)
-------------------------------
identifier {4236c441-c755-11e4-a477-806e6f6e6963}
description USB CD

Firmware Application (101fffff)
-------------------------------
identifier {4236c442-c755-11e4-a477-806e6f6e6963}
description USB FDD

Firmware Application (101fffff)
-------------------------------
identifier {4236c443-c755-11e4-a477-806e6f6e6963}
description ATA HDD0

Firmware Application (101fffff)
-------------------------------
identifier {4236c444-c755-11e4-a477-806e6f6e6963}
description ATA HDD1

Firmware Application (101fffff)
-------------------------------
identifier {4236c445-c755-11e4-a477-806e6f6e6963}
description ATA HDD2

Firmware Application (101fffff)
-------------------------------
identifier {4236c446-c755-11e4-a477-806e6f6e6963}
description USB HDD

Firmware Application (101fffff)
-------------------------------
identifier {4236c447-c755-11e4-a477-806e6f6e6963}
description PCI LAN

Firmware Application (101fffff)
-------------------------------
identifier {4236c448-c755-11e4-a477-806e6f6e6963}
description IDER BOOT CDROM

Firmware Application (101fffff)
-------------------------------
identifier {4236c449-c755-11e4-a477-806e6f6e6963}
description IDER BOOT Floppy

Firmware Application (101fffff)
-------------------------------
identifier {4236c44a-c755-11e4-a477-806e6f6e6963}
description ATA HDD

Firmware Application (101fffff)
-------------------------------
identifier {4236c44b-c755-11e4-a477-806e6f6e6963}
description ATAPI CD

Firmware Application (101fffff)
-------------------------------
identifier {4236c44c-c755-11e4-a477-806e6f6e6963}
description PCI LAN

Windows Boot Loader
-------------------
identifier {default}
device partition=C:
path \windows\system32\winload.efi
description Windows 8.1
locale en-US
inherit {bootloadersettings}
recoverysequence {66eb71d9-c74d-11e4-8254-f38c18a9bf91}
integrityservices Enable
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \windows
resumeobject {34ec8baa-c6ce-11e4-a843-605718e36c69}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {66eb71d9-c74d-11e4-8254-f38c18a9bf91}
device ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{66eb71da-c74d-11e4-8254-f38c18a9bf91}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-us
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{66eb71da-c74d-11e4-8254-f38c18a9bf91}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Resume from Hibernate
---------------------
identifier {34ec8baa-c6ce-11e4-a843-605718e36c69}
device partition=C:
path \windows\system32\winresume.efi
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
recoverysequence {66eb71d9-c74d-11e4-8254-f38c18a9bf91}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems No

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {66eb71da-c74d-11e4-8254-f38c18a9bf91}
description Windows Recovery
ramdisksdidevice partition=D:
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Setup Ramdisk Options
---------------------
identifier {ramdiskoptions}
description Ramdisk options
ramdisksdidevice boot
ramdisksdipath \boot\boot.sdi
Tbarran
 
Posts: 4
Joined: Fri Jun 12, 2015 12:06 am

Re: Can not boot after double space 2

Postby admin » Fri Jun 12, 2015 10:41 pm

Ouch! While unlikely, we cannot rule out SSD corruption in these scenarios, especially since the file system is never formatted by DoubleSpace 2, and thus could not have normally changed its type.

Did you try running chkdsk from your recovery environment?
ZIPmagic
The Next Generation Data Compression Platform
User avatar
admin
Site Admin
 
Posts: 229
Joined: Sat Feb 22, 2014 12:35 pm

Re: Can not boot after double space 2

Postby Tbarran » Sat Jun 13, 2015 3:59 am

I will run chkdsk and report back shortly, don't think its a drive failure since everything worked perfect until the first reboot after the compress was completed.

It feels to me like whatever the boot loader should be booting into in order to access the double space volume isn't booting. I do have LoJack installed, wondering if that could have prevented a proper repointing of the boot manager.

Is it possible that I chose settings that compressed my volume and yet somehow deleted the original partition?
I did not create a restore volume, so this is a bit stressful.
T
Tbarran
 
Posts: 4
Joined: Fri Jun 12, 2015 12:06 am

Re: Can not boot after double space 2

Postby Tbarran » Sat Jun 13, 2015 5:11 am

Running chkdsk /offlinescanandfix allows me access to an uncorrupted c: with an 87 gig ZIPmagic.wim, and my file system looking complete and intact.

Further digging shows an SrtTrail.txt log indicating "Boot Manager failed to find OS loader." And a subsequent automated recovery error of 0x490, Boot configuration data store repair failed.

So in other words I can see the full partition but can't boot in. When I let the computer try to boot it, it reenters the same boot loop and I have to run chkdsk again from recovery partition to access.
T
Tbarran
 
Posts: 4
Joined: Fri Jun 12, 2015 12:06 am

Re: Can not boot after double space 2

Postby admin » Sat Jun 13, 2015 3:21 pm

For some reason, something is corrupting your boot partition every time you boot. Do you have any custom software, possibly even malware, active during boot time which is incompatible with WIMBoot? Perhaps even OEM IBM software?

At any rate, your data seems safe - make sure to backup your ZIPmagic.WIM file to an external disk as soon as possible. If you used an Undo Disk, this backup is already available for you on your Undo Disk. Make sure you also copy files in your folders excluded from compression, if any (typically Microsoft Outlook files on a clean install of ZIPmagic) to ensure they're backed up as well.

Next, on the off chance that you are infected with a virus, or other unwanted malware, I'd do a full system restore to a clean condition. Install ZIPmagic after that, start DoubleSpace 2, plug-in your Undo Disk (or your manual backup disk with ZIPmagic.wim stored at the root), and then choose Clone | Restore | Restore Compressed to try again to enjoy a doubled disk, or just Clone | Restore | Restore Uncompressed to give up on the compression adventure for now. Remember to restore any files you manually backed up in excluded folders.

Please let us know what you find - whether some OEM software breaks things, whether it was malware/a virus/etc.
ZIPmagic
The Next Generation Data Compression Platform
User avatar
admin
Site Admin
 
Posts: 229
Joined: Sat Feb 22, 2014 12:35 pm


Return to Support

Who is online

Users browsing this forum: No registered users and 1 guest

cron