On Wed, Jun 29, 2016 at 11:16:11AM +0200, thibaut noah wrote:
>
You mentioned -
>> I used the "parted /dev/sdb set 3 bios_grub on" command on my /boot
>> partition to manage to install grub, /dev/sdb3 is formatted with
>> ext2 format
I have no idea what that does, but it is clearly NOT a replacement
for actually running grub-install to /dev/sdb [ NOT sdb3 ] from within
chroot. Did you run grub-install ?
For qemu, I have to tell it on the command-line which image(s) [
i.e. disk(s) ] tp use - I assume that qemu is similar and therefore
when you try to boot LFS qemu only sees one virtual disk ?
And, nost importantly - what happens ? "Does not boot" tells us
nothing. Does grub report any error ?
> >
> > Paste the three pastebin contents into your message - not least as
> > they'll be short-enough.
> >
>
> Thought they were too long, my bad.
>
> Please note that my fstab and my grub file have been made with the
> assumption that by having one disk only sdb would become sda on the new
> virtual machine.
That sounds ok - I've never used virtual box, but qemu certainly
worked like that when I last used it.
>
> fstab :
>
>
> 1. /dev/sda1 / ext4 defaults 1 1
> 2. /dev/sda2 swap swap pri=1 0 0
> 3. /dev/sda3 /boot ext2 defaults 1 1
> 4. proc /proc proc nosuid,noexec,nodev 0 0
> 5. sysfs /sys sysfs nosuid,noexec,nodev 0 0
> 6. devpts /dev/pts devpts gid=5,mode=620 0 0
> 7. tmpfs /run tmpfs defaults 0 0
> 8. devtmpfs /dev devtmpfs mode=0755,nosuid 0 0
>
>
>
> >
> >
> grub.cfg :
>
>
> 1. # Begin /boot/grub/grub.cfg
> 2. set default=0
> 3. set timeout=5
> 4.
> 5. insmod ext2
> 6. set root=(hd0,3)
> 7.
> 8. menuentry "GNU/Linux, Linux 4.4.2-noah" {
> 9. linux /vmlinuz-4.4.2-tnoah root=/dev/sda1 ro
> 10. }
>
>
> fdisk -l :
>
> - Disk /dev/sdb: 15 GiB, 16106127360 bytes, 31457280 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: F700B567-368F-4096-BB5B-6B2A5C670F10
> -
> - Device Start End Sectors Size Type
> - /dev/sdb1 2048 20973567 20971520 10G Linux filesystem
> - /dev/sdb2 20973568 29362175 8388608 4G Linux filesystem
> - /dev/sdb3 29362176 31457246 2095071 1023M BIOS boot
>
In GPT, a BIOS boot partition is NOT for '/boot'. I think this is a
protective partition. On the machine I'm currently using, I have
Disklabel type: gpt
Disk identifier: D5D0B479-A376-441C-BEA3-48ABD017C1A3
Device Start End Sectors Size Type
/dev/sda1 2048 206847 204800 100M BIOS boot
/dev/sda2 206848 2303999 2097152 1G Linux filesystem
and so forth.
That sda2 is MY /boot partition, so in grub.cfg I have:
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
If I am right, your partitioning is wrong - you will need to backup
the new system, then partition with:
BIOS boot
new system
swap, if you need it
boot partition.
I guess you could make a new image, partition that, then boot the
original system with both of them mounted, and copy the data to the
new image, reinstall grub, and fix up grub.cfg.
ĸen
--
Democracy is the theory that the common people know what they want,
and deserve to get it good and hard -- H.L. Mencken
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
