Hello friends,
After having problems with FC17 upgrade, I switched to FC18.
In FC17 I had a working Intel software RAID-1 with 2 drives. This required to remove the rd.dm=0 at kernel boot configuration (an earlier post). FC17 was smart to remember that choice, automatically configure the RAID array to be available as partition under /dev/md126p1 and it worked perfectly (until some issues came up after upgrading FC17 recently).
As for FC18, at initial boot into setup (live media), I also removed that definition to enable RAID support. But after installation, grub config includes rd.md=0, so I had to manually remove it.
In addition, even after removal and reboot, RAID is not properly configured and accessible to the system.
I don't want to go through a procedure that requires some assembly/create or others with mdadm, since it's awkward.
The question is how can this be resolved, if at all?
dmesg output:
As for RAID, it's a simple software raid by Intel, well supported under FC17.
The system is pretty new and up-to-date (Core i7 Ivy-Bridge + H77 chipset).
It seem like the raid is not properly configured in the system.
Running:
Is it possible the necessary module wasn't built into the kernel?
Any ideas are more than welcome.
Thanks,
Moti.
---------- Post added at 09:05 PM ---------- Previous post was at 09:00 PM ----------
Another command to manually assemble the array prints:
After having problems with FC17 upgrade, I switched to FC18.
In FC17 I had a working Intel software RAID-1 with 2 drives. This required to remove the rd.dm=0 at kernel boot configuration (an earlier post). FC17 was smart to remember that choice, automatically configure the RAID array to be available as partition under /dev/md126p1 and it worked perfectly (until some issues came up after upgrading FC17 recently).
As for FC18, at initial boot into setup (live media), I also removed that definition to enable RAID support. But after installation, grub config includes rd.md=0, so I had to manually remove it.
In addition, even after removal and reboot, RAID is not properly configured and accessible to the system.
I don't want to go through a procedure that requires some assembly/create or others with mdadm, since it's awkward.
The question is how can this be resolved, if at all?
dmesg output:
Code:
[ 2.444554] md: bind<sdb>
[ 2.647110] md: bind<sdc>
[ 2.650695] md: bind<sdb>
[ 2.650912] md: bind<sdc>
.....
[ 4.398623] md: export_rdev(sdb)
[ 4.398645] md: export_rdev(sdc)The system is pretty new and up-to-date (Core i7 Ivy-Bridge + H77 chipset).
It seem like the raid is not properly configured in the system.
Running:
Code:
# ll /dev/md*
/dev/md126
/dev/md127
/dev/md/imsm -> ../md127
# mdadm -D /dev/md126
/dev/md126:
Container : /dev/md/imsm0, member 0
Raid Level : -unknown-
Raid Devices : 2
Total Devices : 2
State : active, Not Started
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Number Major Minor RaidDevice State
1 8 32 0 active sync /dev/sdc
0 8 16 1 active sync /dev/sdbAny ideas are more than welcome.
Thanks,
Moti.
---------- Post added at 09:05 PM ---------- Previous post was at 09:00 PM ----------
Another command to manually assemble the array prints:
Code:
# mdadm -As -v
mdadm: looking for devices for /dev/md127
mdadm: no RAID superblock on /dev/dm-0
mdadm: /dev/sdc is busy - skipping
mdadm: /dev/sdb is busy - skipping
mdadm: no RAID superblock on /dev/sda8
mdadm: no RAID superblock on /dev/sda7
mdadm: no RAID superblock on /dev/sda6
mdadm: no RAID superblock on /dev/sda5
mdadm: no RAID superblock on /dev/sda4
mdadm: no RAID superblock on /dev/sda3
mdadm: no RAID superblock on /dev/sda2
mdadm: no RAID superblock on /dev/sda1
mdadm: no RAID superblock on /dev/sda
mdadm: /dev/md127 is a container, but we are looking for components
mdadm: looking for devices for /dev/md/Main_Volume
mdadm: no recogniseable superblock on /dev/dm-0
mdadm: /dev/sdc has wrong uuid.
mdadm: /dev/sdb has wrong uuid.
mdadm: no recogniseable superblock on /dev/sda8
mdadm: no recogniseable superblock on /dev/sda7
mdadm: no recogniseable superblock on /dev/sda6
mdadm: no recogniseable superblock on /dev/sda5
mdadm: Cannot assemble mbr metadata on /dev/sda4
mdadm: no recogniseable superblock on /dev/sda3
mdadm: Cannot assemble mbr metadata on /dev/sda2
mdadm: Cannot assemble mbr metadata on /dev/sda1
mdadm: Cannot assemble mbr metadata on /dev/sda
mdadm: looking in container /dev/md127
mdadm: member /md127/0 in /dev/md127 is already assembled