> > Removing the firewire drive when booting doesn't change anything, > right?
Correct. > > >What could be worth a try (unless grub devs show up): > > > > > >* try initramfs-tools >= 0.95.1 > > >* try removing all devices except one disk from the raid1 array > > > > > > and try booting from the single disk then > > > > Uhhh? I use this computer on a daily basis! You are going to have to > > convince me before I experiment anymore. > > > > For trying a new initramfs-tools, I don't think I will be doing that at > > all. For removing all devices from the raid1 array, see the previous > > paragraph... > > I just uploaded initramfs-tools 0.96.1, just upgrade it and give it > a shot. Booting from the single disk isn't necessary therefore, > that would be just another method to isolate the bug. I loaded and booted after the initramfs-tools 0.96.1. The problem persists; I still have to use the backup image to boot the machine. It has something to do with grub not being able to read the image; at least this is what a random error message indicates before the kernel panic previously posted (under Bug#582177) occurs. C. Cropper -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201006092244.29261.crop...@acm.org
