On Thu, Apr 2, 2009 at 5:22 PM, thveillon.debian < [email protected]> wrote:
> Joey L wrote : > > Tom - thanks for the reply - > > Do you think that is the issue ??? > > I am running mirrored drives for /boot. I can not boot off of lvm. > > I have the rest of my drives on software raid5 and i have created lvm > > volume groups and put my / filesystem allong with everything else on > them. > [...]pasted here from lower by me because it relates to the same problem > > I am also getting messeges that raid or array "failed to assemble all > > arrays" ?? This array is working fine under the old kernel - the 2.6.18 > > ... Is there somehting special in the command that i have to run for an > > array configuraiton with lvm ???? > > So you need raid1, raid456 and md_mod loaded at boot time. I use Grub2 > which can load those modules even before the initrd is loaded, so if > you're using grub "legacy" you're going to boot from one of the disks in > the array, have the initrd loaded, and with it must come along raid1, > raid456 and md_mod modules to assemble the arrays. > I think installing mdadm should trigger the inclusion of the modules in > the initrd, but if in doubt add raids and md_mod to > /etc/initramfs-tools/modules > > echo -e "raid1\nmd_mod\nraid456" >> /etc/initramfs-tools/modules > > and rebuild your initrd > > update-initramfs -u -k kernelversion > > > where the "kernelversion" string is the target kernel version > (2.6.29-mykernel), or $(uname -r) for the running kernel, or "all" for > any possible kernel in the known universe ;-) > It's also a good idea to have the partition type of the arrays members > set to "fd" (raid-autodetect) if it's already done. > > I don't use lvm, but I think the important thing is to get your arrays > up, the lvm initialization is done through /etc/init.d/lvm I believe. > > > > > Do you think the issue is that between the 2.6.18 kernel and the 2.6.29 > > kernel - there was a change in the drive naming convention ???? where > > the hd* are now sd* ??? > > > > > > I am concerned if i try to change it, the system will not boot. > > > > When compiling the kernel...does this stuff not happen automatically ??? > > A change occurred in kernel 2.6.19 and up which triggers the naming > convention to shift from hd* to sd* for most configurations. Since > several configuration files relies on this naming convention it's a good > idea to check (fstab, mtab, menu.lst and device.map). A good way around > this in fstab, mtab and menu.lst is using labels or UUID. > It doesn't (at least always) happen automatically in my painful experience > ! > If you change that (hd* to sd*) and try to boot on the old kernel, > you're heading to a nice black screen... Use UUID's or labels to avoid > the need to shift configuration files in between boot attempts. > > Tom - thanks for the points..but need more help !! please I did as you said - 1. echo -e "raid1\nmd_mod\nraid456" >> /etc/initramfs-tools/modules 2. update-initramfs -u -k 2.6.29 and i saw that the modules all loaded successfully. But i still got the error that it was unable to assemble all arrays. am i missing something ??? here are my other files: fstab: # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 /dev/mapper/vg_main-lv_root / ext3 defaults,errors=remount-ro 0 1 /dev/mapper/vg_main-bk_data /data ext3 defaults,errors=remount-ro 0 1 /dev/mapper/vg_main-lv_music /music ext3 defaults,errors=remount-ro 0 1 /dev/md0 /boot ext3 defaults 0 2 /dev/mapper/vg_main-lv_swap none swap sw 0 0 /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0 # usbfs /proc/bus/usb usbfs auto 0 0 # USB for vmware/vbox # none /proc/bus/usb usbfs devgid=5002,devmode=664 0 0 mtab: /dev/mapper/vg_main-lv_root / ext3 rw,errors=remount-ro 0 0 tmpfs /lib/init/rw tmpfs rw,nosuid,mode=0755 0 0 proc /proc proc rw,noexec,nosuid,nodev 0 0 sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0 procbususb /proc/bus/usb usbfs rw 0 0 udev /dev tmpfs rw,mode=0755 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0 /dev/mapper/vg_main-bk_data /data ext3 rw,errors=remount-ro 0 0 /dev/mapper/vg_main-lv_music /music ext3 rw,errors=remount-ro 0 0 /dev/md0 /boot ext3 rw 0 0 menu.lst: title Debian GNU/Linux, kernel 2.6.29 (single-user mode) root (hd0,0) kernel /vmlinuz-2.6.29 root=/dev/mapper/vg_main-lv_root ro single initrd /initrd.img-2.6.29 savedefault title Debian GNU/Linux, kernel 2.6.18-6-amd64 root (hd0,0) kernel /vmlinuz-2.6.18-6-amd64 root=/dev/mapper/vg_main-lv_root ro initrd /initrd.img-2.6.18-6-amd64 savedefault title Debian GNU/Linux, kernel 2.6.18-6-amd64 (single-user mode) root (hd0,0) kernel /vmlinuz-2.6.18-6-amd64 root=/dev/mapper/vg_main-lv_root ro single initrd /initrd.img-2.6.18-6-amd64 savedefault
