Re: RAID1 install fails
On Mon, May 31, 2004 at 12:50:25PM -0300, Martin Michlmayr wrote: * W. Borgert [EMAIL PROTECTED] [2004-05-31 12:13]: GRUB message on vt3: /dev/md0 does not have any corresponding BIOS drive. LILO: An installation step failed. (...) failing step is: Install the LILO boot loader on a hard disk. I don't know how to get LILO and GRUB to boot from RAID. I thought it might just work... anyone got a good idea? When I set up raid, (I always to that after the installation), I edit the menu.lst manually, and changes /etc/kernel-img.conf to not run postinstall/prerm-hooks, but to place symlinks in /boot instead Then I make sure that to create symlinks for the already existing kernel-images. for more info, please see http://developer.skolelinux.no/dokumentasjon/skolelinux_softwareraid_howto.txt -- Finn-Arne Johansen [EMAIL PROTECTED] http://bzz.no/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 install fails
On Sun, May 30, 2004 at 08:50:31PM -0300, Martin Michlmayr wrote: add a line waypoint 5 install_extra so this looks like: waypoint 3 apt_update waypoint 5 install_extra waypoint 1 pick_kernel waypoint 10 install_kernel This should work. Yes, I get one step forward (Muehsam ernaehrt sich das Eichhoernchen) - now the installation of grub/lilo fails. GRUB message on vt3: /dev/md0 does not have any corresponding BIOS drive. LILO: An installation step failed. (...) failing step is: Install the LILO boot loader on a hard disk. Both / on XFS and / on EXT3 give this error. Note 1: The progress bar Starting up the partitioner hangs at 55% (Please wait...) while the RAIDs are synchronising. Because this can take several (e.g. 30) minutes, it would be nice to communicate that fact to the user. Note 2: With linux26 I get two errors: First the os-prober hangs (progress bar at 10%, I just killed the bastard), after grub install fails fatally, I get an endless loop Trying to enable the frame buffer... with a fancy flashing screen. Uhu, the 70s are back! I'm going to try this again with 2.4. Cheers, WB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 install fails
* W. Borgert [EMAIL PROTECTED] [2004-05-31 12:13]: GRUB message on vt3: /dev/md0 does not have any corresponding BIOS drive. LILO: An installation step failed. (...) failing step is: Install the LILO boot loader on a hard disk. I don't know how to get LILO and GRUB to boot from RAID. I thought it might just work... anyone got a good idea? Note 1: The progress bar Starting up the partitioner hangs at 55% (Please wait...) while the RAIDs are synchronising. Because this can take several (e.g. 30) minutes, it would be nice to communicate that fact to the user. Thanks, I'll file a bug. Note 2: With linux26 I get two errors: First the os-prober hangs (progress bar at 10%, I just killed the bastard), This is known; use 2.4. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 install fails
On Mon, May 31, 2004 at 12:50:25PM -0300, Martin Michlmayr wrote: * W. Borgert [EMAIL PROTECTED] [2004-05-31 12:13]: GRUB message on vt3: /dev/md0 does not have any corresponding BIOS drive. LILO: An installation step failed. (...) failing step is: Install the LILO boot loader on a hard disk. I don't know how to get LILO and GRUB to boot from RAID. I thought it might just work... anyone got a good idea? Bulk hackery, that's how. See http://lists.debian.org/debian-boot/2004/05/msg03665.html This worked for me insofar as I got GRUB to install, but I didn't seem to have a menu.lst, despite the above saying I should have. I had to do further hackery at a grub prompt along the lines of: root (hd0,0) kernel /vmlinuz ro root=/dev/md0 md=0,/dev/foo,/dev/bar initrd /initrd.img boot where /dev/foo (and optionally /dev/bar) were the members of my /dev/md0. (Optional, as in my case, I was trying to build a degraded RAID1). If you have an md1, add 1,/dev/baz,/dev/blaz to the above incantation. Once I managed to boot into the sucker, I recreated my initrd for good measure, and ran update-grub, and it built a menu for me. It wasn't for the faint of heart at all. HTH Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RAID1 install fails
With the sarge-i386-netinst.iso of 2004-05-28, a RAID1 install fails for me. I said the installer to use both disks (hda 8.4 and hdb 8.6 GB in size, maybe that is the problem?). I let the installer automatically partition the RAID device (all in one partition) and get the error message: [!!] Partition disks Failed to create a file system The ext3 file system creation in partition #1 of RAID1 device #0 failed. The messages on vt3 are: /sbin/tune2fs: Not a directory while while trying to open /dev/md/0/part1 Couldn't find valid file system superblock. mke2fs 1.35 (28-Feb-2004) Could not stat /dev/md/0/part1 --- Not a directory This is reproducable with both 2.4 and 2.6 and with both EXT3 and XFS (the latter is what I really want...). Note 1: I did not try LVM, nor expert mode. Note 2: Non-RAID1 installation on either disk works perfectly. -- this .signature intentionally left blank. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 install fails
* W. Borgert [EMAIL PROTECTED] [2004-05-30 11:32]: /sbin/tune2fs: Not a directory while while trying to open /dev/md/0/part1 Couldn't find valid file system superblock. When you create a RAID device, you'll see something like this: RAID1 #1 - 8 GB #1 primary8 GB What you did was to choose the first line, then you got a warning and continued. This does not work with RAID or LVM - you _have_ to choose the second line and create your partition there. Ideally, partman should only show one line for RAID and LVM, but this requires many changes. Maybe it's possible to print an error instead of a warning when you choose the first line; or better yet, partman should use the 2nd line even when you choose the 1st line. I'll check later how hard this would be to do. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 install fails
Unfortunately, I cannot yet change the subject line :-( On Sun, May 30, 2004 at 11:58:53AM -0300, Martin Michlmayr wrote: When you create a RAID device, you'll see something like this: RAID1 #1 - 8 GB #1 primary8 GB Yes, I got that: RAID1 device #0 - 0.1 GB Software RAID device #1 8.4 GB The problem was: I thought I can create multiple partitions on top of one RAID1 device - instead I have to create multiple - more or less identically sized - partitions in my two disks and than have to create multiple RAID1 devices. So I just did my partitioning on top of that device :-( If I understand this now, I can autopartition my two hard-disks, but now I have to arrange the six RAID capable partitions manually. Not nice, but OK, if you don't have to do this too often. What you did was to choose the first line, then you got a warning and continued. This does not work with RAID or LVM - you _have_ to choose I don't think, that I got a warning that would help me to understand the problem at this point. Ideally, partman should only show one line for RAID and LVM, but this requires many changes. Maybe it's possible to print an error instead of a warning when you choose the first line; or better yet, partman should use the 2nd line even when you choose the 1st line. I'll check later how hard this would be to do. That sounds good. Other note: I never was able to really get back after that wrong RAID creation step, I had to reboot always. Now, with the multiple RAID1 devices, I could install the base system partly, but dpkg couldn't install kernel 2.4 nor 2.6: /usr/sbin/mkinitrd: RAID support requires raidtools2 Failed to create initrd image. Is the netinst CD missing a udeb? Cheers, WB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 install fails
* W. Borgert [EMAIL PROTECTED] [2004-05-30 18:40]: Now, with the multiple RAID1 devices, I could install the base system partly, but dpkg couldn't install kernel 2.4 nor 2.6: /usr/sbin/mkinitrd: RAID support requires raidtools2 Failed to create initrd image. root on RAID is currently not supported, due to the bug you just saw. With newer d-i images, you should get a warning of root is RAID or LVM. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 install fails
On Sun, May 30, 2004 at 06:35:41PM -0300, Martin Michlmayr wrote: * W. Borgert [EMAIL PROTECTED] [2004-05-30 18:40]: /usr/sbin/mkinitrd: RAID support requires raidtools2 Failed to create initrd image. root on RAID is currently not supported, due to the bug you just saw. With newer d-i images, you should get a warning of root is RAID or LVM. Does somebody have the bug number or at least the name of the package the bug is filed against? Because I'm keen to do a complete RAID1 install, I would like to test again as soon as the bug is closed. TIA! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 install fails
* W. Borgert [EMAIL PROTECTED] [2004-05-30 23:06]: Does somebody have the bug number or at least the name of the package the bug is filed against? Because I'm keen to do a complete RAID1 install, I would like to test again as soon as the bug is closed. TIA! Hmm, I think I mixed things up with LVM. For RAID, you should be able to simply edit /var/lib/dpkg/info/base-installer.postinst when partitioning the disk in d-i (_before_ installing the base). There you'll find (towards the end): waypoint 3 apt_update waypoint 1 pick_kernel waypoint 10 install_kernel add a line waypoint 5 install_extra so this looks like: waypoint 3 apt_update waypoint 5 install_extra waypoint 1 pick_kernel waypoint 10 install_kernel This should work. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 install fails
On Sun, May 30, 2004 at 11:06:16PM +, W. Borgert wrote: On Sun, May 30, 2004 at 06:35:41PM -0300, Martin Michlmayr wrote: * W. Borgert [EMAIL PROTECTED] [2004-05-30 18:40]: /usr/sbin/mkinitrd: RAID support requires raidtools2 Failed to create initrd image. root on RAID is currently not supported, due to the bug you just saw. With newer d-i images, you should get a warning of root is RAID or LVM. Does somebody have the bug number or at least the name of the package the bug is filed against? Because I'm keen to do a complete RAID1 install, I would like to test again as soon as the bug is closed. TIA! Well the problem is with mkinitrd from initrd-tools. And it used to work. Is initrd-tools being maintained by the new kernel team also, in Herbert's absence? Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 install fails
Andrew Pollock wrote: On Sun, May 30, 2004 at 11:06:16PM +, W. Borgert wrote: On Sun, May 30, 2004 at 06:35:41PM -0300, Martin Michlmayr wrote: * W. Borgert [EMAIL PROTECTED] [2004-05-30 18:40]: /usr/sbin/mkinitrd: RAID support requires raidtools2 Failed to create initrd image. root on RAID is currently not supported, due to the bug you just saw. With newer d-i images, you should get a warning of root is RAID or LVM. Does somebody have the bug number or at least the name of the package the bug is filed against? Because I'm keen to do a complete RAID1 install, I would like to test again as soon as the bug is closed. TIA! Well the problem is with mkinitrd from initrd-tools. And it used to work. Is initrd-tools being maintained by the new kernel team also, in Herbert's absence? If this is the same problem I ran into when installing to root on LVM on RAID, mkinitrd's only problem is that it's missing the mdadm program. Simply adding mdadm to the list of packages to install as part of base should fix the problem. See my post on installing to root on LVM on RAID for details: http://lists.debian.org/debian-boot/2004/05/msg03665.html If just installing to a RAID device, you don't have to work around the mkinitrd behavior of defaulting to LVM1 when both LVM1 and LVM2 are present, so simply installing mdadm prior to the kernel should allow mkinitrd to complete successfully, meaning you can install to root on a RAID device. -- Charles Steinkuehler [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
