Re: Silo and Raid1
On Sun, 2005-12-18 at 20:38 +0100, Sebastien LANGE wrote: > > The first few blocks of an ext2 or ext3 filesystem are unused, so > > putting one at the start of the disk doesn't matter - the SILO code and > > the disk label in block 0 of the disk are untouched. > > > > A partition that's part of an MD array will have data written to it from > > its first block, so if it starts on block 0 of the disk then SILO and > > the disk label be overwritten. > > > For me, the first partition is the swap and this partition must start on > block 1 too ? As I understand it - yes. Linux swap doesn't have any meta data thus it just writes over the area you give it - if you include block 0 then it will write over your partition table. Unless swap is the only thing on the disk I'm guessing this isn't what you want. HTH. Cheers, - Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Silo and Raid1
> The first few blocks of an ext2 or ext3 filesystem are unused, so > putting one at the start of the disk doesn't matter - the SILO code and > the disk label in block 0 of the disk are untouched. > > A partition that's part of an MD array will have data written to it from > its first block, so if it starts on block 0 of the disk then SILO and > the disk label be overwritten. > For me, the first partition is the swap and this partition must start on block 1 too ? -- Cordialement, Sébastien LANGE _(__)_ Secrétaire d'Ornix'-e e -'__,--.__) (°> Groupe d'utilisateur (o_o)) //\ des logiciels libres \. /___. | V_/_ dans l'Orne ||| )/ )/ http://ornix.org //_(/_(/_( Registered Linux-User #313144 Registered LFS-ID #12095 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Silo and Raid1
On Wed, 2005-12-14 at 22:35 +0100, Turbo Fredriksson wrote: > Quoting Simon Heywood <[EMAIL PROTECTED]>: > > > On Wed, 14 Dec 2005 11:01:47 +0100, Turbo Fredriksson wrote: > >> If you're going to use RAID on the disk, the first partition MUST start > >> on block 1 (one!), not 0 (zero). Can't remember exactly why (usually I > >> forget 'obvious reasons' :) but it have something to do with with ext2/3 > >> inode list, the boot block or with the RAID system needing block zero for > >> something... > > > > The first few blocks of an ext2 or ext3 filesystem are unused, so > > putting one at the start of the disk doesn't matter - the SILO code and > > the disk label in block 0 of the disk are untouched. > > > > A partition that's part of an MD array will have data written to it from > > its first block, so if it starts on block 0 of the disk then SILO and > > the disk label be overwritten. > > > >> NOTE: This is true EVEN if the first partition isn't an MD! > > > > Why's that? > > Don't know. It's the facts. > > http://lists.debian.org/debian-sparc/2003/08/msg00123.html > http://lists.suse.com/archive/suse-sparc/2002-Mar/0018.html > > I don't have time to prove my point. Believe me or not. Your call. I fully agree. You also have to be careful with the last block of the disk too. From memory the primary cause of these problems (when Raid or LVM are concerned anyway) is the "whole disk" partition. The autoprobing code finds this and in some circumstances decides to use the whole disk rather than your partition with disasterous consequences. Regards Richard -- Richard Mortimer <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Silo and Raid1
Quoting Simon Heywood <[EMAIL PROTECTED]>: > On Wed, 14 Dec 2005 11:01:47 +0100, Turbo Fredriksson wrote: >> If you're going to use RAID on the disk, the first partition MUST start >> on block 1 (one!), not 0 (zero). Can't remember exactly why (usually I >> forget 'obvious reasons' :) but it have something to do with with ext2/3 >> inode list, the boot block or with the RAID system needing block zero for >> something... > > The first few blocks of an ext2 or ext3 filesystem are unused, so > putting one at the start of the disk doesn't matter - the SILO code and > the disk label in block 0 of the disk are untouched. > > A partition that's part of an MD array will have data written to it from > its first block, so if it starts on block 0 of the disk then SILO and > the disk label be overwritten. > >> NOTE: This is true EVEN if the first partition isn't an MD! > > Why's that? Don't know. It's the facts. http://lists.debian.org/debian-sparc/2003/08/msg00123.html http://lists.suse.com/archive/suse-sparc/2002-Mar/0018.html I don't have time to prove my point. Believe me or not. Your call. -- Legion of Doom subway Cuba assassination congress kibo 767 DES PLO NORAD Khaddafi killed toluene Saddam Hussein 747 [See http://www.aclu.org/echelonwatch/index.html for more about this] [Or http://www.europarl.eu.int/tempcom/echelon/pdf/rapport_echelon_en.pdf] If neither of these works, try http://www.aclu.org and search for echelon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Silo and Raid1
On Wed, 14 Dec 2005 11:01:47 +0100, Turbo Fredriksson wrote: > If you're going to use RAID on the disk, the first partition MUST start > on block 1 (one!), not 0 (zero). Can't remember exactly why (usually I > forget 'obvious reasons' :) but it have something to do with with ext2/3 > inode list, the boot block or with the RAID system needing block zero for > something... The first few blocks of an ext2 or ext3 filesystem are unused, so putting one at the start of the disk doesn't matter - the SILO code and the disk label in block 0 of the disk are untouched. A partition that's part of an MD array will have data written to it from its first block, so if it starts on block 0 of the disk then SILO and the disk label be overwritten. > NOTE: This is true EVEN if the first partition isn't an MD! Why's that? S. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Silo and Raid1
Quoting Sebastien LANGE <[EMAIL PROTECTED]>: > I installed Sarge on the /dev/sda1 only. > After, I created the raid1: > > #fdisk /dev/sda : >Device FlagStart EndBlocks Id System > /dev/sda1 0 954976896 83 Linux native > > #fdisk /dev/sdb: >Device FlagStart EndBlocks Id System > /dev/sdb1 u 0 415977740 82 Linux swap I can't SWEAR that this is the problem, but it will break sooner or later.. If you're going to use RAID on the disk, the first partition MUST start on block 1 (one!), not 0 (zero). Can't remember exactly why (usually I forget 'obvious reasons' :) but it have something to do with with ext2/3 inode list, the boot block or with the RAID system needing block zero for something... As i said, can't remember exactly (google if you must know), but I know that every time I forgot (I don't forget any more :) this, I've been bitten. Try repartition the disk... You'll loose whatever's on sd[ab]1... NOTE: This is true EVEN if the first partition isn't an MD! -- Treasury Khaddafi Semtex Panama Mossad AK-47 Uzi Saddam Hussein supercomputer FBI Soviet ammunition Honduras iodine critical [See http://www.aclu.org/echelonwatch/index.html for more about this] [Or http://www.europarl.eu.int/tempcom/echelon/pdf/rapport_echelon_en.pdf] If neither of these works, try http://www.aclu.org and search for echelon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Silo and Raid1
On Mon, 2005-12-12 at 08:29 +0100, Sebastien LANGE wrote: > Martin a écrit : > > > > > I don't see the raid drivers starting up. Does the kernel have in built > > md support / is the initrd loading the modules for it? > I used kernel-image-2.6.8-sparc64-smp with initrd and md/raid1 compiled > in modules. > How can I force to load this modules ? Off the top of my head I don't know. It may be worth having a look at the initrd - that should say if / how it is trying to auto load the modules and if (you should) hardwire it to load them. Can't help but feel this is not an ideal solution though... Cheers, - Martin
Re: Silo and Raid1
Hi, When I installed my E450 I used this post as a guide, worked very well. http://lists.debian.org/debian-sparc/2005/07/msg00143.html Regards Tobias Sebastien LANGE wrote: Martin a écrit : I don't see the raid drivers starting up. Does the kernel have in built md support / is the initrd loading the modules for it? I used kernel-image-2.6.8-sparc64-smp with initrd and md/raid1 compiled in modules. How can I force to load this modules ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Silo and Raid1
Martin a écrit : > > I don't see the raid drivers starting up. Does the kernel have in built > md support / is the initrd loading the modules for it? I used kernel-image-2.6.8-sparc64-smp with initrd and md/raid1 compiled in modules. How can I force to load this modules ? -- Cordialement, Sébastien LANGE _(__)_ Secrétaire d'Ornix'-e e -'__,--.__) (°> Groupe d'utilisateur (o_o)) //\ des logiciels libres \. /___. | V_/_ dans l'Orne ||| )/ )/ http://ornix.org //_(/_(/_( Registered Linux-User #313144 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Silo and Raid1
On Sun, 2005-12-11 at 23:09 +0100, Sebastien LANGE wrote: > Hi, > > I installed Sarge on the /dev/sda1 only. > > After, I created the raid1: > Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 > SCSI device sdb: 35378533 512-byte hdwr sectors (18114 MB) > SCSI device sdb: drive cache: write through > /dev/scsi/host0/bus0/target1/lun0: p1 p2 p3 > Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0 > sr0: scsi3-mmc drive: 12x/12x xa/form2 cdda tray > Uniform CD-ROM driver Revision: 3.20 > pKernel panic: Attempted to kill init! > <0>Press L1-A to return to the boot prom > ivot_root: No such file or directory > /sbin/init: 432: cannot open dev/console: No such file > > What's the problem ? I don't see the raid drivers starting up. Does the kernel have in built md support / is the initrd loading the modules for it? Cheers, - Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Silo and Raid1
Hi, I installed Sarge on the /dev/sda1 only. After, I created the raid1: #fdisk /dev/sda : Disk /dev/sda (Sun disk label): 64 heads, 32 sectors, 17274 cylinders Units = cylinders of 2048 * 512 bytes Device FlagStart EndBlocks Id System /dev/sda1 0 954976896 83 Linux native /dev/sda2 954 17274 16711680 fd Linux raid autodetect /dev/sda3 0 17274 176885765 Whole disk #fdisk /dev/sdb: Disk /dev/sdb (Sun disk label): 19 heads, 248 sectors, 7508 cylinders Units = cylinders of 4712 * 512 bytes Device FlagStart EndBlocks Id System /dev/sdb1 u 0 415977740 82 Linux swap /dev/sdb2 415 7508 16711108 fd Linux raid autodetect /dev/sdb3 0 7508 176888485 Whole disk #mdadm --create /dev/md0 --level 1 --raid-devices=2 /dev/sda2 /dev/sdb2 #cat /proc/mdstat : Personalities : [raid1] md0 : active raid1 sda2[0] sdb2[1] 16711040 blocks [2/2] [UU] unused devices: #mdadm --detail --scan >> /etc/mdadm/mdadm.conf #mkfs.ext3 /dev/md0 #mount /dev/md0 /mnt/md0 #mount /dev/sda1 /mnt/sda1 #rsync -a /mnt/sda1 /mnt/md0 #chroot /mnt/md0 #vi /etc/silo.conf: partition=1 default=Linux read-only timeout=100 image=/boot/vmlinuz root=/dev/sda1 label=Linux initrd=/boot/initrd.img image=/boot/vmlinuz append="md=0,/dev/sda2,/dev/sdb2" root=/dev/md0 label=LinuxRaid initrd=/boot/initrd.img #vi /etc/fstab: # proc/proc procdefaults0 0 /dev/sdb1 noneswapsw 0 0 /dev/md0 / ext3defaults,errors=remount-ro 0 1 /dev/scd0 /media/cdrom0 iso9660 ro,user,noauto 0 0 #silo #exit #umount /mnt #reboot And I have the message with kernel-image-2.6.8-sparc64-SMP: SCSI device sda: 35378533 512-byte hdwr sectors (18114 MB) SCSI device sda: drive cache: write through /dev/scsi/host0/bus0/target0/lun0: p1 p2 p3 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sdb: 35378533 512-byte hdwr sectors (18114 MB) SCSI device sdb: drive cache: write through /dev/scsi/host0/bus0/target1/lun0: p1 p2 p3 Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0 sr0: scsi3-mmc drive: 12x/12x xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 pKernel panic: Attempted to kill init! <0>Press L1-A to return to the boot prom ivot_root: No such file or directory /sbin/init: 432: cannot open dev/console: No such file What's the problem ? -- Cordialement, Sébastien LANGE _(__)_ Secrétaire d'Ornix'-e e -'__,--.__) (°> Groupe d'utilisateur (o_o)) //\ des logiciels libres \. /___. | V_/_ dans l'Orne ||| )/ )/ http://ornix.org //_(/_(/_( Registered Linux-User #313144 Sun Ultra 80 UPA/PCI (4 X UltraSPARC-II 450MHz), No Keyboard OpenBoot 3.23, 2048 MB memory installed. Boot device: /[EMAIL PROTECTED],4000/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:a File and args: SILO Version 1.4.9 boot: LinuxRaid Allocated 8 Megs of memory at 0x4000 for kernel Uncompressing image... Loaded kernel version 2.6.8 Loading initial ramdisk (3194880 bytes at 0xC0 phys, 0x40C0 virt)... Remapping the kernel... done. Booting Linux.. PROMLIB: Sun IEEE Boot Prom 3.23.0 1999/06/30 13:53 Linux version 2.6.8-2-sparc64 ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5-12)) #1 Wed Mar 23 04:23:37 EST 2005 ARCH: SUN4U Ethernet address: 08:00:20:f0:0b:51 Built 1 zonelists Kernel command line: root=/dev/md0 ro md=0,/dev/sda2,/dev/sdb2 PID hash table entries: 4096 (order 12: 65536 bytes) Console: colour dummy device 80x25 Dentry cache hash table entries: 262144 (order: 8, 2097152 bytes) Inode-cache hash table entries: 131072 (order: 7, 1048576 bytes) Memory: 2071680k available (1992k kernel code, 600k data, 152k init) [f800,7ff02000] Calibrating delay loop... 897.02 BogoMIPS Mount-cache hash table entries: 512 (order: 0, 8192 bytes) checking if image is initramfs...it isn't (ungzip failed); looks like an initrd Freeing initrd memory: 3120k freed NET: Registered protocol family 16 PCI: Probing for controllers. PCI: Found PSYCHO, control regs at 01fe PSYCHO: Shared PCI config space at 01fe0100 PCI-IRQ: Routing bus[ 0] slot[ 1] map[0] to INO[21] PCI-IRQ: Routing bus[ 0] slot[ 2] map[0] to INO[10] PCI-IRQ: Routing bus[ 0] slot[ 3] map[0] to INO[20] PCI-IRQ: Routing bus[ 0] slot[ 3] map[0] to INO[26] PCI-IRQ: Routing bus[ 0] slot[ 4] map[0] to INO[18] PCI0(PBMB): Bus running at 33MHz PCI-IRQ: Routing bus[80] slot[ 1] map[0] to INO[00] PCI0(PBMA): Bus running at 33MHz ebus0: [auxio] [power] [SUNW,pll] [sc] [se] [su] [su] [ecpp] [fdthree] [eeprom] [flashprom] [SUNW,CS4231] power: Control reg at 01fff1724000 ... powerd running. usbcore: registered new driver usbfs usbcore: register
