Re: linux software RAID with hot-swap hardware
Russell Coker wrote: > > boot = /dev/hda, map = /boot/map.0301 > > Added Linux * > > boot = /dev/hdc, map = /boot/map.1601 > > Added Linux * > > That looks like an old version of LILO. The latest LILO in Debian is > 22.3.3 and doesn't work like that. Yes, at home I have 22.3.3-2. > > The above is from a Redhat 7.3 system but this worked back in Redhat 6.2, > > I have also done this with a sid system within the past month. > > Strange, it doesn't work like that for me on my SID systems, and I haven't > made a new release of LILO since September last year. My mother's computer has unstable installed and presumably the same lilo (22.3.3-2), if not at least a very close version since I installed her system about a month ago. When I run lilo on her system I see similar output to the lilo output that I quoted from the redhat system. > This is an interesting discussion, but you didn't answer my question of why > anyone would want to run install-mbr on a RAID device. That I don't know (wasn't me that tried to do it). I had thought that maybe install-mbr but I realize now that it is not. I'll have to read up on install-mbr and re-read your howto, sounds like a very useful tool. Fraser -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing horde
On Sat, 25 Jan 2003 [EMAIL PROTECTED] wrote: > and bingo, 'sudo' is a requirement which I unfortunately didn't have > installed... can this be added somewhere to the dependancies for horde? Don't count on it! Did you file a bug in BTS against horde? Cheers, Cristian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problems installing horde
Hi all, after a couple of hours of trying to work out why the automated install for horde together with postgresql didn't work, I decided to go through the install scripts. and bingo, 'sudo' is a requirement which I unfortunately didn't have installed... can this be added somewhere to the dependancies for horde? Cheers Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: linux software RAID with hot-swap hardware
On Sat, 25 Jan 2003 14:15, Fraser Campbell wrote: > > > the way I've tested it also works with > > > > > > install-mbr /dev/md1 > > > > Why would you want to use install-mbr on a RAID device? > > > > I use install-mbr for the MBR on the hard drive (/dev/sda and /dev/sdb in > > this case) and then have it load the real boot block from /dev/md1 which > > was created by LILO. > > In my experience a lilo.conf such as this works: > > boot=/dev/md1 > > Simply run lilo thereafter, you will see that it automatically installs > boot sectors in both drives. Like this: > > boot = /dev/hda, map = /boot/map.0301 > Added Linux * > boot = /dev/hdc, map = /boot/map.1601 > Added Linux * That looks like an old version of LILO. The latest LILO in Debian is 22.3.3 and doesn't work like that. > The above is from a Redhat 7.3 system but this worked back in Redhat 6.2, I > have also done this with a sid system within the past month. Strange, it doesn't work like that for me on my SID systems, and I haven't made a new release of LILO since September last year. > In the above case /dev/md1 is a 24MB partition mounted as /boot, consisting > of /dev/hda1 and /dev/hdb1. Since lilo is supposed to get past the 1024 > cylinder limit these days that is probably not relevant. Correct, and on modern LBA drives 1024 cylinders should be large enough for the entire root file system anyway. > In testing I was able to boot with hda only (that one's obvious), I was > able to boot with hdc only (both directly using BIOS and using lilo > installed on floppy). You've got a good BIOS then. The only time I've had that work for me was when using SCSI on a machine with hot-swap drives (it cost enough so you expect such things to work). For desktop machines I buy mostly what's cheapest. > I'm 90% sure that I physically moved hdc so that it became hda and was able > to boot perfectly but it was getting late and I lost track of what I was > testing. That used to tend to not work on the older versions of LILO with a default setup. With the re-write of the boot code the default seems to work well for that (but may have problems with the drive as /dev/hdc). > All partition types are set to RAID Autodetect (FD), I believe that may be > important. Of course. The root file system on RAID won't work unless you have the partitions labeled as 0xfd or have an initrd that's programmed for it. This is an interesting discussion, but you didn't answer my question of why anyone would want to run install-mbr on a RAID device. -- http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/Postal SMTP/POP benchmark http://www.coker.com.au/~russell/ My home page -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: linux software RAID with hot-swap hardware
Russell Coker wrote: > > > raid-extra-boot="/dev/sda,/dev/sdb" > > > > > > According to the documentation of lilo, this shouldn't be necessary, > > > but apparently either the funcionality or the docs are buggy. Without > > > that line I couldn't boot at all from the second disk, > > > > the way I've tested it also works with > > > > install-mbr /dev/md1 > > Why would you want to use install-mbr on a RAID device? > > I use install-mbr for the MBR on the hard drive (/dev/sda and /dev/sdb in > this case) and then have it load the real boot block from /dev/md1 which > was created by LILO. In my experience a lilo.conf such as this works: map=/boot/map install=/boot/boot.b boot=/dev/md1 timeout=50 prompt default=Linux image=/boot/vmlinuz-2.4.18-19.7.x label=Linux root=/dev/md4 initrd=/boot/initrd-2.4.18-19.7.x.img read-only Simply run lilo thereafter, you will see that it automatically installs boot sectors in both drives. Like this: boot = /dev/hda, map = /boot/map.0301 Added Linux * boot = /dev/hdc, map = /boot/map.1601 Added Linux * The above is from a Redhat 7.3 system but this worked back in Redhat 6.2, I have also done this with a sid system within the past month. In the above case /dev/md1 is a 24MB partition mounted as /boot, consisting of /dev/hda1 and /dev/hdb1. Since lilo is supposed to get past the 1024 cylinder limit these days that is probably not relevant. In testing I was able to boot with hda only (that one's obvious), I was able to boot with hdc only (both directly using BIOS and using lilo installed on floppy). I'm 90% sure that I physically moved hdc so that it became hda and was able to boot perfectly but it was getting late and I lost track of what I was testing. All partition types are set to RAID Autodetect (FD), I believe that may be important. Fraser -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
