I did a clean install of Cassandra (final) on my "test" system and it installs and restarts fine. Everything seems to function properly, and all drives are accessible. It will continue to run fine if I don't do the "recommended" updates that I get prompted to install.
There is a HAL update that seems to go in fine. Then a moment later I am asked to do 18 more updates, and those too seem to install fine. I get a message that all updates installed successfully and my system is up to date. Then the restart icon appears in the tray telling me a restart is needed.
So I click on the icon and the system shuts down normally, but it won't start up again. The system reboots and the Mint splash screen appears, and when the progress bar is about 1.5 ticks up from the beginning it hangs for a very long time. Eventually the splash screen goes away and I am greeted by part of the text boot process, with a red [fail] message that looks like it's after "Loading hardware drivers..."
There is also another error:
"modprobe: WARNING: Not loading blacklisted module ipv6"
but I see that message a lot, even on systems that boot and run fine.
Then the system does a check of the root file system and that passes, and the next message is "* Checking file systems..." and it doesn't get any further than that.
If I unplug my 2 SATA data drives the system will boot normally.
Something that is being updated is breaking SATA support in Cassandra!
This system is pretty standard Intel hardware. 865/ICH5 chipset with a P4 2.4GHz processor and a gig of RAM. It's got an IDE boot drive and optical drive, and 2 sata drives for extra storage.
Anyone else run into this?
And, is there anything I can do to fix it?
Update to 2.6.20-16 kernel breaks SATA in Feisty/Cassandra!
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Update to 2.6.20-16 kernel breaks SATA in Feisty/Cassandra!
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Looks like it's a problem with the new kernel... 
https://bugs.launchpad.net/ubuntu/+sour ... bug/116996
Hopefully a fix is coming soon.
https://bugs.launchpad.net/ubuntu/+sour ... bug/116996
Hopefully a fix is coming soon.
Further reading indicates it may be limited to Intel ICH4, ICH5 & ICH6 controllers. So... if you have SATA drives on any of those controllers, you probably should not do the kernel updates until this has been fixed.
IDE drives seem to be fine. If I unplug my SATA drives, or turn off the SATA controller in the BIOS my system boots fine.
IDE drives seem to be fine. If I unplug my SATA drives, or turn off the SATA controller in the BIOS my system boots fine.
Updates break Feisty/Cassandra for SATA!
I unchecked the 2.6.20-16 kernel updates, thinking I could just install the other updates, and the kernel updates installed anyway! 
Fortunately it's just my test system, but still.... What's the point of the check boxes in the update manager if it's just going to ignore what I select and install them anyway?
And on top of that, it's still telling me those updates need to be installed, even though they were installed when I unchecked them!
Anyway... if anyone else runs into this problem and can't boot, you can still select the previous 2.6.20-15 kernel from the grub boot menu and that should let you boot. Kind of a pain to have to do that every time you want to boot. Fortunately Linux doesn't need to be restarted very often.
So, to recap:
The current 2.6.20-16 kernel breaks SATA support in Ubuntu Feisty and Mint Cassandra for most Intel ICH4, ICH5 & ICH6 controllers (although apparently not all of them). If you install the auto updates and are running any SATA drives on these controllers it is likely your system will fail to boot (or will boot with lots of problems).
If you run into this problem, hit escape at grub boot and select the previous 2.6.20-15 kernel from the menu and you should be able to get back into your system.
It looks like Debian had similar problems and it has been fixed. Hopefully Ubuntu will be fixed soon.
Fortunately it's just my test system, but still.... What's the point of the check boxes in the update manager if it's just going to ignore what I select and install them anyway?And on top of that, it's still telling me those updates need to be installed, even though they were installed when I unchecked them!
Anyway... if anyone else runs into this problem and can't boot, you can still select the previous 2.6.20-15 kernel from the grub boot menu and that should let you boot. Kind of a pain to have to do that every time you want to boot. Fortunately Linux doesn't need to be restarted very often.
So, to recap:
The current 2.6.20-16 kernel breaks SATA support in Ubuntu Feisty and Mint Cassandra for most Intel ICH4, ICH5 & ICH6 controllers (although apparently not all of them). If you install the auto updates and are running any SATA drives on these controllers it is likely your system will fail to boot (or will boot with lots of problems).
If you run into this problem, hit escape at grub boot and select the previous 2.6.20-15 kernel from the menu and you should be able to get back into your system.
It looks like Debian had similar problems and it has been fixed. Hopefully Ubuntu will be fixed soon.
-
Husse
That reminds me of 2.6.17-11... if you don't need to upgrade kernels, hal, dbus, xorg and sensitive things like that.. don't. The hal upgrade was unstable enough not to be included in Cassandra stable. Ubuntu is based on sid, not on testing, and as packages are concerned we're currently based on a non-long-term-support version of it: Feisty, so we can expect them to break a few things now and then... not to mention that all repositories are activated (including backports). Mint releases very frequently... you shouldn't have to upgrade.
In /boot/grub/menu.lst you can make 2.6.20-15 default.
Clem
In /boot/grub/menu.lst you can make 2.6.20-15 default.
Clem
I have never had any problems with the ICH controllers in Windows. I have several systems running on ICH5 and ICH5R controllers and they all work fine. My main system runs Win2K on a RAID-0 stripe and it is very fast (and, yes, I am aware of the risks of RAID-0, which should be called IAD since there is no redundancy).
It's surprizing this got out to the update channel. Those controllers are used on a LOT of motherboards, and SATA has become pretty popular in recent years. You'd think someone on the Ubuntu dev team would have that hardware. Oh well...
Clem,
Yes I shouldn't have to, but when I unchecked the kernel updates they installed anyway. The other updates said they were for security so I figured they were important. Either auto-update ignores the check boxes, or it was some kind of dependancy thing that forced the kernel update in spite of my de-selection.
For me this was a minor annoyance since it was only my test system. Fortunately my main box isn't running any SATA drives that Linux can see so the updates didn't mess anything up.
Aloha, Tim
It's surprizing this got out to the update channel. Those controllers are used on a LOT of motherboards, and SATA has become pretty popular in recent years. You'd think someone on the Ubuntu dev team would have that hardware. Oh well...
Clem,
Yes I shouldn't have to, but when I unchecked the kernel updates they installed anyway. The other updates said they were for security so I figured they were important. Either auto-update ignores the check boxes, or it was some kind of dependancy thing that forced the kernel update in spite of my de-selection.
For me this was a minor annoyance since it was only my test system. Fortunately my main box isn't running any SATA drives that Linux can see so the updates didn't mess anything up.
Aloha, Tim
-
Husse
@Lolo Uila
Long time since I had the unpleasant task of working with ICH 5 or 6, but it was unstable and completely impossible to make a decent RAID1 on it. Lost some money as I had to take back a bunch of mobos for that...
That said, it worked well on some motherboards, not on others...
It's not at all fun not to know if things will work or not when you sell the stuff....
Long time since I had the unpleasant task of working with ICH 5 or 6, but it was unstable and completely impossible to make a decent RAID1 on it. Lost some money as I had to take back a bunch of mobos for that...
That said, it worked well on some motherboards, not on others...
It's not at all fun not to know if things will work or not when you sell the stuff....
I experienced a similar problem with Cassandra: after 24 hours it was broken, I mean nothing was working anymore so I decided to do a fresh install of ... Bianca!
Now I have a question for you guys: is the problem only Feisty related or is it possible that the same disaster will happen also on Bianca?
Should I completely avoid updates?
If and when this bug is fixed, where can I find the announcement?
Thanks.
Now I have a question for you guys: is the problem only Feisty related or is it possible that the same disaster will happen also on Bianca?
Should I completely avoid updates?
If and when this bug is fixed, where can I find the announcement?
Thanks.
I was also a victim of the new kernel, Intel Chipset here too. I only have one sata hard drive and the system would boot. The new kernel gave me an extra CD-ROM drive that did not exist though! Oh well these things happen and I didn't lose any data because of it. Someone might want to create a sticky about this issue and maybe some notes in the Wiki to save other's from having this problem.
Another upgrade subject, if you have upgraded Gimp and would like the new splash screen back here is how to fix it.
From the Live CD go to terminal, sudo nautilus
Go to /usr/share/gimp/2.0/images and copy and save gimp-splash.png
Overwrite the file in the same directory (as root) in your installed version.
It is a minor thing but since someone took the time to make a nice looking splash I thought it was worth the time to put it back.
Another upgrade subject, if you have upgraded Gimp and would like the new splash screen back here is how to fix it.
From the Live CD go to terminal, sudo nautilus
Go to /usr/share/gimp/2.0/images and copy and save gimp-splash.png
Overwrite the file in the same directory (as root) in your installed version.
It is a minor thing but since someone took the time to make a nice looking splash I thought it was worth the time to put it back.
Okay, I spoke too soon. The new kernel messes up my main system as well if the SATA controller is enabled. Even though there are no SATA drives accessible to Linux!
This is related to the second problem with the new kernel. It changes the drive mount ID. If your fstab file has not been edited you may be okay. If you are using /dev/sd... instead of UUID then you will get hit by this bug too. It seems the new kernel is changing the way the drives are mounted, again. Some drives are going back to /dev/hd... while others remain /dev/sd... but are given new letters or numbers. Even without a modded fstab file some people on the Ubuntu forums have reported their optical drives aren't working (optical drives do not have a UUID and can be hit by this bug).
Man this new kernel is really a major screw up.
This is related to the second problem with the new kernel. It changes the drive mount ID. If your fstab file has not been edited you may be okay. If you are using /dev/sd... instead of UUID then you will get hit by this bug too. It seems the new kernel is changing the way the drives are mounted, again. Some drives are going back to /dev/hd... while others remain /dev/sd... but are given new letters or numbers. Even without a modded fstab file some people on the Ubuntu forums have reported their optical drives aren't working (optical drives do not have a UUID and can be hit by this bug).
Man this new kernel is really a major screw up.
Just checked, and I have FOUR optical drives now. Sheesh!
Two of them don't point to anything in particular, of course.
So it looks like my 4 IDE hard drives are still using the "sd" naming convention, but they have been changed from sda/b/c/d, to sdc/d/e/f. Note that these drives are not on the Intel controller; they are on an ITE controller chip. From what I have been reading, drives on the Intel controller get changed back to the "hd" naming convention used prior to Feisty (including optical drives).
Hmmm... my optical drives used to be (from fstab):
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/scd1 /media/cdrom1 udf,iso9660 user,noauto 0 0
And now they are "/dev/hda" & "/dev/hdc" according to the output of lshw.
description: IDE Channel 0
product: BENQ DVD DD DW1640
logical name: /dev/hda
description: IDE Channel 1
product: YAMAHA CRW-F1E
logical name: /dev/hdc
dmesg shows the same thing...
hda: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive.
hdc: ATAPI 44X CD-ROM CD-R/RW drive
So...
/dev/scd0 is now /dev/hda (primary master drive)
/dev/scd1 is now /dev/hdc (secondary master drive)
Which means my mobile rack drives will be "hdb" and "hdd" when I plug them in. This is really messed up. This update was called a "security" update, but it obviously has some major, untested changes in it and should NOT have been released yet.
Two of them don't point to anything in particular, of course.
So it looks like my 4 IDE hard drives are still using the "sd" naming convention, but they have been changed from sda/b/c/d, to sdc/d/e/f. Note that these drives are not on the Intel controller; they are on an ITE controller chip. From what I have been reading, drives on the Intel controller get changed back to the "hd" naming convention used prior to Feisty (including optical drives).
Hmmm... my optical drives used to be (from fstab):
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/scd1 /media/cdrom1 udf,iso9660 user,noauto 0 0
And now they are "/dev/hda" & "/dev/hdc" according to the output of lshw.
description: IDE Channel 0
product: BENQ DVD DD DW1640
logical name: /dev/hda
description: IDE Channel 1
product: YAMAHA CRW-F1E
logical name: /dev/hdc
dmesg shows the same thing...
hda: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive.
hdc: ATAPI 44X CD-ROM CD-R/RW drive
So...
/dev/scd0 is now /dev/hda (primary master drive)
/dev/scd1 is now /dev/hdc (secondary master drive)
Which means my mobile rack drives will be "hdb" and "hdd" when I plug them in. This is really messed up. This update was called a "security" update, but it obviously has some major, untested changes in it and should NOT have been released yet.
-
Husse
-
Husse
-
Husse
)-
oliverjames
- Level 4
- Posts: 418
- Joined: Fri Aug 10, 2007 3:00 am
- Location: Divonne-les-Bains, France
Having read this thread it seems I have fallen foul of the same problem. My laptop has Intel ICH4. I ran the updates (including the kernel) having installed Mint Casandra KDE alongside the XFCE version and Win XP.
A lot of very strange things have been happening with the KDE edition and I cannot do a straight boot of XFCE.
This is content of var/log/fsck/checkfs of the XFCE system.
Log of fsck -C -R -A -a
Tue Aug 21 14:59:12 2007
fsck 1.40-WIP (14-Nov-2006)
/dev/sda10: clean, 6258/523264 files, 681642/1046225 blocks (check in 3 mounts)
fsck.ext3: Unable to resolve 'UUID=2e03d251-f899-413d-b2b8-894b5bdce67c'
fsck.ext3: Unable to resolve 'UUID=32ac3c0b-cb48-4b3f-9161-7f6b1bbfd843'
fsck died with exit status 8
Tue Aug 21 14:59:12 2007
I will reboot with the previous kernel.
Do I need to do anything else to restore things to good health?
How do I uninstall the latest kernel in the 2 systems? Sorry to ask but I'm still feeling my way with Linux.
Thanks
Oliverjames
A lot of very strange things have been happening with the KDE edition and I cannot do a straight boot of XFCE.
This is content of var/log/fsck/checkfs of the XFCE system.
Log of fsck -C -R -A -a
Tue Aug 21 14:59:12 2007
fsck 1.40-WIP (14-Nov-2006)
/dev/sda10: clean, 6258/523264 files, 681642/1046225 blocks (check in 3 mounts)
fsck.ext3: Unable to resolve 'UUID=2e03d251-f899-413d-b2b8-894b5bdce67c'
fsck.ext3: Unable to resolve 'UUID=32ac3c0b-cb48-4b3f-9161-7f6b1bbfd843'
fsck died with exit status 8
Tue Aug 21 14:59:12 2007
I will reboot with the previous kernel.
Do I need to do anything else to restore things to good health?
How do I uninstall the latest kernel in the 2 systems? Sorry to ask but I'm still feeling my way with Linux.
Thanks
Oliverjames
at boot hit escape so you can see the boot menu.
you will now see the new kernel and the old one below it (third one).
boot off the old kernel.
open synaptic and look/search for the new kernel and choose to uninstall it.
apply.
now when you boot you will only have the old kernel.
you will now see the new kernel and the old one below it (third one).
boot off the old kernel.
open synaptic and look/search for the new kernel and choose to uninstall it.
apply.
now when you boot you will only have the old kernel.
Now where was i going? Oh yes, crazy!
-
Husse
@ oliverjames
You may have problems with the kernel, but your large problem is
You must have changed your disks so they got a new UUID, or the new kernel gave them a new UUID.
Check in /boot/gub/menu.lst and /etc/fstab for these UUIDs
Change the lines where they are so that it is the /dev/sdx you see directly above them that is used. Begin with fstab as you won't see the /dev in menu.lst. Remember you must be root to change these files.
If you need more help don't hestitate to post back
You may have problems with the kernel, but your large problem is
This is not going to be fixed with a different kernel I'm afraid. It's the dreaded UUID syndromefsck.ext3: Unable to resolve 'UUID=2e03d251-f899-413d-b2b8-894b5bdce67c'
fsck.ext3: Unable to resolve 'UUID=32ac3c0b-cb48-4b3f-9161-7f6b1bbfd843'
fsck died with exit status 8
You must have changed your disks so they got a new UUID, or the new kernel gave them a new UUID.
Check in /boot/gub/menu.lst and /etc/fstab for these UUIDs
Change the lines where they are so that it is the /dev/sdx you see directly above them that is used. Begin with fstab as you won't see the /dev in menu.lst. Remember you must be root to change these files.
If you need more help don't hestitate to post back