Comment 14 for bug 97325

I upgraded the kernel to 2.6.20-14.* and can confirm that this was a REGRESSION over 2.6.20-13:

On 2.6.20-13, I do get the fsck failure at boot, but continuing the boot without fsck'ing works: one of my 2 IDE disks gets automounted (it contains my /home, so fairly essential), the other is shown in the side panel of the GNOME file manager as "297 Gb Hard drive" and I can mount it to /media/disk by doubleclicking on it and entering my password. This is - needless to say - a hassle but acceptable: the disk is working but is not mounted to where I want it and where I have spesified it in fstab (I want it as /media/shared-files )

On 2.6.20-14 neither IDE disk is recognized at boot, causing the fsck failure at boot and when the login manager comes up, it gives me a warning that /home/{username} is not available and suggests I rectify it.

The two IDE disks are connected as master/slave on one of two ports on a PCI IDE controller card. As they work in 2.6.20-13 (with a bit of fiddling for the second disk) I assume the problem is not with this controller....?

I assume this is a regerssion in 2.6.20-14 over 2.6.20-13? Please let me know any additional info I can submit to help fix this issue?