You are not logged in.

#1 2008-01-08 10:53:46

corrupt
Member
Registered: 2007-06-25
Posts: 74

grub error 18 after kernel panic

bash-3.2$ uname -a
Linux myhost 2.6.23-ARCH #1 SMP PREEMPT Fri Dec 21 19:39:35 UTC 2007 i686 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux

So in the morning after I boot pc, watch some video using smplayer, it ends, then kernel panic occurs.
I reboot and grub shows me "grub error 18" and of course doesn't boot. Then I fix this problem with the help of
grub-install tool. And everything is fine, for now. Anyone familiar with this problem? Should I expect something bad(and maybe back up my hdd)?

also in errors.log I've got this:

Jan  8 12:23:42 myhost ata5.00: exception Emask 0x1 SAct 0x0 SErr 0x300000 action 0x2
Jan  8 12:23:42 myhost ata5.00: CPB resp_flags 0x11: , CMD error
Jan  8 12:23:42 myhost ata5.00: cmd c8/00:90:6e:c1:b1/00:00:00:00:00/e2 tag 0 cdb 0x0 data 73728 in

repeated five times(maybe this will tell some additional info).

Offline

#2 2008-01-09 14:50:17

byte
Member
From: Düsseldorf (DE)
Registered: 2006-05-01
Posts: 2,046

Re: grub error 18 after kernel panic

You could install smartmontools and post smartctl -a output for that drive. Running smartctl -t long /dev/sdX might also be a good idea, but that'll take a while with the current, large disks.


1000

Offline

#3 2008-01-11 15:44:15

corrupt
Member
Registered: 2007-06-25
Posts: 74

Re: grub error 18 after kernel panic

Unfortunately, I have sata drive and new library libata and "it won't work correctly because libata doesn't yet support the needed ATA-passthrough ioctl() calls". Some other programs that support sata drives?

Offline

#4 2008-01-11 17:44:36

byte
Member
From: Düsseldorf (DE)
Registered: 2006-05-01
Posts: 2,046

Re: grub error 18 after kernel panic

man smartctl wrote:

For SATA disks accessed with libata, use "/dev/sd[a-z]" and append "-d ata"

Tried that option already?


1000

Offline

#5 2008-01-11 22:37:01

corrupt
Member
Registered: 2007-06-25
Posts: 74

Re: grub error 18 after kernel panic

Thanks, byte. The problem was solved by executing this command as root.

Offline

Board footer

Powered by FluxBB