[opensuse] OS12.1 is there a known issue with soft-raid1 ?
Hi is there a known issue with soft-raid1 on OS12.1? I've got two PCs that won't start a soft-raid1 on reboot. I can set it up with YAST it gets mounted and I can copy files on MD0 after I close YAST. But on the next reboot apears an error that the superblock were unreadable. This happens on both machines. One is an AMD5200 with 4GB RAM and 2 x 300GB HDD. The other one is an old Pentium4, 512MB RAM, 2 x 40 GB HDD. So they are pretty different but show the same problem. Any idea ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/21/2011 10:25 AM, Andreas wrote:
Hi is there a known issue with soft-raid1 on OS12.1? I've got two PCs that won't start a soft-raid1 on reboot. I can set it up with YAST it gets mounted and I can copy files on MD0 after I close YAST.
But on the next reboot apears an error that the superblock were unreadable.
This happens on both machines. One is an AMD5200 with 4GB RAM and 2 x 300GB HDD. The other one is an old Pentium4, 512MB RAM, 2 x 40 GB HDD. So they are pretty different but show the same problem.
Hi Andreas, I didn't see exactly your problem, but MD-Raid with Intel chipsets has been broken for me since 11.4. In my case, it seems as if the sizes of configured raids aren't reported correctly, leading to strange disk errors. The process fails during a fresh install when the various partitions are being formatted. Their sizes are being reported as 20 TB when the actual sizes are less than 800 GB, for example. I haven't tried 12.1 yet. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Nov 22, 2011 at 12:12 AM, Lew Wolfgang <wolfgang@sweet-haven.com> wrote:
I didn't see exactly your problem, but MD-Raid with Intel chipsets has been broken for me since 11.4. In my case, it seems as if the sizes of configured raids aren't reported correctly, leading to strange disk errors. The
dmraid is "fake" raid. What is the advantage of using dmraid (controlled by motherboard bios) v/s mdadm (kernel software raid)Use mdadm raid instead? Besides mdadm raid setup would be portable across hardware (motherboard) platforms. [1] <http://forums.opensuse.org/english/get-technical-help-here/install-boot-login/458544-dmraid-vs-mdadm-raid-status-monitoring.html> -- Arun Khan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Lunes, 21 de noviembre de 2011 19:25:01 Andreas escribió:
Hi is there a known issue with soft-raid1 on OS12.1? I've got two PCs that won't start a soft-raid1 on reboot. I can set it up with YAST it gets mounted and I can copy files on MD0 after I close YAST.
But on the next reboot apears an error that the superblock were unreadable.
This happens on both machines. One is an AMD5200 with 4GB RAM and 2 x 300GB HDD. The other one is an old Pentium4, 512MB RAM, 2 x 40 GB HDD. So they are pretty different but show the same problem.
Any idea ?
https://bugzilla.novell.com/show_bug.cgi?id=731230 https://bugzilla.novell.com/show_bug.cgi?id=731135 It happens to me too... with sysv-init works but don't with systemd. -- deabru, bai deabrunaiz... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Nov 22, 2011 at 6:44 AM, deabru <deabrufree@gmail.com> wrote:
https://bugzilla.novell.com/show_bug.cgi?id=731230 https://bugzilla.novell.com/show_bug.cgi?id=731135
It happens to me too... with sysv-init works but don't with systemd.
+1 switch to sysvinit; eval systemd init in a VM/non production hw and report bugs with every service that is broken. -- Arun Khan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2011-11-21 at 19:25 +0100, Andreas wrote:
is there a known issue with soft-raid1 on OS12.1? I've got two PCs that won't start a soft-raid1 on reboot. I can set it up with YAST it gets mounted and I can copy files on MD0 after I close YAST. But on the next reboot apears an error that the superblock were unreadable.
My HP wx8400 workstation has four drives in an MD RAID1 configuration. Boots without any issue. awilliam@workstation:~> cat /proc/mdstat Personalities : [raid10] [raid0] [raid1] [raid6] [raid5] [raid4] [linear] md0 : active raid10 sda3[0] sdb3[1] sdc2[2] sdd2[3] 1457512128 blocks super 1.0 32K chunks 2 near-copies [4/4] [UUUU] bitmap: 3/11 pages [12KB], 65536KB chunk -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Adam Tauno Williams -
Andreas -
Arun Khan -
deabru -
Lew Wolfgang