Michael Shell wrote:
> On Wed, 13 Mar 2013 22:34:59 -0400
> Michael Shell wrote:
>
>
>> 1. Changing the BIOS configuration to alter the numbering of
>> an external USB drive so as not to disturb the SATA drive
>> numbers.
>
>
> Or more correctly, "so as not to disturb the SATA boot dev
On Dec 26, 2012, at 2:09 AM, JIA Pei wrote:
Kernel panic - not syncing: VFS: unable to mount root fs on unknown
block(0,0)
http://www.linuxfromscratch.org/lfs/faq.html#unable-to-mount-root
0,0 means no block devices were detected which means:
1) No hard drive controller enabled in the
Hi, all:
Sorry that I started another new topic. BTW, thanks Bruce, thank you for
your answer to my former question, which makes me much clearer already.
However, I still keeps receiving the following error message.
*Kernel panic - not syncing: VFS: unable to mount root fs on unknown
block(0,0
On Sat, 2012-12-22 at 00:31 +, Richard Melville wrote:
> It seems a little churlish to pick holes in what is essentially a good
> article, and, indeed, one that supplied the answer to a question on
> this list.
True. Well, suffice it to say that the /dev/disks symlink tree *does*
support GPT
> On Thu, 2012-12-20 at 14:53 +, Richard Melville wrote:
>
> > I think that was understood; when they said that it was "stupid" it
> > was surely meant that there could be some confusion in the use of
> > similar terms.
>
> Possibly, though if they'd understood it, you'd think they'd have
On Thu, 2012-12-20 at 14:53 +, Richard Melville wrote:
> I think that was understood; when they said that it was "stupid" it
> was surely meant that there could be some confusion in the use of
> similar terms.
Possibly, though if they'd understood it, you'd think they'd have
mentioned the by
On Tue, 2012-12-18 at 11:19 +, Richard Melville wrote
>
> Would't using GPT instead of MBR be a viable alternative?
Nope. GPT assigns UUIDs to the partitions, but that's all - the kernel
still deals only with traditional device names (sda1, sda2, etc). The
initramfs is still needed t
what I believe to be a trace call.
Interestingly, one time when I booted the trace call was short enough
for me to write down the error which I can't normally see due to the
length of the trace prints. Here is the error:
Kernel panic-not syncing: VFS: Unable to mount root fs on unknown
bloc
Richard Melville wrote:
>>
>>> Now it would be nice for it to work using UUIDs so the booting can
>>> be independent of host system.
>>
>> You need to use an initrd of that. See BLFS.
> Would't using GPT instead of MBR be a viable alternative?
No. Mounting the root partition is a kernel issue a
>
> > Now it would be nice for it to work using UUIDs so the booting can
> > be independent of host system.
>
> You need to use an initrd of that. See BLFS.
>
>-- Bruce
>
>
Would't using GPT instead of MBR be a viable alternative?
Richard
--
http://linuxfromscratch.org/mailman/listinfo/lfs-s
Alexander Spitzer wrote:
> I got it to work! Turns out that the root file system changes to /dev/sdc1
> after all the harddisks are found so changing the line root=/dev/sda1 to
> root=/dev/sdc1 and adding a rootdelay successfully booted the system!
>
> Now it would be nice for it to work using UUID
booted the trace call was short enough for me to write down the
> error which I can't normally see due to the length of the trace prints.
> Here is the error:
>
> Kernel panic-not syncing: VFS: Unable to mount root fs on unknown
> block(0,0)
>
> What exactly does "unk
, one time
when I booted the trace call was short enough for me to write down the
error which I can't normally see due to the length of the trace prints.
Here is the error:
Kernel panic-not syncing: VFS: Unable to mount root fs on unknown block(0,0)
What exactly does "unknown block(0,0)&q
On 25/10/12 23:25, Bruce Dubbs wrote:
> spiky wrote:
>> On 25/10/12 22:50, Ken Moffat wrote:
>>> On Thu, Oct 25, 2012 at 10:03:46PM +0100, spiky wrote:
Hi
Ok I,m having real trouble booting my lfs system. Long storey with lfs
7.2 won
>> I rebuilt the kernel after moving to new laptop
spiky wrote:
> On 25/10/12 22:50, Ken Moffat wrote:
>> On Thu, Oct 25, 2012 at 10:03:46PM +0100, spiky wrote:
>>> Hi
>>> Ok I,m having real trouble booting my lfs system. Long storey with lfs
>>> 7.2 won
> I rebuilt the kernel after moving to new laptop. Root is on sda3 ext4
> only 1 harddrive,
>
e before. on to this laptop replacing 7.2.
>> I adjusted fstab file as needed for new partitions.
>> I have tried booting from grub prompt (host grub)
>> set root=(hd0,3)
>> linux /boot/vmlinuz-3.3-rc1-lfs-7.0
>> boot
>>
>> I get a kernel panic
>>
sted fstab file as needed for new partitions.
> I have tried booting from grub prompt (host grub)
> set root=(hd0,3)
> linux /boot/vmlinuz-3.3-rc1-lfs-7.0
> boot
>
> I get a kernel panic
> "VFS unable to mount root fs via NFS trying floppy
> VFS cannot open root de
> I have tried booting from grub prompt (host grub)
> set root=(hd0,3)
> linux /boot/vmlinuz-3.3-rc1-lfs-7.0
> boot
>
> I get a kernel panic
>"VFS unable to mount root fs via NFS trying floppy
> VFS cannot open root device "(null)" or unknown-block(2,0)
prompt (host grub)
set root=(hd0,3)
linux /boot/vmlinuz-3.3-rc1-lfs-7.0
boot
I get a kernel panic
"VFS unable to mount root fs via NFS trying floppy
VFS cannot open root device "(null)" or unknown-block(2,0)
please append a correct "root=" boot option here are availble part
Danny Vukobratovich wrote:
>> I had problems with this in 7.0 also. I ended up having to start over
>> changing the hard drive type to IDE. It is now working for me.
>
> That's a little extreme. The only thing that needed to be fixed is the
> kernel and perhaps fstab or grub.cfg. Those are the
- Original Message -
From: "Bruce Dubbs"
To: "LFS Support List"
Sent: Wednesday, November 16, 2011 1:38:30 PM
Subject: Re: Kernel panic - not syncing: VFS; Unable to mount root fs on
Danny Vukobratovich wrote:
> On Nov 16, 2011, at 6:35, Subrata Paul
>
essfully
>> compiled and installed. However, after the first boot it gives the
>> following error:
>>
>> Kernel panic – not syncing: VFS: Cannot open root device
>> “sda3†or unknown-block(8,2)
>>
>> Please append a correct "root=" boot
- Original Message -
From: "Danny Vukobratovich"
To: "LFS Support List"
Sent: Wednesday, November 16, 2011 6:49:37 AM
Subject: Re: Kernel panic - not syncing: VFS; Unable to mount root fs on
On Nov 16, 2011, at 6:35, Subrata Paul < subrata.m...@gmai
nd installed. However,
> after the first boot it gives the following error:
>
>
>
> Kernel panic – not syncing: VFS: Cannot open root device “sda3” or
> unknown-block(8,2)
>
> Please append a correct "root=" boot option; here are the available
>
> p
Hi,
I am trying to build an LFS system as a guest on VMware workstation
(version – 7.1.4). I am following the 6.8 version of the LFS book. All the
packages mentioned in this book are successfully compiled and installed.
However, after the first boot it gives the following error:
Kernel panic
From: "Michael"
To: "LFS Support List"
Sent: Friday, November 11, 2011 2:26:55 PM
Subject: Re: Kernel panic - not syncing: VFS; Unable to mount root fs on
unknown-block(2.0)
Am Freitag 11 November 2011 20:11:05 schrieb Danny Vukobratovich:
> I saw this thread tha
Am Freitag 11 November 2011 20:11:05 schrieb Danny Vukobratovich:
> I saw this thread that I thought was related but is addressing the issue in
> LFS 6.6
>
> http://www.linuxfromscratch.org/pipermail/lfs-support/2010-April/038457.htm
> l
>
> I'm setting up LFS 7.0. I am doing this in a VMworkstat
I saw this thread that I thought was related but is addressing the issue in LFS
6.6
http://www.linuxfromscratch.org/pipermail/lfs-support/2010-April/038457.html
I'm setting up LFS 7.0. I am doing this in a VMworkstation 8 environment with
the GRML Live CD as my host. The default setup for the
Thank you for your assistance. I did 'lsmod -v' and found a number of
the drivers, compiled them and boot into my first ever LFS system.
Thank you again.
--
Frederick M. Muriithi
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubsc
n; here are the
> available partitions:
> [ 3.585482] Kernel panic - not syncing: VFS: Unable to mount root fs
> on unknown-block(0,0)
> [ 3.585754] Pid: 1, comm: swapper Not tainted 2.6.37 #1
> [ 3.585911] Call Trace:
> [ 3.586084] [] ? printk+0xf/0x11
> [ 3.586243] [] pa
> [ 3.585205] Please append a correct "root=" boot option; here are the
> available partitions:
> [ 3.585482] Kernel panic - not syncing: VFS: Unable to mount root fs
> on unknown-block(0,0)
Sounds like you do not have the proper kernel drivers for your hardware.
>
uot;root=" boot option; here are the
available partitions:
[ 3.585482] Kernel panic - not syncing: VFS: Unable to mount root fs
on unknown-block(0,0)
[ 3.585754] Pid: 1, comm: swapper Not tainted 2.6.37 #1
[ 3.585911] Call Trace:
[ 3.586084] [] ? printk+0xf/0x11
[ 3.58
Tony Hartzell wrote:
> VFS: Cannot open root device "hda2" or unknown-block(2,0)
> Please append a correct "root=" boot option; here are the available
> partitions:
> Kernel panic - not syncing: VFS: unable to mount root fs on
> unknown-block(2,0)
Usually a res
ped that when someone saw 'here are the available partitions' was blank,
> (from just before the kernel panic) that they'd "Oh, silly boy, you forgot
> to..."
Have you read bruces kernel hint?
http://www.linuxfromscratch.org/hints/downloads/files/kernel-configuration.
ing.
> I hoped that when someone saw 'here are the available partitions' was blank,
> (from just before the kernel panic) that they'd "Oh, silly boy, you forgot
> to..."
Well it does look like you have both a SATA and PATA controller, so hda
may be appropriate. Th
e kernel config as per udev's README, and I considered that
PATA drives might be going extinct, but I didn't see any obvious config
parameters that would prevent them from working.
I hoped that when someone saw 'here are the available partitions' was blank,
(from just before the k
Tony Hartzell wrote:
> VFS: Cannot open root device "hda2" or unknown-block(2,0)
> Please append a correct "root=" boot option; here are the available
> partitions:
> Kernel panic - not syncing: VFS: unable to mount root fs on
> unknown-block(2,0)
>
> I
VFS: Cannot open root device "hda2" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available
partitions:
Kernel panic - not syncing: VFS: unable to mount root fs on
unknown-block(2,0)
I think my problem is that /dev isn't being populated.
> VFS: unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "sdb5" or unknown block(2,0)
> Please append a correct "root=" boot option; here are the available
> partitions:
> Ob00 1048575 sr0 driver: sr
> Kernel panic - not syncing
.
VFS: Cannot open root device "sdb5" or unknown block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
Ob00 1048575 sr0 driver: sr
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(2,0)
>>>>
/dev/sdb5 is pr
On Fri, Jun 3, 2011 at 10:34 AM, bsquared wrote:
> bsquared wrote:
>> Hello,
>>
>> Can anyone recommend some resources for troubleshooting a kernel panic.
>>
>> I have been built LFS 6.8 on a USB stick, and moved it to a disk
>> partition using 'dd&
bsquared wrote:
> Hello,
>
> Can anyone recommend some resources for troubleshooting a kernel panic.
>
> I have been built LFS 6.8 on a USB stick, and moved it to a disk
> partition using 'dd'. I modified the grub.cfg file and rebooted.
> Then got a kernel panic.
bsquared wrote:
> Hello,
>
> Can anyone recommend some resources for troubleshooting a kernel panic.
>
> I have been built LFS 6.8 on a USB stick, and moved it to a disk
> partition using 'dd'. I modified the grub.cfg file and rebooted.
> Then got a kernel pani
On Wed, Jun 1, 2011 at 8:15 PM, bsquared wrote:
> Hello,
>
> Can anyone recommend some resources for troubleshooting a kernel panic.
>
> I have been built LFS 6.8 on a USB stick, and moved it to a disk
> partition using 'dd'. I modified the grub.cfg file and reboote
Hello,
Can anyone recommend some resources for troubleshooting a kernel panic.
I have been built LFS 6.8 on a USB stick, and moved it to a disk
partition using 'dd'. I modified the grub.cfg file and rebooted.
Then got a kernel panic.
--
Thank you,
-Brian
--
http://linuxfroms
On 05/10/2011 03:39 AM, shubham jain wrote:
> When I boot from my LFS CD
> I get the message: *Kernel panic - not syncing: Attempted to kill the
> idle task*
>
> I am using *LFS live CD -x86-6.3-r2160-min*
>
> I have windows 7 also installed on my system.
> My system deta
When I boot from my LFS CD
I get the message: *Kernel panic - not syncing: Attempted to kill the idle
task*
I am using *LFS live CD -x86-6.3-r2160-min*
I have windows 7 also installed on my system.
My system details are:
*
Processor: Intel core 2 Quad 2.83 GHz
RAM : 2GB*
This is the full
mas...@mail.com wrote:
> LFS system dmesg | grep IDE:
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> PIIX4: IDE controller at PCI slot :00:07.1
> Probing IDE interface ide0...
> Probing IDE interface ide1...
> hdc: VMware Virtual IDE CDROM Drive, ATAPI CD/DVD-ROM drive
> target0
/input/inp
ut6
Thanks
// Mastah
-Original Message-
From: Justin The Cynical
To: LFS Support List
Sent: Tue, Apr 13, 2010 10:39 am
Subject: Re: Kernel panic - not syncing: VFS; Unable to mount root fs
on unknown-block(2.0)
mas...@mail.com wrote:
> Hi i got this error when i tried to boo
ernel and took every driver for SATA and SCSI just to
> be sure that wont be an issue.
*snip*
> Kernel panic - not syncing: VFS; Unable to mount root fs on
> unknown-block(2.0)
> VFS: Cannot open root device "sda2" or unknown-block(2.0)
*snip*
> linux /vmlinux-2
> I've no idea what vmware is but I expect it has something to do with
your
> problem
It is a virtualization program.
So i have my Ubuntu laptop, in it i use vmware to boot up the LFS live
cd which is the host system and in there i build my LFS system.
> VMWare will not show your guest OS the ac
### END /etc/grub.d/10_linux ###
>
> ### BEGIN /etc/grub.d/30_os-prober ###
> ### END /etc/grub.d/30_os-prober ###
>
> ### BEGIN /etc/grub.d/40_custom ###
> # This file provides an easy way to add custom menu entries. Simply
> type the
> # menu entries you want to add after
h --no-floppy --fs-uuid --set
>> dd263110-8c28-48f1-bb0e-5c779c97e9ac
>> linux /vmlinux-2.6.32.8-lfs-6.6 root=/dev/sda2 ro
>> }
> Are these search lines needed? I don't put them in my grub.cfg
Andy, the search lines are added by GRUB, they are ignored by L
ode)" {
> insmod ext2
> set root=(hd0,1)
> search --no-floppy --fs-uuid --set
> dd263110-8c28-48f1-bb0e-5c779c97e9ac
Are these search lines needed? I don't put them in my grub.cfg
> when i reboot i get:
> Kernel panic - not syncing: VFS; Un
tail' line above.
### END /etc/grub.d/40_custom ###
i set the grub MBR to /dev/sda
when i reboot i get:
Kernel panic - not syncing: VFS; Unable to mount root fs on
unknown-block(2.0)
VFS: Cannot open root device "sda2" or unknown-block(2.0)
Please append a correct "root="
option; here are the available
> partitions:
> 0b00 1048575 dr0 driver: sr
> Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
This looks like you are right, you don't have the right drivers.
There are three levels you need
f
On Sat, Apr 3, 2010 at 3:38 PM, Kaleb Hosie wrote:
> I'm really stumped right now and I could use some help.
>
> I've finished compiling the Kernel for my first LFS deployment and I after I
> finished rebooting it for the first time, I get a Kernel Panic. Here's wha
On Sat, Apr 3, 2010 at 3:38 PM, Kaleb Hosie wrote:
> I'm really stumped right now and I could use some help.
>
> I've finished compiling the Kernel for my first LFS deployment and I after I
> finished rebooting it for the first time, I get a Kernel Panic. Here's wha
I'm really stumped right now and I could use some help.
I've finished compiling the Kernel for my first LFS deployment and I after I
finished rebooting it for the first time, I get a Kernel Panic. Here's what is
looks like:
VFS: Cannot open root device "sda1" or
On Tue, Mar 23, 2010 at 3:55 AM, Yaacov-Yoseph Weiss
wrote:
> I saw that the list places my messages at the top level of the
> threads, and not as a response to previous messages. I assume
> this is because I get the digest version, and reply to that and
> change the subject. If anyone knows how I
I saw that the list places my messages at the top level of the
threads, and not as a response to previous messages. I assume
this is because I get the digest version, and reply to that and
change the subject. If anyone knows how I can reply "correctly",
I'll be glad to comply.
Bruce Dubbs wrote:
>
Yaacov-Yoseph Weiss wrote:
[...]
> I would recommend improving chapter 8.3 of the book (configuring and compiling
> the kernel) by adding these hints about configuring the kernel, i.e.
> using lspci,
> lsmod, and enabling many options.
I would agree with this except that the kernel is such a rap
Yaacov-Yoseph Weiss wrote:
> I would recommend improving chapter 8.3 of the book (configuring and compiling
> the kernel) by adding these hints about configuring the kernel, i.e.
> using lspci, lsmod, and enabling many options.
There's way too many different issues for Chapter 8. Did you read th
Andrew Benton wrote:
>> I added CONFIG_PATA_VIA, and that did not help.
> which CONFIG_PATA_VIA depends? If I were you I'd enable support for lots of
> things that
> may, possibly be needed and compile them all into the kernel. Use lspci as a
> guide and
Thanks. When enabling lots of options I
On 21/03/10 13:10, Yaacov-Yoseph Weiss wrote:
> I installed lfs (around the time of one of the 6.6 release candidates)
> on an old Compaq laptop using jhalfs. After completing the configuration
> (from the current 6.6 release), I tried to boot the new system and
> received a kernel pan
I installed lfs (around the time of one of the 6.6 release candidates)
on an old Compaq laptop using jhalfs. After completing the configuration
(from the current 6.6 release), I tried to boot the new system and
received a kernel panic saying it could not mount the root filesystem.
I'll t
- Original Message
> From: Andrew Benton
> To: lfs-support@linuxfromscratch.org
> Sent: Mon, 8 February, 2010 11:00:38 PM
> Subject: Re: Kernel Panic - not syncing: VFS:
>
> On 08/02/10 15:44, Aditya Bankar wrote:
> > - Original Message
> >&g
On 08/02/10 15:44, Aditya Bankar wrote:
>
>> From: Bruce Dubbs
>>
>> Go ahead and post your full config file at http://pastebin.com/ and let
>> us know the url so we can take a look. I suspect some underlying
>> drivers are missing.
>>
> I have put the config file here: http://pastebin.com/m43ec2f
Andrew Benton wrote:
> On 08/02/10 16:16, Aditya Bankar wrote:
>> If I run menuconfig to recompile, should I first clean& distclean?
>> Or is it ok to just run make again after an update to the .config
>> file?
>>
> Before I recompile the kernel I always run make mrproper
That is the standard re
On 08/02/10 15:44, Aditya Bankar wrote:
> - Original Message
>> From: Bruce Dubbs
>>
>> Go ahead and post your full config file at http://pastebin.com/ and let
>> us know the url so we can take a look. I suspect some underlying
>> drivers are missing.
>>
> I have put the config file here:
Aditya Bankar wrote:
>> If there any way of mapping /mnt/lfs into virtual box (or any other
>> VM) as /. This would help in checking state of the newly compiled
>> OS without rebooting the host.
> I found it here:
> http://ubuntuforums.org/archive/index.php/t-604000.html. This
> required running Vi
On 08/02/10 16:16, Aditya Bankar wrote:
> If I run menuconfig to recompile, should I first clean& distclean? Or is it
> ok to just run make again after an update to the .config file?
>
Before I recompile the kernel I always run
make mrproper
Andy
--
http://linuxfromscratch.org/mailman/listinfo/
> If there any way of mapping /mnt/lfs into virtual box (or any other VM) as /.
> This would help in checking state of the newly compiled OS without rebooting
> the
> host.
I found it here: http://ubuntuforums.org/archive/index.php/t-604000.html. This
required running Virtual Box as root.
But
If I run menuconfig to recompile, should I first clean & distclean? Or is it ok
to just run make again after an update to the .config file?
If there any way of mapping /mnt/lfs into virtual box (or any other VM) as /.
This would help in checking state of the newly compiled OS without rebooting
- Original Message
> From: Bruce Dubbs
>
> Go ahead and post your full config file at http://pastebin.com/ and let
> us know the url so we can take a look. I suspect some underlying
> drivers are missing.
>
I have put the config file here: http://pastebin.com/m43ec2f8f
> The out
On 08/02/10 02:06, Aditya Bankar wrote:
>
> Do you need more information?
>
Yes, the info Bruce asked for would be helpful
Bruce Dubbs wrote:
> Go ahead and post your full config file at http://pastebin.com/ and let
> us know the url so we can take a look. I suspect some underlying
> drivers are
From: Aditya Bankar
To: LFS Support List
Sent: Sun, 7 February, 2010 10:32:53 PM
Subject: Re: Kernel Panic - not syncing: VFS:
- Original Message
> From: Andrew Benton
> To: lfs-support@linuxfromscratch.org
> Sent: Sun, 7 February, 2010 8
> VFS: Unable to mount root fs via NFS trying floppy
> >>>> VFS: Cannot open root device "sda6" on unknown_block (2,0)
> >>>> Please append a correct "root=" boot options; here the options
> >>>> Kernel Panic - not syncing: VFS
t;sda6" on unknown_block (2,0)
>>>> Please append a correct "root=" boot options; here the options
>>>> Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown_block
>> (2,0)
>>>> I did not install grub. I have instead added new entr
- Original Message
> From: Andrew Benton
> To: lfs-support@linuxfromscratch.org
> Sent: Sun, 7 February, 2010 8:57:02 PM
> Subject: Re: Kernel Panic - not syncing: VFS:
>
> On 07/02/10 13:39, Aditya Bankar wrote:
> >
> >
> >
> >
> &g
On 07/02/10 13:39, Aditya Bankar wrote:
>
>
>
>
> - Original Message
>> From: Aditya Bankar
>> To: lfs support
>> Sent: Sun, 7 February, 2010 5:18:26 PM
>> Subject: Kernel Panic - not syncing: VFS:
>>
>> Hi,
>>
>> I am getti
- Original Message
> From: Aditya Bankar
> To: lfs support
> Sent: Sun, 7 February, 2010 5:18:26 PM
> Subject: Kernel Panic - not syncing: VFS:
>
> Hi,
>
> I am getting this problem while launching the new LFS 6.5:
>
> Root NFS: No NFS server availab
Hi,
I am getting this problem while launching the new LFS 6.5:
Root NFS: No NFS server available, giving up
VFS: Unable to mount root fs via NFS trying floppy
VFS: Cannot open root device "sda6" on unknown_block (2,0)
Please append a correct "root=" boot options; here the
Rambabu Dasari wrote:
> Hi all,
>
> I am trying to build Linux from Scratch(LFS), while booting the kernel
> throughing the following error.
>
> [4.586704] Warning: unable to open an initial console.
> [4.592188] Failed to execute /init
> [ 4.595746] Kernel
On 24/01/10 16:40, Rambabu Dasari wrote:
> Hi all,
>
> I am trying to build Linux from Scratch(LFS), while booting the kernel
> throughing the following error.
>
> [4.586704] Warning: unable to open an initial console.
> [4.592188] Failed to execute /init
> [
On 1/24/10, Rambabu Dasari wrote:
> Hi all,
>
> I am trying to build Linux from Scratch(LFS), while booting the kernel
> throughing the following error.
>
> [4.586704] Warning: unable to open an initial console.
> [4.592188] Failed to execute /init
>
6.2.1. Creating Initial Device Nodes,
iled to execute /init
> [ 4.595746] Kernel panic - not syncing: No init found. Try passing
> init= option to kernel.
> [4.604190] Pid: 1, comm: swapper Not tainted 2.6.30.2 #1
> [4.609649] Call Trace:
> [4.612168] [] ? printk+0xf/0x11
> [4.616417] [] panic+0x39/0
Hi all,
I am trying to build Linux from Scratch(LFS), while booting the kernel
throughing the following error.
[4.586704] Warning: unable to open an initial console.
[4.592188] Failed to execute /init
[4.595746] Kernel panic - not syncing: No init found. Try passing init=
option to
n
>>>> external USB harddisk.
>>>> My host system is SUSE 10.3 on one of my two internal harddisks.
>>>>
>>>> Booting from the USB disk fails with
>>>> "[4.410067] Kernel panic - not syncing: VFS: Unable to mount
>>>> root fs
n one of my two internal harddisks.
>>>
>>> Booting from the USB disk fails with
>>> "[4.410067] Kernel panic - not syncing: VFS: Unable to mount
>>> root fs on unknown-block (2,0)"
>>>
>>>
>>>
>> I have done some
USB disk fails with
>> "[4.410067] Kernel panic - not syncing: VFS: Unable to mount
>> root fs on unknown-block (2,0)"
>>
>>
> I have done some more research on your problem.
>
> Try this
>
> in /etc/fstab for the USB disk
>
> UUID=6342a6b5-25cf-
Op Wed, 30 Sep 2009 00:05:52 +0200 schreef Danny Engelbarts
:
> On Tuesday 29 September 2009 22:19:24 Hans Kaper wrote:
>>
>> Good suggestion. So once again I made an entry in Grub's menu.lst,
>> carefully copying the disk/by-id-field from the SUSE-entry that boots
>> allright from the usb-disk
Hans Kaper wrote:
>
> See my reply to Baho Utot. Problem solved now. Thanks for your attention,
> Mike.
I looked at every reply to Baho Utot by you, and I don't see one
which says you solved the problem. I'd be very interested to see
a repost or other report on what did the trick!
Mike
--
p="
ddisks.
>>>
>>> Booting from the USB disk fails with
>>> "[4.410067] Kernel panic - not syncing: VFS: Unable to mount
>>> root fs on unknown-block (2,0)"
>>>
>>>
>> From devices.txt
>>
>> 2 blockFloppy disks
>
USB disk fails with
>> "[4.410067] Kernel panic - not syncing: VFS: Unable to mount
>> root fs on unknown-block (2,0)"
>>
>>
> From devices.txt
>
> 2 blockFloppy disks
> 0 = /dev/fd0Controller 0, drive 0, autodetect
>
Baho Utot wrote:
[...]
> If you have success then try to use UUID in the menu.lst file like this
>
> kernel /boot/lfskernel-2.6.30.2
> root=UUID=6342a6b5-25cf-4d01-a318-68309d12ab5b rootdelay=15 ro quite
-^
Normally, I don't c
2009/9/30 Cliff McDiarmid :
> Hi
>
> When upgrading a version of LFS 6.0 with a much newer kernel(2.6.27.10)in
> order to get a new wireless driver I'm getting a kernel panic and stop.
> Would there be a problem with upgrading an LFS with glibc-2.3.4 and older
> packages
J.P.Kaper wrote:
> I am building LFS from book 6.4 on an ext3 logical partition of an
> external USB harddisk.
> My host system is SUSE 10.3 on one of my two internal harddisks.
>
> Booting from the USB disk fails with
> "[4.410067] Kernel panic - not syncing: VFS: Unabl
On Tuesday 29 September 2009 22:19:24 Hans Kaper wrote:
> Op Tue, 29 Sep 2009 20:25:05 +0200 schreef Philipp Christian Loewner
> The menu.lst entry is:
> root (hd0,7)
> kernel /boot/lfskernel-2.6.27.4
> root=/dev/disk/by-id/usb-SAMSUNG_HM160HI_16113662-0:0-part8 rootdelay=9
I was just rereadi
Baho Utot wrote:
> J.P.Kaper wrote:
>> I am building LFS from book 6.4 on an ext3 logical partition of an
>> external USB harddisk.
>> My host system is SUSE 10.3 on one of my two internal harddisks.
>>
>> Booting from the USB disk fails with
>> &quo
1 - 100 of 230 matches
Mail list logo
