Mailinglist Archive: opensuse-bugs (6755 mails)
| < Previous | Next > |
[Bug 732294] New: External metadata Intel Matrix software raid drops to Verify state on reboot / shutdown
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Wed, 23 Nov 2011 10:22:36 +0000
- Message-id: <bug-732294-21960@http.bugzilla.novell.com/>
https://bugzilla.novell.com/show_bug.cgi?id=732294
https://bugzilla.novell.com/show_bug.cgi?id=732294#c0
Summary: External metadata Intel Matrix software raid drops to
Verify state on reboot / shutdown
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: PC
OS/Version: SuSE Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: saarni@xxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (Ubuntu; X11; Linux x86_64; rv:8.0)
Gecko/20100101 Firefox/8.0
After updating from openSUSE 11.4/Tumbleweed to 12.1 Intel Matrix (ICH10R)
software raid setup with 2 disks in RAID1 started dropping to Verify state on
shutdown/reboot in a somewhat random, but more often than not fashion.
This prevents the system from starting since the raid is left in inactive state
on boot with no partitions created. Quick workaround has been to dual boot to
Windows and verify the raid setup with Intel's tools.
I'm quick to blame systemd for this, since it seems like the most obvious
change between the update (from SysV). I've yet to verify this by choosing SysV
init from boot menu and power cycling the system a few times. Will try that
later today when I get to the machine.
Also there is a spot on bug report at Red Hat bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=732297
Reproducible: Sometimes
Steps to Reproduce:
1. Start up an Intel Matrix software raid system with systemd
2. Reboot
3. Confirm Intel raid state in boot display, should be Normal, but in some
cases has degraded to Verify
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |