SSD, HDD, legacy and a really messed up situation with GRUB - how to revive lost windows and have dual boot...
So I messed up. Like really.
But let's start from the start.
A few hours ago I decided I need Ubuntu in my life, as my work laptop was being purged for the new owner.
As I am a man of my words I installed the latest version of Ubuntu.
My thought process was as follow:
- I have my SSD for Windows 10 and games
- I will use HDD for Ubuntu and work
Sounds simple, right?
As I thought I did. I have formatted the HDD, created a 100GB partition and was happy to configure Ubuntu. But wait.
Why I see no GRUB!? So here goes moment 1.
Fast googling, ha! there is a solution:
https://www.howtogeek.com/114884/how-to-repair-grub2-when-ubuntu-wont-boot/
I did it, once, twice, three times... No results. I tried - I hope every configuration. below one of many versions of outputs:
http://paste.ubuntu.com/p/wmHwNH8YF3/
OK - I did more research on the booting options. This is a Windows issue - no problem. I have created the win 10 booting USB and begun the fun time of fixing it - nothing worked.
UNTIL.
Until I figured out I will purge all of the partition except the one that is with windows and games - because... I have no clue why. Honestly, I just don't.
As I said - I am a man of my words - so I removed it all.
And now I am in a puzzle as I do not have a clue what to do next.
And I will not reinstall windows. I have there too many GB to download I just started Divinity Original Sin 2 and I loved it!
Help me out guys - as I am empty and I have no clue what to do next.
boot dual-boot grub2 partitioning
edited Dec 30 '18 at 20:08
Kristopher Ives
2,25611119
asked Dec 30 '18 at 20:02
tzimtzim
1045
|
show 9 more comments
So I messed up. Like really.
But let's start from the start.
A few hours ago I decided I need Ubuntu in my life, as my work laptop was being purged for the new owner.
As I am a man of my words I installed the latest version of Ubuntu.
My thought process was as follow:
- I have my SSD for Windows 10 and games
- I will use HDD for Ubuntu and work
Sounds simple, right?
As I thought I did. I have formatted the HDD, created a 100GB partition and was happy to configure Ubuntu. But wait.
Why I see no GRUB!? So here goes moment 1.
Fast googling, ha! there is a solution:
https://www.howtogeek.com/114884/how-to-repair-grub2-when-ubuntu-wont-boot/
I did it, once, twice, three times... No results. I tried - I hope every configuration. below one of many versions of outputs:
http://paste.ubuntu.com/p/wmHwNH8YF3/
OK - I did more research on the booting options. This is a Windows issue - no problem. I have created the win 10 booting USB and begun the fun time of fixing it - nothing worked.
UNTIL.
Until I figured out I will purge all of the partition except the one that is with windows and games - because... I have no clue why. Honestly, I just don't.
As I said - I am a man of my words - so I removed it all.
And now I am in a puzzle as I do not have a clue what to do next.
And I will not reinstall windows. I have there too many GB to download I just started Divinity Original Sin 2 and I loved it!
Help me out guys - as I am empty and I have no clue what to do next.
boot dual-boot grub2 partitioning
edited Dec 30 '18 at 20:08
Kristopher Ives
2,25611119
asked Dec 30 '18 at 20:02
tzimtzim
1045
2
A common problem with people who install Linux on systems that already have Windows is that they don't actually shut windows down since Windows 10 goes into a "soft power off' state. This causes problems because when they turn Windows back on it starts writing information over the hard drive that was kept in memory before Windows essentially hibernated.
– Kristopher Ives
Dec 30 '18 at 20:10
1
Your paste shows that you still have NTFS partitions, so those files aren't lost most likely. However, I'm unable to understand what your actual question is or how to help you because the post contains too much information that may or may not be relevant.
– Kristopher Ives
Dec 30 '18 at 20:11
1
It's possible Windows was installed as UEFI and Linux was not, or some other combination that doesn't match.
– Kristopher Ives
Dec 30 '18 at 20:14
1
In your log it says "Windows is hibernated, refused to mount."
– Kristopher Ives
Dec 30 '18 at 20:19
1
Like I mentioned originally Microsoft has made it very obscure of a process to actually shut Windows down completely. Almost all "regular" methods will hibernate it.
– Kristopher Ives
Dec 30 '18 at 20:20
|
show 9 more comments
So I messed up. Like really.
But let's start from the start.
A few hours ago I decided I need Ubuntu in my life, as my work laptop was being purged for the new owner.
As I am a man of my words I installed the latest version of Ubuntu.
My thought process was as follow:
- I have my SSD for Windows 10 and games
- I will use HDD for Ubuntu and work
Sounds simple, right?
As I thought I did. I have formatted the HDD, created a 100GB partition and was happy to configure Ubuntu. But wait.
Why I see no GRUB!? So here goes moment 1.
Fast googling, ha! there is a solution:
https://www.howtogeek.com/114884/how-to-repair-grub2-when-ubuntu-wont-boot/
I did it, once, twice, three times... No results. I tried - I hope every configuration. below one of many versions of outputs:
http://paste.ubuntu.com/p/wmHwNH8YF3/
OK - I did more research on the booting options. This is a Windows issue - no problem. I have created the win 10 booting USB and begun the fun time of fixing it - nothing worked.
UNTIL.
Until I figured out I will purge all of the partition except the one that is with windows and games - because... I have no clue why. Honestly, I just don't.
As I said - I am a man of my words - so I removed it all.
And now I am in a puzzle as I do not have a clue what to do next.
And I will not reinstall windows. I have there too many GB to download I just started Divinity Original Sin 2 and I loved it!
Help me out guys - as I am empty and I have no clue what to do next.
boot dual-boot grub2 partitioning
edited Dec 30 '18 at 20:08
Kristopher Ives
2,25611119
asked Dec 30 '18 at 20:02
tzimtzim
1045
So I messed up. Like really.
But let's start from the start.
A few hours ago I decided I need Ubuntu in my life, as my work laptop was being purged for the new owner.
As I am a man of my words I installed the latest version of Ubuntu.
My thought process was as follow:
- I have my SSD for Windows 10 and games
- I will use HDD for Ubuntu and work
Sounds simple, right?
As I thought I did. I have formatted the HDD, created a 100GB partition and was happy to configure Ubuntu. But wait.
Why I see no GRUB!? So here goes moment 1.
Fast googling, ha! there is a solution:
https://www.howtogeek.com/114884/how-to-repair-grub2-when-ubuntu-wont-boot/
I did it, once, twice, three times... No results. I tried - I hope every configuration. below one of many versions of outputs:
http://paste.ubuntu.com/p/wmHwNH8YF3/
OK - I did more research on the booting options. This is a Windows issue - no problem. I have created the win 10 booting USB and begun the fun time of fixing it - nothing worked.
UNTIL.
Until I figured out I will purge all of the partition except the one that is with windows and games - because... I have no clue why. Honestly, I just don't.
As I said - I am a man of my words - so I removed it all.
And now I am in a puzzle as I do not have a clue what to do next.
And I will not reinstall windows. I have there too many GB to download I just started Divinity Original Sin 2 and I loved it!
Help me out guys - as I am empty and I have no clue what to do next.
boot dual-boot grub2 partitioning
boot dual-boot grub2 partitioning
edited Dec 30 '18 at 20:08
Kristopher Ives
2,25611119
asked Dec 30 '18 at 20:02
tzimtzim
1045
edited Dec 30 '18 at 20:08
Kristopher Ives
2,25611119
asked Dec 30 '18 at 20:02
tzimtzim
1045
edited Dec 30 '18 at 20:08
Kristopher Ives
2,25611119
edited Dec 30 '18 at 20:08
Kristopher Ives
2,25611119
edited Dec 30 '18 at 20:08
Kristopher Ives
2,25611119
2,25611119
asked Dec 30 '18 at 20:02
tzimtzim
1045
asked Dec 30 '18 at 20:02
tzimtzim
1045
asked Dec 30 '18 at 20:02
tzimtzim
1045
1045
2
A common problem with people who install Linux on systems that already have Windows is that they don't actually shut windows down since Windows 10 goes into a "soft power off' state. This causes problems because when they turn Windows back on it starts writing information over the hard drive that was kept in memory before Windows essentially hibernated.
– Kristopher Ives
Dec 30 '18 at 20:10
1
Your paste shows that you still have NTFS partitions, so those files aren't lost most likely. However, I'm unable to understand what your actual question is or how to help you because the post contains too much information that may or may not be relevant.
– Kristopher Ives
Dec 30 '18 at 20:11
1
It's possible Windows was installed as UEFI and Linux was not, or some other combination that doesn't match.
– Kristopher Ives
Dec 30 '18 at 20:14
1
In your log it says "Windows is hibernated, refused to mount."
– Kristopher Ives
Dec 30 '18 at 20:19
1
Like I mentioned originally Microsoft has made it very obscure of a process to actually shut Windows down completely. Almost all "regular" methods will hibernate it.
– Kristopher Ives
Dec 30 '18 at 20:20
|
show 9 more comments
2
A common problem with people who install Linux on systems that already have Windows is that they don't actually shut windows down since Windows 10 goes into a "soft power off' state. This causes problems because when they turn Windows back on it starts writing information over the hard drive that was kept in memory before Windows essentially hibernated.
– Kristopher Ives
Dec 30 '18 at 20:10
1
Your paste shows that you still have NTFS partitions, so those files aren't lost most likely. However, I'm unable to understand what your actual question is or how to help you because the post contains too much information that may or may not be relevant.
– Kristopher Ives
Dec 30 '18 at 20:11
1
It's possible Windows was installed as UEFI and Linux was not, or some other combination that doesn't match.
– Kristopher Ives
Dec 30 '18 at 20:14
1
In your log it says "Windows is hibernated, refused to mount."
– Kristopher Ives
Dec 30 '18 at 20:19
1
Like I mentioned originally Microsoft has made it very obscure of a process to actually shut Windows down completely. Almost all "regular" methods will hibernate it.
– Kristopher Ives
Dec 30 '18 at 20:20
2
2
A common problem with people who install Linux on systems that already have Windows is that they don't actually shut windows down since Windows 10 goes into a "soft power off' state. This causes problems because when they turn Windows back on it starts writing information over the hard drive that was kept in memory before Windows essentially hibernated.
– Kristopher Ives
Dec 30 '18 at 20:10
A common problem with people who install Linux on systems that already have Windows is that they don't actually shut windows down since Windows 10 goes into a "soft power off' state. This causes problems because when they turn Windows back on it starts writing information over the hard drive that was kept in memory before Windows essentially hibernated.
– Kristopher Ives
Dec 30 '18 at 20:10
1
1
Your paste shows that you still have NTFS partitions, so those files aren't lost most likely. However, I'm unable to understand what your actual question is or how to help you because the post contains too much information that may or may not be relevant.
– Kristopher Ives
Dec 30 '18 at 20:11
Your paste shows that you still have NTFS partitions, so those files aren't lost most likely. However, I'm unable to understand what your actual question is or how to help you because the post contains too much information that may or may not be relevant.
– Kristopher Ives
Dec 30 '18 at 20:11
1
1
It's possible Windows was installed as UEFI and Linux was not, or some other combination that doesn't match.
– Kristopher Ives
Dec 30 '18 at 20:14
It's possible Windows was installed as UEFI and Linux was not, or some other combination that doesn't match.
– Kristopher Ives
Dec 30 '18 at 20:14
1
1
In your log it says "Windows is hibernated, refused to mount."
– Kristopher Ives
Dec 30 '18 at 20:19
In your log it says "Windows is hibernated, refused to mount."
– Kristopher Ives
Dec 30 '18 at 20:19
1
1
Like I mentioned originally Microsoft has made it very obscure of a process to actually shut Windows down completely. Almost all "regular" methods will hibernate it.
– Kristopher Ives
Dec 30 '18 at 20:20
Like I mentioned originally Microsoft has made it very obscure of a process to actually shut Windows down completely. Almost all "regular" methods will hibernate it.
– Kristopher Ives
Dec 30 '18 at 20:20
|
show 9 more comments
2 Answers
2
active
oldest
votes
Because your Windows drive is MBR, your Windows install is in BIOS boot mode.
And since you have two drives, you should always use Something Else install option and install grub2's boot loader to Ubuntu drive. Default is normally first drive and most often sda/Window drive.
But you want to keep Windows boot loader in MBR of Windows drive.
When you installed Windows was BIOS set to default boot from HDD? Windows 7 or later normally uses a separate Boot partition with two boot files, bootmgr & /boot/BCD. But you are totally missing those files. They can be in same partition as main install or c:, but normally are not.
You must use Windows repair/recovery disk to fully repair Windows.
Make sure BIOS is set to boot Windows drive. Only after Windows boots, then set BIOS to boot HDD and use grub to dual boot.
Also with multiple drives do not run Boot-Repair's auto-fix. That installs grub to every drive's MBR, so no matter what settings you have in BIOS, it will boot grub. You actually want BIOS set to boot Ubuntu drive, but have Windows boot loader in Windows drive. Grub only boots working Windows or Windows that is not hibernated/fast boot on. And Windows with updates will turn fast start up back on.
http://askubuntu.com/questions/843153/ubuntu-16-showing-windows-10-partitions
answered Dec 30 '18 at 23:04
oldfredoldfred
7,67421321
When you installed Windows was BIOS set to default boot from HDD - no I was booting from SSD. I believe at least. You are correct - as for the partition - I purged it.
– tzim
Jan 1 at 14:45
OK - so if I understood you correctly: a) I am changing in BIOS the order of booting disks (now it is hdd > sdd). b) I am starting a recovery disck and going with the repair windows mode (this did not work before)
– tzim
Jan 1 at 14:47
1
Windows Repair may not have worked if BIOS set to boot Ubuntu drive as Windows could not see NTFS partition with boot flag. That is where it will install/repair boot files.
– oldfred
Jan 1 at 15:53
1
Run new copy of Boot-Repair's summary report. Need to see if you now have Windows boot files. If you have copy of bootmgr you can copy that into your Windows c: drive. And possible use third party tools to create the /boot/BCD file. Otherwise best to try a Windows forum for Windows issues.
– oldfred
Jan 1 at 21:39
1
You are now showing the BCD, but not bootmgr for Windows to boot. There may be a copy somewhere else in Windows, but do not remember. Try repairs again or ask at Windows forum.
– oldfred
Jan 2 at 1:01
|
show 6 more comments
I was not able to find a solution that would allow me to have Windows working.
I was able to have the Ubuntu working fine.
In a long run, I did a format and ran a clean installation of Windows.
answered Jan 3 at 18:10
tzimtzim
1045
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1105680%2fssd-hdd-legacy-and-a-really-messed-up-situation-with-grub-how-to-revive-lost%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Because your Windows drive is MBR, your Windows install is in BIOS boot mode.
And since you have two drives, you should always use Something Else install option and install grub2's boot loader to Ubuntu drive. Default is normally first drive and most often sda/Window drive.
But you want to keep Windows boot loader in MBR of Windows drive.
When you installed Windows was BIOS set to default boot from HDD? Windows 7 or later normally uses a separate Boot partition with two boot files, bootmgr & /boot/BCD. But you are totally missing those files. They can be in same partition as main install or c:, but normally are not.
You must use Windows repair/recovery disk to fully repair Windows.
Make sure BIOS is set to boot Windows drive. Only after Windows boots, then set BIOS to boot HDD and use grub to dual boot.
Also with multiple drives do not run Boot-Repair's auto-fix. That installs grub to every drive's MBR, so no matter what settings you have in BIOS, it will boot grub. You actually want BIOS set to boot Ubuntu drive, but have Windows boot loader in Windows drive. Grub only boots working Windows or Windows that is not hibernated/fast boot on. And Windows with updates will turn fast start up back on.
http://askubuntu.com/questions/843153/ubuntu-16-showing-windows-10-partitions
answered Dec 30 '18 at 23:04
oldfredoldfred
7,67421321
When you installed Windows was BIOS set to default boot from HDD - no I was booting from SSD. I believe at least. You are correct - as for the partition - I purged it.
– tzim
Jan 1 at 14:45
OK - so if I understood you correctly: a) I am changing in BIOS the order of booting disks (now it is hdd > sdd). b) I am starting a recovery disck and going with the repair windows mode (this did not work before)
– tzim
Jan 1 at 14:47
1
Windows Repair may not have worked if BIOS set to boot Ubuntu drive as Windows could not see NTFS partition with boot flag. That is where it will install/repair boot files.
– oldfred
Jan 1 at 15:53
1
Run new copy of Boot-Repair's summary report. Need to see if you now have Windows boot files. If you have copy of bootmgr you can copy that into your Windows c: drive. And possible use third party tools to create the /boot/BCD file. Otherwise best to try a Windows forum for Windows issues.
– oldfred
Jan 1 at 21:39
1
You are now showing the BCD, but not bootmgr for Windows to boot. There may be a copy somewhere else in Windows, but do not remember. Try repairs again or ask at Windows forum.
– oldfred
Jan 2 at 1:01
|
show 6 more comments
Because your Windows drive is MBR, your Windows install is in BIOS boot mode.
And since you have two drives, you should always use Something Else install option and install grub2's boot loader to Ubuntu drive. Default is normally first drive and most often sda/Window drive.
But you want to keep Windows boot loader in MBR of Windows drive.
When you installed Windows was BIOS set to default boot from HDD? Windows 7 or later normally uses a separate Boot partition with two boot files, bootmgr & /boot/BCD. But you are totally missing those files. They can be in same partition as main install or c:, but normally are not.
You must use Windows repair/recovery disk to fully repair Windows.
Make sure BIOS is set to boot Windows drive. Only after Windows boots, then set BIOS to boot HDD and use grub to dual boot.
Also with multiple drives do not run Boot-Repair's auto-fix. That installs grub to every drive's MBR, so no matter what settings you have in BIOS, it will boot grub. You actually want BIOS set to boot Ubuntu drive, but have Windows boot loader in Windows drive. Grub only boots working Windows or Windows that is not hibernated/fast boot on. And Windows with updates will turn fast start up back on.
http://askubuntu.com/questions/843153/ubuntu-16-showing-windows-10-partitions
answered Dec 30 '18 at 23:04
oldfredoldfred
7,67421321
When you installed Windows was BIOS set to default boot from HDD - no I was booting from SSD. I believe at least. You are correct - as for the partition - I purged it.
– tzim
Jan 1 at 14:45
OK - so if I understood you correctly: a) I am changing in BIOS the order of booting disks (now it is hdd > sdd). b) I am starting a recovery disck and going with the repair windows mode (this did not work before)
– tzim
Jan 1 at 14:47
1
Windows Repair may not have worked if BIOS set to boot Ubuntu drive as Windows could not see NTFS partition with boot flag. That is where it will install/repair boot files.
– oldfred
Jan 1 at 15:53
1
Run new copy of Boot-Repair's summary report. Need to see if you now have Windows boot files. If you have copy of bootmgr you can copy that into your Windows c: drive. And possible use third party tools to create the /boot/BCD file. Otherwise best to try a Windows forum for Windows issues.
– oldfred
Jan 1 at 21:39
1
You are now showing the BCD, but not bootmgr for Windows to boot. There may be a copy somewhere else in Windows, but do not remember. Try repairs again or ask at Windows forum.
– oldfred
Jan 2 at 1:01
|
show 6 more comments
Because your Windows drive is MBR, your Windows install is in BIOS boot mode.
And since you have two drives, you should always use Something Else install option and install grub2's boot loader to Ubuntu drive. Default is normally first drive and most often sda/Window drive.
But you want to keep Windows boot loader in MBR of Windows drive.
When you installed Windows was BIOS set to default boot from HDD? Windows 7 or later normally uses a separate Boot partition with two boot files, bootmgr & /boot/BCD. But you are totally missing those files. They can be in same partition as main install or c:, but normally are not.
You must use Windows repair/recovery disk to fully repair Windows.
Make sure BIOS is set to boot Windows drive. Only after Windows boots, then set BIOS to boot HDD and use grub to dual boot.
Also with multiple drives do not run Boot-Repair's auto-fix. That installs grub to every drive's MBR, so no matter what settings you have in BIOS, it will boot grub. You actually want BIOS set to boot Ubuntu drive, but have Windows boot loader in Windows drive. Grub only boots working Windows or Windows that is not hibernated/fast boot on. And Windows with updates will turn fast start up back on.
http://askubuntu.com/questions/843153/ubuntu-16-showing-windows-10-partitions
answered Dec 30 '18 at 23:04
oldfredoldfred
7,67421321
Because your Windows drive is MBR, your Windows install is in BIOS boot mode.
And since you have two drives, you should always use Something Else install option and install grub2's boot loader to Ubuntu drive. Default is normally first drive and most often sda/Window drive.
But you want to keep Windows boot loader in MBR of Windows drive.
When you installed Windows was BIOS set to default boot from HDD? Windows 7 or later normally uses a separate Boot partition with two boot files, bootmgr & /boot/BCD. But you are totally missing those files. They can be in same partition as main install or c:, but normally are not.
You must use Windows repair/recovery disk to fully repair Windows.
Make sure BIOS is set to boot Windows drive. Only after Windows boots, then set BIOS to boot HDD and use grub to dual boot.
Also with multiple drives do not run Boot-Repair's auto-fix. That installs grub to every drive's MBR, so no matter what settings you have in BIOS, it will boot grub. You actually want BIOS set to boot Ubuntu drive, but have Windows boot loader in Windows drive. Grub only boots working Windows or Windows that is not hibernated/fast boot on. And Windows with updates will turn fast start up back on.
http://askubuntu.com/questions/843153/ubuntu-16-showing-windows-10-partitions
answered Dec 30 '18 at 23:04
oldfredoldfred
7,67421321
answered Dec 30 '18 at 23:04
oldfredoldfred
7,67421321
answered Dec 30 '18 at 23:04
oldfredoldfred
7,67421321
answered Dec 30 '18 at 23:04
oldfredoldfred
7,67421321
7,67421321
When you installed Windows was BIOS set to default boot from HDD - no I was booting from SSD. I believe at least. You are correct - as for the partition - I purged it.
– tzim
Jan 1 at 14:45
OK - so if I understood you correctly: a) I am changing in BIOS the order of booting disks (now it is hdd > sdd). b) I am starting a recovery disck and going with the repair windows mode (this did not work before)
– tzim
Jan 1 at 14:47
1
Windows Repair may not have worked if BIOS set to boot Ubuntu drive as Windows could not see NTFS partition with boot flag. That is where it will install/repair boot files.
– oldfred
Jan 1 at 15:53
1
Run new copy of Boot-Repair's summary report. Need to see if you now have Windows boot files. If you have copy of bootmgr you can copy that into your Windows c: drive. And possible use third party tools to create the /boot/BCD file. Otherwise best to try a Windows forum for Windows issues.
– oldfred
Jan 1 at 21:39
1
You are now showing the BCD, but not bootmgr for Windows to boot. There may be a copy somewhere else in Windows, but do not remember. Try repairs again or ask at Windows forum.
– oldfred
Jan 2 at 1:01
|
show 6 more comments
When you installed Windows was BIOS set to default boot from HDD - no I was booting from SSD. I believe at least. You are correct - as for the partition - I purged it.
– tzim
Jan 1 at 14:45
OK - so if I understood you correctly: a) I am changing in BIOS the order of booting disks (now it is hdd > sdd). b) I am starting a recovery disck and going with the repair windows mode (this did not work before)
– tzim
Jan 1 at 14:47
1
Windows Repair may not have worked if BIOS set to boot Ubuntu drive as Windows could not see NTFS partition with boot flag. That is where it will install/repair boot files.
– oldfred
Jan 1 at 15:53
1
Run new copy of Boot-Repair's summary report. Need to see if you now have Windows boot files. If you have copy of bootmgr you can copy that into your Windows c: drive. And possible use third party tools to create the /boot/BCD file. Otherwise best to try a Windows forum for Windows issues.
– oldfred
Jan 1 at 21:39
1
You are now showing the BCD, but not bootmgr for Windows to boot. There may be a copy somewhere else in Windows, but do not remember. Try repairs again or ask at Windows forum.
– oldfred
Jan 2 at 1:01
When you installed Windows was BIOS set to default boot from HDD - no I was booting from SSD. I believe at least. You are correct - as for the partition - I purged it.
– tzim
Jan 1 at 14:45
When you installed Windows was BIOS set to default boot from HDD - no I was booting from SSD. I believe at least. You are correct - as for the partition - I purged it.
– tzim
Jan 1 at 14:45
OK - so if I understood you correctly: a) I am changing in BIOS the order of booting disks (now it is hdd > sdd). b) I am starting a recovery disck and going with the repair windows mode (this did not work before)
– tzim
Jan 1 at 14:47
OK - so if I understood you correctly: a) I am changing in BIOS the order of booting disks (now it is hdd > sdd). b) I am starting a recovery disck and going with the repair windows mode (this did not work before)
– tzim
Jan 1 at 14:47
1
1
Windows Repair may not have worked if BIOS set to boot Ubuntu drive as Windows could not see NTFS partition with boot flag. That is where it will install/repair boot files.
– oldfred
Jan 1 at 15:53
Windows Repair may not have worked if BIOS set to boot Ubuntu drive as Windows could not see NTFS partition with boot flag. That is where it will install/repair boot files.
– oldfred
Jan 1 at 15:53
1
1
Run new copy of Boot-Repair's summary report. Need to see if you now have Windows boot files. If you have copy of bootmgr you can copy that into your Windows c: drive. And possible use third party tools to create the /boot/BCD file. Otherwise best to try a Windows forum for Windows issues.
– oldfred
Jan 1 at 21:39
Run new copy of Boot-Repair's summary report. Need to see if you now have Windows boot files. If you have copy of bootmgr you can copy that into your Windows c: drive. And possible use third party tools to create the /boot/BCD file. Otherwise best to try a Windows forum for Windows issues.
– oldfred
Jan 1 at 21:39
1
1
You are now showing the BCD, but not bootmgr for Windows to boot. There may be a copy somewhere else in Windows, but do not remember. Try repairs again or ask at Windows forum.
– oldfred
Jan 2 at 1:01
You are now showing the BCD, but not bootmgr for Windows to boot. There may be a copy somewhere else in Windows, but do not remember. Try repairs again or ask at Windows forum.
– oldfred
Jan 2 at 1:01
|
show 6 more comments
I was not able to find a solution that would allow me to have Windows working.
I was able to have the Ubuntu working fine.
In a long run, I did a format and ran a clean installation of Windows.
answered Jan 3 at 18:10
tzimtzim
1045
add a comment |
I was not able to find a solution that would allow me to have Windows working.
I was able to have the Ubuntu working fine.
In a long run, I did a format and ran a clean installation of Windows.
answered Jan 3 at 18:10
tzimtzim
1045
add a comment |
I was not able to find a solution that would allow me to have Windows working.
I was able to have the Ubuntu working fine.
In a long run, I did a format and ran a clean installation of Windows.
answered Jan 3 at 18:10
tzimtzim
1045
I was not able to find a solution that would allow me to have Windows working.
I was able to have the Ubuntu working fine.
In a long run, I did a format and ran a clean installation of Windows.
answered Jan 3 at 18:10
tzimtzim
1045
answered Jan 3 at 18:10
tzimtzim
1045
answered Jan 3 at 18:10
tzimtzim
1045
answered Jan 3 at 18:10
tzimtzim
1045
1045
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1105680%2fssd-hdd-legacy-and-a-really-messed-up-situation-with-grub-how-to-revive-lost%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
A common problem with people who install Linux on systems that already have Windows is that they don't actually shut windows down since Windows 10 goes into a "soft power off' state. This causes problems because when they turn Windows back on it starts writing information over the hard drive that was kept in memory before Windows essentially hibernated.
– Kristopher Ives
Dec 30 '18 at 20:10
1
Your paste shows that you still have NTFS partitions, so those files aren't lost most likely. However, I'm unable to understand what your actual question is or how to help you because the post contains too much information that may or may not be relevant.
– Kristopher Ives
Dec 30 '18 at 20:11
1
It's possible Windows was installed as UEFI and Linux was not, or some other combination that doesn't match.
– Kristopher Ives
Dec 30 '18 at 20:14
1
In your log it says "Windows is hibernated, refused to mount."
– Kristopher Ives
Dec 30 '18 at 20:19
1
Like I mentioned originally Microsoft has made it very obscure of a process to actually shut Windows down completely. Almost all "regular" methods will hibernate it.
– Kristopher Ives
Dec 30 '18 at 20:20