Re: [SLUG] RAID-5 array problems
On Mon, 2004-07-19 at 15:53, Ben de Luca wrote: andrew fries message regarding lilo twiged me to what might be going on, I am sure that linux software raid writes some thing to the disk? does hotadd add this? if it doesnt the raid wont recognise it.? For the raid to be seen at boot time, the partitions must be marked as type ... FD I think. This is the linux auto raid type. This is done with fdisk, etc not the raid tools. Cheers, Malcolm V. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] RAID-5 array problems
Dear All, I have a RAID-5 array consisting of three 40GB disks (ext3) on a machine running Redhat 3.0ES. Recently one of the three disks failed; hdf. All continued happily on two disks. Yeterday I bought some new disks; 3 x 80GBs. I replaced the bad disk with a new one, formated and partioned the new disk and did a raidhotadd. All seemed well, see copy of lsraid -A -a md0. [EMAIL PROTECTED] root]# lsraid -A -a /dev/md0 [dev 9, 0] /dev/md0 02EF0419.559F377C.34A1ABA4.2AAE1C59 online [dev 33, 1] /dev/hde102EF0419.559F377C.34A1ABA4.2AAE1C59 good [dev 33, 65] /dev/hdf102EF0419.559F377C.34A1ABA4.2AAE1C59 good [dev 34, 1] /dev/hdg102EF0419.559F377C.34A1ABA4.2AAE1C59 good until I rebooted. hdf was missing. I did another raidhotadd and all was well again. I waited until the disks had completely resynced and tried again. Same result. Below are raidtab and fstab, neither of which have been altered by me. [EMAIL PROTECTED] etc]# cat raidtab raiddev /dev/md0 raid-level 5 nr-raid-disks 3 chunk-size 64k persistent-superblock 1 nr-spare-disks 0 device /dev/hde1 raid-disk 0 device /dev/hdf1 raid-disk 1 device /dev/hdg1 raid-disk 2 also, fstab is quite straightforward. [EMAIL PROTECTED] etc]# cat fstab LABEL=/ / ext3defaults1 1 LABEL=/boot /boot ext3defaults1 2 none/dev/ptsdevpts gid=5,mode=620 0 0 /dev/md0/home ext3defaults1 2 none/proc procdefaults0 0 none/dev/shmtmpfs defaults0 0 /dev/hda3 swapswapdefaults0 0 /dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0 /dev/fd0/mnt/floppy auto noauto,owner,kudzu 0 0 Any suggestions as to why? -- Chris Henman RedBox microSystems ABN 70 946 135 312 Phone: +61 2 6161 4640 Mobile: 0421 597 333 Powered by Linux - Democracy in Information Technology. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
RE: [SLUG] RAID-5 array problems
I wonder if it would come up OK if you formatted and partitioned only 40GB of the new disk, and used the other 40GB as a spare logical drive? That is, trick the hardware into thinking it has three 40 GB disks again. I recently had to replace both halves of a mirrored array (RAID-1 on Solaris/SPARC) because I could not buy the same hardware that was originally installed. I wonder if RAID-5 is similar? The only time I've ever heard of different types of disks used in a RAID system is when people make up a RAID-0 stripe from JBOD. Cheers, Jill. -Original Message- From: Chris Henman [mailto:[EMAIL PROTECTED] Sent: Monday, 19 July 2004 12:12 PM To: [EMAIL PROTECTED] Subject: [SLUG] RAID-5 array problems Dear All, I have a RAID-5 array consisting of three 40GB disks (ext3) on a machine running Redhat 3.0ES. Recently one of the three disks failed; hdf. All continued happily on two disks. Yeterday I bought some new disks; 3 x 80GBs. I replaced the bad disk with a new one, formated and partioned the new disk and did a raidhotadd. All seemed well, see copy of lsraid -A -a md0. [EMAIL PROTECTED] root]# lsraid -A -a /dev/md0 [dev 9, 0] /dev/md0 02EF0419.559F377C.34A1ABA4.2AAE1C59 online [dev 33, 1] /dev/hde102EF0419.559F377C.34A1ABA4.2AAE1C59 good [dev 33, 65] /dev/hdf102EF0419.559F377C.34A1ABA4.2AAE1C59 good [dev 34, 1] /dev/hdg102EF0419.559F377C.34A1ABA4.2AAE1C59 good until I rebooted. hdf was missing. I did another raidhotadd and all was well again. I waited until the disks had completely resynced and tried again. Same result. Below are raidtab and fstab, neither of which have been altered by me. [EMAIL PROTECTED] etc]# cat raidtab raiddev /dev/md0 raid-level 5 nr-raid-disks 3 chunk-size 64k persistent-superblock 1 nr-spare-disks 0 device /dev/hde1 raid-disk 0 device /dev/hdf1 raid-disk 1 device /dev/hdg1 raid-disk 2 also, fstab is quite straightforward. [EMAIL PROTECTED] etc]# cat fstab LABEL=/ / ext3defaults1 1 LABEL=/boot /boot ext3defaults1 2 none/dev/ptsdevpts gid=5,mode=620 0 0 /dev/md0/home ext3defaults1 2 none/proc procdefaults0 0 none/dev/shmtmpfs defaults0 0 /dev/hda3 swapswapdefaults0 0 /dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0 /dev/fd0/mnt/floppy auto noauto,owner,kudzu 0 0 Any suggestions as to why? -- Chris Henman RedBox microSystems ABN 70 946 135 312 Phone: +61 2 6161 4640 Mobile: 0421 597 333 Powered by Linux - Democracy in Information Technology. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html -- IMPORTANT NOTICES This email (including any documents referred to in, or attached, to this email) may contain information that is personal, confidential or the subject of copyright or other proprietary rights in favour of Aristocrat, its affiliates or third parties. This email is intended only for the named addressee. Any privacy, confidence, copyright or other proprietary rights in favour of Aristocrat, its affiliates or third parties, is not lost because this email was sent to you by mistake. If you received this email by mistake you should: (i) not copy, disclose, distribute or otherwise use it, or its contents, without the consent of Aristocrat or the owner of the relevant rights; (ii) let us know of the mistake by reply email or by telephone (+61 2 9413 6300); and (iii) delete it from your system and destroy all copies. Any personal information contained in this email must be handled in accordance with applicable privacy laws. Electronic and internet communications can be interfered with or affected by viruses and other defects. As a result, such communications may not be successfully received or, if received, may cause interference with the integrity of receiving, processing or related systems (including hardware, software and data or information on, or using, that hardware or software). Aristocrat gives no assurances in relation to these matters. If you have any doubts about the veracity or integrity of any electronic communication we appear to have sent you, please call +61 2 9413 6300 for clarification. -- SLUG - Sydney Linux User's Group Mailing List
Re: [SLUG] RAID-5 array problems
Rowling, Jill wrote: The only time I've ever heard of different types of disks used in a RAID system is when people make up a RAID-0 stripe from JBOD. Or the space cadet who created a RAID-5 with Disksuite (Solaris software RAID for the uninitiated) with 2 drives: 1 x 4Gb 1 x 8Gb (sliced as 2 x 4Gb) Presto!! 3 x 4Gb partitions, RAID-5 configured as one meta device ...unf. This provided 8Gb of startling redundancy and speed. Startling being the operative word when I inherited the machine from aforementioned space cadet. -- James -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] RAID-5 array problems
it may be time to replace the whole original array 3x40 gigs isnt much any more, so you might want to dump it off to tape and make the raid5 again from scratch with the new disks seeing as one has died it may be the beginings of more deaths so replacing them all now might save problems in the future. Dean Rowling, Jill wrote: I wonder if it would come up OK if you formatted and partitioned only 40GB of the new disk, and used the other 40GB as a spare logical drive? That is, trick the hardware into thinking it has three 40 GB disks again. I recently had to replace both halves of a mirrored array (RAID-1 on Solaris/SPARC) because I could not buy the same hardware that was originally installed. I wonder if RAID-5 is similar? The only time I've ever heard of different types of disks used in a RAID system is when people make up a RAID-0 stripe from JBOD. Cheers, Jill. -Original Message- From: Chris Henman [mailto:[EMAIL PROTECTED] Sent: Monday, 19 July 2004 12:12 PM To: [EMAIL PROTECTED] Subject: [SLUG] RAID-5 array problems Dear All, I have a RAID-5 array consisting of three 40GB disks (ext3) on a machine running Redhat 3.0ES. Recently one of the three disks failed; hdf. All continued happily on two disks. Yeterday I bought some new disks; 3 x 80GBs. I replaced the bad disk with a new one, formated and partioned the new disk and did a raidhotadd. All seemed well, see copy of lsraid -A -a md0. [EMAIL PROTECTED] root]# lsraid -A -a /dev/md0 [dev 9, 0] /dev/md0 02EF0419.559F377C.34A1ABA4.2AAE1C59 online [dev 33, 1] /dev/hde102EF0419.559F377C.34A1ABA4.2AAE1C59 good [dev 33, 65] /dev/hdf102EF0419.559F377C.34A1ABA4.2AAE1C59 good [dev 34, 1] /dev/hdg102EF0419.559F377C.34A1ABA4.2AAE1C59 good until I rebooted. hdf was missing. I did another raidhotadd and all was well again. I waited until the disks had completely resynced and tried again. Same result. Below are raidtab and fstab, neither of which have been altered by me. [EMAIL PROTECTED] etc]# cat raidtab raiddev /dev/md0 raid-level 5 nr-raid-disks 3 chunk-size 64k persistent-superblock 1 nr-spare-disks 0 device /dev/hde1 raid-disk 0 device /dev/hdf1 raid-disk 1 device /dev/hdg1 raid-disk 2 also, fstab is quite straightforward. [EMAIL PROTECTED] etc]# cat fstab LABEL=/ / ext3defaults1 1 LABEL=/boot /boot ext3defaults1 2 none/dev/ptsdevpts gid=5,mode=620 0 0 /dev/md0/home ext3defaults1 2 none/proc procdefaults0 0 none/dev/shmtmpfs defaults0 0 /dev/hda3 swapswapdefaults0 0 /dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0 /dev/fd0/mnt/floppy auto noauto,owner,kudzu 0 0 Any suggestions as to why? -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] RAID-5 array problems
andrew fries message regarding lilo twiged me to what might be going on, I am sure that linux software raid writes some thing to the disk? does hotadd add this? if it doesnt the raid wont recognise it.? On 19/07/2004, at 1:26 PM, Dean Hamstead wrote: it may be time to replace the whole original array 3x40 gigs isnt much any more, so you might want to dump it off to tape and make the raid5 again from scratch with the new disks seeing as one has died it may be the beginings of more deaths so replacing them all now might save problems in the future. Dean Rowling, Jill wrote: I wonder if it would come up OK if you formatted and partitioned only 40GB of the new disk, and used the other 40GB as a spare logical drive? That is, trick the hardware into thinking it has three 40 GB disks again. I recently had to replace both halves of a mirrored array (RAID-1 on Solaris/SPARC) because I could not buy the same hardware that was originally installed. I wonder if RAID-5 is similar? The only time I've ever heard of different types of disks used in a RAID system is when people make up a RAID-0 stripe from JBOD. Cheers, Jill. -Original Message- From: Chris Henman [mailto:[EMAIL PROTECTED] Sent: Monday, 19 July 2004 12:12 PM To: [EMAIL PROTECTED] Subject: [SLUG] RAID-5 array problems Dear All, I have a RAID-5 array consisting of three 40GB disks (ext3) on a machine running Redhat 3.0ES. Recently one of the three disks failed; hdf. All continued happily on two disks. Yeterday I bought some new disks; 3 x 80GBs. I replaced the bad disk with a new one, formated and partioned the new disk and did a raidhotadd. All seemed well, see copy of lsraid -A -a md0. [EMAIL PROTECTED] root]# lsraid -A -a /dev/md0 [dev 9, 0] /dev/md0 02EF0419.559F377C.34A1ABA4.2AAE1C59 online [dev 33, 1] /dev/hde102EF0419.559F377C.34A1ABA4.2AAE1C59 good [dev 33, 65] /dev/hdf102EF0419.559F377C.34A1ABA4.2AAE1C59 good [dev 34, 1] /dev/hdg102EF0419.559F377C.34A1ABA4.2AAE1C59 good until I rebooted. hdf was missing. I did another raidhotadd and all was well again. I waited until the disks had completely resynced and tried again. Same result. Below are raidtab and fstab, neither of which have been altered by me. [EMAIL PROTECTED] etc]# cat raidtab raiddev /dev/md0 raid-level 5 nr-raid-disks 3 chunk-size 64k persistent-superblock 1 nr-spare-disks 0 device /dev/hde1 raid-disk 0 device /dev/hdf1 raid-disk 1 device /dev/hdg1 raid-disk 2 also, fstab is quite straightforward. [EMAIL PROTECTED] etc]# cat fstab LABEL=/ / ext3defaults 1 1 LABEL=/boot /boot ext3defaults 1 2 none/dev/ptsdevpts gid=5,mode=620 0 0 /dev/md0/home ext3defaults 1 2 none/proc procdefaults 0 0 none/dev/shmtmpfs defaults 0 0 /dev/hda3 swapswapdefaults 0 0 /dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0 /dev/fd0/mnt/floppy auto noauto,owner,kudzu 0 0 Any suggestions as to why? -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
