Re: boot problem LFS 6.5
On Tue, 2009-11-24 at 04:23 -0500, stosss wrote: IDE this is 5 or 6 year old hardware that still runs fine. I do have newer hardware in another box with SATA drives that will get LFS at some point. Not sure I'd have the patience to run an LFS build on something that old. I mean, I've been using LFS on my desktop machines since that machine was an old Pentium II, but I think knowing that there's better hardware available makes it more frustrating to wait for build times. My current machine is a couple of years old and good for a few more, but I just know I'd be happier with a new quad-core box... :) Simon. signature.asc Description: This is a digitally signed message part -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: boot problem LFS 6.5
On Wed, Nov 25, 2009 at 5:06 AM, Simon Geard delga...@ihug.co.nz wrote: On Tue, 2009-11-24 at 04:23 -0500, stosss wrote: IDE this is 5 or 6 year old hardware that still runs fine. I do have newer hardware in another box with SATA drives that will get LFS at some point. Not sure I'd have the patience to run an LFS build on something that old. I mean, I've been using LFS on my desktop machines since that machine was an old Pentium II, but I think knowing that there's better hardware available makes it more frustrating to wait for build times. The entire build from start to finish and that includes booting into the new system was about 4 or 5 hours. I did not keep time by exact measure. Just noted about when I started and about when I finished. One of the big reasons it did not take longer is because I created a lot of shell scripts and ran them one after the other. Making sure my shell scripts were right took a lot longer. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
boot problem LFS 6.5
I went through the lfs 6.5 book and copied and pasted all the commands in the book to a series of shell scripts. I only made changes where it was necessary like with stuff like hda1 and hda5 other than that I left the commands in the book in tact. I used two partitions hda1 and hda5. The lfs build was done on an empty drive (with no installed OS on the machine) using the lfs 6.3 LiveCD the last release of that LiveCD. I had no compilation errors and no problems until I tried to boot. My problem originated with a problem addressed here: FAQ Kernel panic: VFS: unable to mount root fs So I checked everything and even compiled the kernel again (3 more times) to make sure and got the same kernel panic telling me the same thing. I also ran the grub configuration 4 times: at the grub prompt root (hd0,0) setup (hd0) My HDD is hda1 and in Grub I had: title LFS 6.5 root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=/dev/hda1 The kernel panic error was telling me to correct the root= part of the grub menu.lst. It was telling me to use sda1 instead of hda1 (why I don't know). So I tried that to see what would happen. title LFS 6.5 root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=/dev/sda1 I got a new set of errors and I have not been able to find anything that addresses the problem. The new series of errors are: sawpon: /dev/hda5: stat failed: No such file or directory mounting root file system in read-only mode... Checking file systems... fsck.ext3: No such file or directory while trying to open /dev/hda1 /dev/hda1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 device Then it said it has to be fixed manually and to press enter so the machine will stop and be powered off. I have no idea what to do now. If I change grub back to hda1 like I had it then I get the kernel panic, if I leave grub set as root=/dev/sda1 then I get the swap and ext3 problem. So where and what is the problem? Where did I make my mistake? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: boot problem LFS 6.5
Hi, I had a similar problem and the solution was to recompile the kernel with the correct driver for the hard disk. In my case the hard disk was a vmware partition. In your case seems that the kernel can't read the hda1. If you can, try to do an lspci and look for what HD you have than check you kernel conf file if the driver is set =yes. Hope helps. Simone 2009/11/23 stosss sto...@gmail.com I went through the lfs 6.5 book and copied and pasted all the commands in the book to a series of shell scripts. I only made changes where it was necessary like with stuff like hda1 and hda5 other than that I left the commands in the book in tact. I used two partitions hda1 and hda5. The lfs build was done on an empty drive (with no installed OS on the machine) using the lfs 6.3 LiveCD the last release of that LiveCD. I had no compilation errors and no problems until I tried to boot. My problem originated with a problem addressed here: FAQ Kernel panic: VFS: unable to mount root fs So I checked everything and even compiled the kernel again (3 more times) to make sure and got the same kernel panic telling me the same thing. I also ran the grub configuration 4 times: at the grub prompt root (hd0,0) setup (hd0) My HDD is hda1 and in Grub I had: title LFS 6.5 root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=/dev/hda1 The kernel panic error was telling me to correct the root= part of the grub menu.lst. It was telling me to use sda1 instead of hda1 (why I don't know). So I tried that to see what would happen. title LFS 6.5 root (hd0,0) kernel /boot/lfskernel-2.6.30.2 root=/dev/sda1 I got a new set of errors and I have not been able to find anything that addresses the problem. The new series of errors are: sawpon: /dev/hda5: stat failed: No such file or directory mounting root file system in read-only mode... Checking file systems... fsck.ext3: No such file or directory while trying to open /dev/hda1 /dev/hda1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 device Then it said it has to be fixed manually and to press enter so the machine will stop and be powered off. I have no idea what to do now. If I change grub back to hda1 like I had it then I get the kernel panic, if I leave grub set as root=/dev/sda1 then I get the swap and ext3 problem. So where and what is the problem? Where did I make my mistake? -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: boot problem LFS 6.5
stosss wrote:
All Right! I did what you suggested and now I have a command prompt!
Congratulations on being a new LFS user!
Three cheers!
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
