View previous topic :: View next topic |
Author |
Message |
axs n00b
Joined: 23 Nov 2004 Posts: 12
|
Posted: Wed Sep 27, 2006 3:07 pm Post subject: |
|
|
Does genkernel 3.4.x still have issues creating the dmraid device nodes properly?? If so you might want to revert to genkernel 3.3.11d.
Also by default, genkernel uses its own internal version of dmraid, so you'll have to update genkernel.conf (as mentioned above) to use the new dmraid version, and copy the dmraid tar.bz2 from /usr/portage/distfiles/ to /usr/share/genkernel/pkg/ --that is, if you find you need the new dmraid version. |
|
Back to top |
|
|
kami22 Tux's lil' helper
Joined: 14 Apr 2006 Posts: 116
|
Posted: Thu Sep 28, 2006 7:50 am Post subject: |
|
|
Okay i found the error i have to user rc11 then it works really fine. Everything is okay. Thanks a lot. Problem Solved. Just use dmraid-1.0.0_rc11.
Cu kami |
|
Back to top |
|
|
RenaFrita n00b
Joined: 29 Sep 2006 Posts: 6
|
Posted: Fri Sep 29, 2006 3:45 am Post subject: Booting grub in Raid0 (vt6421 IDE RAID) |
|
|
Hi there!
I have a VIA vt6421 IDE RAID Controller, and i followed the HOWTO in:
--> http://gentoo-wiki.com/HOWTO_Install_Gentoo_with_NVRAID_using_dmraid
and i am able to install grub has expected (in the 1st method of the HOWTO).
However, when i reboot, i get the infamous
Error 17: Unable to mount partition
this is my grub.conf:
Code: | timeout 30
default 0
title Gentoo
root (hd0,0)
kernel (hd0,0)/kernel root=/dev/ram0 real_root=/dev/mapper/via_chddijgjah3 init=/linuxrc
initrd (hd0,0)/initrd
title Windows NT / Windows 95 boot menu
rootnoverify (hd0,2)
makeactive
chainloader +1
|
and ive installed grub like this:
Code: | device (hd0,0) /dev/mapper/via_lalalalala1
device (hd0) /dev/mapper/via_lalalalala
root (hd0,0)
setup (hd0) | And all appeared fine.
please, someone help me, im getting CRAZY with this
thanks |
|
Back to top |
|
|
bytesniper n00b
Joined: 12 Mar 2006 Posts: 33 Location: Abq, NM
|
Posted: Fri Sep 29, 2006 6:44 am Post subject: |
|
|
I know that with mdraid the boot parition cannot be a stripe and would think that this would hold true to dmraid as well although I have never used it. gentoo-wiki appears to be down right now so not sure exactly what the how-to says but i would either mirror /boot or put it on a partition thats not in an array.
hth,
joseph |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54214 Location: 56N 3W
|
Posted: Fri Sep 29, 2006 3:22 pm Post subject: |
|
|
RenaFrita,
Welcome to Gentoo
You need to add dodmraid to your kernel line, or dmraid will not be started in the initrd.
What bytesniper says is correct for kernel raid but not true for dmraid. This is because the BIOS shows grub the fake raid as if it were a real physical drive, which keeps grun happy.
With the dodmraid missing, the dmraid kernel module is not started, so the dmraid partitions never appear.
[edit - I've moved yor post here with the other dmraid issues] _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
RenaFrita n00b
Joined: 29 Sep 2006 Posts: 6
|
Posted: Fri Sep 29, 2006 7:02 pm Post subject: |
|
|
you mean like this?
Code: | kernel (hd0,0)/kernel dodmraid root=/dev/ram0 real_root=/dev/mapper/via_chddijgjah3 init=/linuxrc |
|
|
Back to top |
|
|
Phk Guru
Joined: 02 Feb 2004 Posts: 428 Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time
|
Posted: Fri Sep 29, 2006 7:47 pm Post subject: |
|
|
Hi there Rena
Hi there Neddy
We (me+Renafrita) tried fixing the grub.conf.. even deleting it.. No good, same s***
The problem with Rena's computer is very strange. We both have a FakeRaid0 with 2 HDD, and we did the installation side-by-side.
However, my installation required that i boot from diskette (grub said: "Cannot mount selected partition" when i "setup (hd0)"), but Rena's grub behave strangely.
Quote: | grub --device-map=/dev/null
(here, his grub detects (hd0,_), but every partition gets the "unknown" type)
device (hd0,0) /dev/mapper/......
device (hd0) /dev/mapper/.....
setup (hd0,0)
root (hd0)
(here, after the "device" command, his grub correctly detects the partition type and FS.)
|
As you see, the grub behaviour seems quite normal... However, on reboot, a simple "Error 17" message is all that is left.
This (Rena's) computer does not have a Diskette drive, so we booted grub from a USB stick...
Well... I don't know if this is normal, but there is no "DEVICE" command in the Stick's grub shell, and like i sad above, grub detects "(HD0,_)" but every partition has filesystem "unknown".... (since we can't use the "device" command, we can't make it work fine like we did on the normal grub shell)
This is really strange Neddy, could you guess what this can be?
BTW, we also tried to get a version of patched device-mapper raid.. But we couldn't find it Tips??
Thanks! (in name of rena, who can't write more than 4 words... hihihihi)
cheers everyone!
Phk _________________ "# cat /dev/urandom >> /tmp/life" |
|
Back to top |
|
|
natesully n00b
Joined: 23 Feb 2006 Posts: 49
|
Posted: Sat Sep 30, 2006 3:48 am Post subject: My dmraid devices vanished... |
|
|
Well, for once a google search didn't save me. I have an Nforce 5 AMD64 system, and my dmraid devices dissapeared- only "control" is under /dev/mapper. I updated the kernel, wich probably caused that, but now comes the fun part- I can't run the 2006.1 AMD64 livecd. Even with dodmraid and noapic (to stop the hang), dmraid detects no devices. The SATA works fine, I can acces individual drives and my standalone drive- but dmsetup reports "no detected devices".
Obviously, I'm in windows making this post, so I'm pretty sure some devices are there. The NVIDIA bios tool reports the raid is there as well.
Oddly enough, my kernel log shows some "dm-3" with a reiserfs partition on it being mounted as root right before init goes all single-user on me. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54214 Location: 56N 3W
|
Posted: Sat Sep 30, 2006 9:42 am Post subject: |
|
|
Phk,
First, grub does not detect anything - it uses the drive information provided by the BIOS, which is why all drives are (hd... to grub.
Using a USB stick may complicate the issue. The BIOS will see it as a hard drive and that will change all your (hd... numbers, which will confuse grub.
As this threaad warns, genkernel uses its own dmraid, whch can be different to the version you get with emerge dmraid.
The thread also tells how to fix that.
I would order things slighthly differently on the kernel line Code: | kernel (hd0,0)/kernel root=/dev/ram0 init=/linux ramdisk=8192 real_root=/dev/mapper/via_chddijgjah3 dodmraid |
To help with the problem isolation, tell what steps work
1. The BIOS loads the MBR, if that fails you get an error from the BIOS, not grub.
2. The MBR (Grub stage 1) loads Grub stage 1.5. If this fails, you get very terse English error messages
3. Grub stage 1.5 can read the /boot filesystem to load grub stage 2 - This gives the well known Error:nn messages.
4. Grub stage 2 does all the work.
loads the splash screen
displays the grub menu
loads the kernel
loads the initrd
exits by passing control to the kernel Grub stage 2 uses the same list of errors as stage 1.5
From your Error 17, either grub stage 1.5 cannot read /boot to load stage 2. This happens if you chaneg ther /boot filesystem but do not reinstall grub on the MBR, or stage 2 cannot read /boot, or whatever in needs to load the splashimage, kernel or initrd. Error 17 says Code: | 17 : Cannot mount selected partition
This error is returned if the partition requested exists, but the
filesystem type cannot be recognized by GRUB. |
So grub has found the partition, but can't read it.
Please describe the hard drives, the partition schemes, the filesystems on each partition, post your ls -al /boot output and your grub.conf. No copy typing please, its too error prone. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54214 Location: 56N 3W
|
Posted: Sat Sep 30, 2006 10:36 am Post subject: |
|
|
natesully,
You probably have the old dmraid/new kernel issue which is fully descibed, with the solution, in this thread. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
RenaFrita n00b
Joined: 29 Sep 2006 Posts: 6
|
Posted: Sat Sep 30, 2006 2:40 pm Post subject: |
|
|
hi one more time!
Code: | rr4dvd / # ls -al /boot
total 4790
drwxr-xr-x 5 root root 1024 Sep 29 03:36 .
drwxr-xr-x 19 root root 4096 Sep 29 00:05 ..
-rw-r--r-- 1 root root 0 Aug 3 14:23 .keep
-rw-r--r-- 1 root root 0 Sep 28 23:55 .keep_sys-boot_lilo-0
-rw-r--r-- 1 root root 800291 Sep 28 21:43 System.map-genkernel-x86-2.6.15-ge ntoo-r1
lrwxrwxrwx 1 root root 1 Sep 28 15:25 boot -> .
-rw-r--r-- 1 root root 5032 Sep 29 00:07 diag1.img
-rw-r--r-- 1 15198 root 130421 Sep 28 09:20 dmraid-1.0.0.rc8.tar.bz2
drwxr-xr-x 2 root root 1024 Sep 28 22:01 grub
-rw-r--r-- 1 root root 946765 Sep 28 21:44 initramfs-genkernel-x86-2.6.15-gen too-r1
-rw-r--r-- 1 root root 739422 Sep 28 21:53 initrd
lrwxrwxrwx 1 root root 37 Sep 29 03:05 kernel -> kernel-genkernel-x86-2.6 .15-gentoo-r1
-rw-r--r-- 1 root root 2199825 Sep 28 21:43 kernel-genkernel-x86-2.6.15-gentoo -r1
-rwxr-xr-x 1 15198 root 4759 Sep 28 09:20 linuxrc
drwx------ 2 root root 12288 Sep 28 15:18 lost+found
drwxr-xr-x 2 root root 1024 Sep 29 04:28 net
-rw-r--r-- 1 15198 root 28576 Sep 28 09:20 o_meu_config |
My partition scheme
Code: | rr4dvd / # fdisk -l /dev/mapper/via_chddijgjah
Disk /dev/mapper/via_chddijgjah: 200.0 GB, 200060484608 bytes
255 heads, 63 sectors/track, 24322 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/mapper/via_chddijgjah1 * 1 9 72261 83 Linux -> ext3 ->boot
/dev/mapper/via_chddijgjah2 10 3049 24418800 17 Hidden HPFS/NTFS -> windows
/dev/mapper/via_chddijgjah3 3050 6089 24418800 83 Linux ->ext3 -> root
|
I have one more partition extended with two partitions one for swap and other for stuff but fdisk doesnt see it, and i dont know why!
My raid controller
0000:01:07.0 RAID bus controller: VIA Technologies, Inc. VT6421 IDE RAID Controller (rev 50)
My hard Drives
SATA HDD (5400rpm):SATA hard disk
100 GB
and finally my grub.conf
Code: | imeout 30
default 0
splashimage=(hd0,0)/grub/splash.xpm.gz
title Gentoo
root (hd0,0)
kernel (hd0,0)/kernel root=/dev/ram0 real_root=/dev/mapper/via_chddijgjah3 init=/linuxrc dodmraid
initrd (hd0,0)/initrd
title Windows NT / Windows 95 boot menu
rootnoverify (hd0,2)
makeactive
chainloader +1 |
|
|
Back to top |
|
|
RenaFrita n00b
Joined: 29 Sep 2006 Posts: 6
|
Posted: Sat Sep 30, 2006 2:43 pm Post subject: |
|
|
the dmraid and kernel versions that im using are the ones in the ls -al /boot
Thanks for all the help, im starting to get a little crazy with these |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54214 Location: 56N 3W
|
Posted: Sat Sep 30, 2006 4:02 pm Post subject: |
|
|
RenaFrita,
When does the error message come up ?
You have an 'old' kernel, Its before 2.6.16. That needs an old dmraid too.
If you have ever done an emerge sync, and a world update, you will have got the new dmraid and new genkernel.
That combination if know to fail.
If thats the problem, you will have a later kernel in /usr/src, the solution is to update to the newer kernel.
I cannot determine from your posts, what version of dmraid is in your initrd. For that, you need to read the genkernel config files
Your linuxrc should not be in boot, its inside the initrd file. Your Code: | 739422 Sep 28 21:53 initrd | looks to be very small.
You may have more luck using Code: | initrd initramfs-genkernel-x86-2.6.15-gentoo-r1 | which is the initrd that genkernel made for you. Did you tell genkerel to add in dmraid ? _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
RenaFrita n00b
Joined: 29 Sep 2006 Posts: 6
|
Posted: Sat Sep 30, 2006 5:17 pm Post subject: |
|
|
the erro comes up like this
GRUB loading stage1.5.
GRUB loading , please wait...
Error 17
i used the parameter --dmraid when i called genkernel
here is some of my config of genkernel.conf
Code: | DEVICE_MAPPER_VER="1.00.17"
DEVICE_MAPPER_DIR="device-mapper.${DEVICE_MAPPER_VER}"
DEVICE_MAPPER_SRCTAR="${GK_SHARE}/pkg/device-mapper.${DEVICE_MAPPER_VER}.tgz"
DEVICE_MAPPER_BINCACHE="%%CACHE%%/device-mapper-${DEVICE_MAPPER_VER}-%%ARCH%%.tar.bz2"
DMRAID_VER="1.0.0.rc8"
DMRAID_DIR="dmraid/${DMRAID_VER}"
DMRAID_SRCTAR="${GK_SHARE}/pkg/dmraid-${DMRAID_VER}.tar.bz2"
DMRAID_BINCACHE="%%CACHE%%/dmraid-${DMRAID_VER}-%%ARCH%%.tar.bz2"
|
|
|
Back to top |
|
|
RaceTM Apprentice
Joined: 16 Feb 2004 Posts: 281
|
Posted: Tue Oct 03, 2006 1:45 am Post subject: |
|
|
RenaFrita wrote: | the erro comes up like this
GRUB loading stage1.5.
GRUB loading , please wait...
Error 17
i used the parameter --dmraid when i called genkernel
here is some of my config of genkernel.conf
Code: | DEVICE_MAPPER_VER="1.00.17"
DEVICE_MAPPER_DIR="device-mapper.${DEVICE_MAPPER_VER}"
DEVICE_MAPPER_SRCTAR="${GK_SHARE}/pkg/device-mapper.${DEVICE_MAPPER_VER}.tgz"
DEVICE_MAPPER_BINCACHE="%%CACHE%%/device-mapper-${DEVICE_MAPPER_VER}-%%ARCH%%.tar.bz2"
DMRAID_VER="1.0.0.rc8"
DMRAID_DIR="dmraid/${DMRAID_VER}"
DMRAID_SRCTAR="${GK_SHARE}/pkg/dmraid-${DMRAID_VER}.tar.bz2"
DMRAID_BINCACHE="%%CACHE%%/dmraid-${DMRAID_VER}-%%ARCH%%.tar.bz2"
|
|
May I suggest updating the version of dmraid that genkernel uses? The instructions are in this thread |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54214 Location: 56N 3W
|
Posted: Tue Oct 03, 2006 9:06 am Post subject: |
|
|
RenaFrita,
Your initrd is made with Code: | DMRAID_VER="1.0.0.rc8" | That will not work with kernels after 2.6.15.
As RaceTM says, you need to update the dmraid version used in the initrd. Thats not always the version that shows you.
However, Error 17 means grun found your partition but cannot read read it.
Did you change the filesystem on /boot after grub was installed to the MBR ?
That will cause Error 17. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
RenaFrita n00b
Joined: 29 Sep 2006 Posts: 6
|
Posted: Tue Oct 03, 2006 7:31 pm Post subject: |
|
|
No i dint change my filesystem, and changed the genkernel.conf file after i post here to use my dmraid version and it wont work anyway
Anyway i give up on raid0, i dont have time to lose with that now, ill be back on january.
Thanks for all the help, ill be more luck next time;) |
|
Back to top |
|
|
Zordas n00b
Joined: 10 Jun 2003 Posts: 19
|
Posted: Wed Oct 04, 2006 7:56 pm Post subject: Excellent !! |
|
|
I followed the instructions and it worked the very first time !!!
On a side note I wanted to let everyone know that Genkernel 3.4.1 DOES work. (At least it did on my NFORCE3 AMD64 rig). All I had to do was change Genkernel to dmraid-1.0.0.rc11 and move the package to the correct directory.
Thanks for the posts.. Saved me countless hours of heart/head aches. |
|
Back to top |
|
|
hazer n00b
Joined: 02 Sep 2004 Posts: 55
|
Posted: Tue Oct 10, 2006 11:00 pm Post subject: |
|
|
Yet another problem with dmraid and updating...
Old system:
dmraid rc8
gentoo-sources 2.6.16-r1
Updates:
dmraid rc12-pre1
gentoo-sources 2.6.18
I've followed the directions in this thread on how to update dmraid and according to the shell after a reboot I have rc12-pre1 and device-mapper 4.7.0. The reason I'm in the shell is it goes to start dmraid and can't find any devices. I have a /dev/mapper directory, but all that is in there is a control file. I tried compiling dmraid static into the kernel but that puts me further away from this working (device-mapper goes to 'unknown' and /dev/mapper vanishes).
I have support built in for the SATA controller, I have dmraid compiled as a module (and I assume it's being included by genkernel for the boot), I've updated everything I can think of but I have to have missed something.... |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54214 Location: 56N 3W
|
Posted: Tue Oct 10, 2006 11:17 pm Post subject: |
|
|
hazer,
Try Code: | emerge --sync
emerge world -uDNav | Its all supposed to 'just work' with the latest genkernel.
So much so, I was thinking of unsticking this thread.
I don't understant your reference to building dmraid in the kernel.
dmraid is a third party kernel module and cannot be built in. If you need it for booting, you need to use and initrd. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
hazer n00b
Joined: 02 Sep 2004 Posts: 55
|
Posted: Tue Oct 10, 2006 11:47 pm Post subject: |
|
|
NeddySeagoon wrote: | hazer,
Try Code: | emerge --sync
emerge world -uDNav | Its all supposed to 'just work' with the latest genkernel.
So much so, I was thinking of unsticking this thread.
I don't understant your reference to building dmraid in the kernel.
dmraid is a third party kernel module and cannot be built in. If you need it for booting, you need to use and initrd. |
device mapper is an option in the kernel. You have to have support for device mapper in the kernel or dmraid won't work (at least that's what I've been told on multiple occasions). I wasn't paying attention to what I typed a bit ago.
I'd do an emerge world except that's over 300mb of downloads right now and I'm working on it a bit at a time. Updated gcc, glibc, updated Xorg from 6.9 to 7.0 (nightmare in and of itself), updated KDE from 3.5.2 to 3.5.4.... I wouldn't be working on the kernel update now except that the nvidia-driver produced module refuses to load. I figure that since I updated gcc and glibc but hadn't rebuilt 2.6.16-r1 that it was compatability issues so I might as well update the kernel.... I might be better off rebuilding 2.6.16-r1 for now and getting more of the system updated before I attempt to jump to 2.6.18...
It never fails... when I attempt to do major updates there's always *something* nightmare-class that goes wrong. Murphy loves me. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54214 Location: 56N 3W
|
Posted: Wed Oct 11, 2006 9:52 am Post subject: |
|
|
hazer,
Your kernel and all of its modules must be compiled with the same version of gcc.
That means after a gcc update, you can no longer build 3rd party kernel modules, that includes dmraid and the nvidia kernel module. You can either switch back to you old gcc, or rebuild and reinstall the kernel.
There are two things loosly referred to as dmraild. The kernel part is device mapper support, which is under the Multiple Device section and the Red Hat maintained dmraid third party kernel module.
To make it all work nicely together, rebuild and reinstall your kernel using your new gcc and be sure you get the latest genkernel if you want to use genkernel. One recent version left out dmraid entirely. Details in this thread. The most recent genkernel uses a dmraid that works with kernels > 2.15.
Start your kernel build with Code: | cd /usr/src/linux
make clean | to be sure that there are no old binaries, made with the old gcc left in your tree. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
hazer n00b
Joined: 02 Sep 2004 Posts: 55
|
Posted: Wed Oct 11, 2006 2:19 pm Post subject: |
|
|
Yeah, I've been sure to do a manual "make clean" just to verify that nothing was there. I emerged the kernel after having updated gcc (then changed over to it with gcc-config), glibc, KDE and Xorg so it should have been 'clean' from the start but no reason not to make absolutely sure.
The thing that baffles me about the problem with the nvidia-driver is I emerged it after updating X and it ran for a week with multiple reboots with no problem (I have a 40gb IDE drive with a Windows install for playing World of Warcraft with friends). I went to reboot into Linux on Monday and bingo... no more X because the nvidia kernel module fails to load.
I'll revert back to the older gcc and re-emerge the nvidia-driver package. That *should* get me functional for now, but I'm still not sure why I can't get 2.6.18 to build and work.
When I compile device-mapper static in the kernel /dev/mapper doesn't appear in the shell. When I compile it as a module /dev/mapper appears, but only has a control file in it. As I said before I followed the directions in here to update dmraid to rc12-pre1 and I've done an 'emerge device-mapper' to make sure it's up to date.... it's like the hardware isn't being recognised by dmraid anymore and I'm not sure why. |
|
Back to top |
|
|
AngryLlama Tux's lil' helper
Joined: 30 Sep 2004 Posts: 111
|
Posted: Thu Oct 19, 2006 8:53 am Post subject: |
|
|
I'm sorry, but am I the only one who gets Code: | DMRAID directory ${DMRAID_DIR} is invalid! | when I run genkernel with a modified genkernel.conf: Code: | DMRAID_VER="1.0.0.rc12"
DMRAID_DIR="dmraid/${DMRAID_VER}: |
I've tried making a pkg/dmraid directory. I've tried chaning DMRAID_DIR to use a '.' instead of a '/'. Any ideas?
EDIT: Nevermind, it turns out the new genkernel can handle the -pre1 suffix. Unfortunately, I still get a "Block device /dev/mapper/nvidia_fubar# is not a valid root device..." Even though I've followed the instructions and I even compiled the nVidia SATA driver into the kernel. dmraid -V returns rc12 while stuck at the shell during boot. |
|
Back to top |
|
|
AngryLlama Tux's lil' helper
Joined: 30 Sep 2004 Posts: 111
|
Posted: Fri Oct 20, 2006 12:12 am Post subject: |
|
|
Anyone? I've followed the instructions on the first two pages of this thread. |
|
Back to top |
|
|
|
|
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
|
|