Michael Shell wrote:
On Wed, 13 Mar 2013 22:34:59 -0400
Michael Shell li...@michaelshell.org 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
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
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
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
mentioned the
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 to
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-support
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
block(0,0
, 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) mean
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) mean?
The problem appears
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 UUIDs so
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. Root is on sda3
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 partitions
then it lists the sda
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)
please append a correct root= boot option here are availble partitions
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 device (null) or unknown-block(2,0)
please append a correct root
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
VFS unable to mount root fs via NFS trying floppy
VFS cannot open root device (null) or unknown
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,
sda1 will be
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
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 option; here are the available
partitions:
16004194302 hdc driver: ide-cdrom
- Original Message -
From: Danny Vukobratovich dvukobratov...@marianinc.com
To: LFS Support List lfs-support@linuxfromscratch.org
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
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 option; here are the available
partitions:
16004194302 hdc driver
- Original Message -
From: Bruce Dubbs bruce.du...@gmail.com
To: LFS Support List lfs-support@linuxfromscratch.org
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
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 only
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
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 VMworkstation 8
From: Michael lis...@freigeister.org
To: LFS Support List lfs-support@linuxfromscratch.org
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
; 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] [c145f114] ? printk+0xf/0x11
[ 3.586243] [c145f00a
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.
[ 3.585754] Pid: 1, comm: swapper Not tainted 2.6.37 #1
:
[ 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] [c145f114] ? printk+0xf/0x11
[ 3.586243] [c145f00a] panic+0x50/0x14b
[ 3.586404
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.txt
Andy
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http
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 result of a missing driver in the file system
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. During the build,
when I
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 think my problem is that /dev isn't being populated
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 kernel panic) that they'd Oh, silly
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. The next step is
mount| grep hda
Also check your kernel configuration:
Symbol: PATA_VIA
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 proper device ... all lfs files in place.
Following this failure to re
: 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 proper device ... all lfs files
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.
Doh! I forgot that I changed the root
On Fri, Jun 3, 2011 at 10:34 AM, bsquared bwcod...@gmail.com 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'. I modified the grub.cfg file
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://linuxfromscratch.org
On Wed, Jun 1, 2011 at 8:15 PM, bsquared bwcod...@gmail.com 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
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 details are:
*
Processor: Intel core
The Cynical cyni...@penguinness.org
To: LFS Support List lfs-support@linuxfromscratch.org
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 boot in to my LFS system
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:0:0:
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
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.6.32.8-lfs-6.6 root=/dev/sda2 ro
*snip*
My first thought
/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= boot option; here are the available
partitions:
0b00
Are these search lines needed? I don't put them in my grub.cfg
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= boot option; here are the available
partitions
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 LFS, but I
agree that it would be clearer if they were removed. Otherwise, the
entry looks correct.
Kernel panic - not syncing: VFS; Unable to mount root fs
this comment. Be careful not to
change
# the 'exec 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
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
file system (according to how you did your high level format)
device class
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 unknown-block(2,0)
Please append
On Sat, Apr 3, 2010 at 3:38 PM, Kaleb Hosie kho...@spectraaluminum.com 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 what
On Sat, Apr 3, 2010 at 3:38 PM, Kaleb Hosie kho...@spectraaluminum.com 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 what
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:
On Tue, Mar 23, 2010 at 3:55 AM, Yaacov-Yoseph Weiss
yywe...@cs.huji.ac.il 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
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
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 the
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
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 try
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 panic saying
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
- Original Message
From: Bruce Dubbs bruce.du...@gmail.com
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:
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
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 it
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
--
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 Virtual
On 08/02/10 15:44, Aditya Bankar wrote:
- Original Message
From: Bruce Dubbsbruce.du...@gmail.com
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
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 response,
- Original Message
From: Andrew Benton b3n...@gmail.com
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
From: Bruce Dubbs
Go
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 options
Kernel Panic
- Original Message
From: Aditya Bankar adityaban...@yahoo.co.in
To: lfs support lfs-support@linuxfromscratch.org
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
On 07/02/10 13:39, Aditya Bankar wrote:
- Original Message
From: Aditya Bankaradityaban...@yahoo.co.in
To: lfs supportlfs-support@linuxfromscratch.org
Sent: Sun, 7 February, 2010 5:18:26 PM
Subject: Kernel Panic - not syncing: VFS:
Hi,
I am getting this problem while
- Original Message
From: Andrew Benton b3n...@gmail.com
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:
- Original Message
From: Aditya Bankar
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 entries in the host
system's
menu.lst. Since my LFS partition is /dev/sda6 as seen on host system I have
added the following to menu.lst
title LFS6.5
open root device 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 entries in the host
system's
menu.lst. Since my LFS
From: Aditya Bankar adityaban...@yahoo.co.in
To: LFS Support List lfs-support@linuxfromscratch.org
Sent: Sun, 7 February, 2010 10:32:53 PM
Subject: Re: Kernel Panic - not syncing: VFS:
- Original Message
From: Andrew Benton b3n...@gmail.com
To: lfs
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
[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] [c164073c] ? printk+0xf/0x11
[4.616417] [c1640695] panic+0x39/0xd1
[4.620493] [c10012e5
On 1/24/10, Rambabu Dasari babu4...@gmail.com 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
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
[4.595746] Kernel panic
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 panic - not syncing: No init found
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 on unknown-block (2,0)
I have done some more research on your problem.
Try this
in /etc/fstab for the USB disk
UUID
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
1 = /dev/fd1Controller 0, drive 1, autodetect
2 = /dev/fd2
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
0 = /dev/fd0Controller 0, drive 0, autodetect
1 = /dev/fd1Controller 0, drive 1, autodetect
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
--
Op Wed, 30 Sep 2009 00:05:52 +0200 schreef Danny Engelbarts
d.engelba...@gmail.com:
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
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-4d01-a318-68309d12ab5b / ext3 defaults 1 1
change the blkid to the correct
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 more research on your problem.
Try this
in /etc/fstab for the USB disk
UUID=6342a6b5-25cf-4d01-a318-68309d12ab5b / ext3 defaults 1 1
Op Tue, 29 Sep 2009 04:32:17 +0200 schreef Spahn, Daniel
dsp...@cuh2a.com:
Booting from the USB disk fails with
[4.410067] Kernel panic - not syncing: VFS: Unable to mount
root fs on unknown-block (2,0)
Have you tried changing the partition number up or down by one?
Yes, I have
Op Sat, 26 Sep 2009 21:29:08 +0200 schreef Baho Utot
baho-u...@columbus.rr.com:
Ken Moffat wrote:
2009/9/26 J.P.Kaper spaky...@xs4all.nl:
Maybe somebody else can find the right suggestion to let me solve my
problem.
Hans Kaper.
One of the problems with usb drives is that they can
Hi,
have you double-checked that the root= kernel parameter is set
correctly in your menu.lst? So far, I only read about your fstab
in this thread. Check again what suggestions the kernel makes for
valid partition device nodes... Just in case you haven't tried
yet.
- Philipp
--
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: Unable to mount
root fs on unknown
has anybody solved this problem, i have encountered it yet
在2009-09-27，Baho Utot baho-u...@columbus.rr.com 写道：
Ken Moffat wrote:
2009/9/26 J.P.Kaper spaky...@xs4all.nl:
Maybe somebody else can find the right suggestion to let me solve my
problem.
Hans Kaper.
One of the
2009/9/26 J.P.Kaper spaky...@xs4all.nl:
Maybe somebody else can find the right suggestion to let me solve my
problem.
Hans Kaper.
One of the problems with usb drives is that they can
take a long time to appear. I've never tried to boot
from usb, but ISTR that there is a command-line
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: Unable to mount
root fs on unknown
Ken Moffat wrote:
2009/9/26 J.P.Kaper spaky...@xs4all.nl:
Maybe somebody else can find the right suggestion to let me solve my
problem.
Hans Kaper.
One of the problems with usb drives is that they can
take a long time to appear. I've never tried to boot
from usb, but ISTR that
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: Unable to mount
root fs on unknown-block (2,0
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: Unable to mount
root fs on unknown
You write that the kernel has successfully mounted the root file
system. Are you sure? This kind of crash is often due to a failure
to mount /. How is the CF card connected physically?
You also write you have no initramfs. I suggest you create one --
then if initialization cannot mount root
1 - 100 of 178 matches
Mail list logo
