You are not logged in.

#1 2009-10-16 10:48:57

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

[Solved] Can't boot after -Syu

I can't boot into arch. The console says it can't find device /dev/disk/by-UUID and goes to ramfs$.

This occured after I ran powerpill -Syu on 15/10/09. The previous update was 13/10/09. The updated packages were:
dhcpcd-5.1.1-1-x86_64.pkg.tar.gz
libcups-1.4.1-1-x86_64.pkg.tar.gz
curl-7.19.6-2-x86_64.pkg.tar.gz
conky-1.7.2-3-x86_64.pkg.tar.gz
xmonad-0.8.1-3-x86_64.pkg.tar.gz
kernel26-2.6.31.4-1-x86_64.pkg.tar.gz
ghostscript-8.70-2-x86_64.pkg.tar.gz

Fallback won't work, I've tried restoring to the previous kernel, running another -Syu, updating klibc, checking uuid's in menu.lst/fstab, checking hooks in mkinitcpio.conf, searching forums and google. I'm don't think the problem is with grub because it boots into ubuntu and windows.

Help

Last edited by 7x1x (2009-10-20 06:19:18)

Offline

#2 2009-10-16 11:37:31

miau
Member
Registered: 2009-05-06
Posts: 202

Re: [Solved] Can't boot after -Syu

Which hooks do you use? Are you running ext4? Have you tied to boot it with /dev/sdaX (where X is your drive number)?

Last edited by miau (2009-10-16 11:39:14)

Offline

#3 2009-10-16 21:36:21

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] Can't boot after -Syu

Hi, thanks for your help.

HOOKS="base udev autodetect pata filesystems keymap"
/ and /var are ext4.
I have tried swaping both meun.lst/fstab to /dev/sda7 and still no improvement. However one thing I noticed is the hook keymap fails, so something is failing before or during hooks.

Offline

#4 2009-10-16 21:41:20

flamelab
Member
From: Athens, Hellas (Greece)
Registered: 2007-12-26
Posts: 2,160

Re: [Solved] Can't boot after -Syu

Change uuids to /dev/sdX and try again hmm

Offline

#5 2009-10-16 21:50:25

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] Can't boot after -Syu

Hi
No luck with /dev/sd7. Any further ideas?

Offline

#6 2009-10-16 22:29:19

flamelab
Member
From: Athens, Hellas (Greece)
Registered: 2007-12-26
Posts: 2,160

Re: [Solved] Can't boot after -Syu

Νο sd7, but sda7, or sdb7 (if it the first disk on the system, so sda7).

Offline

#7 2009-10-16 22:50:54

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] Can't boot after -Syu

There is only one hdd and I have tried both sda7 and sdb7.

Offline

#8 2009-10-17 01:13:40

sand_man
Member
From: Australia
Registered: 2008-06-10
Posts: 2,164

Re: [Solved] Can't boot after -Syu

You should be able to read the output on the screen. Probably something before it tries to find the partition might give you a clue.
Las kernel update the same thing happened to me because no xfs module was being loaded.
I had to add MODULES="xfs" to /etc/mkinitcpio.conf


neutral

Offline

#9 2009-10-17 04:44:55

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] Can't boot after -Syu

I tried adding ext4 in modules. Same thing happened. Here is an abbreviated first 4 screens of the boot, I've had a look and nothing is obvious to me. If no one can see anything I will post the last 4 screens.

pci: mcfg area at e0000000 resirved in e820
pci: using mmconfig at e0000000 -e09fffff
pci: using conpiguration type 1 for base access
bio: create slab <bio-0> at 0
apci: ec: enabling special treament for ec from msi.
apci: bios _osi(linux) query ignored
apci: ec: non-query interrupt received, switching to interrupt mode
apci: interpriter enabled
acpi: (supports s0 s3 s3 s5)
acpi using ioapic for interrupt routing
apci: ec: gpe = 0x2a, i/o: command/status = 0x66, data = 0x62
apci: ec: driver started in interrupt mode
acpi: no dock devicer found,
apci: pci root bridge [pci0] (0000:00)
pci 0000:00:01.1: pme# supported from d3hot d3cold
pci 0000:00:01.1: pme# dissabled
    this occurs about 13 times with different numbers
pci 0000:00:08.0: transparent bridge
pci 0000:04:00.0: pme# supported from d0 d3hot d3cold
pci 0000:04:00.0: pme# dissabled
apci: pci interrupt link [lnk1] (irqs 5 7 10 1 14 15) *0, disabled.
apci: pci interrupt link [lnk1] (irqs 5 7 *10 1 14 15)
    these two lines occur about 20 times with different values
pci: using apci for irq routing
netlable: domain hash size = 128
netlable: protocols = unlabled cipsov4
netlable: unlabled traffic allowed by default
pnp: pnp acpi init
acpi: bus type pnp registered
pnp: pnp acpi: found 12 devices
acpi: acpi bus type pnp unregistered
system 00:00: oimen range 0xffc00000-0xfffffff could not be reserved
    occurs 4 times and then 3 with reserved
system 00:04: ioport range 0x360-0x362 has been reserved
    occurs 8 times

Offline

#10 2009-10-17 07:45:30

miau
Member
Registered: 2009-05-06
Posts: 202

Re: [Solved] Can't boot after -Syu

Can you please post all screens?

Offline

#11 2009-10-18 02:27:44

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] Can't boot after -Syu

Here's the last screens.

pci 0000:00:08.0: PCI bridge, secondary bus 0000:01
pci 0000:00:08.0:   IO window: disabled
pci 0000:00:08.0:   MEM window: 0xfc100000-0xfc1fffff
pci 0000:00:08.0:   PREFETCH window: disabled
pci 0000:00:0c.0: PCI bridge, secondary bus 0000:06
pci 0000:00:0c.0:   IO window: 0x4000-0x4fff
pci 0000:00:0c.0:   MEM window: 0xf8000000-0xfbffffff
pci 0000:00:0c.0:   PREFETCH window: disabled
pci 0000:00:0d.0: PCI bridge, secondary bus 0000:04
pci 0000:00:0d.0:   IO window: disabled
pci 0000:00:0d.0:   MEM window: 0xfc000000-0xfc0fffff
pci 0000:00:0d.0:   PREFETCH window: disabled
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (odder: 7, 524288 bytes)
TCP established hash table entries: 262144 (order: 10, 419304 bytes)
TCP bind hash table entries: 65536 (order: 8, 104857 bytes)
TCP: hash tables configured (established 262144 bind 65536)
TCP reno registered
NET: registered protocol family 1
Unpacking initramfs...
Freeing initr memory: 707k freed
Simple Boot Flag at 0x36 set to 0x1
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1255798223.337:1): initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 3762
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:00:000: Found enabled HT MSI Mapping
pci 0000:00:000: Found enabled HT MSI Mapping
pci 0000:00:000: Found enabled HT MSI Mapping
pci 0000:00:000: Found enabled HT MSI Mapping
pci 0000:00:000: Found enabled HT MSI Mapping
pci 0000:00:000: Found enabled HT MSI Mapping
pci 0000:00:000: Found enabled HT MSI Mapping
Linux agpgart inteface v0.103
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PN: PS/2 Controller [PNP0303:KBD0,PNP0f13:PS2M] at 0x60,0x64 irq 1.12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registerd protocol family 17
registered taskstats version 1
Initalizing network drop monitor service
Freeing unsed kernel memory: 484k freed
:: Loding Initramfs
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio8/input/input1
:: Running Hook [udev]
:: Loading udev...SCSI subsystem initialized
APCI: PCI Interrupt Link [LSI0] enabled at IRQ 23
pata_acpi 0000:00:09.0 PCI INT A -> Link[LSI0] -> GSI 23 (level, low) -> IRQ 23
pata_acpi 0000:00:09.0 PCI IT A disabled
scsi0 : pata_amd
scsi1 : pata_amd
ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x30c0 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x30c8 irq 15
ata1.00 ATAPI: HL-DT-ST DVDRAM GSA-T20N, WC05, max MWDMA2
ata1.00: configured for MWDMA2
scsi 0:0:0:0: CD-ROM            HL-DT-ST DVDRAM GSA-T20N  WC05 PQ: 0 ANSI: 5
done.
:: Running Hook [keymap]
:: Loading keymap...cannot open file colemak.iso15
done.
Waiting 10 seconds for device /dev/sda7 ...

Root device '/dev/sda7' doesn't exist, attempting to create it
ERROR: Failed to parse block device ids for '/dev/sda7'
You are being dropped to a recovery shell
    Type 'reboot' to reboot
    Type 'exit' to try and continue booting
NOTE: kibc contains no 'ls' binary, use echo *' instead

If the device '/dev/sda7' gets created while you are here,
try adding 'rootdelay=10' or higher to the kernel command-line
ramfs$ ^[[5~atkbd.c: Unknown key pressed (translated set 2, code 0xd9 on iso0060/serio0).
atkbd.c: Use 'setkeycodes eo59 <keycode>' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xd9 on iso0060/serio0).
atkbd.c: Use 'setkeycodes eo59 <keycode>' to make it known.

Last edited by 7x1x (2009-10-18 02:58:17)

Offline

#12 2009-10-18 03:13:18

sand_man
Member
From: Australia
Registered: 2008-06-10
Posts: 2,164

Re: [Solved] Can't boot after -Syu

I can't see anywhere that it's actually loading ext4
Did you rebuild the image after adding ext4 to mkinitcpio.conf?


neutral

Offline

#13 2009-10-18 04:20:05

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] Can't boot after -Syu

I added ext4 to modules in mkinitcpio.conf and ran pacman -U /var/cache/pacman/pkg/kernel26-2.6.31.4-1-x84_64.pkg.tar.gz. In rc.conf it says MOD_AUTOLOAD="yes" should this be set to "no"?

Offline

#14 2009-10-19 12:23:17

TaylanUB
Member
Registered: 2009-09-16
Posts: 150

Re: [Solved] Can't boot after -Syu

I don't know how experienced you are, and i am not very much, but this is some experience i have gathered from a very recent problem i had:

What kind of storage device do you use, in terms of PATA, SATA, USB, etc.?
Whatever it is, it has to be added to the HOOKS line, and then you have to use mkinitcpio to create a new kernel26.img (or name it whatever you want).
Just be sure to use the "-k 2.6.31-ARCH" (or whatever the kernel version is) option for mkinitcpio.

I'm using a USB stick so for me, changing the HOOKS line to "base udev pata scsi sata usb filesystems" (from what i heard autodetect is no good if you want to use it on other computers) and running the command "mkinitcpio -g /boot/mykernel26.img -k 2.6.31-ARCH" (and doing the needed modification to /boot/grub/menu.lst) has worked with the kernel 2.6.31.4-1 (last version at the moment) perfectly.

(I never had to play around with any modules.)

Last edited by TaylanUB (2009-10-19 12:24:19)


``Common sense is nothing more than a deposit of prejudices laid down by the mind before you reach eighteen.''
~ Albert Einstein

Offline

#15 2009-10-20 06:13:13

7x1x
Member
From: Japan
Registered: 2009-10-16
Posts: 34

Re: [Solved] Can't boot after -Syu

Thanks for everyones help. What happen was I edited hooks and didn't update the kernel image. So when the kernel updated it wouldn't boot. The hook in question was supposed to be sata not pata.

Offline

Board footer

Powered by FluxBB