me point there's a message, something like 'mounting /dev/hda1
> > read-only' (don't know exactly since it isn't logged anywhere)
> >
> > The next message is where it ends: 'unable to open an initial
> > console'.
>
> The problem se
by Mitchell Laks (thanks for that!).
> > >
> > > Then I switched the machine off, removed the old harddisk, switched
> > > the new harddisk from slave to master and turned the machine on.
> > >
> > > Grub executed OK, there's a lot of info scrolling ove
lot of info scrolling over the screen. At
> > some point there's a message, something like 'mounting /dev/hda1
> > read-only' (don't know exactly since it isn't logged anywhere)
> >
> > The next message is where it ends: 'unable to open an initi
s where it ends: 'unable to open an initial
console'.
The problem seems to be that some console device is required before
any udev devices are created.
I've solved this by copying all the devices from a live filesystem
onto /dev of the cloned drive, but you probably only need xconsole
o
slave to master and turned the machine on.
>
> Grub executed OK, there's a lot of info scrolling over the screen. At
> some point there's a message, something like 'mounting /dev/hda1
> read-only' (don't know exactly since it isn't logged anywhere)
>
>
like 'mounting /dev/hda1
read-only' (don't know exactly since it isn't logged anywhere)
The next message is where it ends: 'unable to open an initial
console'.
I'm sure I followed the Howto's to the letter and Google doesn't give
me any answers to this
Quoting Marty <[EMAIL PROTECTED]>:
> If /dev is empty in a cloned root filesystem (since udev is its
> own filesystem and /dev files are not copied) it does not boot up
> but hangs with an error message similar to "can't open initial
> console." I've not
If /dev is empty in a cloned root filesystem (since udev is its
own filesystem and /dev files are not copied) it does not boot up
but hangs with an error message similar to "can't open initial
console." I've not narrowed down which console device the kernel
is looking for, no
In article <[EMAIL PROTECTED]>,
pplaw <[EMAIL PROTECTED]> wrote:
>after getting a kernel panic, as a result of
>trying to boot a custom kernel (2.2.18), i managed
>to fsck dev/hda1 (using a rescue floppy). when i try
>to boot via lilo, i can't open an initial conso
debs,
after getting a kernel panic, as a result of
trying to boot a custom kernel (2.2.18), i managed
to fsck dev/hda1 (using a rescue floppy). when i try
to boot via lilo, i can't open an initial console:
fs: mounted root (ext2 filesystem) readonly.
unable to open an initial co
hello!
i have a really critical problem.
i tried hdparm to enable dma access. but after some tests the system hung
and i had to shutdown manually.
now i can't boot debian anymore.
the error messsage is:
Warning: unable to open an initial console
Kernel panic: No init found. Try passing
point after the kernel memory is freed and
after teh disks are check it says
Warning Unable to open Initial console
then it reboots ..
what means with this and what can i do to fix it..
i cant insert the rescue disk and typ
rescue root=/dev/hda1
cause the same thing will happend
but i can startup
Whenever I run install.bat to load linux, I eventually run into a message
unable to open an initial console
this message occurs immediately after the messages
unable to load NLS charset . . .
VFS: Mounted root (msdos filesystem) readonly
I am installing from a dos
ssage "unable to open an initial console". I noticed that Red Hat's
CD has a /dev/console and Debian's CD doesn't, which is probably why I
was able to install Red Hat in the first place.
I have tried root=/dev/fd0 , root=/dev/scd0.
Is there a way to install Debian starti
Unable to boot. Upon boot-up machine stops and hangs and displays the
subject error message.
Have been running all unstable for years with no problems. Am currently
running all potato. Problem may have occured upon nightly ftp update of
potato.
Don't know how to recover from this problem. Is
Holy smoke! I didn't know one could get that much into a Subject
header!!!
--
__ _
Mark Wagnon Debian GNU/ -o) / / (_)__ __ __
Chula Vista, CA /\\/ /__/ / _ \/ // /\ \/ /
[EMAIL PROTECTED] _\_v/_/_//_/\_
>hello there, (please forgive my poor English)
Hi Damiaan
No need, Your English is very good. I don't know anything about your
cdrom, but I do have allot Of experience with bad disks. Try A
different disk and redownload resc1440.bin and rawrite it again it may
have gotten corrupted ( con
I am trying to install Debian 2.1 and I can't get the initial
console to load. I have an old Packard Bell 486sx 16 with 8 MB
of ram and a 120MB hard drive. Obviously it has no SCSI, PCI,
or anything else that's up to date. The machine isn't really
good for anything but familiariz
Hi,
I´m getting this message when i was booting to install.
It occurs booting with the official cdrom or from floopy disks.
The message is:
Unable to open inital console.
Can somebody help me?
Thanks,
ATTENTION: Here are some of my opinions, just it.
I'm not speaking for my Com
I do think that this problem is related to /dev/console file. This file should
exists and should be pointing to /dev/tty0 (usually.)
Bye,
Giuseppe
Andre Luis Cardoso wrote:
>
> Hi,
>
> I´m getting this message when i was booting to install.
> It occurs booting with the official cdrom or from fl
Hi,
I´m getting this message when i was booting to install.
It occurs booting with the official cdrom or from floopy disks.
The message is:
Unable to open inital console.
Can somebody help me?
Thanks,
ATTENTION: Here are some of my opinions, just it.
I'm not speaking for my Com
Martin Waller wrote:
>
> I've put together an old 486 from bits, and am trying to install Debian
> (hamm) on it.
>
> If I use the boot diskette (doesn't support CD bootup), the bootup stops
> with 'Can't open initial console', and if I try the rescue
I've put together an old 486 from bits, and am trying to install Debian
(hamm) on it.
If I use the boot diskette (doesn't support CD bootup), the bootup stops
with 'Can't open initial console', and if I try the rescue disk, it just
says:
Kernel panic: Free list corrupt
Jens Ritter wrote:
>
> Daniel Mashao <[EMAIL PROTECTED]> writes:
>
> > machine. Actually it is from a dual pentium to a single pentium machine. I
> > have been experiencing a lot of crashes with the dual pentium machine so I
> > now decided it is time I moved to a single pentium machine. The
On: Mon, 9 Nov 1998 16:14:06 +0200 (SAT) Daniel Mashao writes:
>
> I am trying to transplant a Debian Linux disk to another formerly
> Debian machine. Actually it is from a dual pentium to a single
> pentium machine. I have been experiencing a lot of crashes with the
> dual pentium machine so I no
Daniel Mashao <[EMAIL PROTECTED]> writes:
> I am trying to transplant a Debian Linux disk to another formerly Debian
> machine. Actually it is from a dual pentium to a single pentium machine. I
> have been experiencing a lot of crashes with the dual pentium machine so I
> now decided it is time I
I am trying to transplant a Debian Linux disk to another formerly Debian
machine. Actually it is from a dual pentium to a single pentium machine. I
have been experiencing a lot of crashes with the dual pentium machine so I
now decided it is time I moved to a single pentium machine. The kernel
loads
There's no need to do that. Just cd /dev (or wherever your dev dir is),
and type "./MAKEDEV *". That should recreate almost all the devices, with the
correct permissions, afaik.
> Perhaps I should just cd /mnt/dev; rm * and then remake the device
> files. I've read about a command to make
On Mon, Aug 03, 1998 at 05:58:46AM -0700, Taren wrote:
> > > VHS: Mounted root (ext2 filesystem) readonly.
> > > thenUnable to open an initial console
> > >
> >
> > Looks like /dev/tty0 isn't there.
> >
> > Are use s
special files, but any sockets
in /dev or /var were turned into pipes. At least, the first mode bit
changed from an 's' to a 'p'. I don't think the device numbers changed, but
the mode bit change was enough to scare me. I used cpio in /dev and /var
and it seemed to pre
ions are named and
> >
> > VHS: Mounted root (ext2 filesystem) readonly.
> > thenUnable to open an initial console
> >
>
> Looks like /dev/tty0 isn't there.
>
Had a look. :( It's there. Symlink to console. Console is there,
too. Perm
In article <[EMAIL PROTECTED]>,
Dirk Bonne <[EMAIL PROTECTED]> wrote:
>They should with tar. e.g.:
>
> tar cf - . | (cd somewhere; tar xvf -)
>
>Of course, you must set umask to 000 beforehand
Or use the "p" option with tar when you unpack i.e. tar xpvf -
Mike.
--
Miquel van Smoorenburg | Our
Taren wrote:
>
> > > VHS: Mounted root (ext2 filesystem) readonly.
> > > then Unable to open an initial console
> > >
> >
> > Looks like /dev/tty0 isn't there.
> >
> > Are use sure you did copy the devices correctly (cp does no
> > VHS: Mounted root (ext2 filesystem) readonly.
> > thenUnable to open an initial console
> >
>
> Looks like /dev/tty0 isn't there.
>
> Are use sure you did copy the devices correctly (cp does not copy
> devices correctly, use tar or cpio).
&
I only get through the first little
> bit of the boot sequence (I can write out the whole thing , one screen full,
> if anyone wants it) up to where all the partitions are named and
>
> VHS: Mounted root (ext2 filesystem) readonly.
> thenUnable to open an initial cons
I can write out the whole thing , one screen full,
if anyone wants it) up to where all the partitions are named and
VHS: Mounted root (ext2 filesystem) readonly.
thenUnable to open an initial console
Does anyone know what I need to do to fix this ?
Thanks,
G
Check that /dev/console is linked to appropriate /dev/tty? file. It's linked
to tty0
in my system. Also remember correct permissions!
--j
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hello,
I somehow messed up one of my long-stable hamm systems during an upgrade.
On boot-up, even a single-user boot, the boot process fails with the
message in the subject line above.
What may have caused this is that I ran out of space on my /usr partition
during the upgrade. Things have been
> itself. I then use the Rescue Disk and boot using the option
>
> rescue root=/dev/hda5
>
> (I had the / partition on an extended logical partition named hda5.)
> and the message "unable to open an initial console" appeared. I then
> tried the default boot option in
le to open an initial console" appeared. I then
tried the default boot option in the Rescus Disk and I was able to
mount my previous partitions on the directory /target. However, I cannot
do anything else. (I would like, at least, to save my data files!) There
does not seem to be a hardwa
On Sun, 7 Sep 1997, Jess Stryker wrote:
: About every 1 out of 3 times my computer boots I get
: a message that says something to the effect of:
: "Unable to open an initial console"
: and the boot process stops. I'm not familiar enough
: with the boot process to know what m
> About every 1 out of 3 times my computer boots I get
> a message that says something to the effect of:
> "Unable to open an initial console"
> and the boot process stops. I'm not familiar enough
> with the boot process to know what might be causing
It's
About every 1 out of 3 times my computer boots I get
a message that says something to the effect of:
"Unable to open an initial console"
and the boot process stops. I'm not familiar enough
with the boot process to know what might be causing
this and was unable to find anything
43 matches
Mail list logo
