recentpopularlog in

kme : systemrecovery   35

Create a recovery drive | https://support.microsoft.com/
This seems to also be how you *delete* the existing recovery drive (which is 300-some megabytes) from the PC. This seems to be necessary in order to extend the Window OS system partition?

Via: https://www.intowindows.com/how-to-delete-the-recovery-partition-in-windows-10/
windows  win10  recoverydrive  bootableusb  systemrecovery  disasterrecovery  howto  maybesolution 
february 2019 by kme
Windows 7 won't boot "The boot selection failed because a - Microsoft Community - http://answers.microsoft.com/
g) At the DOS prompt type the following three commands:
bootrec.exe  /fixmbr
bootrec.exe  /fixboot (may return an 'Eliment not found' message)
bootrec.exe  /RebuildBcd
windows  systemrecovery  bootmanager  troubleshooting  maybesolution 
october 2015 by kme
The boot selection failed because a required device is inaccessible 0xc000000e
Other helpful resources:

https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#MBR_partitioned_disks (this is where I found the partition type for the "System Reserved" partition, but that's only on GPT and/or UEFI [dunno?] systems; the W530 had an MBR partition scheme, and its "system reserved" partition was type 0x07--and formatted to NTFS):
MBR partitioned disks

Create a partition with partition type 0xEF using fdisk (from util-linux pkg). Then format that partition as FAT32 using mkfs.fat -F32 /dev/<THAT_PARTITION>

http://social.technet.microsoft.com/Forums/windows/en-US/aa4d56d7-90f8-4ac4-a327-a3306bce671b/0xc000000f-the-boot-selection-failed-because-a-required-device-is-inaccessible?forum=w7itproinstall (nothing helpful here

http://support.microsoft.com/kb/927392#method1 (this wasn't necessary this time--the "automatic" recovery options worked, eventually)

What DIDN'T work this time:
* The Win 7 "recovery environment"'s first stab at correcting BCD problems (the one that doesn't require you to log in, see http://www.pagestart.com/images/800_SysRepair_WinFoundProblems_01.jpg):
Windows found problems with your computer's startup options.

Do you want to apply repairs and restart your computer?

View details

The details:
The following startup options will be repaired:
Name: Windows Boot Manager
Identifier: {some GUID}

The following startup options will be deleted:
Name: Windows 7
Identifier: {some GUID}
Windows Device: Partition=Not found

The following startup options will be added:
Name: Windows 7 Enterprise (recovered)
Path: Windows
Windows Device: Partition=D: (<capacity> MB)

A copy of the current boot configuration will be saved as C:\Boot\BCD.Backup.0001

* The Win 7 "Startup Repair" option (the one shown here - http://www.windowsreinstall.com/winre/repairstartup/images/index.12.gif - which requires an admin username/password)

* Setting the partition type to 0xEF (EFI reserved) (DANGER WILL ROBINSON!!! The Recovery Console's DISKPART.EXE blows away the 'volume' when you change the partition type with 'SET ID=<whatever>') using DISKPART.EXE (oops), then re-restoring the 'System' drive image using partclone, and setting the partition type (unnecessarily, but correctly) using 'fdisk' in Linux.

What finally *DID* work:

* Setting the partition type back to '07' (NTFS/HPFS/exFAT) and allowing the Windows 7 recovery disc to "apply repairs and restart [my] computer."
systemrecovery  disasterrecovery  cloning  storage  mbr  bcd  windows  win7  bootrec.exe  ibrokeit  errormessage  dammitbrain  solution  ifixedit  worklog 
december 2013 by kme
SystemRescueCd - View topic - usb_install.sh syslinux failed.
"after several attempts of manual installing syslinux I got it:

# bash ./usb_inst.sh syslinux /dev/sdf1
umount: /tmp/syslinux.mnt.23222.0: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
syslinux failed to prepare /dev/sdf1
# bash ./usb_inst.sh syslinux /dev/sdf1
usb_inst.sh: error: /dev/sdf1 is already mounted, cannot continue
# umount /dev/sdf1
# bash ./usb_inst.sh syslinux /dev/sdf1
umount: /tmp/syslinux.mnt.23418.0: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
syslinux failed to prepare /dev/sdf1
# umount /dev/sdf1
# bash ./usb_inst.sh syslinux /dev/sdf1
syslinux has successfully prepared /dev/sdf1"

So, just try it a few times.
sysresccd  bootable  livecd  rescuecd  systemrecovery  disasterrecovery  solution 
may 2013 by kme

Copy this bookmark:





to read