You are not logged in.
Hello,
I having trouble booting a RAID0, Fake Raid on a Intel Matrix Storage Module with a M.2 SSD.
I very much want to use fake raid to duel boot so that I have the speed from the M.2 SSD available for both Windows and Arch.
Any help would be very very much appreciated .
Thanks a lot.
UPDATE FEB 16, 2016
Problem
• mdadm is not assembling the IMSM container & the RAID0 array before the kernel is looking to mount the root partition. i.e. ERROR: Unable to find root device '1a227...
• Once in the recovery shell, mdadm --detail-platform gives:
mdadm: imsm capabilities not found for controller: /sys/device/pci0000:00/0000:00:1f.2 (SATA)
To try and see what is exactly going on, I put /root onto my non-raid /dev/sdc and booted. This successfully loads arch and mdadm assembles the array into RAID0, but very late in the boot process.
Cause
After reading up on initramfs, it appears that configuration is the cause of the problem and I need to include the firmware load for the Intel OROM/ 00:1f.2 controller and build the raid with the initramfs.
Solution
Presently, I don't understand how to modify mkinitcpio to make the array assemble before the kernel looks for the root device.
Reading & Background Material
I have looked at wiki's on mdadm, FAID_RAID, RAID and quite a few forum posts from arch, gentoo and ubuntu. Additionally, my system doesn't seem to like dmraid as it "Couldn't parse stripe destination".
http://download.intel.com/support/chips … _linux.pdf
http://www.intel.com/content/www/us/en/support.html
https://bbs.archlinux.org/viewtopic.php?id=203674
https://bbs.archlinux.org/viewtopic.php?id=178171
and this false bug https://bugs.archlinux.org/task/46295
The code for the Problem is:
:: running early hook [udev]
starting version 228
:: running hook [udev]
:: Triggering uenvents...
ERROR: device '1a227578-4431-4050-8381-f5b9c74929c5' not found. Skipping fsck.
ERROR: Unable to find root device '1a227578-4431-4050-8381-f5b9c74929c5'.
You are being dropped to a recovery shell
Full dmesg for my system with /root put on my /dev/sdc3 partition. Its clear that mdadm does its job, just not at the right time.
http://paste2.org/A5IbNYWK
Here are my settings in arch-chroot:
blkid
/dev/sda: TYPE="isw_raid_member"
/dev/sdb: TYPE="isw_raid_member"
/dev/sdc1: LABEL="Data" UUID="46C00238C0022F2D" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="e0915f11-b04a-4f5e-bcc0-2ce0b07ba8ba"
/dev/sdc2: LABEL="BIOS_RVY" UUID="9032040A3203F44E" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="05a07c6b-c688-407b-bb4e-29bbab4ba8b1"
/dev/sdd1: LABEL="ARCH_201601" UUID="8866-9A65" TYPE="vfat" PARTLABEL="Microsoft Basic Data" PARTUUID="c29df90b-b4e4-4749-b529-22790c3b9380"
/dev/sr0: UUID="2007-02-13-02-23-10-" LABEL="U3 System" TYPE="iso9660"
/dev/loop0: TYPE="squashfs"
/dev/md126p1: LABEL="WinRE tools" UUID="4474F94474F9396E" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="34b40e71-2fb9-486e-ac6b-91ddbfeece86"
/dev/md126p2: LABEL="SYSTEM" UUID="FEFB-34BF" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="b0f2458b-8ffb-4f7e-8c69-5344a399d49f"
/dev/md126p4: UUID="F2FAA956FAA917BD" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="c5fa5fa1-97da-4939-9b28-85a521259b6e"
/dev/md126p5: UUID="7C38C94E38C907DA" TYPE="ntfs" PARTUUID="e75461a7-cf55-4bde-95e7-e569b590c19a"
/dev/md126p6: UUID="3E4456C744568197" TYPE="ntfs" PARTUUID="edb50885-fd0a-4675-8be7-35012fc59189"
/dev/md126p7: UUID="dd529ac1-bf0b-4e42-bfc5-352d54a447c7" TYPE="ext4" PARTUUID="1a227578-4431-4050-8381-f5b9c74929c5"
/dev/md126: PTUUID="2b1d3db7-de05-40a8-81b0-c661bd777580" PTTYPE="gpt"
/dev/md126p3: PARTLABEL="Microsoft reserved partition" PARTUUID="c2da964a-e983-44c3-8e02-c02660ac1719"
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 119.2G 0 disk
└─md126 9:126 0 238.5G 0 raid0
├─md126p1 259:0 0 600M 0 md
├─md126p2 259:1 0 300M 0 md /boot
├─md126p3 259:2 0 128M 0 md
├─md126p4 259:3 0 124.3G 0 md
├─md126p5 259:4 0 450M 0 md
├─md126p6 259:5 0 450M 0 md
└─md126p7 259:6 0 112.3G 0 md /
sdb 8:16 0 119.2G 0 disk
└─md126 9:126 0 238.5G 0 raid0
├─md126p1 259:0 0 600M 0 md
├─md126p2 259:1 0 300M 0 md /boot
├─md126p3 259:2 0 128M 0 md
├─md126p4 259:3 0 124.3G 0 md
├─md126p5 259:4 0 450M 0 md
├─md126p6 259:5 0 450M 0 md
└─md126p7 259:6 0 112.3G 0 md /
sdc 8:32 0 931.5G 0 disk
├─sdc1 8:33 0 915.2G 0 part
└─sdc2 8:34 0 16.3G 0 part
sdd 8:48 1 1.9G 0 disk
└─sdd1 8:49 1 1.9G 0 part
sr0 11:0 1 7M 0 rom
loop0 7:0 0 300.3M 1 loop
/ect/fstab/
# /dev/md126p7
UUID=dd529ac1-bf0b-4e42-bfc5-352d54a447c7 / ext4 rw,relatime,stripe=64,data=ordered 0 1
# /dev/md126p2 LABEL=SYSTEM
UUID=FEFB-34BF /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
/etc/mdadm.conf
DEVICE partitions
ARRAY /dev/md/imsm0 metadata=imsm UUID=1ff0a633:073bcd3f:6c1494e5:f80b0821
ARRAY /dev/md/RAID0IMSVolume_0 container=/dev/md/imsm0 member=0 UUID=0f371f1e:faa85ec7:71cc4cf8:5611024d
/etc/mkinitcpio.conf
MODULES=""
BINARIES="/sbin/mdmon"
FILES=""
HOOKS="base udev autodetect modconf block mdadm_udev filesystems keyboard fsck shutdown"
/boot/loader/entries/arch.conf
title Arch_Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=PARTUUID=1a227578-4431-4050-8381-f5b9c74929c5 rw
Keywords: IMSM IRST FAKE RAID RAID0 Intel Rapid Storage Technology mdadm Windows OROM
Last edited by Quantum_C (2016-02-18 21:12:54)
Offline
Reserved
Last edited by Quantum_C (2016-02-17 02:43:31)
Offline
Did you solve the problem? I have MSI Dragon edition 2 and 3 SSD with fake raid. I did not install the Arch linux with dual boot windows 10.
Offline
I am like you too..
Offline
Dropping this here: https://wiki.archlinux.org/index.php/RA … ux_on_RAID
Offline
I do not know if Quantum_C and redragon ahve the same problem. But in my case the raid 0 array was created before. I already have a windows 10 installed in the raid array.
Offline