>
>Can you please provide output of "cat /proc/mdstat" of
>the running linux system?
>

root@loomis:/# cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4]
md1 : active raid6 sdg4[0] sde4[5](S) sdf4[4] sdb4[3] sdd4[2] sdc4[1]
5851753728 blocks level 6, 256k chunk, algorithm 2 [5/5] [UUUUU]

md0 : active raid1 sdb2[0] sdd2[2](S) sde2[3](S) sdf2[4](S) sdg2[5](S) sdc2[1]
249792 blocks [2/2] [UU]

unused devices: <none>



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201006072127.28639.cropper@acm.org">http://lists.debian.org/201006072127.28639.cropper@acm.org

* Cropper, C. A. <cropper@acm.org> [Mon Jun 07, 2010 at 09:27:28 -0400]:

> >Can you please provide output of "cat /proc/mdstat" of
> >the running linux system?

> root@loomis:/# cat /proc/mdstat
> Personalities : [raid1] [raid6] [raid5] [raid4]
> md1 : active raid6 sdg4[0] sde4[5](S) sdf4[4] sdb4[3] sdd4[2] sdc4[1]
> 5851753728 blocks level 6, 256k chunk, algorithm 2 [5/5] [UUUUU]

> md0 : active raid1 sdb2[0] sdd2[2](S) sde2[3](S) sdf2[4](S) sdg2[5](S) sdc2[1]
> 249792 blocks [2/2] [UU]

> unused devices: <none>

Looks ok. /dev/sda is the device you're booting from?

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

regards,
-mika-

>
>Looks ok. /dev/sda is the device you're booting from?

I don't know. The bios is set to boot from SAS disk 0 which is **usually**
/dev/sda; however, when my firewire drive is connected, on boot all the drives
are shifted one drive letter.
/dev/sda => /dev/sdb
/dev/sdb => /dev/sdc ... etc


>
>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...

C. Cropper



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201006080828.59115.cropper@acm.org">http://lists.debian.org/201006080828.59115.cropper@acm.org

* Cropper, C. A. <cropper@acm.org> [Tue Jun 08, 2010 at 08:28:58AM -0400]:

> >Looks ok. /dev/sda is the device you're booting from?

> I don't know. The bios is set to boot from SAS disk 0 which is **usually**
> /dev/sda; however, when my firewire drive is connected, on boot all the drives
> are shifted one drive letter.
> /dev/sda => /dev/sdb
> /dev/sdb => /dev/sdc ... etc

Removing the firewire drive when booting doesn't change anything,
right?

> >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.

regards,
-mika-

>
> 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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201006092244.29261.cropper@acm.org">http://lists.debian.org/201006092244.29261.cropper@acm.org