Prev: Sugestões para as suas férias
Next: how to automaticaly turn off touchpad using xinput
From: Alan Chandler on 6 Jul 2010 14:10
On 06/07/10 18:15, Miles Fidelman wrote:

>
> 1. start installer, go through initial steps (keyboard, network, etc.)
>
> 2. start up disk partitioner
> -- create partitions - here's what I go with (but for servers) - do this
> for each drive (personally, I find it easer to do this with fdisk)
> ---- part1 boot primary Linux RAID 2G
> ---- part2 primary Linux RAID 3G for swap

Personally. I can't see the point in using RAID for swap. So I use this
partion on each drive as just a SWAP partition and add each swap in to
give (in your case) 6G of swap space.

> ---- part3 primary Linux RAID <rest of the space> for root
> -- set up RAIDs
> ---- /dev/md0 - 2G - ext3 (or ext4) file system, mount point is /boot
What to you envisage going in /boot? I make mine 100 M and that is
always plenty.



--
Alan Chandler
http://www.chandlerfamily.org.uk


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C33702B.9050609(a)chandlerfamily.org.uk
From: Camaleón on 6 Jul 2010 14:10
On Tue, 06 Jul 2010 11:27:31 -0500, Kent West wrote:

> On 07/06/2010 11:13 AM, Camaleón wrote:

>> Second, are you sure you need a raid setup? :-)
>>
>>
> Nope; that's why I asked if I should go RAID or some other cloning
> technique.

Is a home computer or a server/workstation? Can you (or your company)
afford a disk going down or data loss?

>> You should use (regarding raided or not) a good backup strategy :-)
>>
>>
> Yep; I've got an external Buffalo backup appliance that I will also be
> using.

Good. Remember that raid does not prevent from the human error factor ;-)

>> I would not go that way (Intel raid tends to be "fake-raid") :-/
>>
>> If you want to use pure software raid (linux raid), there is no need to
>> setup nothing in the BIOS. Just tell the partitioner you ant to setup a
>> raid1 level between the 2 disks.
>>
>>
> Ah. That's the piece of information I needed to get around my first
> hurdle. Thanks!

Fake-raid (firmware+bios raid) is more used on dual-boot systems (windows
and linux) when windows OS was configured for using a raid setup. In such
cases, one has no other chance and keep the fake-raid in order to use
linux :-(

But if you are not "binded" to windows, better go with "md" (software
linux) that is far more flexible and very well supported in linux.
Although I'm not sure if today md setup allows booting from raid
partition or still boot manager has to be dropped off the raid volume :-?

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/pan.2010.07.06.18.05.15(a)gmail.com
From: Alan Chandler on 6 Jul 2010 14:20
On 06/07/10 16:57, Bob Proulx wrote:
> Kent West wrote:
>
>> partition and set mount points, the installer continues, but then won't
>> install grub or lilo.
>
> I always create a separate /boot partition because I also configure
> LVM and grub doesn't know how to boot off of lvm. Therefore a
> separate /boot (on a software raid /dev/md0 logical partition) enables
> grub to boot. (I am talking grub from Lenny stable and before. I
> don't know if grub2 in Squeeze and later adds this capability.) I
> still thinking having a separate /dev/md0 for /boot makes a lot of
> sense.

I have just (about 10 days ago) set up just such a configuration. I
made my boot partition and used extlinux instead of grub or lilo.

This was a result of a thread on this list about grub v lilo and someone
mentioned extlinux and I decided to give it a go. REALLY easy to set up
once I had installed the debian extlinux package (and removed grub pc).
It helps with kernel upgrades if you adjust /etc/kernel-img.conf to
set link_in_boot = yes (as this gives symlinks vmlinuz and initrd.img in
the /boot directory as opposed to the root directory - which makes it
easier for the extlinux.conf file to have its default kernel as /vmlinuz)

(according to the syslinux/extlinux wiki you install it on the raid
partition - but you then install an MBR into each original device's boot
sector separately )


--
Alan Chandler
http://www.chandlerfamily.org.uk


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C3373A3.3000203(a)chandlerfamily.org.uk
From: Alan Chandler on 6 Jul 2010 14:50
On 06/07/10 19:30, Kent West wrote:
> On 07/06/2010 11:13 AM, Camaleón wrote:
>> On Tue, 06 Jul 2010 10:16:17 -0500, Kent West wrote:
>>> How do I get around the problems I'm seeing in the Debian paritioner (no
>>> bootable flag ...
>>
>
> I'm thinking this must be a bug in the installer's partitioner. If I let
> the install create partitions automatically, the bootable flag is set.
> But if I unset it and then try to re-set it, or if I manually create
> partitions, I can not set the bootable flag. It stays "off".
>
>

If you can't find a better alternative

Alt f2 (I think its alt) to get an alternative console and use fdisk

--
Alan Chandler
http://www.chandlerfamily.org.uk



--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4C3378B2.40203(a)chandlerfamily.org.uk
From: Boyd Stephen Smith Jr. on 6 Jul 2010 15:30
On Tuesday 06 July 2010 13:04:27 Alan Chandler wrote:
> On 06/07/10 18:15, Miles Fidelman wrote:
> > ---- part2 primary Linux RAID 3G for swap
>
> Personally. I can't see the point in using RAID for swap.

If your system is actively using swap [1], and the disk that swap resides on
fails you will experience abnormal process termination at the time of the
failure or in the future as processes need those pages. Since some parts of
kernel memory are considered swappable this could result in a kernel panic.

If you are using RAID to ensure high availability of the system, keeping swap
on RAID is just as important as keeping / on RAID. If you are "simply" using
RAID to avoid losing data, neither need be kept on RAID since all of your data
should be in /var or /home.

[1] By this, I mean specifically that some virtual memory addresses correspond
to pages that exist in swap space (on disk) and do not exist in RAM AND the
process assigned that VMA will be reading or writing to that page before it is
deallocated by the kernel.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss(a)iguanasuicide.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Sugestões para as suas férias
Next: how to automaticaly turn off touchpad using xinput