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 was
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 i
On Tue, 02 Sep 2014 23:26:32 -0400
Gary Dale 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
> frozen system
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
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 requir
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 -u") to s
On Tue, Feb 1, 2011 at 10:38 AM, David Gaudine
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 month ago, so
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
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 proble
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 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
Grub again, but I would expect it to automatically be reinstalled on at
lea
This is so strange. Here's the email I started to write:
==
Thanks to all the folks who replied, both on and off the list. I'm
making some progress, but I'm still not out of the woods and still need
assistance.
This system uses LILO 22.6.1. I wasn't able to use Tab to bring
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
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 post
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 sear
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 sear
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]
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
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: Reboo
19 matches
Mail list logo