kernel panic after pacman upgrade [solved]

bsdson.tw · 2007-02-19 20:26:54

After upgrade and reboot, I've got the following message:

ata1.00: zero err_mask for failed internal command, assuming AC_ERR_OTHER
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x100)
ata1: SATA link up 1.5Gbps (SStatus 113 SControl 310)
scsi1 : sata_sil
ata2: SATA link down (SStatus 0 SControl 310)
done.
:: Running hook [filesystems]
:: Loading root filesystem module...-e
Attempting to create root device '/dev/sda3'
ERROR: failed to parse block device name for '/dev/sda3'
unknown
ERROR: root filesystem cannot be detected. Try using the rootfstype= kernel parameter.
:: Initramfs completed - control passing to kinit
IP-Config: no device to configure
kinit: Unable to mount root fs on device dev(0,0)
kinit: init not found!
kernel panic - not syncing: Attempted to kill init!

I've searched the forum, but thre is no the same situation.

I've one boot SCSI hard drive, and one IDE dvd-rw,
which work okay before pacman upgrade.
If I remember correctly, the IDE dvd-rw was using old IDE driver.

And...
My computer is a AMD/Nforce2 chipset/Nvidia Gforce 4 AGP Card system.
so I think this is nothing about kernel parameter "earlymodules=piix" (or so),
and nor the "bootdelay" parameter (cause I've tried it)
and besides, I've also tried the fallback initramfs, but still no luck.

Any idea about what I can do..?
Thank you very much... in advance.

Last edited by bsdson.tw (2007-03-03 17:46:19)

lilsirecho · 2007-02-20 03:00:30

What was the upgrade? Was it a new kernel? Older kernels have old IDE HDD names. The sda3 referenced in your post suggests you had IDE ID's in an older kernel and either grub or Lilo needs to be modified.

bsdson.tw · 2007-02-20 07:00:33

Yes, I did upgrade the kernel and nvidia video driver,
but I can't remember whether the initramfs did upgrade or not.

And I upgrade frequently, so I believe that the version of kernel is at least from 2.6.19 to 2.6.20.

And I've made a typo in the 1st post, the boot disk drive should be SATA, not SCSI.
So I used to use sda3 as my boot device and it works normally,
I don't know what should I modify it to?

About the dvd-rw, I did use the old IDE driver, but I did not change the configuration to use the new one,
so I think it should retain as before.

ps. I've a ASUS A7N8X mainboard.
ps2. what else information I can give to help diagnose this situation?

thanks again..

lilsirecho · 2007-02-20 17:15:47

Check the newsletter items for info regarding latest changes that may affect your boot .....

noriko · 2007-02-20 17:46:00

ERROR: root filesystem cannot be detected. Try using the rootfstype= kernel parameter.

i doubt u'll get past that stage unless you reolve that issue...

just add rootfstype=[ext4dev,jfs,etc(you file system)] to ur kernel line...
in grub, press `e` at the boot menu..

bsdson.tw · 2007-02-20 19:08:31

Thank both of you, but things' still the same.

After reading Arch Linux Newsletter 02-11-2007,
I can be sure of that before this "kernel panic" one, I did one upgrade after 2/11.
(and it worked normally)

And there is no hint about what if I should modify any configurations with the new kernel 2.6.20
in the announcements.

About the "rootfstype" kernel parameter, I did have tried that,
but the situation is almost the same.
The problem in fact starts while initramfs trying to load device driver,
and response quite some error messages. Part of them is as below:

ata1.00: zero err_mask for failed internal command, assuming AC_ERR_OTHER
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x100)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
BUG: at drivers/ata/libata-core.c:4365 ata_hsm_move()
[<e082d9ae>] ata_hsm_move+0x1be/0x7d0 [libata]
[<c033eb42>] schedule_timeout+0x52/0xd0
[<-address->] __wake_up_common+0x39/0x70
[<-address->] process_timeout+0x0/0x10
[<-address->] ata_pio_task+0x27/0x100 [libata]
[<-address->] run_workqueue+0x93/0x140
[<-address->] ata_pio_task+0x0/0x100
[<-address->] default_wake_function+0x0/0x10
[<-address->] worker_thread+0x0/0x170
[<-address->] kthread+0xbb/0xf0
[<-address->] kernel_thread_helper+0x7/0x18
================
ata1.00: zero err_mask for failed internal command, assuming AC_ERR_OTHER
ata1.00: failed to IDENTIFY (I/O err, err_mask=0x100)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
scsi1 : sata_sil
ata2: SATA link down (SStatus 0 SControl 310)
done.
:: Running Hook [filesystems]
:: Loading root filesystem module...-e
.....

I don't know if this is correct, but I thought that:
Initramfs first loads some necessary device drivers and then pass the control to the kernel.

And while Initramfs' loading the SATA driver, something bad happened.
Which makes it unable to recognize the SATA hard disk,

and hence makes Initramfs unable to recognize the file-system.
(on an in-existed disk)

Could this possible be a bug in the device driver?

Thank you very much.

ravster · 2007-02-21 17:51:58

Have you tried using PATA in your mkinitcpio.conf?
I find that that helps for my computer.
Ravster

primarycircle · 2007-02-21 18:29:38

It may be possible that you didn't have /boot mounted when you installed your new kernel. I had a problem with something similar to this. Try booting up the install cd and mount your existing file system. Reinstall the kernel with these file systems mounted. If this fixes your problem, before you install a new kernel make sure you run [ mount /boot].

Good luck, and I hope this fixes your problem.

bsdson.tw · 2007-02-24 15:26:25

Thank both of you, ravster and primarycircle.

1. I do have my "boot" mounted, cause I have only one partition.

2. I can not be sure how my mkinitcpio is configured right now. But my boot disk is a SATA one, so I wonder if PATA will work... But, since I do not have any idea, I will try this while I get back to my computer.

thanks again.

ps. any other idea?

bsdson.tw · 2007-02-26 04:04:34

I've found someone who has "the same" problem with me.

Here is the link about his post:
http://permalink.gmane.org/gmane.linux.kernel/497140

Hope this would give someone else a little clue...

BR,
bsdson.tw

nazgoul · 2007-02-26 11:45:36

Ever tried adding "earlymodules=piix" to the kernel line ?

Just a thought

supa · 2007-02-26 16:12:53

bsdson.tw wrote:

I've found someone who has "the same" problem with me.
Here is the link about his post:
http://permalink.gmane.org/gmane.linux.kernel/497140
Hope this would give someone else a little clue...
BR,
bsdson.tw

Actually, that's my post on LKML and I'm also using Arch. I think there's a bug somehow in Arch's sata_sil driver recently. I'm still looking for solutions and removal of possible conflicting patches.

mutlu_inek · 2007-02-26 20:55:38

So it seems that there is a more serious bug involved.

However, I noticed that you wrote that you have only one partition:

bsdson.tw wrote:

1. I do have my "boot" mounted, cause I have only one partition.
2. I can not be sure how my mkinitcpio is configured right now. But my boot disk is a SATA one, so I wonder if PATA will work... But, since I do not have any idea, I will try this while I get back to my computer.

From this it seems that you have /dev/sda formatted as one partition on which root, boot and home are located. Also, you never actually changed your /boot/grub/menu.lst since the error happens, because you cannot mount your harddrive. Is that correct?

If yes, then my suggestion is pretty basic. Maybe grub's menu.lst is corrupted in some way (erroneous update, read/write error, or human error). I assume something like this, because there is no reason for the init process to look for /dev/sda3. According to what you say you do not have such partition (or at least it in not root). It should be /dev/sda1.

When starting up, interrupt grub, and enter custom values for grub. I suggest something around these lines (depending on your system):

root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/sda1 ro vga=791
initrd /boot/kernel26.img

What are the results?

ihavenoidea · 2007-02-26 23:46:38

i had this same problem too, but the answer was so simple for me anyway, edit menu.lst because for some reason it doesnt point everything right, the initrd section should say somthing like kernel26.img so change it to initrd26.img, or i could have them mixed around. post your menu.lst please.

mutlu_inek · 2007-02-27 00:16:20

mutlu_inek wrote:

root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/sda1 ro vga=791
initrd /boot/kernel26.img

What are the results?

I forgot the final command:

boot

djidji · 2007-02-27 03:21:17

i had a very similar problem. at first i noticed that under initrd i had /boot/initrd26.img. once i replaced that with /boot/kernel26.img i had the exact same problem as you are having. i added rootfstype=ext3 and earlymodules=piix to the kernel line and that fixed the problem. i hope this works for you.

supa · 2007-02-28 21:42:30

bsdson.tw wrote:

After upgrade and reboot, I've got the following message:
ata1.00: zero err_mask for failed internal command, assuming AC_ERR_OTHER
ata1.00: failed to IDENTIFY (I/O error, err_mask=0x100)
ata1: SATA link up 1.5Gbps (SStatus 113 SControl 310)
scsi1 : sata_sil
ata2: SATA link down (SStatus 0 SControl 310)
done.
:: Running hook [filesystems]
:: Loading root filesystem module...-e
Attempting to create root device '/dev/sda3'
ERROR: failed to parse block device name for '/dev/sda3'
unknown
ERROR: root filesystem cannot be detected. Try using the rootfstype= kernel parameter.
:: Initramfs completed - control passing to kinit
IP-Config: no device to configure
kinit: Unable to mount root fs on device dev(0,0)
kinit: init not found!
kernel panic - not syncing: Attempted to kill init!
I've searched the forum, but thre is no the same situation.
I've one boot SCSI hard drive, and one IDE dvd-rw,
which work okay before pacman upgrade.
If I remember correctly, the IDE dvd-rw was using old IDE driver.
And...
My computer is a AMD/Nforce2 chipset/Nvidia Gforce 4 AGP Card system.
so I think this is nothing about kernel parameter "earlymodules=piix" (or so),
and nor the "bootdelay" parameter (cause I've tried it)
and besides, I've also tried the fallback initramfs, but still no luck.
Any idea about what I can do..?
Thank you very much... in advance.

Upgrade to the kernel26 2.6.20.1-2 package after it hits your local mirror for the fix.

bsdson.tw · 2007-03-01 01:47:29

Thank all of you!

@mutlu_inek:
Sorry that I didn't have it clear: I've only one hard disk and parted it as 4 partitions: 2 NTFS for windows, 1 ext3 for Arch and 1 swap.
(so I think the sda3 and hd(0, 2) are correct...)

@djidji:
I've tried either one but not both at the same time, I'll try it later.

@supa:
Thank you!
But... I have no idea how to upgrade my kernel26 package, since I can't boot into Arch.
Can I un-tar the new kernel26 to the boot partition directly, or what can I do?

BR,
bsdson.tw

supa · 2007-03-01 01:55:34

bsdson.tw wrote:

Thank all of you!
@supa:
Thank you!
But... I have no idea how to upgrade my kernel26 package, since I can't boot into Arch.
Can I un-tar the new kernel26 to the boot partition directly, or what can I do?
BR,
bsdson.tw

You should be able to use the 0.8 beta1 (not beta2, it contains the same kernel bug) to boot specifying the root device on the cmdline.

In a pinch you could untar kernel26 to / with /boot mounted (not /boot directly, since the package contains other files also) but it might overwrite some files because it wasn't installed with pacman. Your best bet is rescue mode with the 0.8beta1 CD.

bsdson.tw · 2007-03-03 17:45:34

Thank all of you, the problem is solved!

I untar-ed kernel26 and the system finally booted correctly.
Now I am upgrading my system via pacman.

Spadearcher · 2007-03-03 22:11:45

By a really fortuitous (I hope) coincidence I have come upon this thread today after having downloaded and installed Arch for the first time also today -- and encountered this exact same problem! I do not consider myself an entire novice at these matters, as I have successfully installed on my system Ubuntu, Gentoo, Slackware and FreeBSD, and I am successfully booting all of them from my grub menu on my first partition (sda1), even though two of them (Slackware and FreeBSD) were not initially set up to boot from grub.

Anyway, I have tried Djidji's recommended solution to my earlier unsuccessful "initrd26" to "kernel26" fix, but that doesn't work. Now I guess that my next course is to try to upgrade my kernel26 package, but I'm also not certain how best to do this. I've installed my Arch through a combination utilization of ios cd (which I downloaded also today) and ftp (for packages). I would think that such a fresh download would have provided me with the latest kernel to install. Anyway, considering that I have a fresh installation cd, what is the best way for me to proceed to get my Arch to boot with a corrected kernel?

Incidentally, as I have also just joined this forum today, this is obviously my first posting.

Last edited by Spadearcher (2007-03-03 22:13:03)

Spadearcher · 2007-03-03 23:48:38

As a postscript, I am fearful that because this thread has been listed as a solved problem, no one further will be reading it -- and therefore respond to my query. If I hear nothing in a day or so, I'll probably have to begin a new thread.

bsdson.tw · 2007-03-05 02:20:10

m.. excuse me if I misunderstand you, cause English is not my native language.
I guess that your problem is just "the same" as mine, and here is the solution:

1. download kernel26 2.6.20.1-2
2. mount your boot and root directory on the other working system
3. untar kernel26 to your mounted directorys. be careful about the path
4. reboot

PS> don't worry about the inconsistency of the version of the kernel26, since you could do a "pacman -S kernel26" after that.

Spadearcher · 2007-03-05 04:59:58

bsdsob.tw: Thank you for your clarification. Actually, I was able to solve my problem by downloading the beta iso and reinstalling that version instead. Everything works fine now. Thanks again.

Arch Linux

#1 2007-02-19 20:26:54

kernel panic after pacman upgrade [solved]

#2 2007-02-20 03:00:30

Re: kernel panic after pacman upgrade [solved]

#3 2007-02-20 07:00:33

Re: kernel panic after pacman upgrade [solved]

#4 2007-02-20 17:15:47

Re: kernel panic after pacman upgrade [solved]

#5 2007-02-20 17:46:00

Re: kernel panic after pacman upgrade [solved]

#6 2007-02-20 19:08:31

Re: kernel panic after pacman upgrade [solved]

#7 2007-02-21 17:51:58

Re: kernel panic after pacman upgrade [solved]

#8 2007-02-21 18:29:38

Re: kernel panic after pacman upgrade [solved]

#9 2007-02-24 15:26:25

Re: kernel panic after pacman upgrade [solved]

#10 2007-02-26 04:04:34

Re: kernel panic after pacman upgrade [solved]

#11 2007-02-26 11:45:36

Re: kernel panic after pacman upgrade [solved]

#12 2007-02-26 16:12:53

Re: kernel panic after pacman upgrade [solved]

#13 2007-02-26 20:55:38

Re: kernel panic after pacman upgrade [solved]

#14 2007-02-26 23:46:38

Re: kernel panic after pacman upgrade [solved]

#15 2007-02-27 00:16:20

Re: kernel panic after pacman upgrade [solved]

#16 2007-02-27 03:21:17

Re: kernel panic after pacman upgrade [solved]

#17 2007-02-28 21:42:30

Re: kernel panic after pacman upgrade [solved]

#18 2007-03-01 01:47:29

Re: kernel panic after pacman upgrade [solved]

#19 2007-03-01 01:55:34

Re: kernel panic after pacman upgrade [solved]

#20 2007-03-03 17:45:34

Re: kernel panic after pacman upgrade [solved]

#21 2007-03-03 22:11:45

Re: kernel panic after pacman upgrade [solved]

#22 2007-03-03 23:48:38

Re: kernel panic after pacman upgrade [solved]

#23 2007-03-05 02:20:10

Re: kernel panic after pacman upgrade [solved]

#24 2007-03-05 04:59:58

Re: kernel panic after pacman upgrade [solved]

Board footer