Dual Boot Nightmare: Recovering from a failed dual boot
Posted: 30 Oct 2021, 14:10
Its been a week since I tried dual booting my Windows 10 laptop with Ubuntu. Windows 10 was working as usual and when I installed Ubuntu and chose Install along side windows. My ssd got corrupted.
I got the Automatic Repair Loop but I can still boot ubuntu and for the past few days I researched about how to repair it ( I didn't know anything about repairing my ssd ) from chkdsk, rebuilding the bcd in order fix booting issues, clearing attributes and even formatting it completely but failed. After I did all of that even my ubuntu didn't boot anymore instead it went to MINIMAL BASH-LIKE Line editing screen ( I don't know much about Linux ) .
I tried reinstalling fresh windows on the SSD still failed to format. Tried reinstalling windows on my other drive which is a Hard drive but it wont let me install it still got errors. Eventually I removed the SSD and tried installing it again on my Hard drive and surprisingly I installed windows without a hitch.
So I got my fresh windows and decided to repair my SSD again. Since I dont have an SSD enclosure I inserted it back to the SSD M.2 slot and tried fixing it in Disk management. But I couldn't do anything about it because it was read-only
Tried clearing attributes again but it didn't also help. Finally I got to here and repairing my ssd using testdisk. Here is what I did .
This is the status of my ssd according to Crystal disk info
After analyzing in test test since its in EFI GPT
this is the result I continued on and I found out that I had 2 partitions that are 250GB one for windows and one for ubuntu. I don't really mind about the Ubuntu but I need to recover the files in windows. Tried writing it but testdisk tells me Partition: write error. I could see the correct list of files and tried copying them but it also failed.
I tried also using Deep search but I cannot identify if is working normally or it stopped working because It got to a point where I think it was stuck and I could not press stop so I closed the testdisk window.
So here I am now asking for help on how to approach this. Is my ssd dead or can it still be recovered ?
I got the Automatic Repair Loop but I can still boot ubuntu and for the past few days I researched about how to repair it ( I didn't know anything about repairing my ssd ) from chkdsk, rebuilding the bcd in order fix booting issues, clearing attributes and even formatting it completely but failed. After I did all of that even my ubuntu didn't boot anymore instead it went to MINIMAL BASH-LIKE Line editing screen ( I don't know much about Linux ) .
I tried reinstalling fresh windows on the SSD still failed to format. Tried reinstalling windows on my other drive which is a Hard drive but it wont let me install it still got errors. Eventually I removed the SSD and tried installing it again on my Hard drive and surprisingly I installed windows without a hitch.
So I got my fresh windows and decided to repair my SSD again. Since I dont have an SSD enclosure I inserted it back to the SSD M.2 slot and tried fixing it in Disk management. But I couldn't do anything about it because it was read-only
Tried clearing attributes again but it didn't also help. Finally I got to here and repairing my ssd using testdisk. Here is what I did .
This is the status of my ssd according to Crystal disk info
After analyzing in test test since its in EFI GPT
this is the result I continued on and I found out that I had 2 partitions that are 250GB one for windows and one for ubuntu. I don't really mind about the Ubuntu but I need to recover the files in windows. Tried writing it but testdisk tells me Partition: write error. I could see the correct list of files and tried copying them but it also failed.
I tried also using Deep search but I cannot identify if is working normally or it stopped working because It got to a point where I think it was stuck and I could not press stop so I closed the testdisk window.
So here I am now asking for help on how to approach this. Is my ssd dead or can it still be recovered ?