Re: Adding extra disk on Raid1?
Did raidhotremove the disk first? Daniel On Sun, 19 Mar 2000, Brian Lavender wrote: > Date: Sun, 19 Mar 2000 02:44:27 -0800 > From: Brian Lavender <[EMAIL PROTECTED]> > To: Linux Raid <[EMAIL PROTECTED]> > Subject: Adding extra disk on Raid1? > > I have a running Raid1 with the mingo patches on the 2.2.14 kernel. I > got everything working, so I decided to turn off the machine and remove > one of the disks. I deleted the contents of the disk one, and then I > restarted the machine. It successfully started in degraded mode. I am running > root raid. I then took the removed disk, and I recreated the partitions on it. > I tried sticking it back in and doing a raidhotadd, but it complains. > > everest:~# raidhotadd /dev/md5 /dev/hda5 > trying to hot-add hda5 to md5 ... > /dev/md5: can not hot-add disk: disk busy! > everest:~# raidhotadd /dev/md6 /dev/hda6 > trying to hot-add hda6 to md6 ... > /dev/md6: can not hot-add disk: disk busy! > > > Here is a snippet of the /etc/raidtab. > > raiddev /dev/md5 > raid-level 1 > nr-raid-disks 2 > nr-spare-disks 0 > chunk-size 4 > persistent-superblock 1 > > device /dev/hde5 > raid-disk 0 > > device /dev/hda5 > raid-disk 1 > > raiddev /dev/md6 > raid-level 1 > nr-raid-disks 2 > nr-spare-disks 0 > chunk-size 4 > persistent-superblock 1 > > device /dev/hde6 > raid-disk 0 > > device /dev/hda6 > raid-disk 1 > > Section from /var/log/syslog > > Mar 19 02:30:06 everest kernel: md6: no spare disk to reconstruct array! -- >continuing in degraded mode > Mar 19 02:30:06 everest kernel: md5: no spare disk to reconstruct array! -- >continuing in degraded mode > > -- DANIEL WIRTH [EMAIL PROTECTED] Tel.: +49 89 890 41 641 Fax.: +49 89 890 41 642
Correction Re: mini root-RAID5-howto
of course I have a level 1 raid (mirroring) NOT level 0 (striping) Daniel On Fri, 22 Oct 1999, Daniel Wirth wrote: > Date: Fri, 22 Oct 1999 11:04:37 +0200 (MEST) > From: Daniel Wirth <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: mini root-RAID5-howto > > > Hi Everybody, > > [cut] > > > Unsolved problem: some distributions want to boot from disk or cdrom before > > upgrading a whole system (e.g. SuSE does that). The problem is that they don' t > > have a RAID kernel on their floppy/cdrom boot system, so you won' t be able to > > access your installation on /dev/md0. > > > > Workarounds: > > - use a non-RAID device: copy all your stuff on it, upgrade and copy all back > > to your raid device > > - make your own boot/install disk with a RAID kernel > > - don' t do this kind of update but update single packages > > here's what I tried while upgrading from SuSE 6.1 to SuSE 6.2. > - raid 0.90 > - raid 0 /dev/hda2 /dev/hdb2 /dev/md0 for / > - raid 5 /home > - /dev/hda1 is /boot non-raid > > I 1st tried to create a SuSE-Bootdisk with a patched kernel, but I did not > suceed. It was booting fine, and started yast, but after chosing "Start > Installation", the system mentioned "Loading Data into RAMDISK" (and > certainly did), but was not able to start yast after loading it. Therefore > I was forced to use the original SuSE-bootdisk. > > I used raidsetfaulty /dev/md0 /dev/hda2 > and raidhotremove /dev/md0 /dev/hda2. > so the raid keeps on running on /dev/hdb2. > > I used fdisk to set the /dev/hda2 partition to an normal Linux-Part. and > mke2fs /dev/hda2. Copied the entire system from to /md0 to /dev/hda2. Then > I booted from the SuSE-Bootdisk and updated that system. After booting it, > I copied the filesys back to /dev/md0. > > Using fdisk, I set the partition-id of /dev/hda2 back to fd and used > raidhotadd /dev/md0 /dev/md0. After resyncing, I runs fine. > > HTH, > > Daniel > > > DANIEL WIRTH | > <[EMAIL PROTECTED]> | > http://www.wirthuell.de| > ____ > Linux: resistance is useless, you will be emulated | > > -- Daniel Wirth DANIEL WIRTH | <[EMAIL PROTECTED]> | http://www.wirthuell.de| Linux: resistance is useless, you will be emulated |
Re: mini root-RAID5-howto
Hi Everybody, [cut] > Unsolved problem: some distributions want to boot from disk or cdrom before > upgrading a whole system (e.g. SuSE does that). The problem is that they don' t > have a RAID kernel on their floppy/cdrom boot system, so you won' t be able to > access your installation on /dev/md0. > > Workarounds: > - use a non-RAID device: copy all your stuff on it, upgrade and copy all back > to your raid device > - make your own boot/install disk with a RAID kernel > - don' t do this kind of update but update single packages here's what I tried while upgrading from SuSE 6.1 to SuSE 6.2. - raid 0.90 - raid 0 /dev/hda2 /dev/hdb2 /dev/md0 for / - raid 5 /home - /dev/hda1 is /boot non-raid I 1st tried to create a SuSE-Bootdisk with a patched kernel, but I did not suceed. It was booting fine, and started yast, but after chosing "Start Installation", the system mentioned "Loading Data into RAMDISK" (and certainly did), but was not able to start yast after loading it. Therefore I was forced to use the original SuSE-bootdisk. I used raidsetfaulty /dev/md0 /dev/hda2 and raidhotremove /dev/md0 /dev/hda2. so the raid keeps on running on /dev/hdb2. I used fdisk to set the /dev/hda2 partition to an normal Linux-Part. and mke2fs /dev/hda2. Copied the entire system from to /md0 to /dev/hda2. Then I booted from the SuSE-Bootdisk and updated that system. After booting it, I copied the filesys back to /dev/md0. Using fdisk, I set the partition-id of /dev/hda2 back to fd and used raidhotadd /dev/md0 /dev/md0. After resyncing, I runs fine. HTH, Daniel DANIEL WIRTH | <[EMAIL PROTECTED]> | http://www.wirthuell.de| Linux: resistance is useless, you will be emulated |
Re: kernel 2.2.13
I did yesterday, same thing as with 2.2.12 - two hunks fail - but running. Daniel On Wed, 20 Oct 1999, Stephen Waters wrote: > Date: Wed, 20 Oct 1999 09:22:21 -0500 > From: Stephen Waters <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: kernel 2.2.13 > > anyone tried the 2.2.11-patch on 2.2.13 yet? same hunks fail as on > 2.2.12 or...? > > -- > stephen waters > amicus, inc. > ____ DANIEL WIRTH | <[EMAIL PROTECTED]> | http://www.wirthuell.de| Linux: resistance is useless, you will be emulated |
Re: booting from raid
The Kernel, which LILO wants to boot is located on which device ? It MUST NOT be located on any of your RAID-Partitions but on a non-striped boot-partition! Could you please post you kernel version and if you applied the raid-patches 0.90? On Mon, 18 Oct 1999, Carol Bosshart - KVG Internet Services wrote: > Date: Mon, 18 Oct 1999 16:48:16 +0200 (MEST) > From: Carol Bosshart - KVG Internet Services <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: booting from raid > > Hello all, > > I set up raid1 on a SuSE Linux Box. > For this i choosed 'method 1' form Jakob Ostergaards Software RAID-HOWTO: > copy the whole installation from a spare (IDE) disk. > > I have 3 partitions: > > DevicePartition Mountpoint > --- > /dev/md0 (sda1, sdb1)/ > /dev/md1 (sda3, sdb3)/usr > /dev/md2 (sda4, sdb4)/info > > /dev/hda (the installation spare disk) > > swap sda2, sdb2 > > My problem is that i cannot boot from my raid partition /dev/md0 > > When the IDE disk /dev/hda is connected, everything works fine, but > without /dev/hda i just get 'LI' from the LILO-Prompt. > > The lilo manpages says that this results from an incorrect map file. > > When i try to install lilo i egt the message: > > 'Sorry, don't know how to handle device 0x0900' > > I think my problems are caused by a wrong lilo bootblock/map. > > Does anyone know a solution for my problem? > > Carol > > -- Gruesse, Daniel __ DANIEL WIRTH | <[EMAIL PROTECTED]> | http://www.wirthuell.de | Fax.: +49 89 66617-48603 | Fak. fuer Physik +49 761 203-5896| Administration CIP-Pool: 203-7682| __
Re: RAID 1 suse 6.1
be careful, it does not make any sense to have several partitions of the same harddisk in the same raid: > device /dev/sdb1 > raid-disk 0 > device /dev/sdb2 > raid-disk 1 if the disk fails, your data will be lost, since at least 2 partitions are gone. you won't gain performance either. better: > device /dev/sda1 > raid-disk 0 > device /dev/sdb1 > raid-disk 1 is ok and please: place your requests in english. HTH Daniel On Fri, 3 Sep 1999, Andreas Gietl wrote: > Date: Fri, 03 Sep 1999 17:27:45 +0200 > From: Andreas Gietl <[EMAIL PROTECTED]> > To: ludo <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > Subject: Re: RAID 1 suse 6.1 > > j'ai fait un erreur.. je vais me corrigier dans le texte suivante. > > Andreas Gietl wrote: > > > > ludo wrote: > > > > > > bonjour , > > > > > > J'ai un systeme avec deux disques SDA et SDB > > > Mon systeme est defini de la facon suivante : > > > > > > /dev/sda1/ > > > /dev/sda2/usr > > > /dev/sda3/opt > > > /dev/sda4partition etendue > > > /dev/sda5/home (partition logique) > > > /dev/sda6swap (partition logique) > > > > > > Sdb est configure a l'identique mais les points de montage associes aux > > > partitions ne sont pas faits , faut il les monter ? > > > > > > le decoupage vous semble il judicieux ? > > > > > > Je souhaite mirorre sda sur sdb , pour cela j'ai cree le fichier raid1.conf de > > > la facon suivante : > > > > > > raiddev /dev/md0 > > > raid-level 1 > > > nr-raid-disks 12 > > > nr-spare-disks 0 > > tu doit faire une /dev/mdx pour jacques partition... > > alors la raid1a.conf > > va être comma ca: > > raiddev /dev/md0 > raid-level 1 > nr-raid-disks 2 > nr-spare-disks 0 > > device /dev/sda1 > raid-disk 0 > > device /dev/sdb1 > raid-disk 1 > > et les autres doit être analoge. > > > > > > > > device /dev/sda1 > > > raid-disk 0 > > > > > > > > device /dev/sda2 > > > raid-disk 0 > > > > -> Vous devez counter les disques > > raid.disk 1,2,3,4, > > > > > > device /dev/sda3 > > > raid-disk 0 > > > > > > device /dev/sda4 > > > raid-disk 0 > > > > > > device /dev/sda5 > > > raid-disk 0 > > > > > > device /dev/sda6 > > > raid-disk 0 > > > > > > device /dev/sdb1 > > > raid-disk 1 > > > > > > device /dev/sdb2 > > > raid-disk 1 > > > > > > device /dev/sdb3 > > > raid-disk 1 > > > > > > device /dev/sdb4 > > > raid-disk 1 > > > > > > device /dev/sdb5 > > > raid-disk 1 > > > > > > device /dev/sdb6 > > > raid-disk 1 > > > > > > est ce que le fichier est correct ? > > > Faut il mirorrer la partition etendue /dev/sda4 ? > > > Les partitions sont montees actuellement , faut il les demonter ? > > qui vouz devez les demonter. > > > merci de votre aide > > > > > > cordialement > > > L-Derlyn > > > > -- > > andreas gietl > > dedicated server systems > > fon +49 9402 2551 > > fax +49 9402 2604 > > mobile +49 171 60 70 008 > > [EMAIL PROTECTED] > > > > > > # Das Handbuch sagt, das Programm benötige # > > # Windows 95 oder besser. Also habe ich # > > # Linux installiert! # > > > > -- Gruesse, Daniel __ DANIEL WIRTH | <[EMAIL PROTECTED]> | http://www.wirthuell.de | Fax.: +49 89 66617-48603 | Fak. fuer Physik +49 761 203-5896| Administration CIP-Pool: 203-7682| __
Re: Problems with mkRaid for RAID1
On Mon, 30 Aug 1999, Georg Rösch wrote: Did you apply the current patches to your kernel? As I understand, the current kernels up to 2.2.12 do not support the 0.90 raid-tools. > i'm running under Suse 6.1 and i want to make a RAID 1 with my two 9.1U2 > HDD's. I already have RAID-Tolls 0.90. Compiling works fine and my Kernel > 2.2.7 already is able to handle RAID 1. > > I did it how it was discribed in the *great* Software-RAID-Howto. > I built the raidtab in the etc path too. > > When i try to execute "mkraid -f /dev/md0" i get this message: > > .. > mkraid: aborted, see the syslog and /proc/mdstat for > potential clues. > > My mdstat looks like this: > > Personalities : [1 linear] [2 raid0] [3 raid1] > read_ahead not set > md0 : inactive > md1 : inactive > md2 : inactive > md3 : inactive > > I don't know which file ist ment by syslog!!? > For the raidtab i used the raid1.conf.sample from the HOWTO's. I only > changed the devices. > > Please help me ... > > Georg Rösch. > > -- Gruesse, Daniel __ DANIEL WIRTH | <[EMAIL PROTECTED]> | http://www.wirthuell.de | Fax.: +49 89 66617-48603 | Fak. fuer Physik +49 761 203-5896| Administration CIP-Pool: 203-7682| __
Re: raidhotremove
On Thu, 26 Aug 1999, Benjamin de los Angeles Jr. wrote: you will have to use raidsetfaulty first, then raidhotremove... > Date: Thu, 26 Aug 1999 19:07:29 +0800 (CST) > From: Benjamin de los Angeles Jr. <[EMAIL PROTECTED]> > To: Linux RAID List <[EMAIL PROTECTED]> > Subject: raidhotremove > > > Hello, > > How can I remove a SCSI disk from a RAID1 array? I tried > '/sbin/raidhotremove /dev/md0 /dev/sdb1' without success. > > > Thanks. > Daniel __ DANIEL WIRTH | <[EMAIL PROTECTED]> | http://www.wirthuell.de | Fax.: +49 89 66617-48603 | Fak. fuer Physik +49 761 203-5896| Administration CIP-Pool: 203-7682| __
