Restore boot-loader after resize dev/sda1 using gparted
up vote
0
down vote
favorite
I've been searching on google and stackoverflow for a solution without result.
Explanation:
I had to install Windows alongside Ubuntu 16.04.
I freed up some space from my dev/sda1 (my Ubuntu was installed on this) using gparted from live usb.
It took too much time; around 40min plus. I intentially canceled operation and then restarted my laptop at this time the actual Ubuntu was not loading in boot options of laptop.
I then again run live usb ubuntu and tried to repair boot using Boot-Repair tool but I got this message:
Please enable a repository containing the [grub-efi-amd64-signed] packages in the software sources of unknown Linux (sda1). Then try again.
The unknown Linux (sda1) is my Ubuntu.
I am not able to access it how can i enable grub*** on it?
please help me
https://paste.ubuntu.com/p/ZVDjbcghY6/
boot-repair
New contributor
Zeeshan Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
I've been searching on google and stackoverflow for a solution without result.
Explanation:
I had to install Windows alongside Ubuntu 16.04.
I freed up some space from my dev/sda1 (my Ubuntu was installed on this) using gparted from live usb.
It took too much time; around 40min plus. I intentially canceled operation and then restarted my laptop at this time the actual Ubuntu was not loading in boot options of laptop.
I then again run live usb ubuntu and tried to repair boot using Boot-Repair tool but I got this message:
Please enable a repository containing the [grub-efi-amd64-signed] packages in the software sources of unknown Linux (sda1). Then try again.
The unknown Linux (sda1) is my Ubuntu.
I am not able to access it how can i enable grub*** on it?
please help me
https://paste.ubuntu.com/p/ZVDjbcghY6/
boot-repair
New contributor
Zeeshan Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I've been searching on google and stackoverflow for a solution without result.
Explanation:
I had to install Windows alongside Ubuntu 16.04.
I freed up some space from my dev/sda1 (my Ubuntu was installed on this) using gparted from live usb.
It took too much time; around 40min plus. I intentially canceled operation and then restarted my laptop at this time the actual Ubuntu was not loading in boot options of laptop.
I then again run live usb ubuntu and tried to repair boot using Boot-Repair tool but I got this message:
Please enable a repository containing the [grub-efi-amd64-signed] packages in the software sources of unknown Linux (sda1). Then try again.
The unknown Linux (sda1) is my Ubuntu.
I am not able to access it how can i enable grub*** on it?
please help me
https://paste.ubuntu.com/p/ZVDjbcghY6/
boot-repair
New contributor
Zeeshan Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I've been searching on google and stackoverflow for a solution without result.
Explanation:
I had to install Windows alongside Ubuntu 16.04.
I freed up some space from my dev/sda1 (my Ubuntu was installed on this) using gparted from live usb.
It took too much time; around 40min plus. I intentially canceled operation and then restarted my laptop at this time the actual Ubuntu was not loading in boot options of laptop.
I then again run live usb ubuntu and tried to repair boot using Boot-Repair tool but I got this message:
Please enable a repository containing the [grub-efi-amd64-signed] packages in the software sources of unknown Linux (sda1). Then try again.
The unknown Linux (sda1) is my Ubuntu.
I am not able to access it how can i enable grub*** on it?
please help me
https://paste.ubuntu.com/p/ZVDjbcghY6/
boot-repair
boot-repair
New contributor
Zeeshan Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Zeeshan Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited yesterday
abu_bua
2,93371021
2,93371021
New contributor
Zeeshan Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
Zeeshan Ahmad
1
1
New contributor
Zeeshan Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Zeeshan Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Zeeshan Ahmad is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
If a resize or move operation is cancelled then the file system can be left in an inconsistent or broken state. This can result in data loss and the inability to restore the ability to boot from a broken file system.
I recommend restoring from backup, or if you do not have a backup then try to recover the file system / important data before proceeding any further.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
If a resize or move operation is cancelled then the file system can be left in an inconsistent or broken state. This can result in data loss and the inability to restore the ability to boot from a broken file system.
I recommend restoring from backup, or if you do not have a backup then try to recover the file system / important data before proceeding any further.
add a comment |
up vote
0
down vote
If a resize or move operation is cancelled then the file system can be left in an inconsistent or broken state. This can result in data loss and the inability to restore the ability to boot from a broken file system.
I recommend restoring from backup, or if you do not have a backup then try to recover the file system / important data before proceeding any further.
add a comment |
up vote
0
down vote
up vote
0
down vote
If a resize or move operation is cancelled then the file system can be left in an inconsistent or broken state. This can result in data loss and the inability to restore the ability to boot from a broken file system.
I recommend restoring from backup, or if you do not have a backup then try to recover the file system / important data before proceeding any further.
If a resize or move operation is cancelled then the file system can be left in an inconsistent or broken state. This can result in data loss and the inability to restore the ability to boot from a broken file system.
I recommend restoring from backup, or if you do not have a backup then try to recover the file system / important data before proceeding any further.
answered 20 hours ago
Curtis Gedak
86154
86154
add a comment |
add a comment |
Zeeshan Ahmad is a new contributor. Be nice, and check out our Code of Conduct.
Zeeshan Ahmad is a new contributor. Be nice, and check out our Code of Conduct.
Zeeshan Ahmad is a new contributor. Be nice, and check out our Code of Conduct.
Zeeshan Ahmad is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1093551%2frestore-boot-loader-after-resize-dev-sda1-using-gparted%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