Thank you Thomas ...


1.

➜  ~ blkid

/dev/sde1: LABEL="XXXXXX" UUID="*d8a7b940-0ff5-41c4-81a0-9fd1797501ed*" TYPE="ext4" PARTUUID="0860eda0-01"

➜  ~ sudo fdisk -l

Disk /dev/sde: 14.8 GiB, 15833497600 bytes, 30924800 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: 0x0860eda0

Device     Boot Start      End  Sectors  Size Id Type
/dev/sde1        2048 30924799 30922752 14.8G 83 Linux


/It is clear that I've correctly partitioned my //*USB stick*//./


2.

➜  ~ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type> <options>       <dump>  <pass>
# / was on /dev/sdc3 during installation
UUID=XXXXXXXXXXXXXXXXXXXXXXXXXXXX /               ext4    errors=remount-ro 0       1
# /dev/sde1
UUID=*d8a7b940-0ff5-41c4-81a0-9fd1797501ed* / ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sdb1 during installation
UUID=YYYYYYYYY  /boot/efi       vfat    umask=0077      0       1
/swapfile


/This is my //*host laptop's fstab*//. Hmm, here is what I'm //*NOT*//quite clear. //*mtab automatically*//mounts my *USB stick* every time if I don't specify this //*USB stick*//in //*fstab*//. Anyway, now I clearly specified this */dev/sde1* via *UUID* in /*/fstab/*/, it's *NOT* showing *in mtab* any more, which is just what I'm expecting. *However*, how about if I *plug out this USB stick* and want to use it on *another laptop*?/


3. Rebooting ... Let me show you some more pictures first...

https://longervision.cc/bugs/grub.jpg

https://longervision.cc/bugs/grub_advanced_option.jpg

https://longervision.cc/bugs/kernel_panic.jpg


/It's weird the names listed in *grub*... Can I change them? But how? I checked my *host's grub.cfg*, and found:/

//

menuentry 'Longer Vision Technology (8.4) (on /dev/sde1)' --class longervisiontechnology --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-d8a7b940-0ff5-41c4-81a0-9fd1797501ed' {
    insmod part_msdos
    insmod ext2
    set root='hd4,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4,msdos1 d8a7b940-0ff5-41c4-81a0-9fd1797501ed
    else
      search --no-floppy --fs-uuid --set=root d8a7b940-0ff5-41c4-81a0-9fd1797501ed
    fi
    linux /boot/vmlinuz-5.0.2-lfs-8.5 rootdelay=10 root=/dev/sde ro
}
submenu 'Advanced options for Longer Vision Technology (8.4) (on /dev/sde1)' $menuentry_id_option 'osprober-gnulinux-advanced-d8a7b940-0ff5-41c4-81a0-9fd1797501ed' {     menuentry 'GNU/Linux, Linux 5.0.2-lfs-8.5 (on /dev/sde1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.0.2-lfs-8.5--d8a7b940-0ff5-41c4-81a0-9fd1797501ed' {
        insmod part_msdos
        insmod ext2
        set root='hd4,msdos1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4,msdos1 d8a7b940-0ff5-41c4-81a0-9fd1797501ed
        else
          search --no-floppy --fs-uuid --set=root d8a7b940-0ff5-41c4-81a0-9fd1797501ed
        fi
        linux /boot/vmlinuz-5.0.2-lfs-8.5 rootdelay=10 root=/dev/sde ro
    }
}


It looks the options are *automatically built* into this*host's* *grub.cfg* while I was doing *sudo update-grub* ? I just do NOT like the name, and I believe I can modify this *host's grub.cfg* into to show a different name (doing it now). However, since it's automatically built into this *host's grub.cfg*, where is the *original place* that I can specify this info? Just cannot remember. It must be ME who specified those info somewhere .....



Anyway, Thank you very much for your prompt reply...



Cheers

Pei




On 2019-03-18 3:22 a.m., thomas wrote:
Am 2019-03-18 11:14, schrieb Pei Jia:
Hi:

I now make some progress:

     * I followed your suggestions, CP -A LFS OUT TO MY HOST, AND
PARTITION THE USB DRIVE.
     * However, I still failed to boot, please refer to my new result:
https://longervision.cc/bugs/lfs_kernel_panic.jpg

I believe I'm already very close to the RIGHT answer...

Anyway, I now have  2 GRUBS, one is ON MY HOST'S LAPTOP GRUB, the
other is ON MY USD DRIVER.

BTW, is this
http://linuxfromscratch.org/lfs/view/stable/chapter08/grub.html for
configuring GRUB2 on the HOST COMPUTER (EXISTING GRUB) ? or for the
NEWLY USB DRIVE?

Cheers

Pei

On 2019-03-17 2:13 p.m., spiky0011 wrote:

On 17/03/2019 20:33, Pei Jia wrote:

...

Please do not top-post. Add your comments *below* the text you're answering. That helps to follow the discussion.

Please provide the grub.cfg file, the fstab of the system to boot and the partition layout including info about which partition contains which file system. Indeed, it looks like we not too far from success, but you never know...  ;-)

--
Thomas
-- 
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

Reply via email to