On Monday August 28, jbrown@xxxxxxxxxx wrote: > Neil Brown wrote: > > On Saturday August 26, jbrown@xxxxxxxxxx wrote: > >> All, > >> > >> [...] > >> > >> * Problem 1: Since moving from 2.4 -> 2.6 kernel, a reboot kicks one > >> device out of the array (c.f. post by Andreas Pelzner on 24th Aug 2006). > >> > >> * Problem 2: When booting my system, unless both disks plugged in, I get > >> a kernel panic (oh dear!): > >> > >> > mdadm md0 stopped > >> > mdadm cannot open device /dev/hda6 no such device or address > >> > mdadm /dev/hda6 has wrong uuid > >> > mdadm no devices found for /dev/md0 > >> > ext3fs unable to read superblock > >> > ecit 2 - unable to read superblock cramfs > >> > kernel panic attempting to kill init > > > > At a guess, I'd say something is wrong with your initramfs/initrd. > > Can you look inside it and see what /etc/mdadm/mdadm.conf contains? > > Sure, this is the first time I've mounted an initrd, here goes: > > # file /boot/initrd.img-2.6.8-3-386 > [...]Linux Compressed ROM File System data, little endian size 4333568 > version #2 sorted_dirs CRC 0xa04ccaa3, edition 0, 2492 blocks, 312 files > > # losetup /dev/loop0 > > # mkdir /tmp/initrdmount > > # mount -t cramfs /dev/loop0 /tmp/initrdmount > > # ls -al /tmp/initrdmount/etc/ > total 1.0K > drwxr-xr-x 1 root root 64 1970-01-01 01:00 modprobe.d/ > -rw-r--r-- 1 root root 0 1970-01-01 01:00 mtab > > There is no mdadm/mdadm.conf! What I should do about this? Sorry, I don't think. You'll have to ask on some Debian list. I don't know the intricacies of Debian initrd. NeilBrown -- VGER BF report: U 0.5 - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
