Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm not exactly sure what you are trying to accomplish here other than mounting hard disks. In this case, if you are able to log in, then do this:
Code:
blkid
Once you see what your disk is recognized as (for each partition), then do this:
(Replace ext with whatever your filesystem is; ext4, vfat, ntfs, ntfs-3g, etc)
(Replace sda# with whatever yours is; sdb, hda, hdb, and the number with whatever partition yours is; sda1, sda3, sda7, etc)
Code:
# For root partition:
mount -t ext3 /dev/sda2 /
# For home partition
mount -t ext3 /dev/sda3 /home
# For swap
swapon /dev/sda1
The problem may be caused by the fact that ISA IDE and SCSI adapters are
no longer attempted to be autodetected. If you use such hardware, load the
proper driver manually with the "modprobe" command and exit from this shell.
For old IDE controllers, the correct module name is "ide-generic", or, if
you want to use the new libata-based driver, "pata-legacy". To avoid this
message next time you boot this CD, use a kernel command line like this:
linux load=ide-generic
This problem can be also caused by a slow SCSI controller or USB/FireWire
CD-ROM that needs more time to be detected. If you see any kernel messages
below, this is the case. In this case, it is sufficient to type "exit",
and the CD will continue the boot process. To avoid this message next
ime you boot this CD, use a kernel command line like this:
linux rootdelay=20
Dropping you to a shell.
I think that my system search for root.ext2 on cdrom and when it didn't find it , it drop to shell sh-3.2#
I think that i must point kernel to find root.ext2 on my hdd .
Can Anybody help me to append my root.ext2 that is on my hdd and don't in the CDROM ? in other words HOW could i boot LFS from my Hard disk Drive ??
Too my knowledge you cannot copy the LFS liveCD to your hard-disk and boot it. It is a liveCD and not installable. I've been working with and following LFS for years and I never read an article/post that mentions how to do this.
menuentry 'LFS livecd from HD test' {
set root='(hd0,4)'
linux /boot/isolinux/linux root=/dev/sda4 rw
initrd /boot/isolinux/initramfs_data.cpio.gz
}
Although I don't know for sure where you placed the linux and initramfs files, I do believe the bold red part is incorrect.
If you followed the instructions from the article those 2 files reside in /boot and not /boot/isolinux. Check if they are at that location and if so change your grub menu entry to:
Code:
menuentry 'LFS livecd from HD test' {
set root='(hd0,4)'
linux /boot/linux root=/dev/sda4 rw
initrd /boot/initramfs_data.cpio.gz
}
In my LFS Live CD image from ftp://66.135.59.49/LFS-LiveCD/lfsliv...-6.3-r2160.iso the 2 files [ linux + initramfs ] are in the isolinux folder but if you want i can move these files to boot folder .
i think that my grub scripts still has an error ,
TNX alot for your suggestions .
I wonder if you fully understand what is being done, 'cause you are looking in the wrong place.
/mnt/lfs-hd holds the copied bootable LFS liveCD files (including the linux and initramfs files in /mnt/lfs-hd/boot). Have a look at stpes 10 and 11, those clearly copy those 2 files to /mnt/lfs-hd/boot/.
After you finished all the 18 steps you can savely remove the /mnt/rootfs, /mnt/iso directories and the lfslivecd-x86-6.3-r2160.iso file. These will not be used to boot.
To create a grub menu entry you need to strip the /mnt/lfs-hd part, that part is only created as a temporary mount point. Assuming you used /dev/sda4 the following should work (same as in my previous post [#10]):
Code:
menuentry 'LFS livecd from HD test' {
set root='(hd0,4)'
linux /boot/linux root=/dev/sda4 rw
initrd /boot/initramfs_data.cpio.gz
}
ONLY , i copy my LFS-LiveCD iso files to my (hd0,4) .
When i booted from (hd0,4) i can boots from my LFS kernel & initrd but at the end of my boot process these message was appeared :
The problem may be caused by the fact that ISA IDE and SCSI adapters are
no longer attempted to be autodetected. If you use such hardware, load the
proper driver manually with the "modprobe" command and exit from this shell.
For old IDE controllers, the correct module name is "ide-generic", or, if
you want to use the new libata-based driver, "pata-legacy". To avoid this
message next time you boot this CD, use a kernel command line like this:
linux load=ide-generic
This problem can be also caused by a slow SCSI controller or USB/FireWire
CD-ROM that needs more time to be detected. If you see any kernel messages
below, this is the case. In this case, it is sufficient to type "exit",
and the CD will continue the boot process. To avoid this message next
ime you boot this CD, use a kernel command line like this:
linux rootdelay=20
Dropping you to a shell.
sh-3.2#
there is not any mnt or ... folder and only my folders is :
.root , bin , dev , etc , lib , proc , root , sbin , sys
The above shown problem is exactly the same as the one in post #4 and that was with the wrong grub entries (the lfs and isolinux parts are still present).
What is shown before the The problem may be caused by the fact that..... message? That might give us a clue, please post the +/- 5 lines before the message.
To be honest, the actions shown in the article are very straight forward. Are you sure you followed them to the letter? If you did decide to start again from step one, did you remove/delete all the old stuff before starting again?
One other question: Is your hardware (very) new or (very) old?
while i connected cdrom [ vs LFS_Livecd ] to my PC And reboot from (hd0,4) , My LFS boots correctly and without any fail messages .( With isolinux or grub boots correct )
It means that my LFS [ on (hd0,4) ] search for root.ext2 on the CDROM !!
And that message [ post #13 ] is in the init of initramfs while find_cd() part gets an error .
Also , we must point kernel to append root.ext2 on the hd0,4 and not on CDROM .
I hope that i could describe my problem correctly .
ok , this error message shown before of post #13 message :
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.