Hello Jochen,
Am 2008-07-09 01:36:10, schrieb Jochen Antesberger:
The device naming was changed. Instead of /dev/hda you've got /dev/sda
now. To make it boot you'll have to adjust menu.lst to give the kernel the
right argument for the boot partition. Also you'll have to change the
entries in
Hello Anthony,
Am 2008-06-30 10:14:02, schrieb Anthony Campbell:
I just installed linux-image-2.6.25-2 from Sid. Boot fails with a
mwwage:
target filesystem doesn't have bootarg
This is followed by:
/bin/sh: can't access tty; job control turned off
I am using Etch with 2.6.18
Am Fri, 04 Jul 2008 01:00:46 +0200 schrieb Michelle Konzack:
Hello Anthony,
Am 2008-06-30 10:14:02, schrieb Anthony Campbell:
I just installed linux-image-2.6.25-2 from Sid. Boot fails with a
mwwage:
target filesystem doesn't have bootarg
This is followed by:
/bin/sh: can't access
On Wed, Jul 02, 2008 at 10:36:33AM +0100, Anthony Campbell wrote:
On 02 Jul 2008, Anthony Campbell wrote:
On 02 Jul 2008, Andrei Popescu wrote:
On Wed, Jul 02, 2008 at 08:46:53AM +0100, Anthony Campbell wrote:
Sorry, I hadn't read the e2label line properly. But I don't think it
On 01 Jul 2008, Andrei Popescu wrote:
On Tue, Jul 01, 2008 at 10:02:39AM +0100, Anthony Campbell wrote:
Well, I finally found the answer but it's very odd. I don't think it
should work but it does. I put the wrong root entry in
/boot/grub/menu.lst. All previous kernels have had /dev/hdb9
On Wed, Jul 02, 2008 at 07:51:20 +0100, Anthony Campbell ([EMAIL PROTECTED])
wrote:
I don't understand label in this context. Where is it set?
This was explained by Florian Kulzer earlier in this thread. (It was
such a good explanation I kept it for future reference!)
On Mon, Jun 30, 2008
On Tue, Jul 01, 2008 at 03:40:12PM -0500, Hugo Vanwoerkom wrote:
and did you use a vga= parm? And did that work?
$ dmesg | grep vga\=791
[0.00] Kernel command line: root=LABEL=sid ro vga=791
$ uname -a
Linux think 2.6.25-2-686 #1 SMP Thu Jun 12 16:26:30 UTC 2008 i686 GNU/Linux
On 02 Jul 2008, Bob Cox wrote:
On Wed, Jul 02, 2008 at 07:51:20 +0100, Anthony Campbell ([EMAIL PROTECTED])
wrote:
I don't understand label in this context. Where is it set?
This was explained by Florian Kulzer earlier in this thread. (It was
such a good explanation I kept it for
Anthony Campbell wrote:
On 02 Jul 2008, Bob Cox wrote:
On Wed, Jul 02, 2008 at 07:51:20 +0100, Anthony Campbell ([EMAIL PROTECTED]) wrote:
I don't understand label in this context. Where is it set?
This was explained by Florian Kulzer earlier in this thread. (It was
such a good explanation
On Wed, Jul 02, 2008 at 08:46:53AM +0100, Anthony Campbell wrote:
Sorry, I hadn't read the e2label line properly. But I don't think it
would affect the issue I encountered here, which was a change in the
actual partition referred to. The label would still be referring to
the wrong partition.
On Wed, Jul 02, 2008 at 10:37:19AM +0300, Andrei Popescu wrote:
On Tue, Jul 01, 2008 at 03:40:12PM -0500, Hugo Vanwoerkom wrote:
and did you use a vga= parm? And did that work?
$ dmesg | grep vga\=791
[0.00] Kernel command line: root=LABEL=sid ro vga=791
$ uname -a
Linux
On Wed, Jul 02, 2008 at 09:09:00AM +0100, Wackojacko wrote:
I think you should be asking yourself how the old kernel boots with hdb9.
Grub numbering system starts from 0 so hd(0,0) is hda1 and hda(1,9) is
hdb10 etc. Are you sure you don't have another debian/linux install on
hdb9 :).
On 02 Jul 2008, Andrei Popescu wrote:
On Wed, Jul 02, 2008 at 09:09:00AM +0100, Wackojacko wrote:
I think you should be asking yourself how the old kernel boots with hdb9.
Grub numbering system starts from 0 so hd(0,0) is hda1 and hda(1,9) is
hdb10 etc. Are you sure you don't have
On 02 Jul 2008, Andrei Popescu wrote:
On Wed, Jul 02, 2008 at 08:46:53AM +0100, Anthony Campbell wrote:
Sorry, I hadn't read the e2label line properly. But I don't think it
would affect the issue I encountered here, which was a change in the
actual partition referred to. The label would
On 02 Jul 2008, Anthony Campbell wrote:
On 02 Jul 2008, Andrei Popescu wrote:
On Wed, Jul 02, 2008 at 08:46:53AM +0100, Anthony Campbell wrote:
Sorry, I hadn't read the e2label line properly. But I don't think it
would affect the issue I encountered here, which was a change in the
On 30 Jun 2008, Andrei Popescu wrote:
On Mon, Jun 30, 2008 at 03:28:10PM +0100, Anthony Campbell wrote:
Uh-oh, speaking of initrds: I forgot that in my previous message; you
should probably rebuild it if you change your fstab to labels or UUIDs.
How do you do that? I changed to UUID
Anthony Campbell wrote:
On 30 Jun 2008, Andrei Popescu wrote:
On Mon, Jun 30, 2008 at 03:28:10PM +0100, Anthony Campbell wrote:
Uh-oh, speaking of initrds: I forgot that in my previous message; you
should probably rebuild it if you change your fstab to labels or UUIDs.
How do you do that? I
On 01 Jul 2008, Hugo Vanwoerkom wrote:
Anthony Campbell wrote:
On 30 Jun 2008, Andrei Popescu wrote:
On Mon, Jun 30, 2008 at 03:28:10PM +0100, Anthony Campbell wrote:
Uh-oh, speaking of initrds: I forgot that in my previous message; you
should probably rebuild it if you change your fstab to
On Tue, Jul 01, 2008 at 10:02:39AM +0100, Anthony Campbell wrote:
Well, I finally found the answer but it's very odd. I don't think it
should work but it does. I put the wrong root entry in
/boot/grub/menu.lst. All previous kernels have had /dev/hdb9 but this
kernel seems to need /dev/hdb10.
I just installed linux-image-2.6.25-2 from Sid. Boot fails with a
mwwage:
target filesystem doesn't have bootarg
This is followed by:
/bin/sh: can't access tty; job control turned off
2.6.23 still boots normally.
Google shows a number of people with similar problems, mainly on Ubuntu.
I also
On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote:
I just installed linux-image-2.6.25-2 from Sid. Boot fails with a
mwwage:
target filesystem doesn't have bootarg
This is followed by:
/bin/sh: can't access tty; job control turned off
Mine works here, but was there any
On 30 Jun 2008, Daniel Dalton wrote:
On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote:
I just installed linux-image-2.6.25-2 from Sid. Boot fails with a
mwwage:
target filesystem doesn't have bootarg
This is followed by:
/bin/sh: can't access tty; job control
On Mon, Jun 30, 2008 at 10:50:03AM +0100, Anthony Campbell wrote:
On 30 Jun 2008, Daniel Dalton wrote:
No error messages. I do get:
aetting up linux-image-2.6.25-2-amd64 (2.6.25-6) ...
Running depmod.
Finding valid ramdisk creators.
should be fine
The kernel is correct;
On 30 Jun 2008, Daniel Dalton wrote:
On Mon, Jun 30, 2008 at 10:50:03AM +0100, Anthony Campbell wrote:
On 30 Jun 2008, Daniel Dalton wrote:
No error messages. I do get:
aetting up linux-image-2.6.25-2-amd64 (2.6.25-6) ...
Running depmod.
Finding valid ramdisk creators.
On Mon, Jun 30, 2008 at 10:50:03 +0100, Anthony Campbell wrote:
On 30 Jun 2008, Daniel Dalton wrote:
On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote:
I just installed linux-image-2.6.25-2 from Sid. Boot fails with a
mwwage:
target filesystem doesn't have bootarg
On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote:
I just installed linux-image-2.6.25-2 from Sid. Boot fails with a
mwwage:
target filesystem doesn't have bootarg
This is followed by:
/bin/sh: can't access tty; job control turned off
2.6.23 still boots normally
On 30 Jun 2008, Andrei Popescu wrote:
On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote:
I just installed linux-image-2.6.25-2 from Sid. Boot fails with a
mwwage:
target filesystem doesn't have bootarg
This is followed by:
/bin/sh: can't access tty; job control
On Mon, Jun 30, 2008 at 13:45:44 +0100, Anthony Campbell wrote:
On 30 Jun 2008, Andrei Popescu wrote:
On Mon, Jun 30, 2008 at 10:14:02AM +0100, Anthony Campbell wrote:
I just installed linux-image-2.6.25-2 from Sid. Boot fails with a
mwwage:
target filesystem doesn't have bootarg
:
target filesystem doesn't have bootarg
This is followed by:
/bin/sh: can't access tty; job control turned off
2.6.23 still boots normally.
Google shows a number of people with similar problems, mainly on Ubuntu.
I also found a Debian recommendation to modify
installed linux-image-2.6.25-2 from Sid. Boot fails with a
mwwage:
target filesystem doesn't have bootarg
This is followed by:
/bin/sh: can't access tty; job control turned off
2.6.23 still boots normally.
Google shows a number of people with similar
On Mon, Jun 30, 2008 at 03:28:10PM +0100, Anthony Campbell wrote:
Uh-oh, speaking of initrds: I forgot that in my previous message; you
should probably rebuild it if you change your fstab to labels or UUIDs.
How do you do that? I changed to UUID and I got the same message with
2.6.25
Hi,
I have the same problem using Etch AMD64 (updated with all the latest
versions as of this morning, ) , booting with Grub. I have read Bob's
mail but I do not understand his solution.
Bob, or anyone else, could you explain your solution a bit more? Maybe
annotate the excerpt/file below?
Done
Done
Begin running /scripts/init-bottom
mount: mounting /root/dev/ on /dev.static/dev/ failed No such file or device
mount: mounting /sys on /root/sys failed no such file or device
Target filesystem doesnt have /sbin/init
My question is, when on reinstalling debian and installing 2.6.17
/scripts/local-bottom
Done
Done
Begin running /scripts/init-bottom
mount: mounting /root/dev/ on /dev.static/dev/ failed No such file or
device
mount: mounting /sys on /root/sys failed no such file or device
Target filesystem doesnt have /sbin/init
My question is, when on reinstalling debian
shell wrote:
Can u tell us how ur /boot/grub/menu.lst set? Most importent is boot
param, esp boot= root=. Did u regenerted initrd.img?
Hi
Thanks for replying.
I use Lilo and I did not regenerted initrd.img.
But if im not mistaken by apt-getting the linux-image package it does it doe
/scripts/local-bottom
Done
Done
Begin running /scripts/init-bottom
mount: mounting /root/dev/ on /dev.static/dev/ failed No such file or
device
mount: mounting /sys on /root/sys failed no such file or device
Target filesystem doesnt have /sbin/init
My question is, when on reinstalling debian
shell wrote:
Looks like script init in initrd.img can't mount root fs in ur system.
The init script will get root= in boot param as root. So check if u get
right param when boot up kernel.
BTW, If I'm right, local script will wait for 1800s before root device
setup, did u really wait so long?
/ failed No such file or
device
mount: mounting /sys on /root/sys failed no such file or device
Target filesystem doesnt have /sbin/init
My question is, when on reinstalling debian and installing 2.6.17 and
this happens again.
My question is, how or what do I edit to force it to work.
If anyone can
Hey all
I seem to be experiencing problems booting up (Thank goodness for Knoppix)
There are a host of errors, but the end message is:
Target filesystem doesn't have /sbin/init
/bin/sh: can't access tty; job control turned off
From googling this seems a common problem.
Would anyone know how
At 1149839151 past the epoch, Brent Clark wrote:
I seem to be experiencing problems booting up (Thank goodness for Knoppix)
There are a host of errors, but the end message is:
Target filesystem doesn't have /sbin/init
/bin/sh: can't access tty; job control turned off
If you boot
Jon Dowland wrote:
At 1149839151 past the epoch, Brent Clark wrote:
I seem to be experiencing problems booting up (Thank goodness for Knoppix)
There are a host of errors, but the end message is:
Target filesystem doesn't have /sbin/init
/bin/sh: can't access tty; job control turned off
On Fri, Jun 09, 2006 at 09:04:39AM -0400, Brent Clark wrote:
Jon Dowland wrote:
At 1149839151 past the epoch, Brent Clark wrote:
I seem to be experiencing problems booting up (Thank goodness for Knoppix)
There are a host of errors, but the end message is:
Target filesystem doesn't
Þann 2006-06-09, 13:33:12 (+0100) skrifaði Digby Tarvin:
Looks more like a problem with booting to the wrong filesystem. We
probably need to know what the first few error messages were rather
that the final result. Have you changed to boot config recently?
What is the kernel command line?
Hi
43 matches
Mail list logo
