Help! Arch does not boot after crash.

nloudon1 · 2010-04-27 06:36:22

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

demian · 2010-04-27 07:27:53

Hi there,

what you need to to is a file system check with your arch linux live cd. Then chroot into your arch and reinstall initscripts - i hope it includes inittab or fixes any other boot related files that might have been damaged. Also check if crucial files like /sbin/init, /etc/rc.* and other system configuration files have been damaged.

Good luck.

Last edited by demian (2010-04-27 07:28:56)

nloudon1 · 2010-04-27 15:19:04

So are the commands I used from this post http://bbs.archlinux.org/viewtopic.php? … 06#p694906 not the right ones I should have used to reinstall initscripts?

Last edited by nloudon1 (2010-04-27 16:15:01)

nloudon1 · 2010-04-27 16:14:38

So I forced a fsck (because it claimed the partition was clean) and this is my result: /dev/sda5: 316121/972944 files (0.1% non-contiguous), 2606174/3887730 blocks.

/sbin/init and 7 /etc/rc.* files are there.

demian · 2010-04-27 16:58:18

So? What's the result? Have you copied the default inittab and tried to boot yet?

nloudon1 · 2010-04-27 17:29:01

Yeah, I copied the inittab before and it didn't work. So I tried rebooting just now after doing the fsck and I still can't boot .

EDIT: Looking at the files in my /var/log folder I found that both xorg and kdm say the same thing:

Fatal server error:
xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call

Last edited by nloudon1 (2010-04-27 17:32:59)

grey · 2010-04-27 18:13:32

To find out which files are missing from your system you can try the following:

1. boot arch liveCD
2. mount arch partition /some/where
3. pacman --root /some/where -Q # lists all installed packages. check if something is missing
4. pacman --root /some/where -Qk # checks for missing files

I've never used it myself from the live CD, but looking at a 32 bit arch install from a 64 bit arch install this worked perfectly.

nloudon1 · 2010-04-29 13:39:58

That didn't work either, same result. Using Ubuntu is really bumming me out, it's so much slower than Arch...

grey · 2010-04-29 14:17:43

Can you be more specific about how this did not work? Are there no missing files reported?

Last edited by grey (2010-04-29 14:18:04)

nloudon1 · 2010-04-29 17:45:10

The only files reported as missing were mscorettf files which I'm sure wouldn't cause a crash of this magnitude.

grey · 2010-04-29 22:45:43

I just noticed something:

nloudon1 wrote:

Looking at the files in my /var/log folder I found that both xorg and kdm say the same thing

This shouldn't be relevant, since you're not getting to the X server, let alone kdm. But just to be sure: if you have kdm in your DAEMON array in rc.conf, take it out.
Then have a look in /var/log/everything.log to check where the boot process runs into difficulties.

nloudon1 · 2010-05-01 01:28:13

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?

grey · 2010-05-01 14:51:17

Are you running plymouth?

nloudon1 · 2010-05-01 15:17:26

I was, yes. I took it out of my /etc/rc.conf when this started happening though. Is there anything else I need to do to further disable it?

nloudon1 · 2010-05-01 17:33:48

Also, I was using ati video drivers from AUR. I never had any stability problems with them and they seemed a bit faster so I kept them around. I wonder if those have anything to do with this? Is there a relatively simple way to revert to the normal video drivers and see if that fixes it?

grey · 2010-05-01 17:41:54

Well, it's mentioned in your log file, right where the trouble starts. Did you run mkinitcpio when installing it?

If you followed the wiki when installing it, try to retrace your steps.

nloudon1 · 2010-05-03 23:44:32

Well, I've decided I'm going to just reinstall instead of trying to keep troubleshooting this thing. I'm getting nowhere with it. Luckily I have my home directory on a separate partition, so all I have to do is install everything and the configuration of everything how I like it will largely be done. I probably won't be able to do it for a little while though because it takes me all day to do it, but when I finally do it I'll not use video drivers from AUR or plymouth. I guess that was my fault for using unstable versions of such crucial things... lesson learned.

Arch Linux

#1 2010-04-27 06:36:22

Help! Arch does not boot after crash.

#2 2010-04-27 07:27:53

Re: Help! Arch does not boot after crash.

#3 2010-04-27 15:19:04

Re: Help! Arch does not boot after crash.

#4 2010-04-27 16:14:38

Re: Help! Arch does not boot after crash.

#5 2010-04-27 16:58:18

Re: Help! Arch does not boot after crash.

#6 2010-04-27 17:29:01

Re: Help! Arch does not boot after crash.

#7 2010-04-27 18:13:32

Re: Help! Arch does not boot after crash.

#8 2010-04-29 13:39:58

Re: Help! Arch does not boot after crash.

#9 2010-04-29 14:17:43

Re: Help! Arch does not boot after crash.

#10 2010-04-29 17:45:10

Re: Help! Arch does not boot after crash.

#11 2010-04-29 22:45:43

Re: Help! Arch does not boot after crash.

#12 2010-05-01 01:28:13

Re: Help! Arch does not boot after crash.

#13 2010-05-01 14:51:17

Re: Help! Arch does not boot after crash.

#14 2010-05-01 15:17:26

Re: Help! Arch does not boot after crash.

#15 2010-05-01 17:33:48

Re: Help! Arch does not boot after crash.

#16 2010-05-01 17:41:54

Re: Help! Arch does not boot after crash.

#17 2010-05-03 23:44:32

Re: Help! Arch does not boot after crash.

Board footer