Ubuntu
grub2 package

ubuntu 10.10 ata boot SError after kernel-update

Asked by nillz

Hello, after a kernel-update i get this error while booting:

ata8: irq_stat 0x00000040, connection status changed
SError: { DevExch }
exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen

This error occures in an infinite loop. Ubuntu does not start.

My System: Dual-Boot: Ubuntu 10.10 and Win7 Prof.

lsscsi
[0:0:0:0] disk ATA Seagate FreeAgen 4115 /dev/sda (external esata)
[3:0:0:0] disk ATA SAMSUNG HD322HJ 1AC0 /dev/sdb (boot, internal, mountpoint /)
[6:0:0:0] cd/dvd HL-DT-ST DVD-RAM GH22LP20 1.02 /dev/sr0
[6:0:1:0] disk ATA ST3250820A 3.AA /dev/sdc (internal)

fstab
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=f4b6da29-8511-4e8c-93a0-302203bf0a9d / ext4 errors=remoun$
# swap was on /dev/sda5 during installation
UUID=228ea939-3b3b-4586-afa4-11f7f38d2462 none swap sw $
#freeagent drive
UUID=AA289EB3289E7E4F /media/FREEAGENT ntfs-3g auto,user 0 2

grub.cfg
[...]
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.35-24-generic' --class ubuntu --class gnu-lin$
        recordfail
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set f4b6da29-8511-4e8c-93a0-302203bf0a9d
        linux /boot/vmlinuz-2.6.35-24-generic root=UUID=f4b6da29-8511-4e8c-93$
        initrd /boot/initrd.img-2.6.35-24-generic
}
[...]
menuentry 'Ubuntu, with Linux 2.6.35-23-generic' --class ubuntu --class gnu-lin$
        recordfail
        insmod part_msdos
        insmod ext2
        set root='(hd0,msdos1)'
        search --no-floppy --fs-uuid --set f4b6da29-8511-4e8c-93a0-302203bf0a9d
        linux /boot/vmlinuz-2.6.35-23-generic root=UUID=f4b6da29-8511-4e8c-93$
        initrd /boot/initrd.img-2.6.35-23-generic
}
[...]
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows 7 (loader) (on /dev/sdb1)" {
        insmod part_msdos
        insmod ntfs
        set root='(hd1,msdos1)'
        search --no-floppy --fs-uuid --set 06df17ad7dba989d
        chainloader +1
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu grub2 Edit question
Assignee:
No assignee Edit question
Solved by:
nillz
Solved:
Last query:
Last reply:
Revision history for this message
Tom (tom6) said : 		#1

Hi :)

From the top taskbar click on

Applications - Accessories - Terminal

and try use the mouse right-click menus to copy&paste the output of this command into here

sudo fdisk -l

where "-l" is a lower-case "-L". This shows the layout of the partitions on your hard-drive. All that we probably need to do is reinstall grub2 to the Ubuntu linux partition, in which case the previous command is step 3 of this guide
https://help.ubuntu.com/community/Grub2#Reinstalling%20from%20LiveCD

Please let us know how the "sudo fdsik -l" goes so that we can guide you through the rest of that guide!
Good luck and regards from
Tom :)

Revision history for this message
nillz (nillz) said : 		#2

Hi, thanks for your answers. But this is not the solution. I had previously tested this solution. Perhaps i did something wrong. Other ideas?

The steps and results:
===============================================
(without my external drive)
fdisk -l

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000488f9

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 38184 306709504 83 Linux
/dev/sda2 38184 38914 5859329 5 Extended
/dev/sda5 38184 38914 5859328 82 Linux swap / Solaris

Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb208f51f

   Device Boot Start End Blocks Id System
/dev/sdb1 * 1 30401 244196001 7 HPFS/NTFS

====================================================
A) boot from livecd 10.10
1. sudo mount /dev/sda1 /mnt
2. sudo grub-install --root-directory=/mnt/ /dev/sda
(no errors)
3. reboot

and then the same error as before. Ubuntu doesn't boot. So i have tested the supergrubdisk.

B) boot from supergrubdisk
1. detect OS -> boot from linux
the system hangs during bootup at this step:

"sdb:
ata7: SATA link down SStatus 0 SControl 300
ata8: SATA link down SStatus 0 SControl 300
sdb1
sd 4:0:1:0 [sdb] Attached SCSI disk"

regards
Nils

Revision history for this message
nillz (nillz) said : 		#3

my problem in german http://forum.ubuntuusers.de/topic/ata-boot-serror-nach-kernel-update-2/

Revision history for this message
delance (olivier-delance) said : 		#4

Could you boot on third line of boot Grub menu, i.e. from old kernel, and so confirm issue is really linked to new kernel, and not another updated packet.

Revision history for this message
Tom (tom6) said : 		#5

Hi :)

I don't really trust SuperGrubDisk because i have never used it. Your steps with the Ubuntu LiveCd looked about perfect tho. Could you re-try but using an Ubuntu 10.04 or another Ubuntu that is not in alpha/beta testing? 9.10, 10.04 or 10.10 would be perfect.

That should give you a boot-menu with several options in it, including a few options to boot into previous kernels as Delance suggested? Please try a couple of previous kernels, ie ones that you know you have successfully used previously.
Regards from
Tom :)

Revision history for this message
nillz (nillz) said : 		#6

this is the solution:

boot from livecd 10.10
test ubuntu --> open terminal

sudo mount /dev/sda1 /mnt
sudo mount -o bind /proc /mnt/proc
sudo mount -o bind /dev /mnt/dev
sudo mount -o bind /sys /mnt/sys
sudo chroot /mnt
dpkg --configure -a
apt-get update
apt-get upgrade
exit
reboot

it probably was a bug...
regards
Nils

Revision history for this message
Tom (tom6) said : 		#7

Wow! That is a somewhat awesome answer. thanks for posting it back into this thread! I agree the problem may have been a bug and worth posting as a bug-report. I am just really glad you have fixed it :)
Congrats and regards from
Tom :)