https://bugzilla.novell.com/show_bug.cgi?id=405264
User olh@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=405264#c4
Olaf Hering changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|olh@novell.com |
--- Comment #4 from Olaf Hering 2009-01-15 04:21:22 MST ---
with sles11rc2:
running 51-md.sh
mdadm: device 1 in /dev/md/0 has wrong state in superblock, but /dev/sdb2 seems
ok
mdadm: /dev/md/0 has been started with 2 drives.
preping 61-lvm2.sh
running 61-lvm2.sh
3 logical volume(s) in volume group "system_huckleberry" now active
3 logical volume(s) in volume group "system_huckleberry" now active
preping 81-resume.userspace.sh
running 81-resume.userspace.sh
preping 82-resume.kernel.sh
running 82-resume.kernel.sh
preping 83-mount.sh
running 83-mount.sh
Waiting for device /dev/system_huckleberry/huckleberry_root to appear: ok
node name not found
fsck 1.41.1 (01-Sep-2008)
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a
/dev/system_huckleberry/huckleberry_root
huckleberry_root: clean, 112256/1245184 files, 804830/4980736 blocks
fsck succeeded. Mounting root device read-write.
Mounting root /dev/system_huckleberry/huckleberry_root
so, why does it have wrong state in superblock?
--
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.