People,
as nobody seems able or willing to answer my thread:
http://forums.opensuse.org/english/get-technical-help-here/install-boot-login/474638-raid-1-array-seems-broken-opensuse-12-1-system.html
I have dug a little deeper.
I added the partition back on te array with the command:
mdadm /dev/md2 --add /dev/sda3
cat /proc/mdstat then showed:
Personalities : [raid1] [raid0] [raid10] [raid6] [raid5] [raid4]
md2 : active raid1 sda3[0] sdb3[1]
109050808 blocks super 1.0 [2/1] [_U]
======>…] recovery = 33.8% (36904576/109050808)
finish=25.4min speed=47210K/sec bitmap: 1/1 pages [4KB], 65536KB chunk
md1 : active raid1 sda2[0] sdb2[1]
5244916 blocks super 1.0 [2/2] [UU]
bitmap: 0/1 pages [0KB], 65536KB chunk
md0 : active raid1 sda1[0] sdb1[1]
41993144 blocks super 1.0 [2/2] [UU]
bitmap: 1/1 pages [4KB], 65536KB chunk
unused devices: <none>
and after a while the output looked like:
cat /proc/mdstat
Personalities : [raid1] [raid0] [raid10] [raid6] [raid5] [raid4]
md2 : active raid1 sda3[0] sdb3[1]
109050808 blocks super 1.0 [2/2] [UU]
bitmap: 1/1 pages [4KB], 65536KB chunk
md1 : active raid1 sda2[0] sdb2[1]
5244916 blocks super 1.0 [2/2] [UU]
bitmap: 0/1 pages [0KB], 65536KB chunk
md0 : active raid1 sda1[0] sdb1[1]
41993144 blocks super 1.0 [2/2] [UU]
bitmap: 0/1 pages [0KB], 65536KB chunk
unused devices: <none>
However,
after booting I get the following error message:
What did I forget to do (for ex, did I have to take a special action to make sure grub can boot both hard drives independently?)
Hope someone can help me fix this.
Thanks in advanced.
Don’t know what you have done wrong, or are missing, but the console gives a hint: run ‘systemctl status md.service’. Enter the rootpassword, system has booted in single user mode. Most of the times this is due to corrupt/incorrect entries in /etc/fstab, or by one or more corrupted file systems. Since there are no messages on the latter, my bet is it’s in the RAID configuration. Now do
systemctl status md.service
and post results here
Hi man,
thanks.
I had to reboot more than 7 times before this error message appeared again (which is strange by itself), But here is the output of the command systemctl status md.service:
md.service - LSB: Multiple Device RAID
Loaded: loaded (/etc/init.d/boot.md)
Active: failed since Sun, 29 Apr 2012 14:29:19 +0200; 10min ago
Process: 447 ExecStart=/etc/init.d/boot.md start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/md.service
If this error does not show up and I can boot normally that same command systemctl status md.service gives:
md.service - LSB: Multiple Device RAID
Loaded: loaded (/etc/init.d/boot.md)
Active: active (exited) since Sun, 29 Apr 2012 14:41:47 +0200; 4min 36s ago
Process: 459 ExecStart=/etc/init.d/boot.md start (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/md.service
And cat /proc/mdstat gives the following output again (notice the [_U] at MD2.
:
cat /proc/mdstat
Personalities : [raid1] [raid0] [raid10] [raid6] [raid5] [raid4]
md2 : active raid1 sdb3[1]
109050808 blocks super 1.0 [2/1] [_U]
bitmap: 1/1 pages [4KB], 65536KB chunk
md0 : active raid1 sdb1[1] sda1[0]
41993144 blocks super 1.0 [2/2] [UU]
bitmap: 1/1 pages [4KB], 65536KB chunk
md1 : active raid1 sdb2[1] sda2[0]
5244916 blocks super 1.0 [2/2] [UU]
bitmap: 0/1 pages [0KB], 65536KB chunk
unused devices: <none>
So what could be wrong here? Analyzing both hard drives with GSmartControl gives no strange results and both hard drives seem to be ok.
At the moment I can’t think of anything else but a systemd bug. Can you produce the error if you boot the system using sysvinit? Done like this
- In GRUB, hit F5
- Pick “System V”
- boot
If this solves your trouble, you can make this permanent by installing sysvinit-init. It will require to uninstall systemd-sysvinit, accept that.
On 2012-04-29 15:06, Knurpht wrote:
> If this solves your trouble, you can make this permanent by installing
> sysvinit-init. It will require to uninstall systemd-sysvinit, accept
> that.
You can also make it permanent by adding “init=/sbin/sysvinit” to the
kernel load line:
kernel /boot/vmlinuz init=/sbin/sysvinit root=
(or creating an alternative entry)
The advantage is that going back is faster, so that when in the Bugzilla
the OP should fill they ask him to try again, he can do it.
Because if this works in systemv mode the OP has to fill a bugzilla.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
