Help System won't boot

I'm stuck...I have several older P3 and K6 systems that won't even POST when I have a PI21AG card inserted. I have looked everywhere I can think of with no success.
TIA, Kirby

Try it with the motherboard outside the case and setting on a non conductive surface having only the cpu with heatsink, video card and one stick of memory in the slot nearest to the cpu in the motherboard. You can use a flat bladed screwdriver to momentarily short across the power switch pins on the motherboard to turn it on. That will eliminate any possibility of the motherboard shorting against something inside the case.
Also check to see if there are any unused mounting posts or other objects underneath the motherboard that could short it out.

Similar Messages

Need some help, system won't boot now.

Yesterday, I was having trouble getting WinXP installed on my SATA drive...after I tried some stuff to no avail, I decided to call it a night. When I got up, I went to boot up the system and now all that happens is the 1 LED light flashes and the CD-ROM LED light flashes(and even these don't happen all the time). Nothing else happens, fans don't start etc. So I need some help on troubleshooting this prob. When I do start it up, the D-bracket LEDs flash 4 red also, just flash like the other LED lights. My first guess would be that the PSU is dead? My PSU is a Antec Truepower 380W. Any help is much appreciated.

Believe Bas; As he is 100% Correct, as even 18 Amps is not anywhere enough on the +12V Rail nowadays, I mean I think the New "Minimum" Should be No Less than 25 Amps on the +12V Rail, With these new Powerful Vidio Cards, that Require thier own "Molex" Power Supply Connected to them (As most of these Top Nvidia FX, and ATI Pro's) Need and they can demand up to 6 Amps themselves, I mean, these Cards Have 400 and 550MHZ GPU's on them with over 100 Million Transistors, Not to mention the Extra 256MB of High Speed Graphics memory, Add this with a New 64BIT CPU, and a Sound Card, and a Couple of S-ATA's in RAID, And the 1GIG of High Speed System RAM, and you Are At or Over 18 Amps Already , And we are not even talking CD and DVD's or the At least 4 Fans that you should have ...Yep I for one say the Day's of the 18 Amp Min. Rating for the +12V Rail are Gone Forever...Why do you think that all the Really Good PSu's have At Least 30 Amp Ratings on thier +12V Rails......And in the Case of Enermax, They even went as Far to Start Building thier PSU's With 2 (Dual) +12V Rails ...Thats right, Now they have a +12V-1, and a +12V-2 , Now the CPU gets it's OWN Dedicated +12V Rail, and the System Gets the +12V-2 Rail.......I just got the new Enermax for my 3RD Rig that I'm Building (Dual Opteron 248) Rig , with Bas's Help of Coarse.....But For $99.00 US It was the Best Money spent yet, so much, for a little Price, as the Antec Units are More expensive...And I hear that they are doing a little Cheating on thier Amp Ratings these Days ..Ask "Wonk" he will tell you... ..............Sean REILLY875

System won't boot. INIT: No inittab file found Enter runlevel:

After the latest update that changed how intel ucode is updated, my system won't boot.
I think I missed a line when I edited "/etc/grub.d/10_linux" and ran grub-mkconfig -o /boot/grub/grub.cfg.
Any ideas on how to fix this?
I can't run grub-mkconfig from another machine, as it uses the live kernel info.
Any help would be greatly appreciated. Otherwise I'll have to reinstall

TheSaint wrote:
SyXbiT wrote:
But I still get the error:
system won't boot. INIT: No inittab file found
Enter runlevel:
It seems to me that you've an old Arch version. inittab is deprecated AFAIK.
What is the Arch iso version?
That would probably be mid-2012 at the very latest I think as that's when I remember completely moving over to systemd...
@SyXbiT: Are you using the current Arch install ISO?

System won't boot up

Help please. I have a kt6 delta running an athlon 2700+ xp chip, 512 mb ddr 400.
When I set the fsb at the correct speed for the chip (166) the system won't boot hard drive led lights up constant. dvd drive and cd-r drive each run but the system won't boot. system seems to run fine at default and 133 mhz but the chip is incorrectly identified in windows (xp pro sp1) Any Ideas whats wrong?

Hi - I have the same board with the same processor, I have not problems rebooting after changing the bus speed. But I have had problems rebooting after adding in any card PCI or AGP. the system seems to have trouble clearing the Cmos, I would try clearing the CMOS with the JBAT. it doesn’t always seem to work but I have had some luck, though I have also pulled out the battery a couple of time too..
Good luck!

System won't boot-no chime.

Despite repeated attempts and resetting the CUDA button, the system won't boot when start button is pressed. In the first few seconds it seems to make normal sounds; but no chime and settles into simply fan noise. This is true even if using C (with an Install CD). or Shift key. Is there anything else I can try? (I know it's actually a G3 B&W Motherboard; but I had nowhwere else to post it)

I do not remember exactly what was happening when it stopped. It may have been executing something , hung up, and wouldn't respond to the Command-Opt-Esc or I do remember one incident when it was booting up and stopped when it was partly thru "searching for local discs.
I checked the ref. article and tried to measure the voltages on the power connector. I was never quite sure what pin was what, since the colors did not jive with those in the article. At any rate 2 were approx. + 5 V (one was 4.85), the rest were essentially zero (I believe 1 or 2 were about 300 mv). I did notice that when the power connector is reconnected and start up is attempted, 3 little green lights come on on the motherboard. One goes off after a while.
I have tried the old Sonnet upgrade and have tried reseating all the RAM modules. All to no avail.
The Hard drive and all other parts seemed to be working fine prior to the failure.

Upgrade from snow leopard 10.6.8 to montain lion on a iMac system won't boot getting a crossed out circle

Upgrade from snow leopard 10.6.8 to montain lion on a iMac system won't boot getting a crossed out circle

Clean install OS.10.6.8 update it completly. May be you ignored some firmware update.
I have two incedents.
My thunderbolt port stopped working after upgrading to ML 10.8. I booted from external 10.6 , 10.7 still didnt work. Then i clean installed 10.6.8 and ran software update it updated the thunderbolt firmware and all is well now. This firmware update for some reason didnt show up in ML 10.8.
Secondly , when i upgraded my Brother's Macbook from 10.5 to 10.6.3 it would install but stuck with crossed out circle. Then i downgraded checked for update found an efi update , then the 10.6.3 worked fine.

[SOLVED] Switch to systemd - Now system won't boot

I saw that todays update upgrade included the installation of systemd. I looked the wiki and did the necessary changes (I already had made the /etc/hostname etc. files). So I added the
init=/bin/systemd
line to grub and now my system won't boot. I get an error saying something about syslog service not enabled and then a black screen. I can boot my machine fine without the "init=/bin/systemd" line but I want to run a pure systemd system since Arch is moving to it anyway. In the wiki it mentions to install systemd-sysvcompat but it conflicts with initscripts it says. What am I doing wrong or missing?
Last edited by fettouhi (2013-12-08 14:42:04)

fettouhi wrote:
Thanks for the clarification about the DAEMONS list. My DAEMONS list is:
DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond @alsa dbus networkmanager ufw cupsd avahi-daemon samba)
when I try to enable alsa and dbus I get this
[root@andre ~]# systemctl enable alsa-store.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable alsa-restore.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable dbus.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
Is LVM handled automatically by systemd? The reason I ask is because I have the USELVM= set to YES in rc.conf.
I made the permanent transition to systemd and did not start alsa at all - sound works fine - so I never bothered with the alsa-store/alsa-restore service files at all - it just works! Also dbus gets handled by default in systemd so you don't need any starting of dbus service at all... it just works.

Btrfs: System won't boot anymore after unclean shutdown

Hi,
I have a problem with my ArchLinux (kernel 3.19.2-1-ARCH).
I have my root partition as BTRFS and no /boot partition.
After an unclean shutdown the system won't boot anymore.
GRUB loads the kernel and the kernel starts but it hangs saying: Mounted /dev/sda3 on real root.
Then, I have to start a Live CD and do:
btrfsck /dev/sda3
After that the system boots correctly.
I've tried adding fsck to the HOOKS in the mkinitcpio.conf file and in fact it tries to fsck the filesystem (but with BTRFS, fsck.btrfs doesn't work...)
What can I do?
Thanks

I'm also having this problem. I tried booting up the netinstall image to debug it, but I can't mount my btrfs volume from there either: mount just hangs. After a while, the kernel goes:
[...] INFO: task mount:612 blocked for more than 120 seconds.
[...] Not tainted 3.19.2-1-ARCH #1
[...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[...] INFO: task btrfs-transacti:636 blocked for more than 120 seconds.
[...] Not tainted 3.19.2-1-ARCH #1
[...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
From this post I guessed that I might just need to wait so that I could defrag the volume once it was mounted, but it's been hanging for over 15min now (the message above continues to come up periodically).
Like the OP in the thread I linked to above, my btrfs volume is inside an LVM volume (which is on dm-crypt). Don't know whether that's relevant.
Output of btrfs-check:
Checking filesystem on /dev/pixie/btrfs
UUID: e04cc661-e31a-4dbf-870d-664bc913e34a
found 76855677062 bytes used err is 1
total csum bytes: 72928436
total tree bytes: 2092515328
total fs tree bytes: 1888452608
total extent tree bytes: 104644608
btree space waste bytes: 357251032
file data blocks allocated: 181197139968
referenced 109440282624
btrfs-progs v3.19
dmesg output:
[ 36.824998] Btrfs loaded
[ 36.826713] BTRFS: device fsid e04cc661-e31a-4dbf-870d-664bc913e34a devid 1 transid 98618 /dev/dm-3
[ 46.219014] BTRFS info (device dm-3): disk space caching is enabled
[ 46.259830] BTRFS: detected SSD devices, enabling SSD mode
[ 240.333313] INFO: task mount:539 blocked for more than 120 seconds.
[ 240.335542] Not tainted 3.19.2-1-ARCH #1
[ 240.337795] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 240.340263] mount D ffff8800cf2837f8 0 539 453 0x00000000
[ 240.340277] ffff8800cf2837f8 ffff8800cf2331b0 0000000000013f00 ffff8800cf283fd8
[ 240.340286] 0000000000013f00 ffffffff81818540 ffff8800cf2331b0 ffff8802094f67a8
[ 240.340291] 0000000000000004 ffff8800cf283758 ffffffffa0a2fc91 ffff8802094f67a8
[ 240.340298] Call Trace:
[ 240.340335] [<ffffffffa0a2fc91>] ? set_extent_buffer_dirty+0x71/0xc0 [btrfs]
[ 240.340357] [<ffffffffa0a05796>] ? btrfs_buffer_uptodate+0x56/0x80 [btrfs]
[ 240.340366] [<ffffffff8155e999>] schedule+0x29/0x70
[ 240.340389] [<ffffffffa0a47745>] btrfs_tree_lock+0x65/0x200 [btrfs]
[ 240.340396] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
[ 240.340410] [<ffffffffa09e5cd9>] btrfs_search_slot+0x799/0xaa0 [btrfs]
[ 240.340425] [<ffffffffa09e79f5>] btrfs_insert_empty_items+0x75/0xd0 [btrfs]
[ 240.340446] [<ffffffffa0a47a37>] btrfs_insert_orphan_item+0x67/0xa0 [btrfs]
[ 240.340465] [<ffffffffa0a4a12e>] insert_orphan_item+0x5e/0x90 [btrfs]
[ 240.340482] [<ffffffffa0a4c531>] replay_one_buffer+0x361/0x380 [btrfs]
[ 240.340504] [<ffffffffa0a2f244>] ? alloc_extent_buffer+0x34/0x370 [btrfs]
[ 240.340523] [<ffffffffa0a488f3>] walk_down_log_tree+0x1d3/0x410 [btrfs]
[ 240.340540] [<ffffffffa0a48bfb>] walk_log_tree+0xcb/0x1d0 [btrfs]
[ 240.340558] [<ffffffffa0a507f7>] btrfs_recover_log_trees+0x1e7/0x490 [btrfs]
[ 240.340575] [<ffffffffa0a4c1d0>] ? replay_one_dir_item+0xf0/0xf0 [btrfs]
[ 240.340596] [<ffffffffa0a08b3e>] open_ctree+0x17ae/0x2030 [btrfs]
[ 240.340609] [<ffffffffa09dd633>] btrfs_mount+0x843/0x920 [btrfs]
[ 240.340618] [<ffffffff8117b7aa>] ? pcpu_alloc+0x35a/0x680
[ 240.340628] [<ffffffff811d5d68>] mount_fs+0x38/0x1c0
[ 240.340634] [<ffffffff8117bb05>] ? __alloc_percpu+0x15/0x20
[ 240.340641] [<ffffffff811f116b>] vfs_kern_mount+0x6b/0x120
[ 240.340647] [<ffffffff811f4184>] do_mount+0x224/0xb40
[ 240.340653] [<ffffffff811f4dae>] SyS_mount+0x7e/0xe0
[ 240.340661] [<ffffffff81562809>] system_call_fastpath+0x12/0x17
[ 240.340671] INFO: task btrfs-transacti:561 blocked for more than 120 seconds.
[ 240.342927] Not tainted 3.19.2-1-ARCH #1
[ 240.345175] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 240.348473] btrfs-transacti D ffff88020b88bd98 0 561 2 0x00000000
[ 240.348483] ffff88020b88bd98 ffff880211edc590 0000000000013f00 ffff88020b88bfd8
[ 240.348491] 0000000000013f00 ffff8802162289f0 ffff880211edc590 ffff8802094a70c8
[ 240.348496] ffff8802094d8000 ffff880200000000 ffff8802094d8000 ffff880200000033
[ 240.348501] Call Trace:
[ 240.348511] [<ffffffff811b5d1a>] ? kmem_cache_alloc+0x16a/0x180
[ 240.348525] [<ffffffffa09e07ca>] ? btrfs_free_path+0x2a/0x40 [btrfs]
[ 240.348543] [<ffffffffa0a64213>] ? __btrfs_run_delayed_items+0xf3/0x1d0 [btrfs]
[ 240.348550] [<ffffffff8155e999>] schedule+0x29/0x70
[ 240.348568] [<ffffffffa0a0b555>] btrfs_commit_transaction+0x2a5/0xbe0 [btrfs]
[ 240.348573] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
[ 240.348590] [<ffffffffa0a06fc5>] transaction_kthread+0x1d5/0x240 [btrfs]
[ 240.348605] [<ffffffffa0a06df0>] ? btrfs_cleanup_transaction+0x5a0/0x5a0 [btrfs]
[ 240.348611] [<ffffffff81091748>] kthread+0xd8/0xf0
[ 240.348617] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
[ 240.348624] [<ffffffff81562758>] ret_from_fork+0x58/0x90
[ 240.348629] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
Last edited by ouroboros8 (2015-04-02 12:37:25)

Need help, system won't start up

Need help, system won't start up
When I turn on the system I hear a loud squeaking noise that could be coming from the hard drive, it does it for moment then a blank white screen appears w/ a tiny folder in the middle of the screen with a "?" blinking on and off on the folder. I never had any problems until now. What can I do, any suggestions.

hi capitala1,
+When I try to install the operating system to the internal drive, I don't see a destination option for that drive like I did for the external+
Do you mean that it doesn't show up when you try to startup holding down the option key, or that it doesn't show up in Disk Utility when started up on the external disk?
+...You think the drive is bad, if so, what can I do to retrieve some of the data off of it.+
Yes, it sounds like your hard drive is bad. Do you have access to techtools or Disk Warrior? either of these may be able to repair the drive enough to extract your info from it, if disk utility can't.
I know that there are shops that specialize in extracting info from bad hard drives, but they tend to be pretty expensive. I am sure others on this forum will be able to help you find one if you are interested.
PB
PS it isn't going to help this time, but remember in the future, backup, everything important to you regularly!

System won't boot. Could really use some help here.

I have the K8T-Neo FISR2 mobo. When I set up the system, the SATA drive was set up as drive F: (onto which I installed Windows XP Home). I added a 2nd SATA drive later, and it became C:. Both drives are plugged into the Promise SATA ports. The system has been running fine for about a year now.
I was having a problem with a program not running properly. I stopped the process and tried to restart it, but it didn't work. It was a program that drives my Logitech gaming keyboard (with LCD screen). After I rebooted, the system would load windows, then after Windows was loaded, it would load up a program when I went into it and crash. It looked like it would crash on PXHELP.DLL (something like that). I booted up into safe mode, renamed the file so it wouldn't load, and now it won't boot at all. It starts to show the Windows logo and then instantly reboots. I can't even get into Safe Mode as it does the same thing.
I tried booting from an XP CD to do a repair, but when it boots, it doesn't see the hard drives. I downloaded the Promise drivers, put them onto a floppy, and load them as Windows is booting from the CD. It seems to load the drivers, but when I choose to do a repair (or even a new install), Windows comes back and tells me that I have no hard drives attached to the computer. I just can't seem to get Windows to see those hard drives!
I could really use some advice here......

Quote from: Tiresmoke on 04-January-06, 01:36:35
Try swapping the Drive Cables. You may have one that is not engaging as well as it should.
When I let the PC boot up like normal (without booting from the CD), it sees the drives and Windows tries to load, so I don't think it's the cables. I'll make sure they're reset, but I really don't think that's it.

Please Help: Installed new CPU (i7) now system won't boot.

I'm hoping someone can help.
I have an MSI H55M-P31 (MS-7636) motherboard, and I updated the BIOS to 1.A0.
But when I installed the new CPU, I get 3 Long beeps, and then my computer won't boot.
I have 4Gigs of Memory
Current CPU: (working 100%)
3.07 gigahertz Intel Core i3 540
64 kilobyte primary memory cache
256 kilobyte secondary memory cache
4096 kilobyte tertiary memory cache
64-bit ready
Multi-core (2 total)
Hyper-threaded (4 total)
500watt PSU
Please Help, I don't know what to do now. (did check CPU compatibility on website - i7870)

What PSU is that and what are the ratings of that PSU ? See the label on the side.
Are you trying to use the onboard graphics?
That CPU does not have integrated graphics. http://ark.intel.com/products/41315

System won't boot with incorrect date/time

Hey, I setup a computer back home for VNC, however there was a power outage and now the BIOS has reset. Unfortunately it defaults the date to 2099 for some reason, anyway now the computer won't boot (I can't remember the exact error). Anyway the trouble is I can't access that computer now, and it has no monitor hooked up, is there anyway I can force a boot with just keyboard and without setting the correct date in the BIOS (no one with access to the computer could do this).
Appreciate any help.

You can try to just press F1.
I have a similar issue with my home server, the battery on the motherboard is dead so when the pc is powered off for a while it will not remember the clock. When trying to boot the system in such a case it spits out an error where it offers to "ignore" the error if you press F1.
In my case I need to wait until my pc beeps before pressing F1, basically you need to get past the BIOS stage.
With a bit of luck it might work for you too.
Also I hope you have some ntp service running on your system to make sure the date gets set correctly on your system on bootup.
Last edited by Neburski (2014-02-19 12:35:00)

System won't boot after increased FSB to 166

I have a K7n2 board with AMD 2100+. The system was working fine until, i increased the FSB to 166. Now when i turn on the system, no beep sound and no video at all. There are power to all of the orther components. I cleared the cmos, nothing happen when i powered up. I have another system, with ECS and AMD 1800+. I swapped the CPU between the two systems. Placing the 1800+ in the K7n2, the system boot up fine. But, the board recogninzing the CPU as AMD(tm) Athlon XP 1924 mhz. It is supposed to be only 1.53 mhz. The system run fine. When placing the 2100+ back in, it won't boot.
When placing the 2100+ in the ECS board the computer boot up fine also. I eliminated the CPU problems.
Thanks for any help.

I got it to work now. I reset the safe mode(100 mhz), rebooted, go to the BIOS set to default, and reset the jumper to user mode (default 133). It work fine now.
Ignore the question, thanks.

System won't boot after switching to higher performance

I recently installed snow leopard on my 2009 MacBook Pro. Things have going going very smoothly so far. However, I have had one setback. When switching to a different energy saver mode (either from higher performance to energy saver or vice versa), the computer won't boot back up. It will sit at the blue screen with the spinning wheel. Sometimes the wheel will freeze and the dock and my desktop will show up, but the computer is frozen. This forces me to do a manual shut down. This happens about every other time I try to boot my system into a different energy saver mode. Anybody else have a problem with this?

Hi DPer & welcome to the forums...
Try resetting some of the hardware involved (PRAM~NVRAM). See this Apple KB for details, etc.:
http://support.apple.com/kb/HT1379
Can't hurt to try, and apparently this has helped others recently.
If still no joy, did you update via Software Update or did you download the combo? If you used Software Update, get the Combo updater instead and re-apply:
http://support.apple.com/kb/DL959

System won't boot up constant spinning colored pinwheel

I installed Leopard on my Mac last night. After it finished I received the message that the install was successful. I noticed that my desktop items were not showing up so I restarted my computer. When it boots up now, I still don't get my desktop items. My icons all appear in the navigation bar at the bottom, but the little colored pinwheel spins and won't stop so I can't access anything.
Any suggestions?
Thanks
Bill

Welcome to the Apple boards:
First, I trust you made a backup of your previous system.
Did you repair HD and permissions prior to install?
Did you choose the default install (merge)? If so some of your older or non-compliant 3rd party apps may cause problems.
If you had any of these non-compliant apps in your "Login Items" list, that might be the problem.
Insert the Leopard DVD and reboot. When the system starts to boot (after the black screen) hold down the "C" key and you should wind up in the DVD. Skip past the Language screen and top left you will see a menu. Select Utilities and Disk Utility and repair HD and permissions.
Remove DVD
Then reboot in the safe mode (hold down shift key at boot) and at the login screen click restart.
See if any of this helps. No guarantees.
Your profile tells us little of your computer. More data would be helpful.
Message was edited by: nerowolfe

Help System won't boot

Similar Messages

Maybe you are looking for