> On Oct 30, 2016, at 7:31 PM, Paul R. Ganci wrote:
>
> Now the question is how did this happen.
I've seen something similar when installing a kernel if /etc/fstab didn't match
df. Mkinitrd bombs out leaving the system unbootable. The rescue .iso/mkinitrd
path you followed was the fastest way
On 10/30/2016 03:05 PM, Eero Volotinen wrote:
so, Just chroot to mountpoint:
http://www.cyberciti.biz/faq/unix-linux-chroot-command-examples-usage-syntax/
chroot /mounted/path /bin/bash and then .. mkinitrd (see man page for
documentation)
Thank you for the hint. The way I fixed this problem
so, Just chroot to mountpoint:
http://www.cyberciti.biz/faq/unix-linux-chroot-command-examples-usage-syntax/
chroot /mounted/path /bin/bash and then .. mkinitrd (see man page for
documentation)
2016-10-30 22:57 GMT+02:00 Eero Volotinen :
> A bit hard to say. Try chrooting into environment and r
A bit hard to say. Try chrooting into environment and rebuilding initrd?
--
Eero
2016-10-30 22:53 GMT+02:00 Paul R. Ganci :
> On 10/30/2016 12:26 PM, Paul R. Ganci wrote:
>
>> I am thinking of putting the CentOS iso out and then booting the VM
>> into it just to poke around the file system. Othe
On 10/30/2016 12:26 PM, Paul R. Ganci wrote:
I am thinking of putting the CentOS iso out and then booting the
VM into it just to poke around the file system. Otherwise my other
option is to just clone a twin VM on another server and then just
change the networking IPs/hostname. Anybody have any
You could mount image ja rebuild initrd.
Eero
2016-10-30 20:26 GMT+02:00 Paul R. Ganci :
> On 10/30/2016 07:33 AM, FrancisM wrote:
>
>> Any error in your host logs?
>>
> Nothing obvious. I checked /var/log/messages, /var/log/libvirt/qemu,
> /var/log/libvirt/lxc & /var/log/qemu-ga. The /var/log/l
On 10/30/2016 07:33 AM, FrancisM wrote:
Any error in your host logs?
Nothing obvious. I checked /var/log/messages, /var/log/libvirt/qemu,
/var/log/libvirt/lxc & /var/log/qemu-ga. The /var/log/libvirt/lxc &
/var/log/qemu-ga were empty. The /var/log/libvirt/qemu directory had a
log file of inter
On 10/30/2016 06:57 AM, Steven Tardy wrote:
On Oct 30, 2016, at 3:27 AM, Paul R. Ganci wrote:
grub> set root=(hd0,msdos2)
grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 root=(hd0,msdos2)/
grub> initrd initrd-plymouth.img
grub> boot
Try the initrd matching the kernel
That is what I tho
Any error in your host logs?
On Sunday, 30 October 2016, Steven Tardy wrote:
>
> > On Oct 30, 2016, at 3:27 AM, Paul R. Ganci > wrote:
> >
> > grub> set root=(hd0,msdos2)
> > grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64
> root=(hd0,msdos2)/
> > grub> initrd initrd-plymouth.img
> > gru
> On Oct 30, 2016, at 3:27 AM, Paul R. Ganci wrote:
>
> grub> set root=(hd0,msdos2)
> grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 root=(hd0,msdos2)/
> grub> initrd initrd-plymouth.img
> grub> boot
Try the initrd matching the kernel?
___
Cen
Hi Yamaban,
On Sun, 2016-10-30 at 11:10 +0100, Leonard den Ottolander wrote:
> Still no argument to replace an existing working one... And as I asked
> Valeri, can you please provide us with links indicating the poor quality
> of Corsair SSDs (in general)?
Well never mind that request, very inter
Hello Yamaban,
On Thu, 2016-10-27 at 19:38 +0200, Yamaban wrote:
> For my personal use I would replace that Drive asap.
> - There is no warranty for it anymore (time since buy)
I fail to see how that is relevant... If you lose your data because of a
failing disk you lose your data. Whether or not
Hello Valeri,
On Fri, 2016-10-28 at 09:28 -0500, Valeri Galtsev wrote:
> Amazing. He suggested you definitely reliable drive (Samsung). Reliable in
> my boot too. You ask his opinion about yet another Corsair. One by Corsair
> failed on you already.
It did not. He asked whether it did but there i
On 10/30/2016 12:47 AM, Ned Slider wrote:
On 30/10/16 07:11, Hadi Motamedi wrote:
But the site is far remote and having alert on battery exhaustion can no
longer help . As I said before , I am suspicious if it comes from
frequent
power cuts so seeking some means to distinguish it among the syst
Thank you very much for your help. I have received plentiful helpful
messages . Please consider this case as solved.
Thank you again
On Sun, Oct 30, 2016 at 12:47 AM, Ned Slider wrote:
> On 30/10/16 07:11, Hadi Motamedi wrote:
>
>> But the site is far remote and having alert on battery exhaustio
On 30/10/16 07:11, Hadi Motamedi wrote:
But the site is far remote and having alert on battery exhaustion can no
longer help . As I said before , I am suspicious if it comes from frequent
power cuts so seeking some means to distinguish it among the system logs.
Thank you in advance
Your UPS s
I have something very strange that occurred. After updating the kernel
on my host CentOS 7 Dell 2950iii I have found that one of my CentOS 7
guest VMs will no longer boot... it just stops at the grub prompt (a
second VM functions just fine). I have no idea why this problem occurred
and have bee
Thank you very much for your time . I got the point and it is a very
helpful message .
Thank you again
On Sun, Oct 30, 2016 at 12:19 AM, John R Pierce wrote:
> On 10/30/2016 12:02 AM, Hadi Motamedi wrote:
>
>> Thank you very much for your reply . So you mean under the
>> /var/log/messages it is
On 10/30/2016 12:02 AM, Hadi Motamedi wrote:
Thank you very much for your reply . So you mean under the
/var/log/messages it is distinguishable that which logs come from operator
initiated reboot and which ones come from sudden power cut and then booting
from scratch when power resumed ? Am I cor
But the site is far remote and having alert on battery exhaustion can no
longer help . As I said before , I am suspicious if it comes from frequent
power cuts so seeking some means to distinguish it among the system logs.
Thank you in advance
On Sun, Oct 30, 2016 at 12:08 AM, Mike Mohr wrote:
>
If your battery backup can handle 2 hours of runtime then it almost
certainly has a network management interface. Why aren't you using it to
send alerts?
On Oct 30, 2016 12:05 AM, "Hadi Motamedi" wrote:
> Thank you for your reply. You are correct and the ups is present there but
> the battery ch
Thank you for your reply. You are correct and the ups is present there but
the battery charger can no longer bear power cuts more than two hours so I
need some means to distinguish frequent power cuts there among the system
logs.
On Sun, Oct 30, 2016 at 12:02 AM, Eero Volotinen
wrote:
> you coul
Thank you very much for your reply . So you mean under the
/var/log/messages it is distinguishable that which logs come from operator
initiated reboot and which ones come from sudden power cut and then booting
from scratch when power resumed ? Am I correct ?
On Sat, Oct 29, 2016 at 11:44 PM, John
you could use smart ups and connect information from it to system, so it
can shutdown system in clean way.
Eero
2016-10-30 7:12 GMT+02:00 Hadi Motamedi :
> Dear All
> I am using a centos server for cdr billing and mediation device on a remote
> network. I am experiencing problem that I am suspic
24 matches
Mail list logo
