From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Real-To: Message-ID: <3EE0487B.9090202@mail333.com> Date: Fri, 06 Jun 2003 11:53:31 +0400 From: "Aleksey Avdeev" User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru-RU; rv:1.3) Gecko/20030331 X-Accept-Language: ru-ru, ru MIME-Version: 1.0 To: sisyphus@altlinux.ru Subject: Re: [sisyphus] Re: raidstart References: <20030605054629.GA12006@regiongarant.ru> <3EDEF3F0.5050405@mail333.com> <20030605083744.GF12006@regiongarant.ru> <20030605135604.GW30440@osdn.org.ua> <20030605153148.GA20015@regiongarant.ru> In-Reply-To: <20030605153148.GA20015@regiongarant.ru> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-MDaemon-Deliver-To: sisyphus@altlinux.ru Sender: sisyphus-admin@altlinux.ru Errors-To: sisyphus-admin@altlinux.ru X-BeenThere: sisyphus@altlinux.ru X-Mailman-Version: 2.0.9 Precedence: bulk Reply-To: sisyphus@altlinux.ru X-Reply-To: solo_oboroten@mail333.com List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Archived-At: List-Archive: Salavat Yarmukhametov пишет: > On Thu, Jun 05, 2003 at 04:56:04PM +0300, Michael Shigorin wrote: > >>On Thu, Jun 05, 2003 at 12:37:44PM +0400, Salavat Yarmukhametov wrote: >> >>> 3. The partition-types of the devices used in the RAID must be set to >>>0xFD (use fdisk and set the type to ``fd'') >>>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >>> п.3 я не делал, может это? Вечером попробую - машина домашняя. >> >>Ну разумеется. > > > > Неа :( > [root@localhost root]# fdisk /dev/hdb > Command (m for help): p > Disk /dev/hdb: 20.5 GB, 20547841536 bytes > 255 heads, 63 sectors/track, 2498 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > > Device Boot Start End Blocks Id System > /dev/hdb1 * 1 1211 9727326 c Win95 FAT32 (LBA) > /dev/hdb2 1212 2498 10337827+ fd Linux raid autodetect > [root@localhost root]# fdisk /dev/hde > Command (m for help): p > > Disk /dev/hde: 61.4 GB, 61492838400 bytes > 16 heads, 63 sectors/track, 119150 cylinders > Units = cylinders of 1008 * 512 = 516096 bytes > > Device Boot Start End Blocks Id System > /dev/hde1 1 20318 10240240+ fd Linux raid autodetect > /dev/hde2 20319 60953 20480040 83 Linux > /dev/hde3 60954 119150 29331288 5 Extended > /dev/hde5 60954 101588 20480008+ 83 Linux > /dev/hde6 101589 117030 7782736+ 83 Linux > /dev/hde7 117031 119062 1024096+ 83 Linux > /dev/hde8 119063 119150 44320+ 83 Linux > > > dmesg: > > md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: Autodetecting RAID arrays. > [events: 00000002] > [events: 00000002] > md: autorun ... > md: considering hde1 ... > md: adding hde1 ... > md: adding hdb2 ... > md: created md0 > md: bind > md: bind > md: bind > md: running: > md: hde1's event counter: 00000002 > md: hdb2's event counter: 00000002 > md: md0: raid array is not clean -- starting background reconstruction > md: RAID level 1 does not need chunksize! Continuing anyway. > kmod: failed to exec /sbin/modprobe -s -k md-personality-3, errno = 2 > md: personality 3 is not loaded! > md :do_md_run() returned -22 > md: md0 stopped. > md: unbind > md: export_rdev(hde1) > md: unbind > md: export_rdev(hdb2) > md: ... autorun DONE. Если дальше покопаться в логах, непомню в каких имеено файлах /var/log/kernel/* (я смотрел все :-)) или внимательно посмотреть на сообщения при загрузке, то можно заметить что приведённая цитата присутствует ДО сообщения о монтировании initrd с требуемыми модулями (почему я и сделал вывод о некорректной работе автораида в модульной конфигурации :-() и, соответственно, реального корня. > > если после загрузки дать: > raidstart /dev/md0 > то в /var/log/messages: > Jun 5 18:58:29 localhost kernel: [events: 00000002] > Jun 5 18:58:29 localhost kernel: [events: 00000002] > Jun 5 18:58:29 localhost kernel: md: autorun ... > Jun 5 18:58:29 localhost kernel: md: considering hde1 ... > Jun 5 18:58:29 localhost kernel: md: adding hde1 ... > Jun 5 18:58:29 localhost kernel: md: adding hdb2 ... > Jun 5 18:58:29 localhost kernel: md: created md0 > Jun 5 18:58:29 localhost kernel: md: bind > Jun 5 18:58:29 localhost kernel: md: bind > Jun 5 18:58:29 localhost kernel: md: running: > Jun 5 18:58:29 localhost kernel: md: hde1's event counter: 00000002 > Jun 5 18:58:29 localhost kernel: md: hdb2's event counter: 00000002 > Jun 5 18:58:29 localhost kernel: md: RAID level 1 does not need > chunksize! Continuing anyway. > Jun 5 18:58:29 localhost kernel: md0: max total readahead window set to > 508k > Jun 5 18:58:29 localhost kernel: md0: 1 data-disks, max readahead per > data-disk: > 508k > Jun 5 18:58:29 localhost kernel: raid1: device hde1 operational as mirror > 1 > Jun 5 18:58:29 localhost kernel: raid1: device hdb2 operational as mirror > 0 > Jun 5 18:58:29 localhost kernel: raid1: raid set md0 active with 2 out of > 2 mirrors > Jun 5 18:58:29 localhost kernel: md: updating md0 RAID superblock on > device > Jun 5 18:58:29 localhost kernel: md: hde1 [events: 00000003]<6>(write) > hde1's sb > offset: 10240128 > Jun 5 18:58:29 localhost kernel: md: syncing RAID array md0 > Jun 5 18:58:29 localhost kernel: md: minimum _guaranteed_ reconstruction > speed: 100 KB/sec/disc. > Jun 5 18:58:29 localhost kernel: md: using maximum available idle IO > bandwith (but not more than 100000 KB/sec) for reconstruction. > Jun 5 18:58:29 localhost kernel: md: using 508k window, over a total of > 10240128 > blocks. > Jun 5 18:58:29 localhost kernel: md: hdb2 [events: 00000003]<6>(write) > hdb2's sb > offset: 10337728 > Jun 5 18:58:29 localhost kernel: [events: 00000000] > Jun 5 18:58:29 localhost kernel: md: ... autorun DONE. > Jun 5 18:58:35 localhost kernel: kjournald starting. Commit interval 5 > seconds > Jun 5 18:58:35 localhost kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on > md(9,0), internal journal А теперь, требуемые модули доступны :-) > > Почему raidstart из /etc/rc.d/rc.sysinit не хочет отрабатываться? > Чего еще я не доделал? Что в /etc/raidtab? -- С уважением. Алексей.