2016-06-29 13:54 GMT+02:00 Ken Moffat <zarniwh...@ntlworld.com>:
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 ?
Yes i did, but if i don't use the parted command i cannot run grub-install,
the command will fail.
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 ?
you mean virtualbox right? i don't use qemu for this, virtualbox only see
the disk i give to it so yes one disk.
And, nost importantly - what happens ? "Does not boot" tells us
nothing. Does grub report any error ?
What i mean is virtualbox doesn't find anything to boot on, so no grub no
anything, i don't have the exact message because i'm home
but it's something like "no boot device detected"
If I am right, your partitioning is wrong - you will need to backup
the new system, then partition with:
Why would i do that? grub needs to have /boot in first position on the
disk?
2016-06-29 14:20 GMT+02:00 Ken Moffat <zarniwh...@ntlworld.com>:
On reflection - since the BIOS boot partition is not protecting the
GPT in your image, try:
1. change your grub.cfg to insmod part_gpt and root 'hd0,gpt3'.
2. if that doesn't work, change the partition type of sdb3 to
regular Linux filesystem.
What do you mean by protecting the gpt?
2016-06-29 14:22 GMT+02:00 akhiezer <lf...@cruziero.com>:
>
>
> From this and what you say in other parts of the thread:
> ==
> * you have got only one _physical_ disk; is that correct?
>
>
Not at all, i don't have ANY Physical disk, i have two virtual disks (said
it earlier) and what i do is creating another virtual machine with just the
virtual drive of lfs
and i want to boot like this.
> * you want to boot directly from power-on thru bios/uefi, directly into
> lfs; is that correct?
>
yes
> ==
>
> Assuming 'yes' to both questions, then very likely:
> --
> * said bios/uefi will see the single disk as sda .
>
>
I verified this by booting with the arch-live iso, disk is indeed seen as
sda.
> * said grub will need to know what are the _real_ partitions on sda that
> '/' and '/boot' are on.
> --
>
>
>
Will run your command as soon as i arrive to work thanks.
>
> .
> .
> >
> > 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.
> >
> > 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 :
>
>
> Was this fdisk-l generated from your Debian host or from your lfs?
>
I actually have no idea, it should be the same from both anyway.
>
>
> > - Disk /dev/sda: 8 GiB, 8589934592 bytes, 16777216 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: dos
> > - Disk identifier: 0x5c2e89f5
> > -
> > - Device Boot Start End Sectors Size Id Type
> > - /dev/sda1 * 2048 15988735 15986688 7.6G 83 Linux
> > - /dev/sda2 15990782 16775167 784386 383M 5 Extended
> > - /dev/sda5 15990784 16775167 784384 383M 82 Linux swap /
> Solaris
> > -
>
>
> Is sda1 there your 7.6 GB Debian host?
>
yes it is.
>
>
> > - 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
> >
>
>
> And is the sdb1 there your 10 GB lfs '/' ; and the sdb2 your (4 GB)
> lfs swap; and the sdb3 your 1 GB lfs /boot ?
>
>
You got the partitionning right.
>
> In any case: where on the single _physical_ disk, do those sdb{1,2,3}
> partitions live? You need to be able to say/know, effectively: 'sdb1'
> is 'really' 'sdaN', for some number 'N'; and similarly for 'sdb2' &
> 'sdb3' .
>
>
>
There is no physical disk.
> Hope that makes sense and am not confusing things (further).
>
>
No worries mate, kind enough to try to help.
>
> --
> --
> 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
>
--
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
