todd@lecus.com

texasgb
texasgb Member Posts: 3 New User
edited November 2023 in 2018 Archives
Acer Swift Laptop  - Installed M2 SSD, cloned the 64GB flash onto the new M2 SSD, all worked fine.  Booted, and everything running from the new (C:) 240GB M2 SSD.  -BIOS was verified as well, to list the SSD as the 1st boot device in order.  So since I didn't need the flash drive, which was now showing as (D:),  I went into disk manager, and deleted the D: partition.  -  Now -- The computer won't boot, and I can't recover.  The D: drive shouldn't even be needed, everything was running from the SSD (C:\).   Any thoughts on why this happened, or how to recover?

Answers

  • padgett
    padgett ACE Posts: 4,532 Pathfinder
    I suspect the 64GB flash also had a BOOT (100MB) and a RECOVERY partition. Did you do anything to them ? Did you make a recovery drive and system image before doing all of this ? Should be able to recover from them.
  • texasgb
    texasgb Member Posts: 3 New User
    I cloned the 64GB Flash, with all the partitions, BOOT, Recovery, etc..  to the M2 SSD.   --   And even tested doing a complete system recover, reload of Windows, from the cloned/new recovery partition on the SSD.  All worked --   But for whatever reason, the system "has" to see, the 64GB flash drive, and all the partitions, on first boot, even though it boots, and runs fine, from the SSD.  I had backed up the flash drive (All the partitions), before removing them, so I restored them, and then everything worked fine -- I tried other things as well - Finally gave up -- It seems, you just don't' want to touch that 64Gb Flash drive, and it's partitions.  I have everything running from the SSD, which is much faster, and all is fine now.  Makes no sense "why" you can't remove the partitions from the flash, when everything is running from the SSD, and I've built 100+ systems, never seen anything so weird.  So I'm just leaving the 64GB flash drive alone.  
  • padgett
    padgett ACE Posts: 4,532 Pathfinder
    edited March 2018
    How far into the boot did it get ? A couple of synapses fired that have seen a note that some BIOSes were storing information on a specific hardware drive. Also did diskmgmt.msi or diskpart.exe identify the new drive as disk0 or disk1 ? I think the BIOS may only look for disk 0 unless you do an F12 boot. BIOSes have gotten a lot more complex when they just looked for a partition marked as 80.