(Jul 07 2005 09:39) Brian Wilson wrote: > Hello -- > > Has anyone succeeded installing 3.0 onto a sw RAID?
I'm guessing I have done this about 150 times during installer development, so yes... :) > It seemed to just ignore my requests to put things on RAID > for / and /boot and installed on /dev/hda anyway. Do you follow the instructions in the installation manual? It seems to me you may be misunderstanding something in the RAID setup. Can you explain in detailed steps how you try to set up RAID? > Also what's with the funny device names? We use evms as backend for the partition part of the installer. Stripping them sounded a bit hackish, so we decided to simply show the user what was really going on. > Is /dev/evms/md/md0 better than /dev/md0 ?? No. But /dev/evms/md/md0 is what is actually used. > I also tried building a RAID1 setup manually and copying things > over with cpio. This worked for 2.2, I have 5 servers running > this way now. Sounds like a hack. TSL 3.0 actually has excellent support for SW RAID setup during installation. In my opinion way better than that of the old installer in 2.2. > When booting into it, it carps about /sysroot/initrd > being missing, drops to a prompt giving detailed instructions on > how to fix it, which of course, do not work. Since you created your system using mdadm and cpio, you need to create an initramdisk that actually handles the raid. It's what you get for doing things manually. :) > This seems like a problem with the initrd image. I figured out I could > mount it with 'mount -o loop -t cramfs /boot/initrd-<VERSION>.img > /mnt' and poke around in it, but cannot modify it. That's because it's a cramfs. It's always read only. Read the manual page of mkinitrd and create a new initrd that works instead of trying to fix the broken one by hand. kind regards c -- Christian H. Toldnes Trustix Developer _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
