On Fri, 6 Jan 2006, Chinook wrote:
> Etch with kernel 2.6.12-1-686 (2.6.12-10) Gnome desktop
> ........................................................
>
> I recently tested imaging and restoring my complete system with Mondo
> (before I screw it up again :-)
good that you can backup/restore ... at least that process/proceedure
works :-)
> ==================
> debian1:/home/leec# sfdisk -l
>
> Device Boot Start End #cyls #blocks Id System
> /dev/hda1 * 0+ 851 852- 6843658+ 83 Linux
> /dev/hda2 852 9728 8877 71304502+ 5 Extended
> /dev/hda3 0 - 0 0 0 Empty
> /dev/hda4 0 - 0 0 0 Empty
what is the point of /dev/hda3 and /dev/hda4 ...
- when you rebuilt the next time .. delete it
> /dev/hda5 852+ 1182 331- 2658726 82 Linux swap / Solaris
> /dev/hda6 1183+ 9728 8546- 68645713+ 83 Linux
it's not clear if you are booting off /dev/hda1 or off of /dev/hda6
> Device Boot Start End #cyls #blocks Id System
> /dev/hdb1 0+ 9725 9726- 78124063+ 5 Extended
very very bad idea ...
> /dev/hdb2 0 - 0 0 0 Empty
> /dev/hdb3 0 - 0 0 0 Empty
> /dev/hdb4 0 - 0 0 0 Empty
delete unused garbage ... hdb2, hdb3, hdb4
> /dev/hdb5 0+ 9725 9726- 78124032 fd Linux raid autodetect
nice that its setup as "raid autodetect" which is correct ..
--------
without seeing your /etc/mdadm.conf files, one can't say what you
have and dont have ..
- as is, you raid setup will not work
- raid1 is mirroring
- /dev/hdaX and /dev/hdbX should be defined "identically"
- raid1 will use the smaller size/partitions of the 2 disks
- raid autodetect MUST be defined for raid1/raid5
- if you like watching jibberish, "cat /proc/mdstat"
but you'd have to understand it to know that its useful
- at a minimum, if you should see "U" and not "_" for
each of the raid devices in the /dev/mdX
- you should never use /dev/hda and /dev/hdb in raid1/raid5
as that does not provide any "redundancy" and more importantly
it will slow you down 2x-4x
c ya
alvin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
