Comment 5 for bug 30333

Revision history for this message
Chris Wagner (chris-wagner) wrote :

To confirm, I am *not* using the HPT370 controller (well, I don't know much what it is -- but I'm not using a RAID device, so...).

I don't believe this issue could be directly related to my hardware, due to the following (as stated in original report):
 * Moving the hard drive (that holds the failing installation) to another PC leads to the same results on that other PC, when booting.
 * For a fresh dapper installation (from the flight 2 CD) on another partition (of the same hard drive), this problem does not occur. I have since performed many "apt-get update; apt-get upgrade" commands on this installation and this problem has not re-occurred *on the 'clean' partition*.

Also notable is, I've since performed many updates to the "bad" installation by mounting the drive and chroot'ing; it still does not work.