Arch not booting after crash

Hey guys,
I'm not a total newbie, but this one is too hard for me. I was having serious trouble with my system, because I hopelessly overloaded it (it just didn't respond anymore, I'm pretty sure it ran out of memory). So I shut down the system forcefully (I know I know, it just took too long to do anything, I was waiting 2 minutes staring at the screen not moving, even in tty2). When I try to reboot it gets up until the point where it says
Arch: xxx/xxx, xxxx/xxxx blocks
and stays there for at least 4 minutes (that's how long I waited). Normally it doesn't show for more than 20 seconds.
Any help or advice is greatly appreciated,
Yorrd
Last edited by yorrd (2013-07-21 22:03:54)

Hey cfr, thanks for your response. I'll try to answer all the questions and use code tags from now on.
What I'm getting is:
Arch: some/someMore files, many/manyMore blocks
The only thing on this machine is a 100% pure Arch install (I love it )
I would boot into a live CD or something, could you link me to a place where i can look up which logs there are and where to find them?
File system is ext4.
I'll try to give you some more information, it's just extremely hard to figure out what to tell you and where to get the information from, because what I said was actually everything I saw
In my specific case I had Skype 4.2 open on an LXDE environment. Also, Chrome was running which I have noticed to hit hard on my performance in certain circumstances. I'm not sure why and when though yet.
I started up Minecraft (Java) and instantly switched to tty2 when I noticed my screen stuttering a lot and loading windows / elements slower. The memory was completely used up, however analyzing which process was the problem was impossible, because top just didn't refresh either after a few seconds.
I'm getting this pretty much only when I have Chrome opened, however I think it's not specifically Chrome's fault, I just have it running almost all the time. Currently I'm investigating if my Chrome could possibly have issues that it shouldn't be having since it used to run better on any other Linux distro I have set up on this machine (which is the only case, other software usually runs faster in my experience).
Thanks for your patience, I'm looking forward to diving into this.
PS.: I rebooted several times now out of desperation and - magically - it boots now. As a matter of fact, I'm writing this in Chrome on Arch. Still interested in what is causing this though.

Similar Messages

  • Help! Arch does not boot after crash.

    I'm so frustrated, I was just using my laptop like normal and I walked away from it for 2 minutes and when I got back it had turned itself off. I pushed the power and now when arch boots it gets as far as "INIT: Entering runlevel: 3" and after that it just hangs. This is extremely annoying because I can't do anything at all, it doesn't respond to any keys I press or anything, it just hangs there. I booted up to my ubuntu partition and got online to research my problem and I found that my inittab file had gone completely missing! I can't really think of any reason why this would happen, but it just vanished. Maybe it had to do with the fact that I upgraded earlier in the day (much earlier than the crash though)?
    So what I ended up doing is taking the inittab skottish posted here http://bbs.archlinux.org/viewtopic.php?id=90539 and trying it, but no luck I get the same results. So then I tried reinstalling initscripts using the method described here http://bbs.archlinux.org/viewtopic.php? … 06#p694906 but that didn't do me any good either. I have no idea where to go from here, if there are any logs or other files I can post that will help you help me get this sorted out I will be happy to oblige. I would really like to be able to use my arch partition again, it had quickly become my favorite .
    Thanks so much, I really appreciate any help I can get,
    Nate

    Here's what it says
    Apr 28 23:03:55 nate-laptop kernel: BUG: scheduling while atomic: plymouthd/707/0x00000002
    Apr 28 23:03:55 nate-laptop kernel: Modules linked in: fuse ext3 jbd snd_hda_codec_idt snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device arc4 ecb snd_hda_intel snd_pcm_oss snd_mixer_oss snd_hda_codec snd_hwdep radeon snd_pcm b44 b43 ttm drm_kms_helper snd_timer snd soundcore drm video sdhci_pci joydev dell_wmi i2c_algo_bit output ssb snd_page_alloc wmi sdhci mii ac battery pcmcia psmouse mmc_core pcmcia_core i2c_piix4 thermal button ohci_hcd processor ricoh_mmc mac80211 shpchp pci_hotplug ehci_hcd serio_raw i2c_core edac_core edac_mce_amd dell_laptop usbcore sg k8temp cfg80211 evdev rfkill dcdbas led_class rtc_cmos rtc_core rtc_lib ext4 mbcache jbd2 crc16 sr_mod cdrom sd_mod ata_generic ahci pata_atiixp pata_acpi libata scsi_mod
    Apr 28 23:03:55 nate-laptop kernel: Pid: 707, comm: plymouthd Tainted: G D W 2.6.33-ARCH #1
    Apr 28 23:03:55 nate-laptop kernel: Call Trace:
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81044071>] __schedule_bug+0x61/0x70
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8135a797>] schedule+0x577/0xad0
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff810785b2>] ? down_trylock+0x32/0x50
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81057241>] do_exit+0x7e1/0x820
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81359dfd>] ? printk+0x3c/0x3f
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81053c35>] ? kmsg_dump+0x145/0x160
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8100e9c5>] oops_end+0xa5/0xf0
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff810310e3>] no_context+0xf3/0x260
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81031365>] __bad_area_nosemaphore+0x115/0x1d0
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8103142e>] bad_area_nosemaphore+0xe/0x10
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8103183a>] do_page_fault+0x25a/0x320
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8135dfa5>] page_fault+0x25/0x30
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8135b90b>] ? __mutex_lock_slowpath+0xcb/0x370
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8135b8f0>] ? __mutex_lock_slowpath+0xb0/0x370
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8113539a>] ? __d_free+0x3a/0x60
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8135bbc1>] mutex_lock+0x11/0x30
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff811fbab4>] fb_release+0x24/0x70
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff811237fa>] __fput+0xda/0x1f0
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8112392d>] fput+0x1d/0x30
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8111ff88>] filp_close+0x58/0x90
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81055187>] put_files_struct+0x77/0xe0
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8105523d>] exit_files+0x4d/0x60
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81056bbe>] do_exit+0x15e/0x820
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81066048>] ? __sigqueue_free+0x38/0x40
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81067047>] ? __dequeue_signal+0xd7/0x1f0
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff810572cc>] do_group_exit+0x4c/0xc0
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81069679>] get_signal_to_deliver+0x2c9/0x500
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81009370>] do_signal+0x70/0x7a0
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81066385>] ? sys_rt_sigaction+0x85/0xc0
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81009b05>] do_notify_resume+0x65/0x90
    Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8100a28e>] int_signal+0x12/0x17
    Apr 28 23:03:55 nate-laptop kernel: b44: eth0: Link is up at 100 Mbps, full duplex.
    Apr 28 23:03:55 nate-laptop kernel: b44: eth0: Flow control is off for TX and off for RX.
    Apr 28 23:03:55 nate-laptop acpid: starting up
    Apr 28 23:03:55 nate-laptop acpid: 4 rules loaded
    Apr 28 23:03:55 nate-laptop acpid: waiting for events: event logging is off
    Apr 28 23:03:56 nate-laptop acpid: client connected from 3563[82:82]
    Apr 28 23:03:56 nate-laptop acpid: 1 client rule loaded
    Apr 28 23:03:56 nate-laptop crond[3580]: /usr/sbin/crond 4.4 dillon's cron daemon, started with loglevel info
    Apr 28 23:03:35 nate-laptop load-modules.sh: Not loading module alias 'pcspkr' because it is blacklisted
    Apr 28 23:03:35 nate-laptop load-modules.sh: 'pci:v00001002d00004384sv00000000sd00000000bc06sc04i01' is not a valid module or alias name
    Apr 28 23:03:35 nate-laptop load-modules.sh: 'pci:v00001022d00001101sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
    Apr 28 23:03:35 nate-laptop load-modules.sh: 'pci:v00001022d00001100sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
    Apr 28 23:03:35 nate-laptop load-modules.sh: 'pci:v00001002d0000438Dsv00001028sd000001F5bc06sc01i00' is not a valid module or alias name
    Apr 28 23:03:35 nate-laptop load-modules.sh: 'acpi:LNXSYSTM:' is not a valid module or alias name
    Apr 28 23:03:35 nate-laptop load-modules.sh: 'pci:v00001002d00005950sv00001028sd000001F5bc06sc00i00' is not a valid module or alias name
    Apr 28 23:03:35 nate-laptop load-modules.sh: 'acpi:LNXSYBUS:' is not a valid module or alias name
    Apr 28 23:03:35 nate-laptop load-modules.sh: Not loading module 'pcspkr' for alias 'platform:pcspkr' because it is blacklisted
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'platform:regulatory' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'platform:dell-laptop' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0100:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0C04:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0000:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:SYN1015:SYN0100:SYN0002:PNP0F13:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0303:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0800:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0200:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'wmi:05901221-D566-11D1-B2F0-00A0C9062910' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'wmi:8D9DDCBC-A997-11DA-B012-B622A1EF5492' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'wmi:A80593CE-A997-11DA-B012-B622A1EF5492' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'wmi:A3776CE0-1E88-11DB-A98B-0800200C9A66' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:37 nate-laptop load-modules.sh: 'ssb:v4243id0817rev03' is not a valid module or alias name
    Apr 28 23:03:37 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:37 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
    Apr 28 23:03:37 nate-laptop load-modules.sh: 'platform:radeon_cp' is not a valid module or alias name
    Apr 28 23:03:37 nate-laptop load-modules.sh: 'ssb:v4243id0807rev03' is not a valid module or alias name
    Apr 28 23:03:40 nate-laptop ntfs-3g[3271]: Version 2010.3.6 external FUSE 28
    Apr 28 23:03:40 nate-laptop ntfs-3g[3271]: Mounted /dev/sda4 (Read-Write, label "OS", NTFS 3.1)
    Apr 28 23:03:40 nate-laptop ntfs-3g[3271]: Cmdline options: rw
    Apr 28 23:03:40 nate-laptop ntfs-3g[3271]: Mount options: rw,silent,allow_other,nonempty,relatime,fsname=/dev/sda4,blkdev,blksize=4096
    Apr 28 23:03:40 nate-laptop ntfs-3g[3271]: Ownership and permissions disabled, configuration type 1
    Apr 28 23:03:43 nate-laptop init: Entering runlevel: 3
    Apr 28 23:03:43 nate-laptop dhcpcd: version 5.2.2 starting
    Apr 28 23:03:43 nate-laptop dhcpcd: eth0: broadcasting for a lease
    Apr 28 23:03:48 nate-laptop dhcpcd: eth0: offered 192.168.1.80 from 192.168.1.254
    Apr 28 23:03:48 nate-laptop dhcpcd: eth0: acknowledged 192.168.1.80 from 192.168.1.254
    Apr 28 23:03:48 nate-laptop dhcpcd: eth0: checking for 192.168.1.80
    Apr 28 23:03:54 nate-laptop dhcpcd: eth0: leased 192.168.1.80 for 86400 seconds
    Apr 28 23:03:54 nate-laptop dhcpcd: forking to background
    Apr 28 23:03:58 nate-laptop kernel: b43 ssb0:0: firmware: requesting b43/ucode5.fw
    Apr 28 23:03:58 nate-laptop kernel: b43 ssb0:0: firmware: requesting b43/pcm5.fw
    Apr 28 23:03:58 nate-laptop kernel: b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
    Apr 28 23:03:58 nate-laptop kernel: b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
    Apr 28 23:03:58 nate-laptop kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
    Apr 28 23:04:01 nate-laptop crond[3580]: FILE /var/spool/cron/root USER root PID 3646 job sys-hourly
    Apr 28 23:04:01 nate-laptop crond[3580]: FILE /var/spool/cron/root USER root PID 3647 job sys-daily
    Apr 28 23:04:19 nate-laptop smbd[3778]: [2010/04/28 23:04:19.414344, 0] printing/print_cups.c:108(cups_connect)
    Apr 28 23:04:19 nate-laptop smbd[3778]: Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No such file or directory
    Apr 28 23:04:19 nate-laptop smbd[3779]: [2010/04/28 23:04:19.426490, 0] printing/print_cups.c:108(cups_connect)
    Apr 28 23:04:19 nate-laptop smbd[3779]: Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No such file or directory
    Apr 28 23:04:20 nate-laptop kernel: NET: Registered protocol family 10
    Apr 28 23:04:20 nate-laptop kernel: lo: Disabled Privacy Extensions
    Apr 28 23:04:23 nate-laptop kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
    Apr 28 23:04:23 nate-laptop kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Apr 28 23:04:43 nate-laptop nmbd[3788]: [2010/04/28 23:04:43.298321, 0] nmbd/nmbd_become_lmb.c:395(become_local_master_stage2)
    Apr 28 23:04:43 nate-laptop nmbd[3788]: *****
    Apr 28 23:04:43 nate-laptop nmbd[3788]:
    Apr 28 23:04:43 nate-laptop nmbd[3788]: Samba name server NATE-LAPTOP is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.80
    Apr 28 23:04:43 nate-laptop nmbd[3788]:
    Apr 28 23:04:43 nate-laptop nmbd[3788]: *****
    Apr 28 23:05:24 nate-laptop shutdown[3819]: shutting down for system reboot
    Apr 28 23:05:24 nate-laptop init: Switching to runlevel: 6
    Apr 28 23:05:25 nate-laptop shutdown[3823]: shutting down for system reboot
    Apr 28 23:05:26 nate-laptop acpid: exiting
    Apr 28 23:05:26 nate-laptop nmbd[3788]: [2010/04/28 23:05:26.169070, 0] nmbd/nmbd.c:71(terminate)
    Apr 28 23:05:26 nate-laptop nmbd[3788]: Got SIGTERM: going down...
    Apr 28 23:05:26 nate-laptop ntfs-3g[3271]: Unmounting /dev/sda4 (OS)
    Apr 28 23:05:26 nate-laptop syslog-ng[3468]: Termination requested via signal, terminating;
    Apr 28 23:05:26 nate-laptop syslog-ng[3468]: syslog-ng shutting down; version='3.1.0'
    Could it have something to do with those errors regarding my CUPS setup? That couldn't cause something like this could it?

  • Arch not booting after update due to udev problems

    Hi,
    since an update yesterday one of my systems won't boot anymore.
    I tried several solutions mentioned in the forum with no success:
    1) went back to an older kernel
    2) uninstalled and reinstalled mkinitcpio, delete and got a new mkinitcpio.conf
    and ran mkinitcpio -p kernel26 on the kernel
    I had a sort of success by disabling autoloading in rc.conf. Instead of just crashing
    as with autoload enabled it went through to the boot prompt. But I couldn't test any further because I had only usb-keyboard available and that didn't work due to some a missing module I guess . I'll try to get my hands on a PS2 keyboard and look how far I can get later.
    I think the key to the problem might be that I use JFS for both root and home partition (ext2 for boot). From the error messages before the crash it looks like the computer can't reach the root-device. I tried to add jfs to the modules section of mkinitcpio.conf and ran mkinitcpio -p kernel26 again but no change.
    Maybe someone can give me a hint how to get the system up again and fixing the udev problems. This setup did work for the last couple of months so maybe there was some recent change in this regard I overlooked.
    I'm using testing repos and thats what might happen at bleeding edge, no complaining . Nevertheless I would be very interested to understand whats happening and how do get the system up again.
    Thanks and best regards

    Hi,
    thanks for your answer.
    I had merged the pacnew-files already. I read through the udev-readme and did the suggested changes (for example in modprobe.conf) but still not able to boot.
    If I boot failsafe I can actually read an error message on the screen instead of blanking out:
    md: raid10 personality registered for level 10
    :: Running Hook [filesystems]
    :: Loading root filesystem module...
    Attempting to create root device '/dev/sda3'
    /bin/mknod "dev/root" b 8 3
    /init: 1: cannot open /dev/root: No such device or address
    and after some more lines
    kinit: Unable to mount root fs on device dev(8,3)
    kinit: init not found
    Kernel panic - not syncing: Atempted to kill init
    /dev/sda3 is the correct root-device but I have no raid. I have two hdd's (one IDE, one SATA) and one DVD-RAM on IDE as slave, nothing more, nothing less.
    If I boot via install-cd I can mount /dev/sda3. Sometimes I have to run fsck first because mount complains about bad superblock but after fsck I can mount without problem although it didn't report any error. I'm confused.
    Any ideas?

  • Mac Mini will not boot after Security Update 2008-007

    Hello,
    A G4 Mac Mini machine I was asked to take a look at will not boot after the owner (succesfully) installed Security Update 2008-007 from Software Update. Booting always hangs at the blue screen after the Apple logo, and booting in verbose mode reveals that WindowServer is crashing repeatedly. Permissions and filesystems have been repaired, PRAM reset, etc. Safe boot also exhibits the same problem, but it is possible to boot to single user mode. Hardware checks out fine with diagnostic utilities.
    Any suggestions on how to fix this? Unfortunately, backups are not available (it's not my machine =).

    Hi Arkku , and a warm welcome to the forums!
    I'd certainly give Sig's advice a try first.
    If that should fail...
    applesetupdone...
    This was Posted by: JoseAranda at September 9, 2006 3:48 AM
    "OK, restart your computer, hold down Command-s and type in the following:
    /sbin/fsck -fy Enter
    /sbin/mount -uaw Enter
    rm /var/db/.applesetupdone Enter
    # The rm command is the remove command which deletes the file.
    # Robert: I'd rename the file via: mv /var/db/.applesetupdone /var/db/.applesetupdone.old
    reboot Enter
    Once you've done that the computer reboots and it's like the first time you used the machine. Your old accounts are all safe. From there you just change all other account passwords in the account preferences!!
    end of posted by: JoseAranda"
    Reset OS X Password Without an OS X CD...
    http://theappleblog.com/2008/06/22/reset-os-x-password-without-an-os-x-cd/

  • MacBook Pro will not boot after software update

    MacBook Pro will not boot after doing an Apple Software Update (of course they will not help you).  MONEY, MONEY, MONEY is the name of the game.  They can cause your computer to crash and still charge you! 
    Does anyone have an answer to why my computer is showing a little gear spinning for hours?  I have tried several things with NO luck.
    Thanks-

    Run through the list of fixes here
    Step by Step to fix your Mac

  • Not Booting after recent Security Patch/Java update

    My wife has experienced what many have experienced with the recent update.
    MacBook not booting after update (i.e. - "I have no name!")
    I have tried everything posted on this topic since 2/13/09, but without any success. Does anyone have the fix for this yet?
    Things I have tried:
    * I can boot in safe mode (holding "Shift" while restarting)
    * I cannot boot from an install disk(s) (holding C while restarting) - I have both a black one from purchase, and two gray ones with purchase from MiniMac
    * Booting with verbose - gets stuck at same place as everyone else
    Operating in safe mode:
    * I can run DU and "repair" drive
    * I can see and access the CD/DVD
    * I cannot see drive in target drive mode (doesn't ever connect the 2 systems)
    * I downloaded the update files from apple and reinstalled them individually (via USB ext Drive) with a reboot in between
    * I attempted to update & archive, but I cannot run install CD from any systems disks (see above)
    Has anyone figured out how to fix this yet?

    Same problem than the other guy who is not mentioning the update in the title.
    Powerbook 1.67.
    System log said "No user defined computer name" and "using blah blah name" or so.
    Mac Os X report (for apple) says:
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000003900FF1C PC=0x00000000008FC020
    Latest crash info for cpu 0:
    Exception state (sv=0x4299D280)
    PC=0x008FC020; MSR=0x00009030; DAR=0x3900FF1C; DSISR=0x40000000; LR=0x008FE348; R1=0x2C47B9F0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x008FE348 0x008E0014 0x002E9A80 0x002EB94C 0x0008C248 0x00029234
    0x000233F8 0x000ABEAC 0xFF9BA29B
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.ATIRadeon9700(4.1.8)@0x8d8000
    dependency: com.apple.iokit.IOPCIFamily(1.7)@0x48d000
    dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0x85a000
    dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x87e000
    Proceeding back via exception chain:
    Exception state (sv=0x4299D280)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x43D0D000)
    PC=0x9000AF48; MSR=0x0200F030; DAR=0x0ECA77FE; DSISR=0x42000000; LR=0x9000AE9C; R1=0xBFFFD6C0; XCP=0x00000030 (0xC00 - System call)
    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
    Proceeding back via exception chain:
    Exception state (sv=0x4299D280)
    PC=0x008FC020; MSR=0x00009030; DAR=0x3900FF1C; DSISR=0x40000000; LR=0x008FE348; R1=0x2C47B9F0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x008FE348 0x008E0014 0x002E9A80 0x002EB94C 0x0008C248 0x00029234
    0x000233F8 0x000ABEAC 0xFF9BA29B
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.ATIRadeon9700(4.1.8)@0x8d8000
    dependency: com.apple.iokit.IOPCIFamily(1.7)@0x48d000
    dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0x85a000
    dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x87e000
    Exception state (sv=0x43D0D000)
    PC=0x9000AF48; MSR=0x0200F030; DAR=0x0ECA77FE; DSISR=0x42000000; LR=0x9000AE9C; R1=0xBFFFD6C0; XCP=0x00000030 (0xC00 - System call)
    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC

  • [Solved] No boot bc changed file(Old:not booting after battery runout)

    x86_64
    kernel 3.7.9-1
    Cinnamon DE
    I was copying files from an external USB HDD and I didn't notice the battery was running out, and so it did run out.
    Therefore it shut down, and now I can't access Linux. (Also tried fallback mode)
    Also I'm dual-booting arch and w7, and w7 does boot, it's weird that arch just won't.
    So Grub menu does load, but after selecting Arch , it just hangs with one text line and prompt, also can't input anything; it shows like this:
    /dev/sda4: clean, 250964/1638400 files, 2039871/6553600 blocks
    That's shown when I don't have the USB HDD connected (the one I copied files from)
    And when I do have it connected, it's the same just some more lines:
    /dev/sda4: clean, 250969/1638400 files, 2040885/6553600 blocks
    [ 8.08436]sd 4:0:0:0: [sdb] No Caching mode page present
    [ 8.084698]sd 4:0:0:0: [sdb] Assuming drive cache: write through
    [ 8.09866]sd 4:0:0:0: [sdb] No Caching mode page present
    [ 8.108374]sd 4:0:0:0: [sdb] Assuming drive cache: write through
    [ 8.109660]sd 4:0:0:0: [sdb] No Caching mode page present
    Journalctl
    --Reboot--
    Feb 21 11:43:19 arclin pulseaudio[469][pulseaudio]bluetooth-util.c:'org.bluez.Manager.Get.Properties()failed:org:freedesktop.systemd1.LoadFailed:Unitdbus-org.bluez.service failed to load
    Feb 21 11:43:22 arclin pulseaudio[446][pulseaudio]pid.c:Daemon already running
    Feb 21 13:18:01 arclin gnome-session[440]WARNING:Failed to start app: Unable to start application:Failed to execute child proccess "gnome-screensaver"(No such file or directory)
    Feb 21 13:18:45 arclin gnome-session[440]WARNING:Application 'cinnamon.desktop' killed by signal 15
    Feb 21 14:58:57 arclin gnome-session[440]Gdk-WARNING:gnome-session:Fatal IO error 11 (Resource temporarily unavailable on X server :0
    END
    /var/log/Xorg.0.log
    [ 11.138]
    X.Org X Server 1.13.2
    Release Date: 2013-01-24
    [ 11.138] X Protocol Version 11, Revision 0
    [ 11.138] Build Operating System: Linux 3.7.4-1-ARCH x86_64
    [ 11.138] Current Operating System: Linux arclin 3.7.9-1-ARCH #SMP PREEMPT Mon Feb 18 02:13:30 EET 2013 x86_64
    [ 11.138] Kernel command line:BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx ro quiet
    [ 11.138] Build Date: 25 January 2013 09:33:50 AM
    [ 11.138] Current Version of pixman 0.28.2
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 11.138] Markers: (--)probed, (**) from config file, (==) default setting, (++) from command line, (!!)notice, (II) informational,(WW) warning, (EE) error, (NI) not implemented, (??)unknown.
    [ 11.138](==)Log file: "/var/log/Xorg.0.log", Time: Thu Feb 21 16:43:09 2013
    [ 11.174](==)Using config directory: "/etc/X11/xorg.conf.d"
    [ 11.208]Parse error on line 6 of section InputClass in file /etc/X11/xorg.conf.d/10-keyboard.conf
    "Section" is not a valid keyword in this section.
    [ 11.208](EE)Problem parsing the config file
    [ 11.208](EE)Error parsing the config file
    [ 11.208]
    Fatal Server Error:
    [ 11.208]no screens found
    [ 11.208](EE)
    Please consult the The X.Org Foundation support at http://wiki.x.org for help.
    [ 11.208](EE)Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 11.208](EE)
    [ 11.209]Server terminated with error (1). Closing log file.
    (Copied by hand BTW)
    Any suggestion/help is appreciated
    Thanks in advance
    Last edited by arcaid (2013-02-23 01:47:19)

    Without the 'quiet' kernel parameter, it says that dhcpcd service failed and it stucks at [OK] Graphical User Interface.
    Also managed to get the logs (dmesg,journalctl,xorg.0.log). And with all of your input I realized that I recently modified several files to have another keyboard layouts, which I still haven't managed to achieve. I remember I did reboot after the changes to those files, but other layouts never showed up, so I left those files modified (mistake)
    Now the thing is that I thought that I had fixed one of them '10-keyboard.conf' in the above posts, as frank604 suggested commenting out the whole section inputclass. For some reason I Interpreted that as 'coment out only ''inputclass' line'' and never checked the log (xorg.0.log) after the change...
    Well now after checking the new log, it says 'error on line 7' so after commenting out the whole section, like this:
    Section "InputClass"
    Identifier "Keyboard Defaults"
    MatchIsKeyboard "ye"
    Option "XbkLayout" "us"
    #Section "InputClass"
    # Identifier "Keyboard-layout"
    # MatchIsKeyboard "on"
    # Option "XkbLayout" "us,es"
    # Option "XkbOption" "grp:caps_toggle"
    EndSection
    I typed startx ,it didn't mark another error but it still wouldn't start,so I decided to reboot.
    After that... arch does enter now !
    All of this just because I wanted to change the keyboard layouts.
    Having said that.. the problem was that file I modified and after removing my changes and rebooting, now it boots!. Seems like the 'battery run out while copying files' was not related to arch not booting, or so I think.
    Thanks for all your attention

  • HP Pavilion 15-n268sa will not boot after windows update (windows 8.1)

    After a series of windows update (windows 8.1) my HP Pavilion 15-n268sa will not boot up, no fan noises, no lights no nothing. 
    I have tried a "hard reset" a number of times with no success. 
    When the battery is present the white LED flashes 3 times when the power button is pressed. 
    Please please help. 

    Hello Cuffy,
    Welcome to the HP Forums!
    I understand you notebook will not boot after a series of Windows updates.
    Can you tell me if you are able to access the HP Recovery Manager by repeatedly tapping the F11 key while the notebook turns on? If you can access this, try doing a system restore to before you installed the updates. If not I would suggest you go through this document: Computer Does Not Start and the LEDs Blink or the Computer Beeps.
    If it's the Caps Lock light that is blinking this document will tell you exactly what the error is (spoiler: 3 beeps is a memory failure). This could also explain the failed updates. The updates are stored in the RAM before being applied to the operating system.
    You can try reseating the RAM, or using only 1 of the RAM cards, as you have 2x4GB cards. If it still doesn't work with 1 card, try the other card to confirm it has failed.
    You can replace defective cards via HP Phone Support if covered under warranty or at the HP Part Store if not covered. You can contact HP Technical Support at 1-800-474-6836 in North America. For all other regions click here.
    Hopefully this information helps!
    Please click the "Kudos, Thumbs Up" at the bottom of this post if you want to say "Thanks" for helping!
    Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
    The Great Deku Tree
    I work on behalf of HP.

  • HT4623 iPhone 4s will not boot after trying to install ios7 beta 4. Stops at apple logo with progress line under it. how can I reset it or get it back up to do a restore then try the iOS 7 beta 4 install again. Issue was probably caused by disconnection

    iPhone 4s will not boot after trying to install ios7 beta 4. Stops at apple logo with progress line under it. how can I reset it or get it back up to do a restore then try the iOS 7 beta 4 install again. Issue was probably caused by disconnection

    Obviously since you have iOS 7 you're a developer.  As a developer, you signed a NDA with Apple not to discuss the iOS on a public forum.  Please log in to the Developer Forum using your credentials and ask for help there, lest you risk having your credentials terminated.
    Thanks, and best of luck to you.
    GDG

  • Macbook Pro Will Not Boot After Full Timemachine Restore

    Hope someone can help. I upgraded my HD and attempted to restore from time machine. Everything appears to have worked well and the restoration was a success according to what the computer says. However, when I go to reboot I hear the startup sound then the apple pops up on the screen followed by a kernal panic error and the black box telling me that I need to hold down the start button and restart. I've tried resetting the pram, reinstalling from TM again and a couple of other things but it won't start up. I tried doing a clean install and it worked fine then I migrated files from my TM backup and that worked fine as well. However, that's not what I'm looking for, I wanted to get the machine exactly the way it looked before the upgrade and I thought TM was supposed to do that. I've read other forums were people have done it with no problems and am completely stumped at why it is not working. If anyone can shed some light I'd appreciate it.

    I booted with the CD and after selecting the language, went to the utilities pane and used the partition feature.
    Last night in desperation, I booted back to the CD and once again told it to do a full restore from TM. This was the third time that I had done it so far. The previous two times I had gone into the partition feature and partitioned the drive first. This time I skipped that step and just told it to restore from TM. It said if it did this it would erase everything on the drive. I agreed and let it do its work. This morning it once again, as in both previous times, said it had restored from TM successfully. I told it to restart and lo and behold, it booted and everything is just as I had it on the other drive.
    Needless to say, I'm confused but happy. I just wish I knew why it would not boot after restoring the previous two times? Maybe it just wanted me to spend more money:) I tried booting today only after I had gone to frys electronics and bought a SATA to USB cable and cloning software.
    Anyway, thanks for your help and if anyone knows why it wouldn't boot, let me know. It would be good to know for the future just in case. For anyone else having this trouble, keep trying. Third time was a charm for me.

  • My mac mini does not boot, after backing the enire system onto an external drive with Carbon Copy Clone

    My Mac Mini does not boot, after backing the enire system onto an external drive with Carbon Copy Clone. I had switched the start-up disk back to the original of course. Now all I see is the Apple logo. What should I do? Thanks in advance.

    Try disconnecting any external devices, especially hard drives
    and try rebooting.
    If that doesn't help, then :
    If you are running Lion, boot to the Recovery HD and run a
    Repair Disk on the OSX partition.
    If Snow Leopard, boot to the installl DVD and run Repair Disk.
    Also, you may want to bookmark this:
    http://reviews.cnet.com/8301-13727_7-57345273-263/troubleshooting-the-boot-proce ss-for-intel-macs/?tag=txt;title
    for future reference.  It is a pretty good explanation of the
    Mac boot process and how to identify where problems may be.

  • Power Book G 4 wil not boot after oz update Snow leapard os

    Power book G4 did not boot after Lastesat Mozilla update,  Runing snow leapard, message updatenis not compatable  with computer tried to delete update, and will not boot from then on?

    You can't run Snow Leopard on a PowerBook G4.
    Please straighten your story out.

  • My mac book pro is not booting after sleep

    My mac book pro is not booting after sleep...Pls anyone help me!!!

    Hello adibah2731,
    We've an article that proivdes a host of useful tips that can get your Mac booting up again.
    Troubleshooting: My computer won't turn on
    http://support.apple.com/kb/TS1367
    Cheers,
    Allen

  • My Laptop B490 not booting after bios update

    My laptop not booting after updating bios i used windows 8 OS.
    I downloaded Bios from following link.
    Bios Download Link
    After updating bios, system restarted automaticaly, after that only power led is glowing, screen stays blank.
    Help me solve it.
    Solved!
    Go to Solution.

    hi sathish291
    Welcome to the Forums.
    Can you try the following:
    1. Power down the machine, remove the AC adapter and battery.
    2. Hold the power button for 30secs and reconnect the AC adapter only then turn the computer ON.
    If the machine still doesn't power up normally and boot into WIndows then it's likely that something went wrong (could be a bad BIOS flash or an internal component might have gone defective during or after the BIOS update). In this case, you may need to contact lenovo on how to go about getting the unit serviced.
    Support phone list
    Regards
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • Will not boot after reload of OS

    Ok, so here is my tale of trouble.  I have a Lenovo T61 Type 6463-5BU, S/N L3-xxxxx.  The hard drive died a couple of weeks ago, and I have since then received a replacement drive under warranty, i.e. the exact same type of drive.  We had a backup image of the old system under Norton Ghost and managed to get the image back onto the new drive once it was installed.  To do this we used a utility OS called
    "BartPC".
    Since then I have done just about everything I can think of to get the system to boot, including playing with the BIOS settings, setting the drive to "boot" and "active" using a number of utilities including good old "diskpart" and several others.  The drive will simply not boot.  A couple of times I was able to read the drive using Bart in command prompt mode, but I never managed to boot from it.
    The laptop does have a finger print reader, but I have been told several times that this does not have anything to do with the problem.  So... before I cut someone's finger off and swipe it across the reader... what am I doing wrong here?
    Moderator Note; s/n edited for members own protection
    Solved!
    Go to Solution.

    Absolute pre-req / reset that BIOS to default settings, lets eliminate any setting that can also hose you up even after you've solved the problem
    Clarify when you described reading the drive a couple times from "BartPC" , are the drives contents viewable EVERY TIME BART is used for boot ? //// did you mean Bart PE?  It has to be asked since the PE's and BART is the widely accepted recovery tool and saved myself on numerous sytems and esatblishing the post with access to a BART-PE will assist with follow up suggestions knowledable of the tools at your dispoalsa.
    If I had to make a best guess and from a decent portfolio of steps you've tried, I would speculate you need a chkdsk  because drives afflicted with mechanical failure will corrupt files while they're physically dying.  More often the cause of disk failure isn't mechanical inside but actually a scorched or failed circuit off the bottom of side and removing the circuit board to view the hidden side can be extremely revealing of where the problem lies. 
    if you haven't already returned the dead drive, then examine the PCB and it is often affixed with TORX heads to prevent the toddlers from removing it while the rest of the world had received a torx head screwdriver set before their 8th birtday.  Your probelm could be asily sovled by swapping the pcb from the new unbootable replacement onto your old drive where the data is still hostage and resuming a normal life.
    A drive that is accessible and only sporadically between sessions or seems to crash inexplicably and incosnteslty could be easily solved with a chkdsk repair included form Micrsofot,
    chkdsk c:  /f  /x and if that data is really trashed those can take a day or even more to finish.
    Assuming you aren't trying something heroic such as taking an image from an IDE drive and reloading to a SATA disk,  get a USB floppy drive and create an NT boot disk. Your description hints you're familiar with boot loaders and the comforting part of NT boot disks is they only require being formatted by an NT kernel and even a format a: /q is the necessary first part and no /sys switches such as Windows95 and FAT32.
    - Copy a compatible from equal or newer version of boot.ini, ntldr and ntdetect.com to the floppy, in the history of Windows most often an older ste of boot files can still kick off a newer version such as NT4 / SP4 versions of those files could still load Windows 2000, but it seem XP was a delineation and w/o any knowledge of how isolated you and this system may be located take the best road and load those startup files from the old image but that is assuming you know they weren't damaged or from a comparble OS
    The key to this step is having the right boot.ini settings and if the drive is mounted in the native bay you can keep the boot.ini lines to "basic"
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="DontG​etPreoccupedWithTheOSdecreiptoin, but don't make it too long enteirh and if you still insist on spaces then ensure you use quote3s.l" Notice how Cutler chose to use Zero notation for the controller and disk ID but got cheeky on the partiont numbers so the first partyion INS'T PARTIOTION ZERO LIKE THE REST OF HIS PATHS.
    Just becase you see a boot menu doesn't mean the problem is becoming solvede, the floppy disk should give you the same boot menu even if the system was diskless.
    I'm advising you try tidfeeretn partiton numbers since you mentioned you've been dinking around with this disk and with ut's and it is possible the actual boot partion ID# could've been changed depending on just what was excueted/
    Assuming you didn't use a diffetrent direcoty name than Windows then this one should work rather well and you can copy this block of text as the test boot.ini
    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW​S
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="PARTI​TION 1" /fastdetect /sos
    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="PARTI​TION 2" /fastdetect /sos
    multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="PARTI​TION 3" /fastdetect /sos
    multi(0)disk(0)rdisk(0)partition(4)\WINDOWS="PARTI​TION 4" /fastdetect /sos
    multi(0)disk(0)rdisk(0)partition(5)\WINDOWS="PARTI​TION 5" /fastdetect /sos
    multi(0)disk(0)rdisk(0)partition(6)\WINDOWS="PARTI​TION 6" /fastdetect /sos
    Still failing, then eject as much as possible from the TPad to eliminate some wieird interfeance or electrical short and this inlcudes any accessible DIMM's while still leaving enough RAM for minimal sysatem boot, if you can just reach POST then it seems your problems may be solved.
    I
    Still failingg,,,, if you have access to an ultrabay adapter, mount the new but unbootable disk into the ulotra Bay, power off the sytsem and drop the batteries but leave the BIOS battery alone
    REmain unpowered for a few seoncs and to lfush remanants, the Intel Chip Set has gained sophistaicantion and has really nhice tigtht mini os of its own and can even be interaced with hypertmenail and some port commands.
    It is unlikey the chipset is corrupt but it can retain last session info longer than you'd think and dropping all batteries is the reason by elimiatinng this variable.
    Restart and the fialed disk inside slot 2 and w/o the boot disk and boot.ini I gave you, observe for any differences or progression versus before
    If that still fails, then return here with details from your tests, ...but you get to a point where you realize you waste more time trying to repair something than just replacing it and unless there is software on this system you can't afford to lose and it has to be preserved in its state, then you could consider laying that existing image from your new but non starter onto a separaete locaiotn and erinstalling your pre3ferrred OS to migrate the data back and your best to merge the session state.
    Another altrenative and aasuming you have the horsepower and free space, take that coy of ghost and lay it down onto a virtual machine, since Microsoft Virtual PC and VMWare emulate better than anytihing else,  it is possible to migrate a physical disk and array into a vhd and the transplated OS will never see a difference.
    This is an emerging solution for tradiioanal users whoa re loathe to change when they find and manage to get a computer that works just the way they want ( can you blame them ?).  I volunteer at an assited living center and a violinist who had configured her 12 year old Windows95 laptop just the way she liked it and only went online about four times a year her box died and the center upgradedher to a lightweight x200 and she boots into windows XP and it aumoatmaily loads MS Virtual PC and her old Win95 system and music software and w/o er interaction so she can have her old computer on new deck and allowed to eat with metal utensils sicne she's calmer now.
    If you can
    Don't just sit there, take a second and use the Kudo's button to compliment the people who help you.

Maybe you are looking for