I had this same issue as I was trying to perform regular updates in Jaunty.
Based on the comments here, I changed one line from:
# updatedefaultentry=true
to:
# updatedefaultentry=false
The update succeeded this time. I restored the original line afterwards.
It seems to be related to certain entries related to a 160GB IDE hard disk that insists on being the boot drive if it is connected. My other hard drives are SATA. I have attached the output from fdisk -l.
All of my Linux partitions are reiserfs, except for /dev/sdc5, which is ext2.
sda = SATA
sdb = SATA
sdc = IDE
The entries in menu.lst:
boot hard drive that I had removed. I think, but can not guarantee, that this is the first kernel update since I removed the hard disk permanently. I had used grub to install to both hard drives, knowing that I would be experimenting with the removal of the one, but still wanted the computer to boot with only the first hard drive connected.
I am willing to help test if anyone has suggestions.
I had this same issue as I was trying to perform regular updates in Jaunty.
Based on the comments here, I changed one line from: try=true try=false
# updatedefaulten
to:
# updatedefaulten
The update succeeded this time. I restored the original line afterwards.
It seems to be related to certain entries related to a 160GB IDE hard disk that insists on being the boot drive if it is connected. My other hard drives are SATA. I have attached the output from fdisk -l.
All of my Linux partitions are reiserfs, except for /dev/sdc5, which is ext2.
sda = SATA
sdb = SATA
sdc = IDE
The entries in menu.lst:
boot hard drive that I had removed. I think, but can not guarantee, that this is the first kernel update since I removed the hard disk permanently. I had used grub to install to both hard drives, knowing that I would be experimenting with the removal of the one, but still wanted the computer to boot with only the first hard drive connected.
I am willing to help test if anyone has suggestions.