migrating system drive and boot messed up

Kernels & Hardware, configuring network, installing services

migrating system drive and boot messed up

Postby creepwood » 2017-06-23 03:31

First off, I'm very novice and I'm stuck in a bind.

I'm running debian 8 as a home server and my sdh drive started to get smart messages about failing drive so I thought I would migrate to a newer drive (sda) so during this process I believe I messed up my boot, I still don't know for sure because I haven't dared rebooting the machine.


both sda and sdh partitioning is identical except the size of partition 3 but it all fitted on my newer drive (60G, the older one was a 12 year old mechanical 250G drive)

Code: Select all
sda                          8:0    0  55.9G  0 disk
├─sda1                       8:1    0   512M  0 part /boot/efi
├─sda2                       8:2    0   244M  0 part /boot
└─sda3                       8:3    0  55.2G  0 part
  ├─arkham--vg-root        254:0    0  46.6G  0 lvm  /
  └─arkham--vg-swap_1      254:1    0   7.9G  0 lvm  [SWAP]


I added the new drive to the same LV, did a PVmove and then removed the old one from the LV and VG. So this is where I'm at now, I've tried grub-install, upgrade-from-grub-legacy but none of them are doing fine. The machine does support EFI and their is a mount called /boot/efi so I think it should be efi, however, some of the error messages implies that it's not (or isn't anymore because I messed up?) I copied over the contens from sdh1 and sdh2 to sda1 and sda2 with cp -av. I might've written a gpt table when I partitioned the drives


Code: Select all
Disk /dev/sdh: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B10783C8-6FF8-43FE-ABE2-C67F60995D07

Device       Start       End   Sectors   Size Type
/dev/sdh1     2048   1050623   1048576   512M EFI System
/dev/sdh2  1050624   1550335    499712   244M Linux filesystem
/dev/sdh3  1550336 488396799 486846464 232.2G Linux LVM

Disk /dev/sda: 55.9 GiB, 60022480896 bytes, 117231408 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 13780D60-6C95-4C58-AD9B-F63E8E7DCFB0

Device       Start       End   Sectors  Size Type
/dev/sda1     2048   1050623   1048576  512M EFI System
/dev/sda2  1050624   1550335    499712  244M Linux filesystem
/dev/sda3  1550336 117231374 115681039 55.2G Linux LVM




This is the error message I get when I try update-from-grub-legacy
Code: Select all
core.img doesn't exist, trying to create it.

Installing for i386-pc platform.
Installation finished. No error reported.
dpkg: warning: version 'dummy-version' has bad syntax: version number does not start with digit
dpkg: warning: version 'dummy-version' has bad syntax: version number does not start with digit
dpkg: warning: version 'dummy-version' has bad syntax: version number does not start with digit
dpkg: warning: version 'dummy-version' has bad syntax: version number does not start with digit
Installing for i386-pc platform.
grub-install: warning: File system `ext2' doesn't support embedding.
grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
Installation finished. No error reported.
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
done

GRUB Legacy has been removed, but its configuration files have been preserved,
since this script cannot determine if they contain valuable information.  If
you would like to remove the configuration files as well, use the following
command:

  rm -f /boot/grub/menu.lst*


I might've messed up the

AT this point I think I might have screwed up the boot all together. I still have the older data on on sdh1 and sdh2 (/boot/efi and /boot) I have a debian 9 live on and USB stick and GRML full 64 on an USB stick if that helps. There is no more space on sda unless I try to shrink sda3 (OS). The machine is still running but I feel confident that it won't boot as is.

Edit: I looked at the grub loaders command prompt and the guide. My system is on an LVM volume and it seems to be slightly different. I tried google a little bit but since I'm just a novice much of it is stuff I don't dare to touch
creepwood
 
Posts: 25
Joined: 2013-09-15 20:29

Return to System configuration

Who is online

Users browsing this forum: No registered users and 7 guests

fashionable