| Summary: | RAID not initialized on start up after fresh install. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Peter Wallace <worzel910> |
| Component: | Installer | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | critical | ||
| Priority: | High | CC: | mageia, tmb |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | dmesg output | ||
|
Description
Peter Wallace
2012-04-16 11:33:54 CEST
Initialing storage arrays( LVM, Raid, etc) is what is shown during boot, fedora-storage-init is the service.
Thierry Vignaud
2012-04-16 16:57:51 CEST
CC:
(none) =>
mageia
Peter Wallace
2012-04-16 17:11:37 CEST
Priority:
Normal =>
High Some info about your system: 1. What partitions are on the raid? /home ? 2. Does this say "yay" (before manually fixing - i.e. from the prompt during boot)?: [ -r /proc/mdstat ] && [ -r /dev/.mdadm/map ] && echo "yay" 3. When fixing manually, rather than passing "mdadm --assemble --scan" does "mdadm -IRs" work? 4. Related to the above, is the mdadm command definitely needed? (i.e. is the raid array really not assembled and running yet - perhaps it's just the mounting that failed? I might have some followup questions. Depending on the results of the above. Many thanks. Created attachment 2007 [details]
dmesg output
Thought I listed that, sorry. Partitions on the raid are / /swap /home mdadm -IRs returns nothing as well as just doing the mount command. mdadm has to be run! This is what doesn't work out. the root partition is on the raid and that is mounted. but to mount swap and /home mdadm is needed. /proc/mdstat shows the same before and after mdadm is run. Personalities : unused devices: <none> /dev/.mdadm/map does not exist. I've attached my dmesg output up to the command promt before above commands are run. I have tried this fix here http://superuser.com/questions/364354/mandriva-linux-fails-to-boot-after-installing-systemd. still fails at the same point but only the mount, swapon and sytemctl default commands are needed OK, so this is an interesting one I think. The fact you do not have a /dev/.mdadm/map file is interesting and the fact that /proc/mdstat is not showing anything even after starting things manually makes me wonder what's up here. I'm beginning to suspect you want dmraid rather than mdadm (you are using BIOS to configure the raid after all which is sometimes an indicator - tho' intel raid stuff is left to mdadm these days - you can tell intel due to the isw_ prefix on the dmraid set name). Can you give the output of: /sbin/dmraid -s -c -i Adding Thomas in case he can add insight here. CC:
(none) =>
tmb
Thomas Backlund
2012-04-17 09:42:52 CEST
Attachment 2007 mime type:
application/octet-stream =>
text/plain First a few things about this report... you state MG2B2 live boot ... we didn't release any live beta2 Then reading dmesg I see more unsupported stuff: Linux version 3.1.10-desktop-2mib (mario@localhost.localdomain) (gcc version 4.6.1 20110627 (Mandriva) (GCC) ) #1 SMP PREEMPT Fri Mar 23 00:35:29 CET 2012 systemd[1]: systemd 29 running in system mode. (+PAM +LIBWRAP +AUDIT -SELINUX +SYSVINIT +LIBCRYPTSETUP; mandriva) systemd[1]: /etc/mtab is not a symlink or not pointing to /proc/self/mounts. This is not supported anymore. Please make sure to replace this file by a symlink to avoid incorrect or misleading mount(8) output. and finally, mdadm does not support pdc biosraid, you need dmraid Status:
NEW =>
RESOLVED Wow, thanks Thomas. I didn't even spot all the really old stuff there.. everything is ancient and weird. Thanks for that :) |