Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
intel fakeraid (imsm) + raid0 root partition + mdadm + genke
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
Ginta
Tux's lil' helper
Tux's lil' helper


Joined: 17 Feb 2006
Posts: 127
Location: Spain

PostPosted: Sat Aug 01, 2015 10:33 am    Post subject: intel fakeraid (imsm) + raid0 root partition + mdadm + genke Reply with quote

HI there, I am two days trying to solve this nasty issue with my raid0 setup on the root partition.

I've read and read, without coming to a solution, but now I can manually boot my system by dropping to a rescue shell, and issuing the command:
mdadm -I /dev/md127

Once I do that, I hit ctrl+D and the system boots, but.. isn't the purpose of genkernel-next and --mdadm option to automatically do this for me before init?

Any hint so the system can boot automatically?

Thanks
_________________
Somebody should use emerge brain on theirselves...
Back to top
View user's profile Send private message
frostschutz
Advocate
Advocate


Joined: 22 Feb 2005
Posts: 2932
Location: Germany

PostPosted: Sat Aug 01, 2015 10:54 am    Post subject: Reply with quote

Are you dual boot with Windows? Otherwise just get rid of the imsm and use pure mdadm.

What dost your mdadm.conf look like?
Back to top
View user's profile Send private message
Ginta
Tux's lil' helper
Tux's lil' helper


Joined: 17 Feb 2006
Posts: 127
Location: Spain

PostPosted: Sat Aug 01, 2015 12:08 pm    Post subject: Reply with quote

Yes, I do use dual boot with windows, otherwise Id just use btrfs raid, which is not so complicated.

Anyway, this is my file

Code:

ARRAY /dev/md/imsm0 metadata=imsm UUID=07fe4dab:3a3f5afa:03cb190e:a43c4c6b
ARRAY /dev/md/vol0 container=/dev/md/imsm0 member=0 UUID=a7feeae2:1954a831:1adb49c8:cc29ac18

_________________
Somebody should use emerge brain on theirselves...
Back to top
View user's profile Send private message
Ginta
Tux's lil' helper
Tux's lil' helper


Joined: 17 Feb 2006
Posts: 127
Location: Spain

PostPosted: Mon Aug 03, 2015 8:00 am    Post subject: Reply with quote

What more info do you need from my system?

I can also tell that once I type shell when it says no / partition found, and execute the command manually, after boot, my /proc/mdstat seems good:

Code:

Personalities : [raid0]
md126 : active raid0 sda[2] sdb[1] sdc[0]
      351654912 blocks super external:/md127/0 16k chunks
     
md127 : inactive sdb[2](S) sda[1](S) sdc[0](S)
      7929 blocks super external:imsm
       
unused devices: <none>

_________________
Somebody should use emerge brain on theirselves...
Back to top
View user's profile Send private message
frostschutz
Advocate
Advocate


Joined: 22 Feb 2005
Posts: 2932
Location: Germany

PostPosted: Mon Aug 03, 2015 10:51 am    Post subject: Reply with quote

That does not look wrong to me. So for some reason something goes awry in your Initramfs. Unfortunately I don't have first hand experience with genkernel(-next)/imsm so maybe somebody else has some ideas.

Edit:

You could try changing /dev/md/imsm0 and /dev/md/vol0 to /dev/md126 /dev/md127 (or /dev/md0 /dev/md1 if you prefer those numbers) resp. in your mdadm.conf just in case initramfs gets confused about /dev/md/NAME style. Then update initramfs and try again.
Back to top
View user's profile Send private message
buddyabaddon
n00b
n00b


Joined: 05 May 2004
Posts: 3
Location: USA

PostPosted: Fri Nov 24, 2017 11:47 pm    Post subject: Reply with quote

I had the same issue with my root imsm raid0 array as well.

My initramfs is created via 'genkernel-next --udev --mdadm --no-dmraid' and it too would always drop me into an emergency shell upon boot. From there I would run 'mdadm --run /dev/md127' and my root partition would be forced active and the system would continue to boot. Back before systemd with the old genkernel and initrc, everything worked as expected.

It turns out the issue is a bug in genkernel-next. The udev rules that are part of the sys-fs/mdadm package are not appended to the initramfs causing the behavior you are seeing.

I modified genkernel-next's 'gen_initramfs.sh' script to include these udev rules (63-md-raid-arrays.rules and 64-md-raid-assembly.rules) in the initramfs and everything begins to work as it should. The container and arrays assemble automatically and the kernel successfully loads root.

Here's the submitted fix to genkernel-next:
https://github.com/Sabayon/genkernel-next/pull/57
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum