hi ya paul
On Sun, 1 Aug 2004, Paul Gear wrote:
> I know - that is why i was very disappointed to find that it wasn't
> supported even in the latest Sarge snapshot (i honestly expected it to
> be supported in Woody as well).
yup ... people's ( developer's ) preferences and requirements are
different or "just plain it'd be fun to do this wy instead of that way"
> > - it all assumes that /boot is in / and "/" is less than 1024
> > cylinders ( 520MB or so for "/" )
>
> It appears that this is not a limitation in the latest installer (from
> what i can tell). Having a separate /boot seems to be supported from
> the reading and testing i've done.
the only reason to have had a /boot was to get around the 1024 cylinder
problem when the bios was limited to 1024 cylinders which is no
longer an issue with lba capable bios
> I know. I tried to do this, but Debian's mkinitrd is not giving me the
> joy the Red Hat one did (see below).
initrd is for the fun of things and a pat-pat on the shoulders when it
works ( time vs other stuff to do issue )
> Why? I can't see a reason for not making it. It then allows you to put
> / on more exotic filesystems, or even on a volume manager (i haven't
> done the former, but the majority of my machines use LVM).
more exotic/different and more fun one has :-)
> > - creating / bigger than 128MB or 256MB is a bad idea ...
>
> Again, why? My preferred setup for a workstation is *everything* in /.
that's an age old preferences or time or ??? issue ...
- it will become an issue at 3:00am when you;re sleeping and
get called in to fix the disks cause it crashed because a user
created the wrong kinda of files or filenames
- you can't fix it if you can't boot it into single user mode
> This is the preferred arrangement for new users according to the Sarge
> installer, as well. It saves a lot of stuffing around with partitioning.
doesn't make it the "rigth way" depending on the side on the table
one comes from
- knowing how big the partitions should be for a particular
server is knowing one's tasks that machine needs to do
you can move things around as needed to meet what you consider important
on the server ... and maintenance of it and reliability and fixability
and crashed and restore ... blah .. blah ..
> What exactly do you think is a bad idea? RAID 1 for / and /boot has
> been an extremely trouble-free setup for me on all of my servers (around
> 20 of them),
all good ... except like i said... i would not be using /boot
and / will be small as possible
> and has saved me from machines crashing when hard drives go
> bad (especially the ones that don't even know they're going bad ;-).
if you dint know the drives went bad... thats a bad thing???
- one should know say withing the hour that a disk crashed
so that you can go replace it asap before the 2nd disk crashes
and you lose all the data between the time of the first crashes
and time you found the dead machine
> I've tried that - i must be missing something. Below is what i posted
> on debian-boot, and got no replies. (I'm trying to install to 2 x 200
> Gb WD2000JD-00GBB0 SATA drives.)
sata can make things messy ... [un]lucky me, i dont get to play with new
sata toys lately ...
> -- Snip --
> 4. Install latest Sarge snapshot to standard ATA drive. Set up RAID
> devices (md0 = 1 Gb /boot, md1 = 4 Gb swap, md2 = 195 Gb /), rsync ATA
> partition to SATA partitions, chroot to target partitions and run LILO.
too hard for me ...
i'd boot a standard standalone cdrom ...
- build the raid out of the 2 disks
- install from the cdrom or network
- lilo/grub it
- reboot ....
- write a 2GB file... power down and pull out /dev/hda
- reboot aand see if it works ( hands off )
- reconnect .. resync ... should now have that 2GB on both
disks
- reboot .. pull out /dev/hdc and see if it works ( handsoff )
- write more data
- reconnect .. resync ... send invoice :-)
> This last method seems to be on the verge of working, but when i boot
> from the /boot partition, it can't mount md2 on /.
usually means a partition problem ( should be "FD" ) or
fix lilo or grub ... and do NOT use initrd you didnt create unless
you know it works for booting on 1/2 or 1/4 of the working raid disk
> I can boot from the
> SATA /boot and use the ATA /. It seems the md devices aren't started,
> and i can't work out how to include them in the initrd.
to look at the initrd ..
mount -o loop initrd.gz /mnt/initrd ( fix for the exact syntax )
ls -la /mnt/initrd
fix what you want
recompress it and replace the original one
> On RH, you
> could just specify preload modules on the mkinitrd command line, but
> that doesn't seem to be the case here. I added raid1 and md to
> /etc/mkinitrd/modules, but that doesn't help. Any suggestions?
i say mkinitrd and its variations is all broken in most versions i played
with
- and better yet, its not needed if the kernel is built right
( raid built into the kernel and not a module )
> mkinitrd --preload sr_mod --preload iteraid /boot/initrd-2.4.20-30.9
> 2.4.20-30.9
use your own kernel ... and use 2.4.26 with whatever kernel patches
to minimize buffer overflow attacks
> It just gives a warning that the way i set it up is not supported, fails
> to install both GRUB and LILO (i tried both), and fails to boot after
> installation.
post the lilo.conf and/or grub/grub.conf and grub/menu.list
thee should be only one grub config files in /boot/grub
and watch out for duplicates in /etc/grub*
- i don't use grub since it wants to get to the disk before
it starts to work and dot its magic whereas, lilo is more
self contained and can boot w/o caring about the disk
c ya
alvin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
