Try another console like ALT-F2. See if you have a black screen login prompt. I opened a bug with RedHat for a system that when I went from 6.7 to 6.8 booted but would not start the X server. Problem was in the MACH64 driver. It is missing an external symbol that the X server requires. -----Original Message----- From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Leroy Tennison Sent: Monday, March 20, 2017 1:35 PM To: centos <centos at centos.org> Subject: Re: [CentOS] Need help This is a wild guess since the problem I had occurred on Ubuntu 16.04 LTS but the symptoms are identical. Try 'systemctl enable console-getty.service' then 'systemctl start console-getty.service' or, if it is headless (serial console only), 'systemctl enable serial-getty at ttyS0.service' then 'systemctl start serial-getty at ttyS0.service' assuming it's ttyS0). For VMs (specifically kvm/qemu) neither of these "solutions" worked. ----- Original Message ----- From: "Rosenthal, Shoshana" <srosenthal at cfa.harvard.edu> To: "centos" <centos at centos.org> Sent: Monday, March 20, 2017 3:25:06 PM Subject: Re: [CentOS] Need help I figured out that the system boots OK and it is possible to login remotely. However the monitor does not start up. Do you know how to fix it? On Mon, Mar 20, 2017 at 3:15 PM, Rosenthal, Shoshana < srosenthal at cfa.harvard.edu> wrote:> You are right it is a Dell PowerEdge. However as I said it stops in the > middle of booting with no message. > > > > On Mon, Mar 20, 2017 at 3:11 PM, John R Pierce <pierce at hogranch.com> > wrote: > >> On 3/20/2017 11:54 AM, Scott Robbins wrote: >> >>> I am running centos 6.8 >>>> The system went down when we try to reboot it we get the >>>> message ST:3P7Y9Y1 >>>> Do you know what the problem might be. >>>> >>> I'm guessing you mean the message on the front panel, which is the >>> service >>> tag number. >>> >> >> indeed, thats the service tag for a Dell PowerEdge T620, shipped in >> September 2013, with dual Xeon E5-X2667, 48GB ram, and 10 3TB drives, >> originally running RHEL 6.5 >> >> indeed, you need to connect a monitor to it to determine what stage of >> the boot is failing and why. >> >> >> -- >> john r pierce, recycling bits in santa cruz >> >> >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> https://lists.centos.org/mailman/listinfo/centos >> > >_______________________________________________ CentOS mailing list CentOS at centos.org https://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS at centos.org https://lists.centos.org/mailman/listinfo/centos
I did try other console and it did not work. I did go from 6.7 to 6.8 but with centos not redhat. On Mon, Mar 20, 2017 at 4:59 PM, Styma, Robert (Nokia - US) < robert.styma at nokia.com> wrote:> Try another console like ALT-F2. See if you have a black screen login > prompt. I opened a bug with RedHat for a system that when I went from 6.7 > to 6.8 booted but would not start the X server. Problem was in the MACH64 > driver. It is missing an external symbol that the X server requires. > > -----Original Message----- > From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Leroy > Tennison > Sent: Monday, March 20, 2017 1:35 PM > To: centos <centos at centos.org> > Subject: Re: [CentOS] Need help > > This is a wild guess since the problem I had occurred on Ubuntu 16.04 LTS > but the symptoms are identical. Try 'systemctl enable > console-getty.service' then 'systemctl start console-getty.service' or, if > it is headless (serial console only), 'systemctl enable > serial-getty at ttyS0.service' then 'systemctl start > serial-getty at ttyS0.service' assuming it's ttyS0). For VMs (specifically > kvm/qemu) neither of these "solutions" worked. > > ----- Original Message ----- > From: "Rosenthal, Shoshana" <srosenthal at cfa.harvard.edu> > To: "centos" <centos at centos.org> > Sent: Monday, March 20, 2017 3:25:06 PM > Subject: Re: [CentOS] Need help > > I figured out that the system boots OK and it is possible > to login remotely. However the monitor does not start up. > > Do you know how to fix it? > > > On Mon, Mar 20, 2017 at 3:15 PM, Rosenthal, Shoshana < > srosenthal at cfa.harvard.edu> wrote: > > > You are right it is a Dell PowerEdge. However as I said it stops in the > > middle of booting with no message. > > > > > > > > On Mon, Mar 20, 2017 at 3:11 PM, John R Pierce <pierce at hogranch.com> > > wrote: > > > >> On 3/20/2017 11:54 AM, Scott Robbins wrote: > >> > >>> I am running centos 6.8 > >>>> The system went down when we try to reboot it we get the > >>>> message ST:3P7Y9Y1 > >>>> Do you know what the problem might be. > >>>> > >>> I'm guessing you mean the message on the front panel, which is the > >>> service > >>> tag number. > >>> > >> > >> indeed, thats the service tag for a Dell PowerEdge T620, shipped in > >> September 2013, with dual Xeon E5-X2667, 48GB ram, and 10 3TB drives, > >> originally running RHEL 6.5 > >> > >> indeed, you need to connect a monitor to it to determine what stage of > >> the boot is failing and why. > >> > >> > >> -- > >> john r pierce, recycling bits in santa cruz > >> > >> > >> _______________________________________________ > >> CentOS mailing list > >> CentOS at centos.org > >> https://lists.centos.org/mailman/listinfo/centos > >> > > > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >
> Date: Monday, March 20, 2017 17:24:02 -0400 > From: "Rosenthal, Shoshana" <srosenthal at cfa.harvard.edu> > > I did try other console and it did not work. > I did go from 6.7 to 6.8 but with centos not redhat. > >Did you try another monitor -- one that you know works, and that turns on when plugged into the outlet near the machine in question? Also, some monitors go to sleep, so even an otherwise working monitor may require a couple of taps on the attached keyboard to wake them up.
I am also using CentOS, but to get a bug fixed, you have to go upstream to RedHat. I think John Pierce is right, I had to change my run level to get the alternate consoles to work. I still have the machine at run level 3 hoping that a bug fix lets me go back to run level 5. Other machines work fine, just the 2 with the MACH64 video on the motherboard will no longer run X. Bob S. -----Original Message----- From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Rosenthal, Shoshana Sent: Monday, March 20, 2017 2:24 PM To: CentOS mailing list <centos at centos.org> Subject: Re: [CentOS] Need help I did try other console and it did not work. I did go from 6.7 to 6.8 but with centos not redhat. On Mon, Mar 20, 2017 at 4:59 PM, Styma, Robert (Nokia - US) < robert.styma at nokia.com> wrote:> Try another console like ALT-F2. See if you have a black screen login > prompt. I opened a bug with RedHat for a system that when I went from 6.7 > to 6.8 booted but would not start the X server. Problem was in the MACH64 > driver. It is missing an external symbol that the X server requires. > > -----Original Message----- > From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Leroy > Tennison > Sent: Monday, March 20, 2017 1:35 PM > To: centos <centos at centos.org> > Subject: Re: [CentOS] Need help > > This is a wild guess since the problem I had occurred on Ubuntu 16.04 LTS > but the symptoms are identical. Try 'systemctl enable > console-getty.service' then 'systemctl start console-getty.service' or, if > it is headless (serial console only), 'systemctl enable > serial-getty at ttyS0.service' then 'systemctl start > serial-getty at ttyS0.service' assuming it's ttyS0). For VMs (specifically > kvm/qemu) neither of these "solutions" worked. > > ----- Original Message ----- > From: "Rosenthal, Shoshana" <srosenthal at cfa.harvard.edu> > To: "centos" <centos at centos.org> > Sent: Monday, March 20, 2017 3:25:06 PM > Subject: Re: [CentOS] Need help > > I figured out that the system boots OK and it is possible > to login remotely. However the monitor does not start up. > > Do you know how to fix it? > > > On Mon, Mar 20, 2017 at 3:15 PM, Rosenthal, Shoshana < > srosenthal at cfa.harvard.edu> wrote: > > > You are right it is a Dell PowerEdge. However as I said it stops in the > > middle of booting with no message. > > > > > > > > On Mon, Mar 20, 2017 at 3:11 PM, John R Pierce <pierce at hogranch.com> > > wrote: > > > >> On 3/20/2017 11:54 AM, Scott Robbins wrote: > >> > >>> I am running centos 6.8 > >>>> The system went down when we try to reboot it we get the > >>>> message ST:3P7Y9Y1 > >>>> Do you know what the problem might be. > >>>> > >>> I'm guessing you mean the message on the front panel, which is the > >>> service > >>> tag number. > >>> > >> > >> indeed, thats the service tag for a Dell PowerEdge T620, shipped in > >> September 2013, with dual Xeon E5-X2667, 48GB ram, and 10 3TB drives, > >> originally running RHEL 6.5 > >> > >> indeed, you need to connect a monitor to it to determine what stage of > >> the boot is failing and why. > >> > >> > >> -- > >> john r pierce, recycling bits in santa cruz > >> > >> > >> _______________________________________________ > >> CentOS mailing list > >> CentOS at centos.org > >> https://lists.centos.org/mailman/listinfo/centos > >> > > > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >_______________________________________________ CentOS mailing list CentOS at centos.org https://lists.centos.org/mailman/listinfo/centos