error ICRC ABRT at boot, impossible to log in

[Tib-Tib]

Hi,
I just got a laptop (DELL PP06S) from a friend set up on kubuntu. He told me to download and run the updates packages if I had time. So so did I and now the computer stops on an error at boot and I can't log in at all to type any command.
The error message coming up is:

ata1.00: exeption Emask 0x0 SAct 0x0 action 0x6
ata1.00: BMDMA stat 0x24
ata1.00: failed command: WRITE DMA
ata1.00: cmd ca/00:38:e7:14c/00:00:00:00/e0 tag 0 dma 28672 out
ata1.00: res 51/84:00:1e:15:7c/00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }

And it seems to try that action over and over but I never get to log in and type any command.

Does anyone have any idea of what I could do?

Thanks heaps

TiBo

[lmilano]

Re: error ICRC ABRT at boot, impossible to log in

Hi, welcome to the forum

Do you see a bootup (grub) menu before the operating system starts loading? If it does, please try with the different boot options there. I suspect you have a new kernel that is not booting up for some reason. Maybe worth a try?

[dibl]

Re: error ICRC ABRT at boot, impossible to log in

ata1.00: failed command: WRITE DMA
ata1.00: cmd ca/00:38:e7:14c/00:00:00:00/e0 tag 0 dma 28672 out
ata1.00: res 51/84:00:1e:15:7c/00:00:00:00/e0 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { ICRC ABRT }

Those are coming from the libata hard disk driver: https://ata.wiki.kernel.org/index.ph...error_messages

Usually indicates IRQ interference of some kind. Try booting with noapic and noacpi options, first one at a time, and then with both of them.

[lmilano]

Re: error ICRC ABRT at boot, impossible to log in

Ah, good idea dibl!

Instructions here:
https://help.ubuntu.com/community/Grub2#Editing Menus During Boot

You need to add these option in the line where you see "ro quiet splash". You can also try nolapic.

[Tib-Tib]

Re: error ICRC ABRT at boot, impossible to log in

The different options available in the GRUB menu are:

Ubuntu, with Linux 2.6.32-26-generic
Ubuntu, with Linux 2.6.32-26-generic (recovery mode)
Ubuntu, with Linux 2.6.32-25-generic
Ubuntu, with Linux 2.6.32-25-generic (recovery mode)
Ubuntu, with Linux 2.6.32-24-lowlatency
Ubuntu, with Linux 2.6.32-26-lowlatency (recovery mode)
Memory test (memtest86+)
Memory test (memtest86+, serial console 115200)

And they all (exept memory test) bring me back to the same error message and no way to get a console.

From my understanding these are the new and older kernels, is that right?
I had to do the updates in 3 times so I guess the kernel from before then isn't in the list anymore.

dibl and lmilano's comments sound very helpful but unfortunately I don't quite know how to proceed.
I looked at the link lmilano sent but didn't find out how to proceed.

Could you please give me the procedure step by step?

Thanks

[vinnywright]

Re: error ICRC ABRT at boot, impossible to log in

so you highlight one of the Kernel entrys

then pres e i think it is to edit the boot string (it is writen under the kernel list)

then remove the quiet splash and add the ones dibl & lmilano gave you as thay discribed.

VINNY

[lmilano]

Re: error ICRC ABRT at boot, impossible to log in

Yes, Vinny is right, you press "e" to edit the kernel of choice, try the latest one (2.6.32-26-generic). You also need ctrl-x to boot after editing. Also, note that the link I posted before was broken . Let me try again (if it doesn;t work, please go to section "Editing Menus During Boot"):

https://help.ubuntu.com/community/Gr...us During Boot

Oh, and yes, what you are seeing are all the kernels present in the system, new an old. Keep us posted!

[Tib-Tib]

Re: error ICRC ABRT at boot, impossible to log in

Thanks for all that!

I actually managed to get on the website after I posted, I found the infos you were pointing out and it was quite useful.

So I tried noapic, noacpi and then nolapic with each of the kernels but none worked.

The same error message keeps coming up.
Sometimes the start screen shows up with Ubuntu 10.04 and the 4 dots, then it goes to a busy cursor like if it was gonna start but then the error message comes back.

I think am gonna go for the rescue USB stick (got no CD player)

Unless anyone has any other suggestion?

[vinnywright]

Re: error ICRC ABRT at boot, impossible to log in

how did you do your upgrades?
and did they complete with ought error?

can you boot (recovery mode)? if you can and get a maintenance shell do

sudo apt-get update && sudo apt-get upgrade

and see if you get eney errors!

VINNY

[Tib-Tib]

Re: error ICRC ABRT at boot, impossible to log in

My updates were kind of complicated, I started with the normal way (running the upgrade package from the desktop) but my connection cut off half way through and when I rebooted, impossible to get back on the desktop.
Had to find a plug in connection and I did the upgrades through the console with "sudo apt-get update" then "sudo apt-get upgrade" and I had to do that twice.

Since then no way to start it anymore.

Even Recovery mode does not make any difference.

Where can I ownload the recovery CD?

[lmilano]

Re: error ICRC ABRT at boot, impossible to log in

I found some interesting suggestions here:
https://bugs.launchpad.net/ubuntu/+s...ux/+bug/397096

This might help:

Ok, I am doing an experiment. So far it worked... I went to BIOS and changed from SATA mode, to AHCI mode. My BIOS is an ASUS Bios, M3A78-EM. There is SATA Configuration entry right in the first BIOS screen. Then it gives you three modes:

SATA
RAID
AHCI

It was on SATA all this time, and I have changed to AHCI.
So far problem is gone.

Another thing to try, perhaps, is this:

(some of these) kernel command line parameters: hpet=disable highres=off nohz=off nohdparm

Hope one of these helps, I'll hunt for the 10.04 download in the meantime ...

[edit: you can download the latest update to 10.04 here: http://www.kubuntu.org/getkubuntu/do...ownload-block]

[Tib-Tib]

Re: error ICRC ABRT at boot, impossible to log in

Right!

after hours and hours of unsuccessful trials from different suggestions from different members of different forums, I decided to reinstall the whole thing.
Really that's what I should have done from the start!

Though the same error message seems to still show up at the start very quickly but everything runs perfectly.

And my hard drive seems to work perfectly fine.

Thanks everyone for your help!

TiBo