On Tuesday, 24 November 2020 17:23:41 GMT the...@sys-concept.com wrote: > On 11/23/2020 01:29 AM, Neil Bothwick wrote: > > On Sun, 22 Nov 2020 18:27:53 -0700, the...@sys-concept.com wrote: > >>> I would confirm that you are really booted from the new disk and not > >>> the old one. It is possible that the MBR from the new disk was used > >>> to boot, but if /etc/fstab says /boot is mounted from /dev/sda1 then > >>> that does seem wrong. I almost always put an empty file in the root > >>> of each partition named for the disk/partition just so I can be sure > >>> what's actually mounted. Is /etc/fstab identical on both disks? > >>> What does fstab say about where / is mounted from? > >> > >> You are absolutely correct. I was booting the whole time the Western > >> Digital (old drive). :-/ My mistake, once I removed the WD drive the > >> new M.2 SSD doesn't even boot. > > > > Check the settings in your BIOS/firmware to make sure it detects the > > drive and is set to boot from it. > > I'm back. > > Yes, BIOS recognized the system, I have one SATA disk connected to it and it > is booting OK. But disconnected it so I don't mess something up.
You'll need to reconnect the old SATA in a minute - see below. > >> I think the easiest way would be to re-install the Getnoo from scratch > > > > And if it still doesn't work because of a firmware issue, you still have > > a non-booting system but with no OS installed either. It's better to try > > and diagnose the problem rather than throwing everything away in the hope > > that the problem goes with it. > > I booted from Gontoo bootable USB and running: blkid > showing: > blkid > /dev/loop0: TYPE="squashfs" > /dev/nvme0n1p1: UUID="5db43d49-810a-4806-955e-d59c4d35ec23" > BLOCK_SIZE="4096" TYPE="ext2" > PARTUUID="743a7887-c02e-4855-8cb7-865247682bff" /dev/nvme0n1p2: > UUID="0c23b340-b5c6-437d-bde9-c5539e64677a" BLOCK_SIZE="4096" TYPE="ext4" > PARTUUID="696091c3-ed27-4a4a-b371-8fd59e2b7a4d" /dev/nvme0n1p3: > UUID="77e449db-7dca-410d-9e70-50165c6ccbb8" TYPE="swap" > PARTUUID="b2871b7b-5bd0-4db3-90a5-50545b129a97" > > > Disk /dev/nvme0n1: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors > Disk model: Force MP600 > 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: FE896335-0C8D-487E-9391-ED43A85D3292 > > Device Start End Sectors Size Type > /dev/nvme0n1p1 2048 1050623 1048576 512M Linux filesystem > /dev/nvme0n1p2 1050624 1971752959 1970702336 939.7G Linux filesystem > /dev/nvme0n1p3 3840102400 3907028991 66926592 31.9G Linux swap > > Shouldn't: /dev/nvme0n1p1 be "Bios Boot" > Do I need to change it with "fdisk" The /dev/nvme0n1p1 partition type should be whatever the /dev/sda1 of the old disk was. If you are using a GPT disk on a Legacy BIOS MoBo, with a Hybrid MBR configuration, then yes, it should be a 'BIOS Boot partition' to contain the GRUB Stage 2 code. However, if /dev/nvme0n1p1 is just a conventional /boot partition with an ext2 fs as you show above, containing your /boot/grub/ directory files, then 'Linux filesystem' is the correct partition type. > When trying to mount /boot > mount /dev/nvme0n1p1 /mnt/gentoo/boot > livecd ~ # ll /mnt/gentoo/boot/ > total 16 > drwx------ 2 root root 16384 Nov 22 22:26 lost+found > > There is nothing there. So the contents of /dev/sda1 were not copied over. Were the contents of /dev/sda2 copied over to dev/nvme0n1p2 ? > I'm not sure if there is a point of fixing it at this point. It might take > less time to reinstall gentoo. It will take much less time to use clonezilla to clone the whole disk as I originally suggested, change the UUIDs of the partitions, update GRUB on the new disk, then update GRUB on the old disk. Alternatively, it will also take less time to use Gparted to create and format the partitions you want, then use rsync/tar/cp to copy over the filesystem contents from the old to the new partitions, then update GRUB. If /dev/nvme0n1p1 is the only partition which needs fixing and since this is a small partition in size, it won't take long to reconnect /dev/sda to the MoBo, boot a LiveUSB and run: dd if=/dev/sda1 of=/dev/nvme0n1p1 If you have not copied over the MBR boot loader in sector 0, or have not installed afresh GRUB on the new disk, then you will also need to copy over the MBR sector: dd if=/dev/sda of=/dev/nvme0n1 bs=446 count=1 Or, if you want to also copy over the MBR partition table as it was on the old disk, change the block size to 512 bytes: dd if=/dev/sda of=/dev/nvme0n1 bs=512 count=1 Any of the above should take significantly less time than reinstalling gentoo, then fishing old ebuilds of your required applications from the attic, fetching corresponding source files, only to discover they won't compile on the new installation because of whatever changes may have taken place in your installed toolchain. Anyway, once you get the knack of this, you'll be able to back up or clone disks/partitions in the future for all sorts of reasons.
signature.asc
Description: This is a digitally signed message part.
