still upload the content of the files to "www.pastebin.com"
After 'waiting for root file system' and the 5 minute wait, initrd drops
to a shell and says "/dev/dis/by-label/wd80_0jd-60.06 does not exist"
and sure enough it don't and that us the new sata conne
e). Also, include the output of "fdisk -l" that will help us to
>> get a better understanding of your current system structure :-)
>>
>>
> I can't attach files: TB hangs forever then, will register via yahoo!
You mean Thunderbird is facing any problem? :-?
Maybe now is a good time for you to put your Grub's menu config (either upload
the full file to an external server or attach the file to the message). Also,
include the output of "fdisk -l" that will help us to get a better
understanding of your current system structure :-)
I use SGD. I at
angs after initrd with "waiting for root file system"
So, you have changed not only the board but also the disk interface (it
was ide and now is sata)? Does the new kernel has "libata" module loaded?
It was a sata disk in an external enclosure connected with USB, now it
nd boots it, but
> it hangs after initrd with "waiting for root file system"
So, you have changed not only the board but also the disk interface (it
was ide and now is sata)? Does the new kernel has "libata" module loaded?
Maybe now is a good time for you to put your Grub&#x
On Sun, 21 Nov 2010 09:58:00 -0600, Hugo Vanwoerkom wrote:
> I changed motherboards and now when I boot I get "waiting for root file
> system".
(...)
Same motherboard or a different (brand/model) one?
How are the sata BIOS settings now and then (sata/ahci/raid)? Maybe you
Camaleón wrote:
On Sun, 21 Nov 2010 09:58:00 -0600, Hugo Vanwoerkom wrote:
I changed motherboards and now when I boot I get "waiting for root file
system".
(...)
Same motherboard or a different (brand/model) one?
Different motherboard/cpu/memory old:epox 8VTAI new:asus M
Hi,
I changed motherboards and now when I boot I get "waiting for root file
system".
But the disks have not changed, they are the same ones as with the old
motherboard. All partitions are labelled.
One disk had a USB connection on the old motherboard and now has a SATA
connection.
On Sat, 22 Aug 2009, Niu Kun wrote:
> Robert P. J. Day 写道:
> > On Fri, 21 Aug 2009, Robert P. J. Day wrote:
> >
> >
> > > On Sat, 22 Aug 2009, Niu Kun wrote:
> > >
> > > (with respect to getting my /dev/sda* device files built)
> > >
> > >
> > > > So here, your best choice seems to try.
> > > > he
Robert P. J. Day 写道:
On Fri, 21 Aug 2009, Robert P. J. Day wrote:
On Sat, 22 Aug 2009, Niu Kun wrote:
(with respect to getting my /dev/sda* device files built)
So here, your best choice seems to try.
here's my z60_hdparm.rules file:
i'm assuming that's a brand new rules fil
On Fri, 21 Aug 2009, Robert P. J. Day wrote:
> On Sat, 22 Aug 2009, Niu Kun wrote:
>
> (with respect to getting my /dev/sda* device files built)
>
> > So here, your best choice seems to try.
> > here's my z60_hdparm.rules file:
>
> i'm assuming that's a brand new rules file, right? not just add
On Sat, 22 Aug 2009, Niu Kun wrote:
(with respect to getting my /dev/sda* device files built)
> So here, your best choice seems to try.
> here's my z60_hdparm.rules file:
i'm assuming that's a brand new rules file, right? not just adding
to an existing rules file since i have no such file.
>
d to)
etch system to the newly-installed 2.6 kernel (either 2.6.18 or
2.6.24, either original or rebuilt), i got:
Waiting for root file system...
and it hung, with all evidence pointing to the fact that the booting
system simply couldn't see the hard drive, which it could see under
the earli
Niu Kun wrote:
>>
>>
>>
> Pretty cool.
> Really appreciate your detailed reply.
>
>
NP. hope it helps or gives you at least an idea how I'm doing this.
I've had several times related issues as I've been using raid/lvm and also
encryption, so years ago I wrote my own scripts to create initrd
Emanoil Kotsev 写道:
Niu Kun wrote:
and last but not least it's pretty tricky to boot broken initram but not
too hard if you know the steps.
Would you please say something about this?
Or any useful link that can be referenced?
regards
First of all I would try to provi
Niu Kun wrote:
>> and last but not least it's pretty tricky to boot broken initram but not
>> too hard if you know the steps.
>>
> Would you please say something about this?
> Or any useful link that can be referenced?
>> regards
First of all I would try to provide the root kernel option. If y
the newly-installed 2.6 kernel (either 2.6.18 or
2.6.24, either original or rebuilt), i got:
Waiting for root file system...
and it hung, with all evidence pointing to the fact that the booting
system simply couldn't see the hard drive, which it could see under
the earlier (devfs-enabled
Emanoil Kotsev 写道:
Robert P. J. Day wrote:
On Fri, 21 Aug 2009, Niu Kun wrote:
Have you ever run update-initramfs command manually on the
pre-compiled kernel? I remember that I fixed such a problem once.
Hope this will help. And look forward to your feedback.
nope -- as i me
Robert P. J. Day wrote:
> On Fri, 21 Aug 2009, Niu Kun wrote:
>
>> Have you ever run update-initramfs command manually on the
>> pre-compiled kernel? I remember that I fixed such a problem once.
>> Hope this will help. And look forward to your feedback.
>
> nope -- as i mentioned earlier, i'm
On Fri, 21 Aug 2009, Niu Kun wrote:
> Have you ever run update-initramfs command manually on the
> pre-compiled kernel? I remember that I fixed such a problem once.
> Hope this will help. And look forward to your feedback.
nope -- as i mentioned earlier, i'm fairly new to debian so a good
deal
On Fri, 21 Aug 2009, Robert P. J. Day wrote:
> that is the *ultimate* goal, but i'm doing this in steps. on the
> chance that it's the default 2.6.18 etch kernel, i just upgraded that
> to the 2.6.24 etchnhalf kernel. we'll see if that fixes things.
upgrading to the 2.6.24 etchnhalf kernel
n fact contain
megaraid modules.)
thoughts? the last few lines of boot diagnostics are:
Done.
Begin: Mounting root file system ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system ...
then ... hang. it's pretty clearly a problem in just
seeing/accessin
garaid controller that might be relevant? i've
> > opened up the relevant initrd image and it does in fact contain
> > megaraid modules.)
> >
> > thoughts? the last few lines of boot diagnostics are:
> >
> > Done.
> > Begin: Mounting root file system
of boot diagnostics are:
Done.
Begin: Mounting root file system ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system ...
then ... hang. it's pretty clearly a problem in just
seeing/accessing the sole hard drive in the system. i just
stics are:
Done.
Begin: Mounting root file system ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system ...
then ... hang. it's pretty clearly a problem in just
seeing/accessing the sole hard drive in the system. i just
Dear all,
I've got an old Debian sarge box.
And I want to upgrade it to the newest lenny stable version.
I've encountered the problem mentioned in the following link:
http://www200.pair.com/mecham/spam/kernel.html
I had tried to upgrade my system to etch once, but the system failed to
boot after
On Friday 2009 January 23 01:38:57 lovecreatesbeauty.g-mail.c0m wrote:
>I updated kernel on debian-40r6 (2.6.18) to 2.6.28 from kernel.org,
>and got the error* "Waiting for root file system..." when booting the
>new kernel.
Ah, I've seen that a few times, myself.
>T
On Jan 23, 4:00 pm, "lovecreatesbeauty.g-mail.c0m"
wrote:
> kernel /boot/vmlinuz-2.6.28.1 root=/dev/sda1 ro
> initrd /boot/initrd.img-2.6.28.1
>
sorry the occurences of "28.1" above should be "28" .
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subj
[I'm sorry if it's boring you]
I updated kernel on debian-40r6 (2.6.18) to 2.6.28 from kernel.org,
and got the error* "Waiting for root file system..." when booting the
new kernel.
The linux's hosted in VMware Workstation 6.0. The commands I issued
were: m
On Mon, May 05, 2008 at 10:04:12AM -0700, [EMAIL PROTECTED] wrote:
> On May 5, 5:40 am, Alex Samad <[EMAIL PROTECTED]> wrote:
> > On Sun, May 04, 2008 at 03:50:28AM -0700, [EMAIL PROTECTED] wrote:
> > > $ cat /proc/partitions
> > > major minor #blocks name
> > >8 08388608 sda
> > >
On May 4, 7:20 pm, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
[...]
The mount reports this inside that broken newly built 2.6.25
(initramfs) mount
none on /sys type sysfs (rw)
none on /proc type proc (rw)
udev on /udev type tmpfs (rw, size=10240k,mode=755)
(initramfs)
--
To UNSUBSCRIBE, ema
On May 5, 5:40 am, Alex Samad <[EMAIL PROTECTED]> wrote:
> On Sun, May 04, 2008 at 03:50:28AM -0700, [EMAIL PROTECTED] wrote:
> > $ cat /proc/partitions
> > major minor #blocks name
> >8 08388608 sda
> >8 1 273073 sda1
> >8 2 1 sda2
> >8 530603
On Sun, May 04, 2008 at 03:50:28AM -0700, [EMAIL PROTECTED] wrote:
> On May 4, 6:40 pm, Alex Samad <[EMAIL PROTECTED]> wrote:
> > On Sat, May 03, 2008 at 11:35:29PM -0700, [EMAIL PROTECTED] wrote:
> > > Under the (initramfs) prompt, the uname -r reports 2.6.25.
> > what is the output of cat /proc/
On May 4, 6:40 pm, Alex Samad <[EMAIL PROTECTED]> wrote:
> On Sat, May 03, 2008 at 11:35:29PM -0700, [EMAIL PROTECTED] wrote:
> > Under the (initramfs) prompt, the uname -r reports 2.6.25.
> what is the output of cat /proc/partitions, can you
> see /dev/sda.
> maybe the driver for you had is not i
On Sat, May 03, 2008 at 11:35:29PM -0700, [EMAIL PROTECTED] wrote:
> Hi,
[snip]
> Under the (initramfs) prompt, the uname -r reports 2.6.25.
what is the output of cat /proc/partitions, can you see /dev/sda.
maybe the driver for you had is not in .25
>
>
> Thank you for your time.
>
>
> --
Hi,
It presents the following error when I'm booting kernel 2.6.25 from
Debian40r3 with built-in kernel 2.6.18-6-486 in VMWare:
>Begin: Waiting for root file system... ...
>Done.
> Check root= bootarg cat /proc/cmdline
> or missing modules. devices: cat /proc/modules ls
[EMAIL PROTECTED] skrev:
> [This message has also been posted to linux.debian.user.]
> This is becoming a FAQ. There is a problem with udev.
> Before udev, there was a strong association between
> device names and devices. With udev, that association
> is much weaker.
> There's new randomness in
l-top ...
> ide0: I/O resource 0x1F0-0x1F7 not free.
> ide0: ports already in use, skipping probe
> ide1: I/O resource 0x170-0x177 not free.
> ide1: ports already in use, skipping probe
> Done.
> Begin: Waiting for root file system... ...
>
> And it stops right
Florian Kulzer skrev:
> On Thu, Jan 03, 2008 at 06:39:11 -0500, dave N wrote:
>
> [...]
>
>> Question: In the menu.lst grub file, how would I use
>> the label assignment in the line:
>>
>> kernel /vmlinuz-2.6.18-5-686 root=/dev/sdc2 ro
>
> I think this should be OK:
>
> kernel /vmlinuz-2.6.1
On Fri, Jan 04, 2008 at 07:23:06AM -0500, [EMAIL PROTECTED] wrote:
> I've been trying to find what the UUID of my swap file is but can't find
blkid (as it was already suggested in this thread)
from man blkid
The blkid program is the command-line interface to working with
libuuid(3) library.
- Original Message -
From: "NN_il_Confusionario" <[EMAIL PROTECTED]>
To:
Sent: Friday, January 04, 2008 1:15 AM
Subject: Re: 3rd SATA scrambles drive order? "Begin: Waiting for root file
system . . . . . ."
On Thu, Jan 03, 2008 at 11:52:29AM -0600, Jona
On Thu, Jan 03, 2008 at 11:52:29AM -0600, Jonathan Wilson wrote:
> Someone else said using IDs in fstab only works with ext2/3, obviously
> tune2fs
> does, and I use ReiserFS. What then?
from man mount:
It is possible to indicate a block special device using its volume
label or UUID (see th
On Thursday 03 January 2008 13:02, Ron Johnson wrote:
> On 01/03/08 11:52, Jonathan Wilson wrote:
> > Someone else said using IDs in fstab only works with ext2/3, obviously
> > tune2fs does, and I use ReiserFS. What then? I'm interested in thre
> > "Maybe" part, since UUIDs won't work for my situat
On Thu, Jan 03, 2008 at 06:39:11 -0500, dave N wrote:
[...]
> Question: In the menu.lst grub file, how would I use
> the label assignment in the line:
>
> kernel /vmlinuz-2.6.18-5-686 root=/dev/sdc2 ro
I think this should be OK:
kernel /vmlinuz-2.6.18-5-686 root=LABEL=your_root_label ro
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/03/08 11:52, Jonathan Wilson wrote:
> On Wednesday 02 January 2008 23:40, Paul Johnson wrote:
>> On Jan 2, 2008 9:37 PM, Jonathan Wilson <[EMAIL PROTECTED]> wrote:
>>> Is there something I can do about this? To make the new drive be sdc, I
>>> me
On Wednesday 02 January 2008 23:40, Paul Johnson wrote:
> On Jan 2, 2008 9:37 PM, Jonathan Wilson <[EMAIL PROTECTED]> wrote:
> > Is there something I can do about this? To make the new drive be sdc, I
> > mean?
>
> Why not mount by filesystem label instead of device name? The
> filesystem label do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/03/08 08:05, Stuart Gall wrote:
> In article <[EMAIL PROTECTED]>, Jonathan Wilson
> <[EMAIL PROTECTED]> wrote:
>
>> I have a computer with an Intel mainboard (I"ll look up the
>> exact model later if it matters) running Etch.
>>
>> / is an 80G
e just fine, the boot info
> shows sdc, but after all the drive and ethernet detection, I get the
> following message:
>
> Begin: Waiting for root file system . . .. . .
>
> (I'll note here that as soon as I unplug the SATA cable from the new drive
> and
> reboot ever
--- Daniel Burrows <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 02, 2008 at 10:24:07AM -0800, Andrew
> Sackville-West <[EMAIL PROTECTED]> was
> heard to say:
> > On Wed, Jan 02, 2008 at 06:24:07AM -0500, dave N
> wrote:
> > If you wait long enough (at least 30 seconds,
> maybe a couple minutes,
> > I
On Wed, Jan 02, 2008 at 10:24:07AM -0800, Andrew Sackville-West <[EMAIL
PROTECTED]> was heard to say:
> On Wed, Jan 02, 2008 at 06:24:07AM -0500, dave N wrote:
> If you wait long enough (at least 30 seconds, maybe a couple minutes,
> I can't remember) you should get dropped to a busybox shell. The
On Jan 2, 2008 9:37 PM, Jonathan Wilson <[EMAIL PROTECTED]> wrote:
> Is there something I can do about this? To make the new drive be sdc, I mean?
Why not mount by filesystem label instead of device name? The
filesystem label doesn't change just because disks decided to detect
in a different ord
. I've only got
2 SATA ports left, 3 and 4. If I plug the new drive into either one, the
machine boots, the bios recognizes the new drive just fine, the boot info
shows sdc, but after all the drive and ethernet detection, I get the
following message:
Begin: Waiting for root file system .
Andrei Popescu <[EMAIL PROTECTED]> wrote: On Wed, Jan 02, 2008 at 06:04:18AM
-0500, dave N wrote:
> I booted with Knoppix live and there is nothing in /var/log/messages, none of
> the logs appear to have changed since I last booted 2 days ago. I have not
> run fsck or anything else on this yet
photo of the screen
> messages)
>
> Begin: Mounting root file system... ...
> Begin: running /scripts/local-top ...
> ide0: I/O resource 0x1F0-0x1F7 not free.
> ide0: ports already in use, skipping probe
> ide1: I/O resource 0x170-0x177 not free.
> ide1: port
On Wed, Jan 02, 2008 at 06:04:18AM -0500, dave N wrote:
> I booted with Knoppix live and there is nothing in /var/log/messages, none
> of the logs appear to have changed since I last booted 2 days ago. I have not
> run fsck or anything else on this yet.
>
> Ideas?
This is usually a
resource 0x1F0-0x1F7 not free.
ide0: ports already in use, skipping probe
ide1: I/O resource 0x170-0x177 not free.
ide1: ports already in use, skipping probe
Done.
Begin: Waiting for root file system... ...
And it stops right there. 0's above may be 8's, can't tell f
de0: ports already in use, skipping probe
ide1: I/O resource 0x170-0x177 not free.
ide1: ports already in use, skipping probe
Done.
Begin: Waiting for root file system... ...
And it stops right there. 0's above may be 8's, can't tell from the picture.
I booted with
e have had this
same hang, and most of them got there by some other path than I did.
So I think it may be a more general problem than that.
Yes, and I is one of them who just experienced it. Just installed Etch but on
first boot after installation I got the "Waiting for root file system...
that.
Yes, and I is one of them who just experienced it. Just installed Etch but on
first boot after installation I got the "Waiting for root file system..."
My (old) mainbord (BE6) have two IDE hardisk controlles onboard. One generic
IDE controller (piix) and a hpt366 controller.
It
On Mon, Nov 05, 2007 at 09:14:18AM -0500, Douglas A. Tutty wrote:
> On Sat, Nov 03, 2007 at 09:14:44PM -0700, Andrew Sackville-West wrote:
>
> > it turns out you can do a reasonable amount of stuff in that busybox
> > shell and if the system is close to booting, you can get it to
> > go. What I w
On Sat, Nov 03, 2007 at 09:14:44PM -0700, Andrew Sackville-West wrote:
> it turns out you can do a reasonable amount of stuff in that busybox
> shell and if the system is close to booting, you can get it to
> go. What I was missing, and desperately wanted, was some kind of text
> editor. I ended
On Sat, Nov 03, 2007 at 02:38:36AM +, Cameron L. Spitzer wrote:
> In article <[EMAIL PROTECTED]>, Andrew Sackville-West wrote:
>
> > I've had to learn my
> > way around that having just reconfigured my laptop. The critical item
> > is the contents of $ROOT. The value of $ROOT gets set by the k
evice names changed and the
Lenny kernel wouldn't boot, but the Etch kernel still worked. ]
>> > If I understand correctly, you upgraded the kernel and the new kernel
>> > would not boot. Then it would be a kernel bug.
[cls:]
>> My friend in Los Angeles tried to instal
> So I think it may be a more general problem than that.
>
> My friend in Los Angeles tried to install Ubuntu for a friend,
> and got stuck "waiting for root file system" in the middle of
> a fresh install from CD. When he booted his trusty Knoppix CD
> it revealed the r
ent some time
googling for the error messages. A lot of people have had this
same hang, and most of them got there by some other path than I did.
So I think it may be a more general problem than that.
My friend in Los Angeles tried to install Ubuntu for a friend,
and got stuck "waiting for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cameron L. Spitzer wrote:
[snip upgrade instructions]
Thanks for posting your experience! I am sure it will be useful to others.
> You could have a debate about whether this is an installer
> bug, a kernel package bug, a udev bug, or operator error.
, the October 29 2007 weekly CD.
This leaves a GRUB menu with an Etch kernel and a Lenny kernel.
The Etch kernel boots just fine. The Lenny kernel hangs at
"Waiting for root file system..."
and eventually you get that (initramfs) prompt from the Busybox
shell, which means it never fo
PC and not
> inside the VM. The boot process starts normally, but then hangs. The
> last lines that appear in the boot are:
>
> Begin: Mounting root file system... ...
> Begin: Running /scripts/local-top ...
> Done.
> Begin: Waiting for root file system... ...
>
> And
Cassiano Bertol Leal wrote:
> Begin: Mounting root file system... ...
> Begin: Running /scripts/local-top ...
> Done.
> Begin: Waiting for root file system... ...
> And from there, I can only Control-Alt-Delete or do a cold reset.
> The machine is a Dell Optiplex GX280 P4-HT
. The
last lines that appear in the boot are:
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...
And from there, I can only Control-Alt-Delete or do a cold reset.
The machine is a Dell Optiplex GX280 P4-HT with 2GB RAM
70 matches
Mail list logo
