On Sat, Apr 11, 2009 at 9:29 AM, Timothy D. Lenz <tlenz@xxxxxxxxxx> wrote: > From: "CoolCold" <coolthecold@xxxxxxxxx> > >> Yes, he should provide correct /etc/mdadm/mdadm.conf and >> update-initramfs -u on md boot, smth like >> chroot /mnt/md0 >> update-initramfs -u > > How would this help in a system that doesn't ramdisk built in to the kernel or as a module? Or does it change some other stuff? Looking into "I have 2 computers that I am trying to convert to raid. Both where setup with debian netinst cd to hda" - debian has initrd support within their kernels. > > > I started looking at the stuff that was copied to md0 and /md0/dev is empty. Looking through the guides I found a few things. One > said that using cp had to be from root or not everything would get coppied. I used sudo but I know some things require you to root. > Also this: > =============================== > # rsync -avHhx --progress / /mnt/raid-md0 > > * If the system wasn't previously in single user mode, move to single user mode and update the data that changed during the > first copy: > (--delete flag tells rsync to delete files from the destination which do not exist on the source): > > # rsync -avHhx --progress --delete / /mnt/raid-md0 > > * Create needed device nodes: > > # cd /mnt/raid-md0/dev/ && MAKEDEV generic > =============================== > Using rsync from single user mode still left /mnt/md0/dev empty. I read up in "makedev generic" and it seems to be a shotgun fix > adding way more then is needed. Is there a way to create just what is in /dev? > > -- > 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 > -- -- Best regards, [COOLCOLD-RIPN] -- 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
