I clicked on a window to try to raise it and get a good look. Instead, my screen turned the baby blue mentioned in the subject and I could do nothing else. The mouse cursor was not even visible. It's possible an alternate terminal was available, but I didn't think of it at the time. Eventually I hit the reset button. My Daktech machine has a reset button separate from the power button. The blue went away, but it hung after the CentOS logo appeared. The watch mouse cursor appeared and stayed. I could move it with the mouse, but that was all I could do on that terminal. The possilbility that it might have some major file system checking to do caused me to wait for a few hours, but the nothing changed.
It's my expectation that when the logo appears, any file system checking has already been done. Is that correct?
What is the incantation to get a text view of the start up so that I can get a hint of what CentOS is waiting for?
I manged to boot an old Fedora 14 install, but could not login because I had forgotten the passwords. I'm doing this from Knoppix.
On another terminal, I can login to CentOS as root, but do not know what else to do.
From Koppix, I ran fsck on some file systems:
root@Knoppix:~# fsck LABEL=sata400-3-slash fsck 1.40-WIP (14-Nov-2006) e2fsck 1.40-WIP (14-Nov-2006) sata400-3-slash: clean, 364784/977280 files, 2005224/3907811 blocks root@Knoppix:~# fsck LABEL=sata400-5-var fsck 1.40-WIP (14-Nov-2006) e2fsck 1.40-WIP (14-Nov-2006) sata400-5-var: clean, 5650/428240 files, 289518/1710914 blocks root@Knoppix:~# fsck LABEL=sata400-12-homes fsck 1.40-WIP (14-Nov-2006) e2fsck 1.40-WIP (14-Nov-2006) sata400-12-homes: clean, 279637/5242880 files, 10138872/20971520 blocks root@Knoppix:~#
They ran rather quickly. Should I trust the result? Here is my fstab: # # /etc/fstab # Created by anaconda on Sun Jun 24 18:14:46 2012 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # LABEL=sata400-3-slash / ext3 defaults 1 1 LABEL=sata400-5-var /var ext3 defaults 1 2 LABEL=sata400-12-homes /homes ext3 defaults 1 2 LABEL=ide5-swap swap swap defaults 0 0 LABEL=sata400-6-swap swap swap defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0
As you can see, I changed it to use labels instead of UUIDs. /home is a soft link into /homes .
How do I change passwords on an install, e.g. my F14, into which I cannot login? I can edit the files from either Knoppix or from a CentoS terminal.
On 10/22/2013 2:24 PM, Michael Hennebry wrote:
How do I change passwords on an install, e.g. my F14, into which I cannot login? I can edit the files from either Knoppix or from a CentoS terminal.
edit /mnt/.../etc/shadow and delete the password hash between the first two :'s, so it looks like username::.....
then boot that system, log into it without any password, and set a password immediately.
On Tue, 22 Oct 2013, John R Pierce wrote:
On 10/22/2013 2:24 PM, Michael Hennebry wrote:
How do I change passwords on an install, e.g. my F14, into which I cannot login? I can edit the files from either Knoppix or from a CentoS terminal.
edit /mnt/.../etc/shadow and delete the password hash between the first two :'s, so it looks like username::.....
then boot that system, log into it without any password, and set a password immediately.
Thanks. I'll do that.
On Tue, 22 Oct 2013, John R Pierce wrote:
On 10/22/2013 2:24 PM, Michael Hennebry wrote:
How do I change passwords on an install, e.g. my F14, into which I cannot login? I can edit the files from either Knoppix or from a CentoS terminal.
edit /mnt/.../etc/shadow and delete the password hash between the first two :'s, so it looks like username::.....
That worked after I also deleted the x from passwd. I still do not know how to fix anything.
From my point of view it just stops for no apparent reason.
I forgot to edit the kernal line the last time I boot centos, but if the output oof dmesg is an indication, it got a bit further this time:
ip6_tables: (C) 2000-2006 Netfilter Core Team nf_conntrack version 0.5.0 (16384 buckets, 65536 max) ip_tables: (C) 2000-2006 Netfilter Core Team e100 0000:02:08.0: eth0: NIC Link is Up 100 Mbps Full Duplex ADDRCONF(NETDEV_UP): eth0: link is not ready ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts eth0: no IPv6 routers present 802.1Q VLAN Support v1.8 Ben Greear greearb@candelatech.com All bugs added by David S. Miller davem@redhat.com SELinux: initialized (dev autofs, type autofs), uses genfs_contexts SELinux: initialized (dev autofs, type autofs), uses genfs_contexts SELinux: initialized (dev autofs, type autofs), uses genfs_contexts eth0: no IPv6 routers present Bridge firewalling registered tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max Krasnyansky maxk@qualcomm.com device virbr0-nic entered promiscuous mode virbr0: starting userspace STP failed, starting kernel STP Ebtables v2.0 registered SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs SELinux: initialized (dev proc, type proc), uses genfs_contexts SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs lo: Disabled Privacy Extensions SELinux: initialized (dev proc, type proc), uses genfs_contexts
The SELinux line is new.
Is there somewhere I can put print statements to try to figure out what is going on?
On Tue, Oct 22, 2013 at 04:24:08PM -0500, Michael Hennebry wrote:
What is the incantation to get a text view of the start up so that I can get a hint of what CentOS is waiting for?
To view the startup, when you boot, hit any key, then hit e as in edit (I think--otherwise, just use the arrow key to get down to the line beginning with Linux and when you highlight that line hit e to edit.
At the end of that line you will see rhgb quiet. Remove those two words, hit enter, which should take you back the main menu, and then hit b for boot. (I'm doing this from memory, but I think there are instructions on the screen once you get to the e for edit part.
That will give you text, at least for awhile. However, if you boot into GUI mode, you will also have to change /etc/inittab, where it says id:5:default---change the 5 to a 3, which will boot into text mode and end at a login prompt. Once you log in, you can type startx to start the GUI.
On Tue, 22 Oct 2013, Scott Robbins wrote:
To view the startup, when you boot, hit any key, then hit e as in edit (I think--otherwise, just use the arrow key to get down to the line beginning with Linux and when you highlight that line hit e to edit.
At the end of that line you will see rhgb quiet. Remove those two words, hit enter, which should take you back the main menu, and then hit b for boot. (I'm doing this from memory, but I think there are instructions on the screen once you get to the e for edit part.
Here is the last bit of the startup output, copied by hand: Starting abrt daemon OK user had insufficient privilege Starting crond OK Starting atd OK Starting virt-who OK Starting libvird daemon OK Bridge firewalling registered tun: Universal TUN/TAP device driver 1.6 tun: (C) 1994-2004 Max Krasnyansky maxk@qualcomm.com device virb0-nic entered promiscous mode virb0: starting userspace STP failed, starting kernel STP Ebtable v20 registered lo: Disabled Provacy Extensions _
At that point the watch mouse cursor appeared. The text stayed. After going back and forth between virtual erminals, the mouse cursor was gone.
Does this help with diagnosis?
On 10/23/2013 12:01 AM, Michael Hennebry wrote:
On Tue, 22 Oct 2013, Scott Robbins wrote:
To view the startup, when you boot, hit any key, then hit e as in edit (I think--otherwise, just use the arrow key to get down to the line beginning with Linux and when you highlight that line hit e to edit.
At the end of that line you will see rhgb quiet. Remove those two words, hit enter, which should take you back the main menu, and then hit b for boot. (I'm doing this from memory, but I think there are instructions on the screen once you get to the e for edit part.
Here is the last bit of the startup output, copied by hand: Starting abrt daemon OK user had insufficient privilege Starting crond OK Starting atd OK Starting virt-who OK Starting libvird daemon OK Bridge firewalling registered tun: Universal TUN/TAP device driver 1.6 tun: (C) 1994-2004 Max Krasnyansky maxk@qualcomm.com device virb0-nic entered promiscous mode virb0: starting userspace STP failed, starting kernel STP Ebtable v20 registered lo: Disabled Provacy Extensions _
At that point the watch mouse cursor appeared. The text stayed. After going back and forth between virtual erminals, the mouse cursor was gone.
Does this help with diagnosis?
Have you looked at /var/log/Xorg.0.log file - it sounds like there is a problem with X.
Also someone mentioned editing /etc/inittab and setting the run level to 3. id:5:initdefault: - change the 5 to a 3. If it boots to a non-gui login prompt then the problem is definitely X related.
HTH, Steve
-
John R Pierce -
Michael Hennebry -
Scott Robbins -
Steve Clark