Dell XPS non-bootable after SupportAssist, glance over my proposed fix
Original-Beitrag von::
Summarized: SSD issues, not booting due to missing EFI, primary volume recognized as RAW. The concern: losing data. I believe I'm comfortable with rewriting the EFI with bootable image, but will relabeling the RAW volume to NTFS where my primary data storage is have a chance of losing data? My understanding is the command will re-label the volume without formatting.
Daily driver with usage within 24 hours previous, boot up to error "No bootable image" - have seen this issue with this very Dell XPS (and many other reports online) prior due to updates and usage a toggle of the UEFI to legacy boot or verifying secure boot is disabled fixed it.
[br]
This case is different, UEFI shows two partitions with neither bootable. When manually attempting to set path for \EFI\Boot\bootx64.efi is nowhere to be found under file system 0 or 1. I only see a BOOTSECT.BAK file and IndexerVolumeGuid under system volume information.
[br]
So it seems to me my EFI volume needs to be rewritten which I can follow along from this guide:
[br]
Desired outcome: Get bootable again, no loss of data.
Planned solution: Rewrite MBR and rebuild Boot Configuration File as advised above to get bootable. Targeting Volume 1 labeled ESP.
[br]
Then set the primary storage volume back to NTFS using command "format fs=ntfs label=volume label quick"
[br]
My questions: Am I misunderstanding/missing anything here or have you some additional guidance? Further, is the above command necessary and will it risk losing my data, does it actually format the partition? Or are we simply telling the filesystem to be NTFS and that's all?
Why do I show 3 more additional RAW filesystems and should I change them to NTFS also?
I don't understand why I show so many volumes (5) and partitions (7) on this disk - 3 recovery partitions, one of which nears 7GB, but I am not able to use that as a bootable image to get to command prompt like I am the bootable USB...
[br]
-
Volume 0 RAW PARTITION 110GB Volume 1 - ESP FAT32 PARTITION 500MB Volume 2 RAW PARTITION 750MB Volume 3 RAW PARTITION 511MB Volume 4 RAW PARTITION 7110MB
Changing UEFI/Legacy Ensuring Secure Boot is disabled Adding boot delay Attempting to manually navigate to bootx64 Startup repair via Win10 bootable image Updating BIOS to latest
[br]
During this process, before trying the BIOS update solution, I noticed it said I was on A03, I know I did a BIOS update last year, the newest BIOS is A20 - how in the world did that happen?
[br]
Additional details:
[br]
I noticed some battery abnormalities, I went to run a diagnostic (forgetting there was onboard diagnostic) and via the Dell website SupportAssist was installed. Apparently there's some security vulnerabilities with this and it was just after the install and diagnostic ran that my machine became non-bootable. Diagnostics showed me what I already knew that battery is in fair health. Ran a thorough diagnostic on SSD via onboard and it passed.
Dell XPS non-bootable after SupportAssist, glance over my proposed fix
Original-Beitrag von::
Summarized: SSD issues, not booting due to missing EFI, primary volume recognized as RAW. The concern: losing data. I believe I'm comfortable with rewriting the EFI with bootable image, but will relabeling the RAW volume to NTFS where my primary data storage is have a chance of losing data? My understanding is the command will re-label the volume without formatting.
[br]
Details:[br]
Dell XPS 13 9343, Win10 x64, Lite-On L8T128L9G-11 (128GB)
[br]
Daily driver with usage within 24 hours previous, boot up to error "No bootable image" - have seen this issue with this very Dell XPS (and many other reports online) prior due to updates and usage a toggle of the UEFI to legacy boot or verifying secure boot is disabled fixed it.
[br]
This case is different, UEFI shows two partitions with neither bootable. When manually attempting to set path for \EFI\Boot\bootx64.efi is nowhere to be found under file system 0 or 1. I only see a BOOTSECT.BAK file and IndexerVolumeGuid under system volume information.
[br]
So it seems to me my EFI volume needs to be rewritten which I can follow along from this guide:
[br]
Desired outcome: Get bootable again, no loss of data.
++http://woshub.com/how-to-repair-uefi-bootloader-in-windows-8/++
Planned solution: Rewrite MBR and rebuild Boot Configuration File as advised above to get bootable. Targeting Volume 1 labeled ESP.
[br]
Then set the primary storage volume back to NTFS using command "format fs=ntfs label=volume label quick"
[br]
My questions: Am I misunderstanding/missing anything here or have you some additional guidance? Further, is the above command necessary and will it risk losing my data, does it actually format the partition? Or are we simply telling the filesystem to be NTFS and that's all?
Why do I show 3 more additional RAW filesystems and should I change them to NTFS also?
I don't understand why I show so many volumes (5) and partitions (7) on this disk - 3 recovery partitions, one of which nears 7GB, but I am not able to use that as a bootable image to get to command prompt like I am the bootable USB...
[br]
Volume 0 RAW PARTITION 110GB Volume 1 - ESP FAT32 PARTITION 500MB Volume 2 RAW PARTITION 750MB Volume 3 RAW PARTITION 511MB Volume 4 RAW PARTITION 7110MB
[br]
Partition 1 System 500MB 1024KB Partition 2 OEM 40MB 501MB Partition 3 Reserved 128MB 541MB Partition 4 Recovery 750MB 669MB Partition 5 Primary 110GB 1419MB Partition 6 Recovery 511MB 111GB Partition 7 Recovery 7110MB 112GB
[br]
Previously attempted solutions:
Changing UEFI/Legacy Ensuring Secure Boot is disabled Adding boot delay Attempting to manually navigate to bootx64 Startup repair via Win10 bootable image Updating BIOS to latest
[br]
During this process, before trying the BIOS update solution, I noticed it said I was on A03, I know I did a BIOS update last year, the newest BIOS is A20 - how in the world did that happen?
[br]
Additional details:
[br]
I noticed some battery abnormalities, I went to run a diagnostic (forgetting there was onboard diagnostic) and via the Dell website SupportAssist was installed. Apparently there's some security vulnerabilities with this and it was just after the install and diagnostic ran that my machine became non-bootable. Diagnostics showed me what I already knew that battery is in fair health. Ran a thorough diagnostic on SSD via onboard and it passed.
Thank you for your time
[image|2444270]
[image|2444271]
[image|2444272]