On 11/08/2016 04:16 PM, Michael Milliman wrote:
On Tue, 2016-11-08 at 15:56 -0500, Tony Baldwin wrote:
On 11/08/2016 02:57 PM, Anthony Baldwin wrote:
I've been hvaving trouble for over a month, I can't boot the same system
twice.
I replaced a hardrive because it was suggested the problem
On 11/08/2016 02:57 PM, Anthony Baldwin wrote:
I've been hvaving trouble for over a month, I can't boot the same system
twice.
I replaced a hardrive because it was suggested the problem was a hard drive,
but now, with a brand spanking new hard drive, any time Ihave to halt
the system and boot
Hi list,
on my latptop (lightdm + XFCE) I can't reboot nor shutdown properly;
each command ends with a black screen with a blinking cursor at top
left and that's all. I waited several times more than 5 minutes,
hoping some timeout was there, but nope; stopping with the power
button isn't very
On 02/09/14 10:49 PM, B wrote:
Hi list,
on my latptop (lightdm + XFCE) I can't reboot nor shutdown properly;
each command ends with a black screen with a blinking cursor at top
left and that's all. I waited several times more than 5 minutes,
hoping some timeout was there, but nope; stopping
On Tue, 02 Sep 2014 23:26:32 -0400
Gary Dale garyd...@torfree.net wrote:
Can't help you with the error message but to shutdown, have you tried
the SysRq key? See http://en.wikipedia.org/wiki/Magic_SysRq_key for
details.
This often gives you all kinds of ways of getting around an otherwise
On Wed, Jul 31, 2013 at 10:28 PM, Russell Warren r...@perspexis.com wrote:
Ow. Uninstalling the running init is likely to cause problems. If
possible, install upstart and sysvinit alongside each other... No, wait.
upstart conflicts with sysvinit.
I would suggest that, unless you meant to
I've recently done a small dist-upgrade on 7.1/wheezy that failed (
https://dpaste.de/iVgQo/raw/) and I can now no longer do a reboot or halt.
When I try, I get this error:
shutdown: timeout opening/writing control channel /run/initctl
init: timeout opening/writing control channel
On Wed, Jul 31, 2013 at 11:14:58AM -0400, Russell Warren wrote:
I've recently done a small dist-upgrade on 7.1/wheezy that failed
([1]https://dpaste.de/iVgQo/raw/) and I can now no longer do a reboot or
halt. When I try, I get this error:
shutdown: timeout opening/writing
Ow. Uninstalling the running init is likely to cause problems. If
possible, install upstart and sysvinit alongside each other... No, wait.
upstart conflicts with sysvinit.
I would suggest that, unless you meant to switch inits, you re-install
upstart (which will remove sysvinit again).
If
On 11-01-31 8:47 PM, Andrew Reid wrote:
The easy way out is to boot from a rescue disk, fix the mdadm.conf
file, rebuild the initramfs, and reboot.
The Real Sysadmin way is to start the array by hand from inside
the initramfs. You want mdadm -A /dev/md0 (or possibly
mdadm -A
In 4d49816b.1040...@alcor.concordia.ca, David Gaudine wrote:
I have one more question, just out of curiousity so bottom priority.
Why does this work? mdadm.conf is in the initramfs which is in /boot
which is on /dev/md0, but /dev/md0 doesn't exist until the arrays are
assembled, which requires
Hello,
dav...@alcor.concordia.ca a écrit :
My system went down because of a power failure, and now it won't start. I
use RAID 1, and I don't know if that's related to the problem. The screen
shows the following.
Loading, please wait...
Gave up waiting for rood device. Common problems:
On 11-01-31 8:47 PM, Andrew Reid wrote:
On Monday 31 January 2011 10:51:04 dav...@alcor.concordia.ca wrote:
I posted in a panic and left out a lot of details. I'm using Squeeze, and
set up the system about a month ago, so there have been some upgrades. I
wonder if maybe the kernel or Grub was
On Tue, Feb 1, 2011 at 10:38 AM, David Gaudine
dav...@alcor.concordia.ca wrote:
On 11-01-31 8:47 PM, Andrew Reid wrote:
On Monday 31 January 2011 10:51:04 dav...@alcor.concordia.ca wrote:
I posted in a panic and left out a lot of details. I'm using Squeeze,
and
set up the system about a
show md_mod.
David
Original Message
Subject: Can't reboot after power failure (RAID problem?)
From:dav...@alcor.concordia.ca
Date:Mon, January 31, 2011 10:18 am
To: debian-user@lists.debian.org
My system went down because of a power failure, and now it won't start. I
use RAID 1, and I don't know if that's related to the problem. The screen
shows the following.
Loading, please wait...
Gave up waiting for rood device. Common problems:
- Boot args (cat /proc/cmdline)
- Check
On Monday 31 January 2011 10:51:04 dav...@alcor.concordia.ca wrote:
I posted in a panic and left out a lot of details. I'm using Squeeze, and
set up the system about a month ago, so there have been some upgrades. I
wonder if maybe the kernel or Grub was upgraded and I neglected to install
I'm hoping someone can help me with this urgent problem. I just applied
the updates that became available in the last couple days to my Debian
etch host running on a Dell PowerEdge 2450 server. This included an
update to the kernel, so I rebooted the host. The host failed to
restart. The first
On Jul 29, 10:50 am, Zembower, Kevin [EMAIL PROTECTED] wrote:
I'm hoping someone can help me with this urgent problem. I just applied
the updates that became available in the last couple days to my Debian
etch host running on a Dell PowerEdge 2450 server. This included an
update to the kernel,
now, but rather a hardware problem.
-Kevin
-Original Message-
From: Zembower, Kevin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 29, 2008 10:43 AM
To: debian-user@lists.debian.org
Subject: Can't reboot after update
I'm hoping someone can help me with this urgent problem. I just applied
On Thu, Apr 19, 2007 at 03:42:50PM +0700, Sarawuth Buaruang wrote:
I have mainboard model Asus P4S800D-X and I used Debian 3.1 r3
kernel 2.6.8-3-686. When I reboot system by init 6 or reboot my system
is hang(I can't control by keyboard) and show
...
system when I use Ubuntu. But I can't reboot system
by Redhat,Fedora and Debian (When I use mainboard Asus P4S800D-X).
Help me Pleases!!! Thank.
_
Express yourself instantly with MSN Messenger! Download today it's FREE
Sarawuth Buaruang wrote:
I can reboot system when I use Ubuntu. But I can't reboot
system by Redhat,Fedora and Debian (When I use mainboard Asus P4S800D-X).
Which kernel are you using for ubuntu? If it is more recent than the
debian one this problem might be solved by upgrading
I redirected back to the list as this might be interesting for others ... and I
don't know if I can help :(
On Fri, 3 Feb 2006 16:51:35 +0800
linux china [EMAIL PROTECTED] wrote:
I use 'reboot' to reboot my machine, the output message of the command is
normal, no error message. what else info
Hi,
I can poweroff My 3.1 system by modprobe apm, and add a line apm into /etc/modules, but I still can't reboot my Debian, any comments?
On Wed, 1 Feb 2006 22:34:00 +0800
linux china [EMAIL PROTECTED] wrote:
Hi,
I can poweroff My 3.1 system by modprobe apm, and add a line apm into
/etc/modules, but I still can't reboot my Debian, any comments?
What is the command you are using, what is the resulting error message, if any
Apologies for the alarm. I've managed to fix it - at least until the
next reboot (sickly grin).
Cheers,
Adam Bogacki,
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Apparently, _Adam Bogacki_, on 25/10/04 06:31,typed:
Apologies for the alarm. I've managed to fix it - at least until the
next reboot (sickly grin).
Cheers,
Adam Bogacki,
[EMAIL PROTECTED]
I think you should also mention the steps you took to fix it so that
others who hit this post in their
Apparently, _Adam Bogacki_, on 25/10/04 06:31,typed:
Apologies for the alarm. I've managed to fix it - at least until the
next reboot (sickly grin).
Cheers,
Adam Bogacki,
[EMAIL PROTECTED]
I think you should also mention the steps you took to fix it so that
others who hit this post in their
H. S. wrote:
Apparently, _Adam Bogacki_, on 25/10/04 06:31,typed:
Apologies for the alarm. I've managed to fix it - at least until the
next reboot (sickly grin).
Cheers,
Adam Bogacki,
[EMAIL PROTECTED]
I think you should also mention the steps you took to fix it so that
others who hit this
Todd Myhre wrote:
I've set up gdm on a new laptop but the System menu does not
seem to work correctly. When I try to halt the system, it
simply reloads gdm and the following error messages appear
in my syslog:
gdm_slave_xioerror_handler: Fatal X error - Restarting :0
gdm_child_action:
Oki wrote:
I've set up gdm on a new laptop but the System menu does not
seem to work correctly. When I try to halt the system, it
simply reloads gdm and the following error messages appear
in my syslog:
gdm_slave_xioerror_handler: Fatal X error - Restarting :0
gdm_child_action:
I've set up gdm on a new laptop but the System menu does not
seem to work correctly. When I try to halt the system, it
simply reloads gdm and the following error messages appear
in my syslog:
gdm_slave_xioerror_handler: Fatal X error - Restarting :0
gdm_child_action: Reboot or Halt request
33 matches
Mail list logo
