Configure separated GRUB to run Linux from LVM ddrescued device
I got new 120GB SSD and I want to restore my Linux Mint from my ddrescued /dev/mapper/mint--vg-root
I splited SSD to 500MB sdb1 Ext4 and 119GB sdb2 LVM as it was before crash.
Then I created mint-vg group and made root volume. Restored ddrescued Mint image to mint--vg-root.
Then I installed GRUB to mounted sdb1 with this:
sudo grub-install --root-directory=/media/user/mouted_sdb1 /dev/sdb
Now when I boot from SSD I get GRUB black screen
I tried how-rescue-non-booting-grub-2-Linux, but GRUB says, that my lvm partitition has unknown filesystem:
grub> ls (hd0,msdos <TAB>
Available partititions are
Partitition hd0,msdos1: Filesystem type ext* - Last modified .....
Partitition hd0,msdos2: No known filesystem detected - Partitition start at ....
I tried boot-repair with GUI. It lists my mapper/mint--vg-root, but after repair my mint not in list of systems. Mark mapper/mint--vg-root as default requires LiveCD.
Tried to:
insmod lvm
In grub console without result (still no known):
Tried this:
sudo grub-mkconfig -o grub.cfg
It says that /dev/mapper/mint--vg-root is found, but in grub.cfg is no record about this.
How make GRUB to load my Mint from lvm?
UPDATE:
Here some Boot Info Summary from my old system and from new. In new I have no "Extended partitition"
OLD:
sdb1:
File system: ext2
Boot sector type: -
Boot sector info:
Operating System:
Boot files: /grub/grub.cfg /grub/i386-pc/core.img
sdb2:
File system: Extended Partition
Boot sector type: -
Boot sector info:
sdb5:
File system: LVM2_member
Boot sector type: -
Boot sector info:
mint-vg-root:
File system: ext4
Boot sector type: -
Boot sector info:
Mounting failed: mount: wrong fs type, bad option, bad superblock on /dev/mapper/mint--vg-root,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
mint-vg-swap_1:
File system: swap
Boot sector type: -
Boot sector info:
new Boot Info Summary:
sdb1:
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files: /boot/grub/grub.cfg /boot/grub/i386-pc/core.img
sdb2:
File system: LVM2_member
Boot sector type: -
Boot sector info:
mint-vg-root:
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Linux Mint 18.1
Boot files: /etc/fstab
SOLVED with how-rescue-non-booting-grub-2-Linux with some modifications in GRUB console:
grub> set root=(lvm/mint--vg-root)
grub> linux (hd0,msdos1)/boot/vmlinuz-4.4.0-112-generic root=/dev/mapper/mint--vg-root
grub> initrd (hd0,msdos1)/boot/initrd.img-4.4.0-112-generic
grub> boot
After boot I ran boot-repair and it works now.
grub2 lvm grub2-mkconfig
edited Jan 30 '18 at 9:52
galoget
35729
asked Jan 29 '18 at 11:39
serebukaserebuka
43
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 2 more comments
I got new 120GB SSD and I want to restore my Linux Mint from my ddrescued /dev/mapper/mint--vg-root
I splited SSD to 500MB sdb1 Ext4 and 119GB sdb2 LVM as it was before crash.
Then I created mint-vg group and made root volume. Restored ddrescued Mint image to mint--vg-root.
Then I installed GRUB to mounted sdb1 with this:
sudo grub-install --root-directory=/media/user/mouted_sdb1 /dev/sdb
Now when I boot from SSD I get GRUB black screen
I tried how-rescue-non-booting-grub-2-Linux, but GRUB says, that my lvm partitition has unknown filesystem:
grub> ls (hd0,msdos <TAB>
Available partititions are
Partitition hd0,msdos1: Filesystem type ext* - Last modified .....
Partitition hd0,msdos2: No known filesystem detected - Partitition start at ....
I tried boot-repair with GUI. It lists my mapper/mint--vg-root, but after repair my mint not in list of systems. Mark mapper/mint--vg-root as default requires LiveCD.
Tried to:
insmod lvm
In grub console without result (still no known):
Tried this:
sudo grub-mkconfig -o grub.cfg
It says that /dev/mapper/mint--vg-root is found, but in grub.cfg is no record about this.
How make GRUB to load my Mint from lvm?
UPDATE:
Here some Boot Info Summary from my old system and from new. In new I have no "Extended partitition"
OLD:
sdb1:
File system: ext2
Boot sector type: -
Boot sector info:
Operating System:
Boot files: /grub/grub.cfg /grub/i386-pc/core.img
sdb2:
File system: Extended Partition
Boot sector type: -
Boot sector info:
sdb5:
File system: LVM2_member
Boot sector type: -
Boot sector info:
mint-vg-root:
File system: ext4
Boot sector type: -
Boot sector info:
Mounting failed: mount: wrong fs type, bad option, bad superblock on /dev/mapper/mint--vg-root,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
mint-vg-swap_1:
File system: swap
Boot sector type: -
Boot sector info:
new Boot Info Summary:
sdb1:
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files: /boot/grub/grub.cfg /boot/grub/i386-pc/core.img
sdb2:
File system: LVM2_member
Boot sector type: -
Boot sector info:
mint-vg-root:
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Linux Mint 18.1
Boot files: /etc/fstab
SOLVED with how-rescue-non-booting-grub-2-Linux with some modifications in GRUB console:
grub> set root=(lvm/mint--vg-root)
grub> linux (hd0,msdos1)/boot/vmlinuz-4.4.0-112-generic root=/dev/mapper/mint--vg-root
grub> initrd (hd0,msdos1)/boot/initrd.img-4.4.0-112-generic
grub> boot
After boot I ran boot-repair and it works now.
grub2 lvm grub2-mkconfig
edited Jan 30 '18 at 9:52
galoget
35729
asked Jan 29 '18 at 11:39
serebukaserebuka
43
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
So you took an image of your old drive and copied it to the new one using dd?
– Raman Sailopal
Jan 29 '18 at 11:43
Yes. I took image from /dev/mapper/mint--vg-root from old drive. Then put image to new prepared /dev/mapper/mint--vg-root. All with dd
– serebuka
Jan 29 '18 at 11:46
Probably I had to copy partitition with grub too. But that SSD is gone
– serebuka
Jan 29 '18 at 11:49
Yeah, taking a copy of the actual disk partitions would have been the best way to go.
– Raman Sailopal
Jan 29 '18 at 11:51
I added old and new boot info summary. Seems different. New is without Extended partitition containing LVM.
– serebuka
Jan 29 '18 at 12:07
|
show 2 more comments
I got new 120GB SSD and I want to restore my Linux Mint from my ddrescued /dev/mapper/mint--vg-root
I splited SSD to 500MB sdb1 Ext4 and 119GB sdb2 LVM as it was before crash.
Then I created mint-vg group and made root volume. Restored ddrescued Mint image to mint--vg-root.
Then I installed GRUB to mounted sdb1 with this:
sudo grub-install --root-directory=/media/user/mouted_sdb1 /dev/sdb
Now when I boot from SSD I get GRUB black screen
I tried how-rescue-non-booting-grub-2-Linux, but GRUB says, that my lvm partitition has unknown filesystem:
grub> ls (hd0,msdos <TAB>
Available partititions are
Partitition hd0,msdos1: Filesystem type ext* - Last modified .....
Partitition hd0,msdos2: No known filesystem detected - Partitition start at ....
I tried boot-repair with GUI. It lists my mapper/mint--vg-root, but after repair my mint not in list of systems. Mark mapper/mint--vg-root as default requires LiveCD.
Tried to:
insmod lvm
In grub console without result (still no known):
Tried this:
sudo grub-mkconfig -o grub.cfg
It says that /dev/mapper/mint--vg-root is found, but in grub.cfg is no record about this.
How make GRUB to load my Mint from lvm?
UPDATE:
Here some Boot Info Summary from my old system and from new. In new I have no "Extended partitition"
OLD:
sdb1:
File system: ext2
Boot sector type: -
Boot sector info:
Operating System:
Boot files: /grub/grub.cfg /grub/i386-pc/core.img
sdb2:
File system: Extended Partition
Boot sector type: -
Boot sector info:
sdb5:
File system: LVM2_member
Boot sector type: -
Boot sector info:
mint-vg-root:
File system: ext4
Boot sector type: -
Boot sector info:
Mounting failed: mount: wrong fs type, bad option, bad superblock on /dev/mapper/mint--vg-root,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
mint-vg-swap_1:
File system: swap
Boot sector type: -
Boot sector info:
new Boot Info Summary:
sdb1:
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files: /boot/grub/grub.cfg /boot/grub/i386-pc/core.img
sdb2:
File system: LVM2_member
Boot sector type: -
Boot sector info:
mint-vg-root:
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Linux Mint 18.1
Boot files: /etc/fstab
SOLVED with how-rescue-non-booting-grub-2-Linux with some modifications in GRUB console:
grub> set root=(lvm/mint--vg-root)
grub> linux (hd0,msdos1)/boot/vmlinuz-4.4.0-112-generic root=/dev/mapper/mint--vg-root
grub> initrd (hd0,msdos1)/boot/initrd.img-4.4.0-112-generic
grub> boot
After boot I ran boot-repair and it works now.
grub2 lvm grub2-mkconfig
edited Jan 30 '18 at 9:52
galoget
35729
asked Jan 29 '18 at 11:39
serebukaserebuka
43
I got new 120GB SSD and I want to restore my Linux Mint from my ddrescued /dev/mapper/mint--vg-root
I splited SSD to 500MB sdb1 Ext4 and 119GB sdb2 LVM as it was before crash.
Then I created mint-vg group and made root volume. Restored ddrescued Mint image to mint--vg-root.
Then I installed GRUB to mounted sdb1 with this:
sudo grub-install --root-directory=/media/user/mouted_sdb1 /dev/sdb
Now when I boot from SSD I get GRUB black screen
I tried how-rescue-non-booting-grub-2-Linux, but GRUB says, that my lvm partitition has unknown filesystem:
grub> ls (hd0,msdos <TAB>
Available partititions are
Partitition hd0,msdos1: Filesystem type ext* - Last modified .....
Partitition hd0,msdos2: No known filesystem detected - Partitition start at ....
I tried boot-repair with GUI. It lists my mapper/mint--vg-root, but after repair my mint not in list of systems. Mark mapper/mint--vg-root as default requires LiveCD.
Tried to:
insmod lvm
In grub console without result (still no known):
Tried this:
sudo grub-mkconfig -o grub.cfg
It says that /dev/mapper/mint--vg-root is found, but in grub.cfg is no record about this.
How make GRUB to load my Mint from lvm?
UPDATE:
Here some Boot Info Summary from my old system and from new. In new I have no "Extended partitition"
OLD:
sdb1:
File system: ext2
Boot sector type: -
Boot sector info:
Operating System:
Boot files: /grub/grub.cfg /grub/i386-pc/core.img
sdb2:
File system: Extended Partition
Boot sector type: -
Boot sector info:
sdb5:
File system: LVM2_member
Boot sector type: -
Boot sector info:
mint-vg-root:
File system: ext4
Boot sector type: -
Boot sector info:
Mounting failed: mount: wrong fs type, bad option, bad superblock on /dev/mapper/mint--vg-root,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
mint-vg-swap_1:
File system: swap
Boot sector type: -
Boot sector info:
new Boot Info Summary:
sdb1:
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files: /boot/grub/grub.cfg /boot/grub/i386-pc/core.img
sdb2:
File system: LVM2_member
Boot sector type: -
Boot sector info:
mint-vg-root:
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Linux Mint 18.1
Boot files: /etc/fstab
SOLVED with how-rescue-non-booting-grub-2-Linux with some modifications in GRUB console:
grub> set root=(lvm/mint--vg-root)
grub> linux (hd0,msdos1)/boot/vmlinuz-4.4.0-112-generic root=/dev/mapper/mint--vg-root
grub> initrd (hd0,msdos1)/boot/initrd.img-4.4.0-112-generic
grub> boot
After boot I ran boot-repair and it works now.
grub2 lvm grub2-mkconfig
grub2 lvm grub2-mkconfig
edited Jan 30 '18 at 9:52
galoget
35729
asked Jan 29 '18 at 11:39
serebukaserebuka
43
edited Jan 30 '18 at 9:52
galoget
35729
asked Jan 29 '18 at 11:39
serebukaserebuka
43
edited Jan 30 '18 at 9:52
galoget
35729
edited Jan 30 '18 at 9:52
galoget
35729
edited Jan 30 '18 at 9:52
galoget
35729
35729
asked Jan 29 '18 at 11:39
serebukaserebuka
43
asked Jan 29 '18 at 11:39
serebukaserebuka
43
asked Jan 29 '18 at 11:39
serebukaserebuka
43
43
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 7 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
So you took an image of your old drive and copied it to the new one using dd?
– Raman Sailopal
Jan 29 '18 at 11:43
Yes. I took image from /dev/mapper/mint--vg-root from old drive. Then put image to new prepared /dev/mapper/mint--vg-root. All with dd
– serebuka
Jan 29 '18 at 11:46
Probably I had to copy partitition with grub too. But that SSD is gone
– serebuka
Jan 29 '18 at 11:49
Yeah, taking a copy of the actual disk partitions would have been the best way to go.
– Raman Sailopal
Jan 29 '18 at 11:51
I added old and new boot info summary. Seems different. New is without Extended partitition containing LVM.
– serebuka
Jan 29 '18 at 12:07
|
show 2 more comments
So you took an image of your old drive and copied it to the new one using dd?
– Raman Sailopal
Jan 29 '18 at 11:43
Yes. I took image from /dev/mapper/mint--vg-root from old drive. Then put image to new prepared /dev/mapper/mint--vg-root. All with dd
– serebuka
Jan 29 '18 at 11:46
Probably I had to copy partitition with grub too. But that SSD is gone
– serebuka
Jan 29 '18 at 11:49
Yeah, taking a copy of the actual disk partitions would have been the best way to go.
– Raman Sailopal
Jan 29 '18 at 11:51
I added old and new boot info summary. Seems different. New is without Extended partitition containing LVM.
– serebuka
Jan 29 '18 at 12:07
So you took an image of your old drive and copied it to the new one using dd?
– Raman Sailopal
Jan 29 '18 at 11:43
So you took an image of your old drive and copied it to the new one using dd?
– Raman Sailopal
Jan 29 '18 at 11:43
Yes. I took image from /dev/mapper/mint--vg-root from old drive. Then put image to new prepared /dev/mapper/mint--vg-root. All with dd
– serebuka
Jan 29 '18 at 11:46
Yes. I took image from /dev/mapper/mint--vg-root from old drive. Then put image to new prepared /dev/mapper/mint--vg-root. All with dd
– serebuka
Jan 29 '18 at 11:46
Probably I had to copy partitition with grub too. But that SSD is gone
– serebuka
Jan 29 '18 at 11:49
Probably I had to copy partitition with grub too. But that SSD is gone
– serebuka
Jan 29 '18 at 11:49
Yeah, taking a copy of the actual disk partitions would have been the best way to go.
– Raman Sailopal
Jan 29 '18 at 11:51
Yeah, taking a copy of the actual disk partitions would have been the best way to go.
– Raman Sailopal
Jan 29 '18 at 11:51
I added old and new boot info summary. Seems different. New is without Extended partitition containing LVM.
– serebuka
Jan 29 '18 at 12:07
I added old and new boot info summary. Seems different. New is without Extended partitition containing LVM.
– serebuka
Jan 29 '18 at 12:07
|
show 2 more comments
1 Answer
1
active
oldest
votes
SOLVED with how-rescue-non-booting-grub-2-Linux with some modifications in GRUB console:
grub> set root=(lvm/mint--vg-root)
grub> linux (hd0,msdos1)/boot/vmlinuz-4.4.0-112-generic root=/dev/mapper/mint--vg-root
grub> initrd (hd0,msdos1)/boot/initrd.img-4.4.0-112-generic
grub> boot
Where (hd0,msdos1) is sdb1.
After boot I ran boot-repair and it works now
Also I fixed UUIDs in /etc/fstab, because my boot /folder is mounted from (hd0,msdos1) partitition. There are all files like vmlinuz... and initrd.img to boot properly.
edited Jan 30 '18 at 9:51
galoget
35729
answered Jan 29 '18 at 18:48
serebukaserebuka
43
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f420383%2fconfigure-separated-grub-to-run-linux-from-lvm-ddrescued-device%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
SOLVED with how-rescue-non-booting-grub-2-Linux with some modifications in GRUB console:
grub> set root=(lvm/mint--vg-root)
grub> linux (hd0,msdos1)/boot/vmlinuz-4.4.0-112-generic root=/dev/mapper/mint--vg-root
grub> initrd (hd0,msdos1)/boot/initrd.img-4.4.0-112-generic
grub> boot
Where (hd0,msdos1) is sdb1.
After boot I ran boot-repair and it works now
Also I fixed UUIDs in /etc/fstab, because my boot /folder is mounted from (hd0,msdos1) partitition. There are all files like vmlinuz... and initrd.img to boot properly.
edited Jan 30 '18 at 9:51
galoget
35729
answered Jan 29 '18 at 18:48
serebukaserebuka
43
add a comment |
SOLVED with how-rescue-non-booting-grub-2-Linux with some modifications in GRUB console:
grub> set root=(lvm/mint--vg-root)
grub> linux (hd0,msdos1)/boot/vmlinuz-4.4.0-112-generic root=/dev/mapper/mint--vg-root
grub> initrd (hd0,msdos1)/boot/initrd.img-4.4.0-112-generic
grub> boot
Where (hd0,msdos1) is sdb1.
After boot I ran boot-repair and it works now
Also I fixed UUIDs in /etc/fstab, because my boot /folder is mounted from (hd0,msdos1) partitition. There are all files like vmlinuz... and initrd.img to boot properly.
edited Jan 30 '18 at 9:51
galoget
35729
answered Jan 29 '18 at 18:48
serebukaserebuka
43
add a comment |
SOLVED with how-rescue-non-booting-grub-2-Linux with some modifications in GRUB console:
grub> set root=(lvm/mint--vg-root)
grub> linux (hd0,msdos1)/boot/vmlinuz-4.4.0-112-generic root=/dev/mapper/mint--vg-root
grub> initrd (hd0,msdos1)/boot/initrd.img-4.4.0-112-generic
grub> boot
Where (hd0,msdos1) is sdb1.
After boot I ran boot-repair and it works now
Also I fixed UUIDs in /etc/fstab, because my boot /folder is mounted from (hd0,msdos1) partitition. There are all files like vmlinuz... and initrd.img to boot properly.
edited Jan 30 '18 at 9:51
galoget
35729
answered Jan 29 '18 at 18:48
serebukaserebuka
43
SOLVED with how-rescue-non-booting-grub-2-Linux with some modifications in GRUB console:
grub> set root=(lvm/mint--vg-root)
grub> linux (hd0,msdos1)/boot/vmlinuz-4.4.0-112-generic root=/dev/mapper/mint--vg-root
grub> initrd (hd0,msdos1)/boot/initrd.img-4.4.0-112-generic
grub> boot
Where (hd0,msdos1) is sdb1.
After boot I ran boot-repair and it works now
Also I fixed UUIDs in /etc/fstab, because my boot /folder is mounted from (hd0,msdos1) partitition. There are all files like vmlinuz... and initrd.img to boot properly.
edited Jan 30 '18 at 9:51
galoget
35729
answered Jan 29 '18 at 18:48
serebukaserebuka
43
edited Jan 30 '18 at 9:51
galoget
35729
edited Jan 30 '18 at 9:51
galoget
35729
edited Jan 30 '18 at 9:51
galoget
35729
35729
answered Jan 29 '18 at 18:48
serebukaserebuka
43
answered Jan 29 '18 at 18:48
serebukaserebuka
43
answered Jan 29 '18 at 18:48
serebukaserebuka
43
43
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f420383%2fconfigure-separated-grub-to-run-linux-from-lvm-ddrescued-device%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
So you took an image of your old drive and copied it to the new one using dd?
– Raman Sailopal
Jan 29 '18 at 11:43
Yes. I took image from /dev/mapper/mint--vg-root from old drive. Then put image to new prepared /dev/mapper/mint--vg-root. All with dd
– serebuka
Jan 29 '18 at 11:46
Probably I had to copy partitition with grub too. But that SSD is gone
– serebuka
Jan 29 '18 at 11:49
Yeah, taking a copy of the actual disk partitions would have been the best way to go.
– Raman Sailopal
Jan 29 '18 at 11:51
I added old and new boot info summary. Seems different. New is without Extended partitition containing LVM.
– serebuka
Jan 29 '18 at 12:07