Re: [Cooker] glibc upgrade causes disk read failures
On Monday 13 May 2002 00:52, Lonnie Borntreger wrote: I tried to upgrade from glibc 2.2.4 to 2.2.5. Upon rebooting I got a whole bunch of dma read failures on my disk (ext3) right after I got the message that it was starting init. Obviously this made so that none of the filesystems got mounted, and none of the init scripts ran. Downgrading again (using a rescue CD), corrected the problem. This doesn't make sense since LILO was able to read everything just fine, and the kernel had no problem reading/loading the modules it needed, it happened after the kernel finished loading. Everything ran correctly during the time between upgrading the libs and the reboot. I'm at a loss. Did I miss something? I think your problem can be atributed to the headers being tied to the glibc libraries. -- Altoine B Maximum Time Unlimited Chicago Based and Operated When a man's wife learns to understand him, she usually stops listening to him -- Murphy's Laws on Sex n°13 --- 2.4.18-16mdk Mandrake Linux release 8.3 (Cooker) for i586
Re: [Cooker] glibc upgrade causes disk read failures
On 13 May 2002 00:52:39 -0500 Lonnie Borntreger [EMAIL PROTECTED] wrote: I tried to upgrade from glibc 2.2.4 to 2.2.5. Upon rebooting I got a whole bunch of dma read failures on my disk (ext3) right after I got the message that it was starting init. Obviously this made so that none of the filesystems got mounted, and none of the init scripts ran. Downgrading again (using a rescue CD), corrected the problem. This doesn't make sense since LILO was able to read everything just fine, and the kernel had no problem reading/loading the modules it needed, it happened after the kernel finished loading. Stupid question, but... You did upgrade the rest of the distro? I mean, you did not install this glibc from cooker on a 8.2 system I hope? -- Marcel Pol Linux 2.4.18-13mdksmp, up 5 days, 23:55
Re: [Cooker] glibc upgrade causes disk read failures
On Mon, 2002-05-13 at 05:27, Marcel Pol wrote: On 13 May 2002 00:52:39 -0500 Lonnie Borntreger [EMAIL PROTECTED] wrote: I tried to upgrade from glibc 2.2.4 to 2.2.5. Upon rebooting I got a whole bunch of dma read failures on my disk (ext3) right after I got the message that it was starting init. Obviously this made so that none of the filesystems got mounted, and none of the init scripts ran. Downgrading again (using a rescue CD), corrected the problem. This doesn't make sense since LILO was able to read everything just fine, and the kernel had no problem reading/loading the modules it needed, it happened after the kernel finished loading. Stupid question, but... You did upgrade the rest of the distro? I mean, you did not install this glibc from cooker on a 8.2 system I hope? I run 100% cooker, updated with urpmi/rpmdrake every two to three days. (although due to gcc 3.1-3.0.4 clashes, I haven't been able to update gcc and so I'm falling a little behind.) -- TTFN, Lonnie Borntreger
[Cooker] glibc upgrade causes disk read failures
I tried to upgrade from glibc 2.2.4 to 2.2.5. Upon rebooting I got a whole bunch of dma read failures on my disk (ext3) right after I got the message that it was starting init. Obviously this made so that none of the filesystems got mounted, and none of the init scripts ran. Downgrading again (using a rescue CD), corrected the problem. This doesn't make sense since LILO was able to read everything just fine, and the kernel had no problem reading/loading the modules it needed, it happened after the kernel finished loading. Everything ran correctly during the time between upgrading the libs and the reboot. I'm at a loss. Did I miss something? -- TTFN, Lonnie Borntreger
