hi, After rebuilding my raid i was unable to install grub (failed at setup(hd0)), booting from my notebook hd i found out, that the naming-scheme was different. finally i found out why grub wouldn't install anymore on my fakeraid. i am using the latest dmraid-1.0.0_rc16 with genkernel. (also does the sysrescuecd i always used to recover). Looks like the "dmraid-1.0.0_rc16-undo-p-rename.patch" is responsible. genkernel seems to build dmraid without that patch, and during boot detect the raidpartitions with the additional "p". After boot, the systems dmraid (including the undo-patch) kicks in, and makes it impossible to install grub. if i run "dmraid -ay" by hand i get additional mapper-interfaces without p and cann install grub using those device-names. Suggestion: either make genkernel use the ebuild / the patch from the ebuild or remove that patch from the ebuild Reproducible: Always Steps to Reproduce: 1. emerge sys-fs/dmraid-1.0.0_rc16 2. make genkernel use dmraid-1.0.0_rc16 3. rebuild kernel 4. try reinstalling grub on a fakeraid Actual Results: grub fails to install on fakeraid Expected Results: grub succesfully installs on fakeraid
The current version of dmraid installs a distfile for you to use with genkernel, called dmraid-[whatever-version]-prepatched.tar.bz2, and stores it in /usr/share/dmraid/ Could you confirm that this is the file you're telling genkernel to use?
actually, to make it easier, could you attach your /etc/genkernel.conf so i could see your settings? Thanks,
(In reply to comment #2) > actually, to make it easier, could you attach your /etc/genkernel.conf so i > could see your settings? I will do that when i get back to that machine. My guess is, genkernel uses its own src-file, because all i changed was the dmraid-version string to DMRAID_VER="1.0.0.rc16" and it complained about the src-file not being in /var/cache/genkernel/src/. I didn't know about the prepatched version, but i guess i will just change the line in genkernel to use it. thx so far...
Ahh, ok yes that would do it. Genkernel does use its own tarball for (i believe) all of its components. The post-install message from sys-fs/dmraid provides instructions on what you need to do to use it with Genkernel: [quote="ebuild"] If you would rather use this version of DMRAID with Genkernel, update the following in /etc/genkernel.conf: DMRAID_VER="1.0.0.rc16" DMRAID_SRCTAR="/usr/share/dmraid/dmraid-1.0.0.rc16-prepatched.tar.bz2" [/quote]
(In reply to comment #4) > Ahh, ok yes that would do it. Genkernel does use its own tarball for (i > believe) all of its components. The post-install message from sys-fs/dmraid > provides instructions on what you need to do to use it with Genkernel: Ouch, yes you are right! This is my bad, i ignored the postinst (or it just scrolled by..), because it it looked just like the one from -rc15, except the changed path.
