|
まずは、パーティションの確認。
qube:~# fdisk -l /dev/sdb WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdb: 163.9 GB, 163928604672 bytes 255 heads, 63 sectors/track, 19929 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 1 125 1004031 83 Linux /dev/sdb2 126 748 5004247+ 83 Linux /dev/sdb4 749 19929 154071382+ 5 Extended /dev/sdb5 749 873 1004031 82 Linux swap / Solaris /dev/sdb6 874 19354 148448601 83 Linux qube:~#LS-XHL で使ったからか、GPT detected といわれる。無視。
パーティションを削除する。
qube:~# fdisk /dev/sdb WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. The number of cylinders for this disk is set to 19929. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): d Partition number (1-6): 4 Command (m for help): d Partition number (1-4): 2 Command (m for help): d Selected partition 1 Command (m for help): p Disk /dev/sdb: 163.9 GB, 163928604672 bytes 255 heads, 63 sectors/track, 19929 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. qube:~#
HDD1 のパーティションは、、、
qube:~# fdisk -l /dev/sda Disk /dev/sda: 163.9 GB, 163928604672 bytes 255 heads, 63 sectors/track, 19929 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 1 125 1004031 83 Linux /dev/sda2 126 748 5004247+ 83 Linux /dev/sda4 749 19929 154071382+ 5 Extended /dev/sda5 749 873 1004031 82 Linux swap / Solaris /dev/sda6 874 19354 148448601 83 Linux qube:~#同じようにパーティションを切っていく。
qube:~# fdisk /dev/sdb WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. The number of cylinders for this disk is set to 19929. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-19929, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-19929, default 19929): 125 Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 2 First cylinder (126-19929, default 126): Using default value 126 Last cylinder or +size or +sizeM or +sizeK (126-19929, default 19929): 748 Command (m for help): n Command action e extended p primary partition (1-4) e Partition number (1-4): 4 First cylinder (749-19929, default 749): Using default value 749 Last cylinder or +size or +sizeM or +sizeK (749-19929, default 19929): Using default value 19929 Command (m for help): n Command action l logical (5 or over) p primary partition (1-4) l First cylinder (749-19929, default 749): Using default value 749 Last cylinder or +size or +sizeM or +sizeK (749-19929, default 19929): 873 Command (m for help): n Command action l logical (5 or over) p primary partition (1-4) l First cylinder (874-19929, default 874): Using default value 874 Last cylinder or +size or +sizeM or +sizeK (874-19929, default 19929): Using default value 19929 Command (m for help): p Disk /dev/sdb: 163.9 GB, 163928604672 bytes 255 heads, 63 sectors/track, 19929 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 1 125 1004031 83 Linux /dev/sdb2 126 748 5004247+ 83 Linux /dev/sdb4 749 19929 154071382+ 5 Extended /dev/sdb5 749 873 1004031 83 Linux /dev/sdb6 874 19929 153067288+ 83 Linux Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. qube:~#
qube:~# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sda2[1]
5004160 blocks [4/1] [_U__]
md10 : active raid1 sda5[1]
1003904 blocks [4/1] [_U__]
md0 : active raid1 sda1[1]
1003904 blocks [4/1] [_U__]
unused devices: <none>
qube:~#
それぞれに sdb を追加していく。qube:~# mdadm --help -su: mdadm: command not found qube:~#がー。
qube:~# apt-cache search mdadm mdadm - tool to administer Linux MD arrays (software RAID) qube:~#そのまま mdadm 。
qube:~# apt-get install mdadm Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: ca-certificates citadel-common citadel-mta citadel-server db4.6-util libcitadel1 libcurl3 libexpat1 libglib2.0-0 libglib2.0-data libical0 libidn11 libpcre3 libsieve2-1 libssh2-1 libxml2 openssl sgml-base shared-mime-info xml-core Suggested packages: sgml-base-doc debhelper Recommended packages: mail-transport-agent The following NEW packages will be installed: ca-certificates citadel-common citadel-mta citadel-server db4.6-util libcitadel1 libcurl3 libexpat1 libglib2.0-0 libglib2.0-data libical0 libidn11 libpcre3 libsieve2-1 libssh2-1 libxml2 mdadm openssl sgml-base shared-mime-info xml-core 0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded. Need to get 6132kB of archives. After this operation, 19.6MB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://ftp.jp.debian.org lenny/main libidn11 1.8+20080606-1 [140kB] Get:2 http://ftp.jp.debian.org lenny/main libpcre3 7.6-2.1 [213kB] Get:3 http://ftp.jp.debian.org lenny/main libxml2 2.6.32.dfsg-5 [791kB] Get:4 http://ftp.jp.debian.org lenny/main openssl 0.9.8g-15 [1032kB] Get:5 http://ftp.jp.debian.org lenny/main ca-certificates 20080809 [151kB] Get:6 http://ftp.jp.debian.org lenny/main db4.6-util 4.6.21-11 [106kB] Get:7 http://ftp.jp.debian.org lenny/main libssh2-1 0.18-1 [63.7kB] Get:8 http://ftp.jp.debian.org lenny/main libcurl3 7.18.2-8 [224kB] Get:9 http://ftp.jp.debian.org lenny/main libexpat1 2.0.1-4 [119kB] Get:10 http://ftp.jp.debian.org lenny/main libglib2.0-0 2.16.6-1 [761kB] Get:11 http://ftp.jp.debian.org lenny/main libglib2.0-data 2.16.6-1 [696kB] Get:12 http://ftp.jp.debian.org lenny/main libical0 0.31-1 [183kB] Get:13 http://ftp.jp.debian.org lenny/main libsieve2-1 2.2.6-1 [75.4kB] Get:14 http://ftp.jp.debian.org lenny/main mdadm 2.6.7.2-1 [277kB] Get:15 http://ftp.jp.debian.org lenny/main sgml-base 1.26 [11.7kB] Get:16 http://ftp.jp.debian.org lenny/main shared-mime-info 0.30-2 [649kB] Get:17 http://ftp.jp.debian.org lenny/main xml-core 0.12 [23.1kB] Get:18 http://ftp.jp.debian.org lenny/main citadel-common 7.37-8 [8548B] Get:19 http://ftp.jp.debian.org lenny/main libcitadel1 7.37-4 [36.2kB] Get:20 http://ftp.jp.debian.org lenny/main citadel-server 7.37-8 [555kB] Get:21 http://ftp.jp.debian.org lenny/main citadel-mta 7.37-8 [16.5kB] Fetched 6132kB in 11s (516kB/s) Preconfiguring packages ... Package configuration lqqqqqqqqqqqqqqqqqqqqqqqqqqqu Configuring mdadm tqqqqqqqqqqqqqqqqqqqqqqqqqqqk x If the system's root file system is located on an MD array (RAID), it x x needs to be started early during the boot sequence. If it is located on x x a logical volume (LVM), which is on MD, all constituent arrays need to x x be started. x x x x If you know exactly which arrays are needed to bring up the root file x x system, and you want to postpone starting all other arrays to a later x x point in the boot sequence, enter the arrays to start here. x x Alternatively, enter 'all' to simply start all available arrays. x x x x If you do not need or want to start any arrays for the root file system, x x leave the answer blank (or enter 'none'). This may be the case if you x x are using kernel autostart or do not need any arrays to boot. x x x x Please enter 'all', 'none', or a space-separated list of devices such as x x 'md0 md1' or 'md/1 md/d0' (the leading '/dev/' can be omitted). x x x x MD arrays needed for the root file system: x x x x all______________________________________________________________________ x x x xむむむ。えらい大げさ。x x x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj Package configuration lqqqqqqqqqqqqqqqqqqqqqqu Configuring citadel-server tqqqqqqqqqqqqqqqqqqqqqqk x Please specify the IP address which the server should be listening to. x x If you specify 0.0.0.0, the server will listen on all addresses. x x x x This can usually be left to the default unless multiple instances of x x Citadel are running on the same computer. x x x x Listening address for the Citadel server: x x x x 0.0.0.0_________________________________________________________________ x x x x x x x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj Package configuration lqqqqqqqqqqqqqqqqqqqqqqu Configuring citadel-server tqqqqqqqqqqqqqqqqqqqqqqqk x Please enter the name of the Citadel user account that should be granted x x administrative privileges once created. x x x x Citadel administrator username: x x x x Administrator____________________________________________________________ x x x x x x x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj Package configuration lqqqqqqqqqqqqqqqqqqqqqqu Configuring citadel-server tqqqqqqqqqqqqqqqqqqqqqqqk x x x Please choose the user authentication mode. By default Citadel will use x x its own internal user accounts database. If you accept this option, x x Citadel users will have accounts on the host system, authenticated via x x /etc/passwd (or LDAP). x x x x Do not accept this option unless you are sure it is required, since x x changing back requires a full reinstall of Citadel. x x x x Enable external authentication mode? x x x x x x x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj Selecting previously deselected package libidn11. (Reading database ... 10020 files and directories currently installed.) Unpacking libidn11 (from .../libidn11_1.8+20080606-1_armel.deb) ... Selecting previously deselected package libpcre3. Unpacking libpcre3 (from .../libpcre3_7.6-2.1_armel.deb) ... Selecting previously deselected package libxml2. Unpacking libxml2 (from .../libxml2_2.6.32.dfsg-5_armel.deb) ... Selecting previously deselected package openssl. Unpacking openssl (from .../openssl_0.9.8g-15_armel.deb) ... Selecting previously deselected package ca-certificates. Unpacking ca-certificates (from .../ca-certificates_20080809_all.deb) ... Selecting previously deselected package db4.6-util. Unpacking db4.6-util (from .../db4.6-util_4.6.21-11_armel.deb) ... Selecting previously deselected package libssh2-1. Unpacking libssh2-1 (from .../libssh2-1_0.18-1_armel.deb) ... Selecting previously deselected package libcurl3. Unpacking libcurl3 (from .../libcurl3_7.18.2-8_armel.deb) ... Selecting previously deselected package libexpat1. Unpacking libexpat1 (from .../libexpat1_2.0.1-4_armel.deb) ... Selecting previously deselected package libglib2.0-0. Unpacking libglib2.0-0 (from .../libglib2.0-0_2.16.6-1_armel.deb) ... Selecting previously deselected package libglib2.0-data. Unpacking libglib2.0-data (from .../libglib2.0-data_2.16.6-1_all.deb) ... Selecting previously deselected package libical0. Unpacking libical0 (from .../libical0_0.31-1_armel.deb) ... Selecting previously deselected package libsieve2-1. Unpacking libsieve2-1 (from .../libsieve2-1_2.2.6-1_armel.deb) ... Selecting previously deselected package mdadm. Unpacking mdadm (from .../mdadm_2.6.7.2-1_armel.deb) ... Selecting previously deselected package sgml-base. Unpacking sgml-base (from .../sgml-base_1.26_all.deb) ... Selecting previously deselected package shared-mime-info. Unpacking shared-mime-info (from .../shared-mime-info_0.30-2_armel.deb) ... Selecting previously deselected package xml-core. Unpacking xml-core (from .../archives/xml-core_0.12_all.deb) ... Selecting previously deselected package citadel-common. Unpacking citadel-common (from .../citadel-common_7.37-8_all.deb) ... Selecting previously deselected package libcitadel1. Unpacking libcitadel1 (from .../libcitadel1_7.37-4_armel.deb) ... Selecting previously deselected package citadel-server. Unpacking citadel-server (from .../citadel-server_7.37-8_armel.deb) ... Selecting previously deselected package citadel-mta. Unpacking citadel-mta (from .../citadel-mta_7.37-8_armel.deb) ... Processing triggers for man-db ... Setting up libidn11 (1.8+20080606-1) ... Setting up libpcre3 (7.6-2.1) ... Setting up libxml2 (2.6.32.dfsg-5) ... Setting up openssl (0.9.8g-15) ... Setting up ca-certificates (20080809) ... Updating certificates in /etc/ssl/certs....done. Running hooks in /etc/ca-certificates/update.d....done. Setting up db4.6-util (4.6.21-11) ... Setting up libssh2-1 (0.18-1) ... Setting up libcurl3 (7.18.2-8) ... Setting up libexpat1 (2.0.1-4) ... Setting up libglib2.0-0 (2.16.6-1) ... Setting up libglib2.0-data (2.16.6-1) ... Setting up libical0 (0.31-1) ... Setting up libsieve2-1 (2.2.6-1) ... Setting up mdadm (2.6.7.2-1) ... Package configuration lqqqqqqqqqqqqqqqqqqqqqqqqqqqu Configuring mdadm tqqqqqqqqqqqqqqqqqqqqqqqqqqqk x x x Once the base system has booted, mdadm can start all MD arrays (RAIDs) x x specified in /etc/mdadm/mdadm.conf which have not yet been started. This x x is recommended unless multiple device (MD) support is compiled into the x x kernel and all partitions are marked as belonging to MD arrays, with x x type 0xfd (as those and only those will be started automatically by the x x kernel). x x x x Do you want to start MD arrays automatically? x x x x x x x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj Generating array device nodes... /var/lib/dpkg/info/mdadm.postinst: line 27: /dev/MAKEDEV: No such file or directory failed. Generating mdadm.conf... done. Starting MD monitoring service: mdadm --monitor. Generating udev events for MD arrays...done. Setting up sgml-base (1.26) ... Setting up shared-mime-info (0.30-2) ... Setting up xml-core (0.12) ... Setting up citadel-common (7.37-8) ... Adding group `citadel' (GID 106) ... Done. Adding system user `citadel' (UID 103) ... Adding new user `citadel' (UID 103) with group `citadel' ... Not creating home directory `/var/lib/citadel'. Setting up libcitadel1 (7.37-4) ... Setting up citadel-server (7.37-8) ... applying your settings. sendcommand: started (pid=3004) running in citadel Attaching to server... qube Citadel server ready. Authenticated as an internal program. CREU Administrator| 200 User 'Administrator' created with no password. sendcommand: processing ended. no /etc/aliases found. sendcommand: started (pid=3010) running in citadel Attaching to server... qube Citadel server ready. Authenticated as an internal program. DOWN 231 Shutting down server. Goodbye. sendcommand: processing ended. Setting up citadel-mta (7.37-8) ... qube:~#
MAKEDEV がないと言われてるが、、、
まずは、/boot
qube:~# mdadm -a /dev/md1 /dev/sdb2
mdadm: re-added /dev/sdb2
qube:~# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[4] sda2[1]
5004160 blocks [4/1] [_U__]
[>....................] recovery = 3.5% (177088/5004160) finish=1.8min speed=44513K/sec
md10 : active raid1 sda5[1]
1003904 blocks [4/1] [_U__]
md0 : active raid1 sda1[1]
1003904 blocks [4/1] [_U__]
unused devices: <none>
qube:~#
DISK1 と DISK2 の LED が激しく点滅している。
qube:~# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[0] sda2[1]
5004160 blocks [4/2] [UU__]
md10 : active raid1 sda5[1]
1003904 blocks [4/1] [_U__]
md0 : active raid1 sda1[1]
1003904 blocks [4/1] [_U__]
unused devices: <none>
qube:~#
できた。
続いて /
qube:~# mdadm -a /dev/md0 /dev/sdb1
mdadm: re-added /dev/sdb1
qube:~# !cat
cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[0] sda2[1]
5004160 blocks [4/2] [UU__]
md10 : active raid1 sda5[1]
1003904 blocks [4/1] [_U__]
md0 : active raid1 sdb1[4] sda1[1]
1003904 blocks [4/1] [_U__]
[=====>...............] recovery = 25.5% (257472/1003904) finish=0.2min speed=43094K/sec
unused devices: <none>
qube:~#
swap も逝ってしまう。
qube:~# mdadm -a /dev/md10 /dev/sdb5
mdadm: re-added /dev/sdb5
qube:~# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[0] sda2[1]
5004160 blocks [4/2] [UU__]
md10 : active raid1 sdb5[4] sda5[1]
1003904 blocks [4/1] [_U__]
[===>.................] recovery = 19.8% (200064/1003904) finish=0.2min speed=50017K/sec
md0 : active raid1 sdb1[0] sda1[1]
1003904 blocks [4/2] [UU__]
unused devices: <none>
qube:~# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[0] sda2[1]
5004160 blocks [4/2] [UU__]
md10 : active raid1 sdb5[0] sda5[1]
1003904 blocks [4/2] [UU__]
md0 : active raid1 sdb1[0] sda1[1]
1003904 blocks [4/2] [UU__]
unused devices: <none>
qube:~#
ヲワタ。
qube:~# shutdown -r now Broadcast message from root@qube (pts/0) (Mon Mar 2 21:04:21 2009): The system is going down for reboot NOW! qube:~#再起動後にログインして、mdstat を見る
yasunari@qube:~$ cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[0] sda2[1]
5004160 blocks [4/2] [UU__]
md10 : active raid1 sdb5[0] sda5[1]
1003904 blocks [4/2] [UU__]
md0 : active raid1 sdb1[0] sda1[1]
1003904 blocks [4/2] [UU__]
unused devices: <none>
yasunari@qube:~$
行けてそう。
yasunari@qube:~$ cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sda2[1]
5004160 blocks [4/1] [_U__]
md10 : active raid1 sda5[1]
1003904 blocks [4/1] [_U__]
md0 : active raid1 sda1[1]
1003904 blocks [4/1] [_U__]
unused devices: <none>
yasunari@qube:~$
何のエラーもなく（？）起動。DISK が壊れても気が付かない？yasunari@qube:~$ touch onlydisk1 yasunari@qube:~$
yasunari@qube:~$ cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sda2[1]
5004160 blocks [4/1] [_U__]
md10 : active raid1 sdb5[0] sda5[1]
1003904 blocks [4/2] [UU__]
md0 : active raid1 sda1[1]
1003904 blocks [4/1] [_U__]
unused devices: <none>
yasunari@qube:~$ ls
onlydisk1
yasunari@qube:~$
なんで、RAID1 が崩れているの？
qube:~# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[0] sda2[1]
5004160 blocks [4/2] [UU__]
md10 : active raid1 sdb5[0] sda5[1]
1003904 blocks [4/2] [UU__]
md0 : active raid1 sdb1[0] sda1[1]
1003904 blocks [4/2] [UU__]
unused devices: <none>
qube:~#
yasunari@qube:~$ cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sda2[0]
5004160 blocks [4/1] [U___]
md10 : active raid1 sda5[0]
1003904 blocks [4/1] [U___]
md0 : active raid1 sda1[0]
1003904 blocks [4/1] [U___]
unused devices: <none>
yasunari@qube:~$
起動してきた。
yasunari@qube:~$ cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[0]
5004160 blocks [4/1] [U___]
md10 : active raid1 sdb5[0] sda5[1]
1003904 blocks [4/2] [UU__]
md0 : active raid1 sdb1[0]
1003904 blocks [4/1] [U___]
unused devices: <none>
yasunari@qube:~$
やっぱり、こっそり RAID1 が崩れている。
監視を入れてやらないといけないな。
|
|
← LS-XHL, LS-QL 対応ハックキットの確認（７）LS-QL：インストール～ |
ハックの記録 LinkStation／玄箱 をハックしよう |
→ データ領域の RAID1 化 |
