[opensuse] RAID disarray
In my old machine I had a two disk RAID1 array mounted on /home. I have transferred these two disks to a new machine, on which I have installed openSUSE 11.0. The operating system partitions are all on a separate (third) drive. During the installation process, while in the Partitioner, Yast detected my /dev/md0 so I happily mounted it on /home, and everything seemed to proceed nicely. That was a few days ago, and since then quite a lot of data has been written to /home I have now discovered that /dev/md0 only consists of a single drive, /dev/sdc1, and /dev/sdb1 has been sitting idle, twiddling it's thumbs! I'd be grateful if someone could guide me through the process of reassembling the array, without losing/overwriting the new data on /dev/sdc1. I have read through man mdadm, but I'm not confident about my understanding. Or perhaps I could do it in Yast? Many thanks, and Happy New Year to you all :) Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.0, Kernel 2.6.25.18-0.2-default, KDE 3.5.10 Intel Celeron 2.53GHz, 2GB DDR RAM, nVidia GeForce 7600GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob Williams wrote:
In my old machine I had a two disk RAID1 array mounted on /home. I have transferred these two disks to a new machine, on which I have installed openSUSE 11.0. The operating system partitions are all on a separate (third) drive. During the installation process, while in the Partitioner, Yast detected my /dev/md0 so I happily mounted it on /home, and everything seemed to proceed nicely. That was a few days ago, and since then quite a lot of data has been written to /home
I have now discovered that /dev/md0 only consists of a single drive, /dev/sdc1, and /dev/sdb1 has been sitting idle, twiddling it's thumbs!
I'd be grateful if someone could guide me through the process of reassembling the array, without losing/overwriting the new data on /dev/sdc1. I have read through man mdadm, but I'm not confident about my understanding. Or perhaps I could do it in Yast?
I think it's easily dealt with by removing sdb1 from the array and then re-adding it, but let's see the output of 'cat /proc/mdstat'. /Per -- /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 01 January 2009 11:31:15 Per Jessen wrote:
I think it's easily dealt with by removing sdb1 from the array and then re-adding it, but let's see the output of 'cat /proc/mdstat'.
~> cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdc1[1] 976759864 blocks super 1.0 [2/1] [_U] bitmap: 396/466 pages [1584KB], 1024KB chunk unused devices: <none> Thanks. Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.0, Kernel 2.6.25.18-0.2-default, KDE 3.5.10 Intel Celeron 2.53GHz, 2GB DDR RAM, nVidia GeForce 7600GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob Williams wrote:
On Thursday 01 January 2009 11:31:15 Per Jessen wrote:
I think it's easily dealt with by removing sdb1 from the array and then re-adding it, but let's see the output of 'cat /proc/mdstat'.
~> cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdc1[1] 976759864 blocks super 1.0 [2/1] [_U] bitmap: 396/466 pages [1584KB], 1024KB chunk
unused devices: <none>
This is what you need: mdadm --manage /dev/md0 --add /dev/sdb1 With that, you're hot-adding sdb1 and your array will immediately start re-synchronising. You can verify and follow that with 'cat /proc/mdstat' /Per -- /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 01 January 2009 12:49:29 Per Jessen wrote:
This is what you need:
mdadm --manage /dev/md0 --add /dev/sdb1
With that, you're hot-adding sdb1 and your array will immediately start re-synchronising. You can verify and follow that with 'cat /proc/mdstat'
Wonderful. Many thanks, Per. mdadm: re-added /dev/sdb1 I am now watching the re-synchronisation in gkrellm :) -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.0, Kernel 2.6.25.18-0.2-default, KDE 3.5.10 Intel Celeron 2.53GHz, 2GB DDR RAM, nVidia GeForce 7600GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-01-01 at 10:35 -0000, Bob Williams wrote:
I have now discovered that /dev/md0 only consists of a single drive, /dev/sdc1, and /dev/sdb1 has been sitting idle, twiddling it's thumbs!
Argh!
I'd be grateful if someone could guide me through the process of reassembling the array, without losing/overwriting the new data on /dev/sdc1. I have read through man mdadm, but I'm not confident about my understanding. Or perhaps I could do it in Yast?
I'm not aware that yast can repair raids :-? Here are my notes on mdadm (change device names as appropriate for your setup): State of things: mdadm --detail /dev/md0 Simulate a failure: mdadm --manage --set-faulty /dev/md0 /dev/hdb11 Remove a disk: mdadm /dev/md0 -r /dev/hdb11 Add a disk: mdadm /dev/md0 -a /dev/hdb11 Usually adding the disk is enough to trigger the rebuild process. But first, try to learn what happened. By the way, there is a daemon that could have emailed you the problem.
Many thanks, and Happy New Year to you all :)
Same to you :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklcrZUACgkQtTMYHG2NR9UmGgCgiR6edN2vu3yIOz8OZntxuH1F ro0An2Xv9/Sn+ooWmLwvPuTeRXO+Q0JR =zko4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 01 January 2009 11:48:34 Carlos E. R. wrote:
On Thursday, 2009-01-01 at 10:35 -0000, Bob Williams wrote:
I have now discovered that /dev/md0 only consists of a single drive, /dev/sdc1, and /dev/sdb1 has been sitting idle, twiddling it's thumbs!
Argh!
I'd be grateful if someone could guide me through the process of reassembling the array, without losing/overwriting the new data on /dev/sdc1. I have read through man mdadm, but I'm not confident about my understanding. Or perhaps I could do it in Yast?
I'm not aware that yast can repair raids :-?
Here are my notes on mdadm (change device names as appropriate for your setup):
State of things:
mdadm --detail /dev/md0
This gives the following info: /dev/md0: Version : 01.00.03 Creation Time : Fri Jun 20 14:18:54 2008 Raid Level : raid1 Array Size : 976759864 (931.51 GiB 1000.20 GB) Used Dev Size : 1953519728 (1863.02 GiB 2000.40 GB) Raid Devices : 2 Total Devices : 1 Preferred Minor : 0 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Thu Jan 1 12:26:29 2009 State : active, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : 0 UUID : 28fda9e6:9d4b3d1c:69069ea4:c79be70e Events : 99990 Number Major Minor RaidDevice State 0 0 0 0 removed 1 8 33 1 active sync /dev/sdc1 -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.0, Kernel 2.6.25.18-0.2-default, KDE 3.5.10 Intel Celeron 2.53GHz, 2GB DDR RAM, nVidia GeForce 7600GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-01-01 at 12:29 -0000, Bob Williams wrote:
State of things:
mdadm --detail /dev/md0
This gives the following info:
/dev/md0: ... Update Time : Thu Jan 1 12:26:29 2009 State : active, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0
Name : 0 UUID : 28fda9e6:9d4b3d1c:69069ea4:c79be70e Events : 99990
Number Major Minor RaidDevice State 0 0 0 0 removed 1 8 33 1 active sync /dev/sdc1
sdc only, so you have to add /dev/sdb1. I see you have done it already. Check the contents of "/etc/mdadm.conf", too. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklczUYACgkQtTMYHG2NR9XscACeKqCBJkcWmz8H6C+DvPSQqkB9 fIIAoIny7jlb3HjF/oETX2wxjdquoRFT =8YZi -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Bob Williams -
Carlos E. R. -
Per Jessen