The display freezes/hangs, but the kernel is still kind of responsive because I can hit Ctrl-Alt-Del and after many seconds it reboots.
I can get it (Slackware 13.0) to boot this same kernel just fine from CD; it's only the normal bootup, after the install finishes, that this happens.
I enabled netconsole so I could see the messages, shown below, but there are no errors reported. The display corrupts and hangs at the "TCP cubic registered" message which appears to be unrelated to anything video-wise.
I have 11.4 with kde 4.6, all up to date via YAST. Radeon driver, legacy ATI display hardware. LibreOffice is latest from the Stable:11.4 repo.
When I open LO, it causes the desktop to break up - diagonal stripes of blocks, and garbage (offset blocks) form all mouse movements from there until kdm restarted.
I restart by switching to F1 console, init 3, the init 5 as root. I can't seem to find any useful messages or logs.
I have a home build computer that has data corruption problems at boot time. I have exhausted all the troubleshooting steps that I know to try. Do you have any additional troubleshooting techniques that I should try?
Symptoms: I run both linux(ubuntu, mint and fedora) and win7 on this machine.Sometimes I have just one installed.Other times both in a dual boot setup. The OS installs just fine.The system runs just fine for a while.Then it fails to boot.At first I can fix the boot problems with grub or bootrec (/RebuildBcd, /FixMbr or /FixBoot) as indicated by the error messages.Eventually the system fails to boot at all and I have to wipe the disk(s) and reinstall the operating system.The linux installs seem to last a bit longer. I typically have linux running for a month before the troubles start, but I have to repave and rebuild within 3 months. The windows installs last at most 2 weeks before troubles develop. The system is turned on for the day or evening then turned off overnight.Once the system has booted all checks that I have run pass. On windows fciv.exe, sfc.exe have never deteced and troubles. On linux tripwire shows everything unchanged. Chkdsk and fsck have never reported errors.
Hardware:ASUS M3A78-EM motherboard. 2x2GB kingston memory from the ASUS QVL for this motherboard.I have used two hard disks in this system.WD caviar black 640G (WDC WD6401AALS-00L3B2).Seagate barracuda 7200.7 (ST3120026A).On some rebuilds I have used just one of the drives, sometimes I have both installed.The DVD burner is a LG 4x (HL-DT-ST DVD-RAM GH22NS30 ).The power supply was originally an el-cheapo Allied unit that came with the case.That has since been replaced with a Seasonic X650.And that is all that is in this system. I use the onboard video, sound and network. I have never plugged an external device into the system (not even a USB flash drive!).
Trouble shooting so far...I have run the memtest utility from both the ubuntu CD and the windows DVD many times. Even when run for several day neither test utility has ever found a memory error.I have run the seagate and western digital provided test and diagnostic tools on both of the hard disks. I have done this on both the unstable ASUS M3A778-EM system and a very stable gateway system.I have swapped out the HDD cables several times.I have replaced the cables with new cables and with cables pulled from a stable system.Because the corruption happens only at boot time I suspected the power supply was having problems under the extra load of disk spinup.So, I replaced the power supply. No success.
I have run the system with every version of the MB BIOS from the version that it shipped with to the latest and greatest. The BIOS upgrades made no noticeable difference.I have enabled and disabled automatic updates on both win7 and ubuntu linux. That made no noticeable difference.That is it. That is all the troubleshooting ideas I have had.
This is a strange problem, 2 Fedora 11 machines, both Dell's. On machine A, remote desktop is okay. On Machine B, remote desktop display is corrupt/unusable.
However, prior to upgrading to Fedora 11, both machines had Fedora 10, and, remote desktop on Machine A was corrupt and Machine B was okay.
Any idea what happened? Why did the upgrade fix one and break the other? Both machines where upgraded with Pre-upgrade. The two machines are in to separate locations, un-related to each other.
Installed Natty a few days ago and everything was working fine. I have a dual head setup with the left monitor rotated Clockwise 90 degrees (AKA rotate left). When I setup the the displays properly, instead of just cloning, I noticed a problem, making Unity unusable. When I apply the rotation either in the xorg.conf fle or using xrandr, the display shows a corrupt looking image. When I turn compiz off and use metacity instead it works perfectly fine.
Display Adapter:
Code:
01:00.0 VGA compatible controller: ATI Technologies Inc Cedar PRO [Radeon HD 5450]
I am trying to update a few pixmap engine themes and can't get the ruler to display/work without corruption in gimp. Works in Inkscape. The two themes have have tried are Scutum
** Warning -- SELinux relabel is required. *** *** Disabling security enforcement. *** *** Relabeling could take a very long time, *** *** depending on file system size. ***
On the next screen the boot hangs. There is a solution posted here: [URL] it states I booted my VM from a rescue CD ISO, mounted the root directory, and:
# cd /mnt/local # rm -f .autorelabel
Once this is done you may want to consider upgrading your VM to more -current that has this fixed. I've booted using a knoppix CD, but I don't know how to mount the root directory to try the fix.
spent endless time trying to get multiple monitors going and have had a bit of success -- got two showing just fine. However, when I try to access the page I mention in the title, Slackware hangs hard -- only the red button will get me out. This is recent. I had dual monitors going before and that didn't happen, I think one monitor was at 800x600 and the other at some wide screeen rez. Anyway all by itself the 800x600 decided to go to 1024x768. Now, note that it all shows fine, no issues of any kind on the monitors themselves, xrandr works
I'm having an interesting issue with my computer right now. It has Ubuntu lucid installed, which was upgraded from karmic shortly after it became available and was up to date as of September 1.
The issue is as follows: It will not boot the internal hard drive (250GB Seagate barracuda). When I select any of the kernels, it appears to be booting, but 6 Hours later, no joy. If I select any of the Kernels in recovery mode, it does nothing, so again no joy.
It will boot my 500GB removable drive via USB (Samsung on the inside), which contains a backup of my lucid (cloned with Clonezilla) from June-ish, but will not do so if the internal hard drive is hooked up, so I cannot access the internals contents while using the backup USB HD.
Now this is where it get's interesting, at least for me. It will boot up a livecd while the internal HD is connected, which was the only way for me to access the contents of my Ubuntu partitions in the internal HD. I have since pulled the Internal out, removed the USB 500GB HD from it's case, installed it into the internal HD bay, hooked up all the cables, turned the computer on and it did boot. While it did seem to take a long while to boot, I'm hoping this may be because it needs a serious amount of updates (294 updates, 485MB are ready via synaptic!). So I now have placed the 250GB Seagate into the USB HD case and can now access it, but the only contents that can be seen, are the items in my defunct vista partition and I cannot find any remnants of my Ubuntu installation, despite gparted being able to see all of the partitions.
While trying to boot into the normal user the system aborts the login and tells me that /home does not have write permission.
The login manager gives:
Code:
If I log in as root and do a
Code:
Or to open some files, it works and no problem seems to exist.
All this happened for the first time after running luckybackup to fusion the old files of one home directory under EXT4 with the new files from my notebook (ext3, Opensuse 11.1 KDE3) in order to come to a unified home. But then the system did not boot any more. I tried to change the owner but some files did not have write access (not even as root, "the file does not exist"). So I thought I might have a a file system problem.
So I thought: unmount the /dev/sdb1 and then do a fschk on it. Runs and was perfect. So I did run it with forcing to control inode per inode.
No error.
So I thought: you screwed up the system. I then decided to reinstall OpensSuse11.3 from the scratch and create the same user for home. I formatted the rest (/swap /boot /root) and left only /home. Installation runs brilliantly, all ok, it comes to the login..................
I have Fedora 13 installed on a new PC and have two types of intermittent boot hangups. What logs exist within Fedora 13 that may help me identify the cause or causes of these hangups? Todate, a reboot gets over the problems but I wish to get this sorted whilst the PC is still under warranty.
I upgraded my ubuntu 64 bit from 10.04 to 10.10 using the update manager on my Laptop ASUS, F80Series, 4Gb Ram, CPU Duo T8100. Ubuntu 10.10 could never boot: it always gets stuck. I tried the "recovery mode". The last two messages written, before getting stuck are:
[1.729408 ] NET: Registered Protocol Family 1 [1.730110] Registered Taskstat Version 1
My machine is running in Pentium(R) 4 CPU 1.7Ghz, Nvidia legacy Riva tnt/tnt2 and a 512mb ram. I have a Network adapter, Realtek RTL8139 Family PCI Fast Ethernet NIC. I have installed Ubuntu in my Window Xp, and used the ACPI workaround to install ubuntu on my PC. Now that I have installed Ubuntu, when I try to boot ubuntu, it always hang before it start to boot.
Upgraded dual boot XP / Ubuntu 2.6.31-22 (still works) to 2.6.32-22, which hangs on boot. "2.6.32-22 recovery mode"(and "continue" dies at "Checking battery state". Ctrl Alt F3 gets a prompt and the login works.
The machine is a Thinkpad g40, which has worked on 9.10, except for wireless distance issues (the G40 has the Atheros AR5211, which seems to be a problem, at least per the forums, and my distance limits experience)
I get the same mount and chroot messages, followed by scrolling msgs, and then a blank screen on attempting to boot 2.6.32-22. And, as indicated, 2.6.31-22 boots and the apps I checked work fine. On the upgrade, there were several msgs about non supported apps and a grub question, which I (naively) answered as use the package version (and was somewhat surprised when dual boot still worked - but impressed and happy
I cloned my hard drive prior to the upgrade, so can revert to 9.10, but would like to run 10.04 LTS. Any suggestions. or should I wait for a while to upgrade?
I had to replace the motherboard, processor, memory on a machine because the old motherboard died. It worked fine under the old board but the new board (Gigabyte 880GA-UD3H) is causing Fedora 11 (and the Fedora 14 Live CD) to fail when initializing an Adaptec AHA-3940UW SCSI adapter.
I was able to display the boot messages and found that the first channel on the adapter is fine, but the second channel causes the boot to hang. The messages are:
aic7xxx 0000:05:04.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 scsi6 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 <Adaptec 3940 Ultra SCSI adapter> aic7880: Ultra Wide Channel A, SCSI Id=7, 16/254 SCBs aic7xxx 0000:05:05.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
I've been having problems with start_udev on my machine post kernel 2.6.18-162 on my CentOS machine. A previous install would work on the old kernelut not the newer ones. I recently did a completely fresh install of CentOS 5.5o see if maybe there was a orruption in my install when it upgraded,t I still have the problem of udev hanging on startup.Using the rescue option on the disk, I've managed to track the problem down to the 50-udev.rules file. Through trial and error, I moved all the .rules files out of the rules.d directory, and added them back one at a time to see which one(s) caused the system to hang, and which ones it carried on booting as normal with. The only one that causes it to hang is the 50-udev.rules.
From what I can tell, this rules file is responsible for letting udev check various pieces of hardware. I think that it is failing whent runs modprobe on a pci device address.Only problem is I don't understand the rules file syntax, so I don't know if I can simply comment out or change a line in this file to skip the device that its looking for.Can anybody help me track down the specific device/line that is doing this?(I've kept the file out of the folder for now and my system appears to continue operating, but I get the occasional problem that for all I know could be due to udev not having a complete start up).
I have a box that has been running fine for a few years primarily as apache/tomcat/mysql server.Just recently, it has started spitting out a bunch of messages and shutting down.The computer is running FC11, x86x64.If anyone can glean anything from the messagesIf you need any more info, let me know. I can get someone to start it up, and get as much as I can before it crashes.From looking at the messages, it seems like it could be something going on with the swap, but I'm not sure.The messages are below.(The box is on the other side of the country from me, so I don't have a ton of info, and it's hard for me to get someone to physically restart it for me...so it's kind of a pain.)(You'll see a lot of errors related to SSHD. I don't know if that's because SSHD is the culprit, or if it's because I was connected using SSH. For some reason I'm leaning towards it being something other than SSHD.)
Code: setroubleshootd[2852]: segfault at 33cb1fe909 ip 00000033caf06e8d sp 00007fffe4bf4ec0 error 4 in libpython2.6.so.1.0[33cae00000+165000]
Fedora hanging during boot when new drives are connected.
I'm running an FC12 install on a 750gig Samsung SATA drive. BIOS is set for drives to be AHCI
I've got 3 other identical 750's, two of which have never been used (as in never been written to). None of the drives have any jumpers set on them, as I've read that SATA handles that. At some point, all 4 drives were connected, and I had formatted one of the drives and backed some data up to it. But a reboot left me with FC hanging on load and the solution was to unplug all 3 other drives. I left it alone for a month.
Troubleshooting this weekend, I found with just my active drive and one of the untouched drives connected, FC still hangs. What I mean by hanging is that the blue background appears with the un-filled 'F' logo which filles diagnally under normal conditions. Mine will not begin to fill, and keyboard commands are not recognized.
It almost resembles a master/slave problem, but I thought that was gotten rid of with SATA. I tried setting the BIOS to use IDE-compatibility mode and set the order of the drives but the problem was the same, though I did not try any jumper arrangements.
I've down loaded the live CD for SUSE 11.3 and, using isohybrid and dd, I put the contents onto a USB stick and made it bootable. All good so far.
I then installed SUSE on one of the partitions on my hard disk (Windows is also on the disk). I set 4GB for SWAP, 16 GB for ROOT and the rest ~270 for /HOME.
I set the bootloader to be installed in the MBR.
The installation completed with no problems indicated.
I was asked to reboot and did so, removing the usb stick so that 11.3 would boot. The reboot failed! I was presented with a black screen and nothing else happened.
I tried again, selecting openSUSE 11.3 from the boot menu. - Again a black screen shortly after pressing enter.
I can boot in Failsafe mode and then login with text prompt. I can't boot into runlevel 3 (same problem - black screen)
Does anyone know whether this is a problem with network configuration or graphics?
I have a notebook with ATI Radeon Mobility HD 5650 graphics card and ATHEROS ar8132 ethernet controller.
I have 2 NVidia graphics cards, a GTX275 and a GT210. My system boots just fine in 32-bit Windows 7, so I know it isn't a hardware problem.Linux boots fine with either the GTX275 or the GT210 installed, but hangs after the file system check if both are installed. My motherboard has 3 pci-e slots, an x1, x4, and an x16. I've tried various configurations, all fail except 1 graphics card installed in either of these slots. I got my system to boot a couple of times with both cards installed in Xbuntu 9.10. Then this problem randomly happened.
System Specs: Ubuntu 10.04 Beta, 2.6.32-16 Kernel MSI N275GTX Twin-Frozr 896MB MSI N210GT 512MB (got it for VDPAU on an HDTV )[code].....
I'm not inclined to believe the problem is here. I don't even get a bootsplash, let alone XServer to start. The system hangs after a flurry of HDD activity. Checked partition, and it's ok.
/var/log/boot.log
Code: fsck from util-linux-ng 2.17.2 /sbin/fsck.xfs: XFS file system.
I'll say up front I'm still new to Ubuntu, so if I've missed anything obvious please forgive me. I chose to upgrade my 9.10 installation to 10.04 via the update manager. Especially since I was going to be gone for long periods of time, this seemed like a good idea.
Downloading went fine, but I had to leave for a two day trip once I clicked install. When I returned, I noticed the machine was still on the purple loading screen with four dots. When I shut it down and rebooted, it got to the same screen. Pressing escape to show the text behind the screen showed two fails and one oddity:
(1) Setting sensors limits "Rather than invoking init scirpts through /etc/init.d, use the service( utility, e.g. service S49console-setup start
Since the script you are attempting to invoke has been converted to an upstart job, you may also use the start( utility, e.g. start S49console-setup start: Unkown job: S49consile-setup"
(2) Starting VirtualBox kernel modules No suitable module for running kernels found
I was having this issue with my server when I tried upgrading (fresh install) to 10.04 from 9.04. But to test it out after going back to 9.04 I installed 10.04 server in a virtual machine and found the same issues. I was using the AMD64 version for everything. In the virtual machine I chose openssh and samba server in the initial configuration. After the install I ran a dist-upgrade and installed mdadm. I then created an fd partition on 3 virtual disks and created a RAID5 array using the following command:
This is the same command I ran on my physical RAID5 quite a while ago which has been working fine ever since. After running a --detail --scan >> mdadm.conf (and changing the metadata from 00.90 to 0.90) I rebooted and found that the array was running with only one drive which was marked as a spare. On the physical server I kept having this issue with one drive which would always be left out when I assembled the array and would work fine after resyncing until I rebooted. After I rebooted the array would show the remaining 6 drives (of 7) as spares.
I updated mdadm to 3.1.1 using a deb from debian experimental and the RAID was working fine afterward. But then the boot problems started again. As soon as I added /dev/md0 to the fstab the system would hang on boot displaying the following before hanging:
After a kernel update action, it seems that I'm unable to boot a system anymore. First off, after installing the kernel, and trying to shutdown to boot to the new kernel, the system replied with INIT: no more processes left in this runlevel. Kernel update was performed from to the following versions 2.6.18-128.el5.img -> 2.6.18-164.11.1.el5.img . The system is a VMWare virtual machine. When trying to reboot, the system passes GRUB, starts initializing and after loading the dm it stops for a few seconds at the message Waiting for new devices, show the following message:
Setting up new root fs no fstab.sys, mounting internal defaults. After this and a few other messages, it displays : INIT: version 2.85 booting INIT - No more processes left in this runlevel INIT: Id "x" respawning too fast : disabled for 5 minutes And then it just hangs. This is the output of my inittab:
[code]...
The system boots into failsafe, but still shows the errors mentioned.
I'm trying to RMA a month old SSD, and they're giving me a hassle about it. The drive currently seems to work just fine, but I'm 95% sure that a few blocks went bad and corrupted some data about a week ago. I was able to mostly recover the data and correct for the bad blocks, but I don't really trust the drive anymore.
I'm running an up to date Debian Squeeze install with ext4 on this drive. My system started doing some bizarre things, to the point that it was unusable, so I rebooted it. As it was booting up, it complained about needing an fsck, which found dozens of non-trivial errors that it was mostly able to fix. It then proceeded to boot normally, except the drive mounted itself as read only (due to errors). Another fsck turned up a similar number of problems. This happened a couple of times before I ran fsck with '-c', which is supposed to scan for and work around bad blocks. That seemed to fix the problem, it hasn't given any more problems since then.
The manufacturer is refusing to RMA the drive unless it's completely unmountable right now this minute, saying that it was a one time problem that could have been caused by anything. Am I right in thinking that the problem has to have been with the drive if 'fsck -c' fixed it, or could something else be going on? If it was the drive, am I somehow being unreasonable in asking for a new one while the current one is "working"?
New install of Fedora 12 64-bit from DVD on an Optiplex 740 (AMD) with 8GB memory I had to use the mem= option to get the install past the EDD probe, but it seemed to install successfully. Now on boot it goes all the way through the "filling icon" progress meter, then switches to a completely black screen with an X pointer cursor that responds to mouse movement, but nothing else happens. Ctrl-Alt-F{2-5} do not switch to a console login, so the system's inaccessible.
Now, all of a sudden, after I restarted after a system update, My dell desktop inspiron hangs on boot. The kernel is: 2.6.34.8-68.fc13.i686. Not only that, but the system won't boot for any of the remaining previous kernels.
i have just upgraded from f14 to f15 using preupgrade. i am now still waiting for the first boot to finish. the screen is stuck for more than an hour and the last line written was:
Started LSB: Start up the OpenSSH server daemon. and there is a blinking cursor.
I'm migrating from XP to Ubunta 11.04. My PC: Toshiba Sat A30-921 L/top CPU: Pentium(R) 42.84GHz RAM: 512Mb Display Adapter: ATI Radeon 9000 IGP K/board: std 102/103 PS2 Pointing Device: Alps PCMCIA Adapter: ENE CB1410 Cardbus Controller Wireless Adapter: D-LINK GDWA 610
The installation went well from start to finish. Made it dual boot with XP. Hooked in the Eth cable & went online right away. Then enabled the W/less network adapter - all OK. Using 'Classic', so it's just normal screen after boot. Problem is random 'Freeze' or 'Hang Ups'. It's hung 12 - 14 times in 2 days! K/brd T/pad frozen out. Only recovery is to use master power switch & reboot. NEVER hung in XP in 7 years! (done other bad things though) Does Ubunta have switch like Cntrl + Alt + Delete in Win?
Tried many combinations but to no avail. I've tried quite a few Linux flavours (from Live CD) & they all displayed the same fault!! Before it hangs, I've been able to browse around Ubunta Apps: Places: System: Firefox: Internet: etc. Where do I start to track the problem down? I'm vaguely familiar (XP) with Terminal & cmd line processor but dont know any of the codes used.
I just finished installing CentOS 5.2 x86_64 on a Dell Dimension 3100 (Pentium 4 with 64-bit support). On the first boot, after completing the final config steps (firewall, SELinux, time server, etc), the boot hangs on "Starting xend:". I have completed a successful installation on another Dell machine (different processor), with the same installation options (I recorded all of the steps and followed them for the second installation).
