this in
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5334838b.5030...@b2-fortbildung.de
ladly
do two-to-three more until the computer is deactivated. Please get any tests
or instructions to me soon.
Regards,
C. Cropper
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or
the original problem. Repeat: I do NOT need to load the initramfs
backup image now.
The above acts identically with and without the firewire device attached.
I am still using the 0.96.1 version of initramfs-tools.
C. Cropper
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.o
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 messa
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-requ...@lists.
>
>Can you please provide output of "cat /proc/mdstat" of
>the running linux system?
>
r...@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
"synchronize"? I don't understand...
I have actually pulled different devices in-and-out of the MD devices, let the
MD driver "rebuild" each MD device and made sure the "real" sda is disk number
0. It does not seem to change...
C. Cropper
>
> To
ted (no evidence of
drivers loading)
___
Questions:
1) Could this be grub?
2) Could "resynchronizing" md0 fix this problem? I seem to remember doing
something like this and the problem went away in March... :-/
3) Any other suggestions?
Thank
dvise...
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/201005191036.10170.crop...@acm.org
rerun update-grub)
the computer will still NOT boot (i.e it still fails to load the ramdisk).
Summary: I am wondering if this is a GRUB problem. I still believe it is a
initramfs-tools problem because it only happened when the initramfs-tools
package was changed.
C. Cropper
--
To
e
hard drives or any USB devices for that mater, 2) fails to start the RAID
devices, and thus 3) the kernel panics at about 2secs into the boot sequence.
Thank you for all your work. Squeeze really is shaping into a mighty force.
C. Cropper
-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=
11 matches
Mail list logo
