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: random crash
> "Clint" == Clint Adams <[EMAIL PROTECTED]> writes: Clint> What is this odd error message? Did it happen with 2.4.27 or Clint> 2.6.8? It happened with 2.6.8 and 2.4.27... I have an oops but i don't know exactly because i haven't physical access to the box (my mother told me the message which was on the screen). Regards, -- Arnaud Fontaine <[EMAIL PROTECTED]> - http://www.andesi.org/ | GPG Public Key available on pgp.mit.edu | Fingerprint: D792 B8A5 A567 B001 C342 2613 BDF2 A220 5E36 19D3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: random crash
> and installed Linux kernel 2.4.27 with SMP support. However, one week > after the startup of the server, the box crashs with a odd error message > and i must reboot it. I tested it with Linux kernel 2.6.8. What is this odd error message? Did it happen with 2.4.27 or 2.6.8? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: random crash
> "Emmanuel" == Emmanuel Kasper <[EMAIL PROTECTED]> writes: Emmanuel> A good thing would be to use a serial console on your Emmanuel> machine, so you can have a least the kernel oops, it is Emmanuel> not written in the logs. It also allows use the reboot the Emmanuel> machine and go into OpenBoot from remote. Hello, Ok, then i will use a serial console ASAP. However, what could i do to check hardware (i think that this kind of crash comes from memory, it isn't ?), so how to use openboot to check the hardware and to be sure ? Regards, -- Arnaud Fontaine <[EMAIL PROTECTED]> - http://www.andesi.org/ | GPG Public Key available on pgp.mit.edu | Fingerprint: D792 B8A5 A567 B001 C342 2613 BDF2 A220 5E36 19D3 -- 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: USB on Ultra 10
Hi, Worked without any problems on my U10. That includes USB2.0 :) Haven't tried firewire yet but I'm soon gonna. Modules load without problem. [EMAIL PROTECTED]:~$ uname -a Linux ra 2.6.12-1-sparc64 #1 Tue Sep 27 23:45:57 UTC 2005 sparc64 GNU/Linux [EMAIL PROTECTED]:~$ cat /proc/cpuinfo cpu : TI UltraSparc IIi (Sabre) fpu : UltraSparc IIi integrated FPU promlib : Version 3 Revision 25 prom: 3.25.3 type: sun4u ncpus probed: 1 ncpus active: 1 Cpu0Bogo: 876.54 Cpu0ClkTck : 1a39de00 MMU Type: Spitfire [EMAIL PROTECTED]:~$ lspci :00:00.0 Host bridge: Sun Microsystems Computer Corp. Ultra IIi :00:01.0 PCI bridge: Sun Microsystems Computer Corp. Simba Advanced PCI Bridge (rev 13) :00:01.1 PCI bridge: Sun Microsystems Computer Corp. Simba Advanced PCI Bridge (rev 13) :01:01.0 Bridge: Sun Microsystems Computer Corp. EBUS (rev 01) :01:01.1 Ethernet controller: Sun Microsystems Computer Corp. Happy Meal (rev 01) :01:02.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev 5c) :01:03.0 IDE interface: Silicon Image, Inc. PCI0646 (rev 03) :02:01.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev61) :02:01.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev61) :02:01.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) :02:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) I'm just using some dirt cheap USB controler. Don't even remember the brand. First one I tried (a combined USB2.0 Firewire card) failed to be seen on the pci bus completely. Worked in a (normal) PC though. With the one I'm using now I was just lucky i guess... My advice: try another one? Good Luck! Vincent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: USB on Ultra 10
VV> i tried to install an USB2.0 controller on Ultra 10 (to be able to VV> connect an external USB device); but unfortunately the system does not VV> boot with the USB controller inserted into a PCI slot: upon power on, VV> the display switches on, but nothing is comes up, - even not the openboot. I tried a generic Opti OHCI USB 1.1 controller in my U5 (same mainboard as U10) and it worked fine. So there is some hope. -- Meelis Roos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
random crash
Hello, I have bought an U60 (with two 450Mhz CPUs and 2Gb of RAM) recently. I have put in this server my old HD (Debian GNU/Linux Sarge) from my U30 and installed Linux kernel 2.4.27 with SMP support. However, one week after the startup of the server, the box crashs with a odd error message and i must reboot it. I tested it with Linux kernel 2.6.8. I would like to know how i could identify what is causing a crash randomly. What should i do ? Should i use OpenBoot (and how ?) or is there linux specific tools to do that (i have only physical access to the box the weekend) ? Regards, -- Arnaud Fontaine <[EMAIL PROTECTED]> - http://www.andesi.org/ | GPG Public Key available on pgp.mit.edu | Fingerprint: D792 B8A5 A567 B001 C342 2613 BDF2 A220 5E36 19D3 -- 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]
