| View previous topic :: View next topic |
| Author |
Message |
devsk
Advocate
Joined: 24 Oct 2003
Posts: 2995
Location: Bay Area, CA
|
 Posted: Wed Sep 13, 2006 8:55 pm Post subject: |
 |
|
@thauer: not necessarily because I ran the same 'find' command on my setup and came up with nothing, but I know udev is there.
The reason might be that genkernel of late has changed the initramfs construction. Now its a "cat" of all the cpio archives, earlier it was a cpio archive in itself. So, find no longer works on it. Niether does cpio.
So, that's not your problem. |
|
| Back to top |
|
 |
thauer
n00b
Joined: 28 Aug 2004
Posts: 22
Location: Switzerland
|
| Posted: Wed Sep 13, 2006 9:17 pm Post subject: |
|
|
| Quote: | @thauer: not necessarily because I ran the same 'find' command on my setup and came up with nothing, but I know udev is there.
The reason might be that genkernel of late has changed the initramfs construction. Now its a "cat" of all the cpio archives, earlier it was a cpio archive in itself. So, find no longer works on it. Niether does cpio.
|
Just to clarify: I was running that find on a fully unpacked initramfs in both cases. I know it's a cat of cpios. And I can see the content when the boot process hangs too using the busybox shell. |
|
| Back to top |
|
|
thauer
n00b
Joined: 28 Aug 2004
Posts: 22
Location: Switzerland
|
| Posted: Thu Sep 14, 2006 7:15 am Post subject: |
|
|
| OK, finally I think I begin to see the light at the end of the tunnel. I have not been able to boot my system yet, but I am definitely affected by this bug |
|
| Back to top |
|
|
burger
n00b
Joined: 07 Mar 2004
Posts: 35
Location: Sweden
|
| Posted: Thu Sep 14, 2006 5:40 pm Post subject: |
|
|
| devsk wrote: | | burger wrote: |
But I have installed the bootloader in the linux partition (hd0,2). |
I wonder why you did that? |
Because I use the Windows Vista RC1 bootloader in (hd0) =) |
|
| Back to top |
|
|
devsk
Advocate
Joined: 24 Oct 2003
Posts: 2995
Location: Bay Area, CA
|
| Posted: Thu Sep 14, 2006 5:43 pm Post subject: |
|
|
| Quote: |
Because I use the Windows Vista RC1 bootloader in (hd0) =) |
oh, you bugger!...shame on you...  |
|
| Back to top |
|
|
burger
n00b
Joined: 07 Mar 2004
Posts: 35
Location: Sweden
|
| Posted: Thu Sep 14, 2006 5:54 pm Post subject: |
|
|
| thauer wrote: | | OK, finally I think I begin to see the light at the end of the tunnel. I have not been able to boot my system yet, but I am definitely affected by this bug |
Thanx to a patch from that bug I got a bit further in booting my linux. Now it says something like:
| Code: | >> The root block device is unspecified or not detected
Please specify a device to boot, or "shell" for a shell...
boot() :: |
I got a /dev/mapper/ directory with a control and nvidia_echfgbbb file, but not the others... and the dmraid version is .r10 so now I need to update the dmraid that is in the kernel or something like that? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54209
Location: 56N 3W
|
| Posted: Thu Sep 14, 2006 6:14 pm Post subject: |
|
|
burger,
yes - you need -rc12 I think
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
burger
n00b
Joined: 07 Mar 2004
Posts: 35
Location: Sweden
|
| Posted: Thu Sep 14, 2006 7:10 pm Post subject: |
|
|
| NeddySeagoon wrote: | burger,
yes - you need -rc12 I think |
yes... but how do I modify genkernel to use -rc12 then? |
|
| Back to top |
|
|
devsk
Advocate
Joined: 24 Oct 2003
Posts: 2995
Location: Bay Area, CA
|
| Posted: Thu Sep 14, 2006 7:26 pm Post subject: |
|
|
| look at /etc/genkernel.conf and search for DMRAID |
|
| Back to top |
|
|
burger
n00b
Joined: 07 Mar 2004
Posts: 35
Location: Sweden
|
| Posted: Thu Sep 14, 2006 7:57 pm Post subject: |
|
|
| devsk wrote: | | look at /etc/genkernel.conf and search for DMRAID |
Thanx... I did like this:
| LoSeR_5150 wrote: | I believe I have found an easier solution... I modified my /etc/genkernel.conf ... edited
| Code: |
DMRAID_VER="1.0.0.rc10"
DMRAID_DIR="dmraid/${DMRAID_VER}"
DMRAID_SRCTAR="${GK_SHARE}/pkg/dmraid-${DMRAID_VER}.tar.bz2"
DMRAID_BINCACHE="%%CACHE%%/dmraid-${DMRAID_VER}-%%ARCH%%.tar.bz2"
|
to
| Code: |
DMRAID_VER="1.0.0.rc11"
DMRAID_DIR="dmraid/${DMRAID_VER}"
DMRAID_SRCTAR="${GK_SHARE}/pkg/dmraid-${DMRAID_VER}.tar.bz2"
DMRAID_BINCACHE="%%CACHE%%/dmraid-${DMRAID_VER}-%%ARCH%%.tar.bz2"
|
then I downloaded
http://people.redhat.com/~heinzm/sw/dmraid/tst/old/dmraid-1.0.0.rc11-pre1.tar.bz2
to /usr/share/genkernel/pkg/
and renamed it to dmraid-1.0.0.rc11.tar.bz2 because the pre1 confuses genkernel.
after that I re-ran genkernel --menuconfig --dmraid --gensplash=livecd-2006.0 all , installed my kernel and rebooted Now I have a 2.6.17 kernel. Hope this helps someone |
but I used the .rc12pre1 instead of .rc11 and I booted my linux flaslessly! |
|
| Back to top |
|
|
krnlbg
n00b
Joined: 04 Sep 2006
Posts: 5
Location: Russia, Krasnoyarsk
|
| Posted: Fri Sep 15, 2006 3:14 pm Post subject: |
|
|
Hi all.
I have problem with install Gentoo on fake raid:
I had successfully installed it with 2006.0 minimal cd, genkernel 3.3 and dmraid rc12-pre1, but after update gcc to 4.1 compiling fails on udev in initrd building. With 2006.1 same problem. With 3.4 genkernel it's ok, but dmraid does not work. I tried to use udev 087 instead 077, it's building, but doesn't boot- error with devfs. |
|
| Back to top |
|
|
burger
n00b
Joined: 07 Mar 2004
Posts: 35
Location: Sweden
|
| Posted: Sat Sep 16, 2006 7:43 am Post subject: |
|
|
| krnlbg wrote: | Hi all.
I have problem with install Gentoo on fake raid:
I had successfully installed it with 2006.0 minimal cd, genkernel 3.3 and dmraid rc12-pre1, but after update gcc to 4.1 compiling fails on udev in initrd building. With 2006.1 same problem. With 3.4 genkernel it's ok, but dmraid does not work. I tried to use udev 087 instead 077, it's building, but doesn't boot- error with devfs. |
Then try what I did in my previous post: Thu Sep 14, 2006 8:57 pm. |
|
| Back to top |
|
|
BlackHatRob
Tux's lil' helper
Joined: 20 Feb 2005
Posts: 140
|
| Posted: Sat Sep 16, 2006 3:13 pm Post subject: Installing Gentoo on a Raid System |
|
|
Greetings!
I have been trying unsuccessfully to install gentoo\windows dualboot on my raid system (A8N-SLI Premium with nForce 4 chipset and software raid). I think I have been fairly successful but I am stuck at a particular point. Here is what I have done.
I have 2 striped 36gb sata raptors and 2 mirrored 250gb sata WD drives. I would like to use the 2 striped raptors as the primary drive for my system as the performance is greater.
I have followed the directions from this site: http://gentoo-wiki.com/HOWTO_Install_Gentoo_with_NVRAID_using_dmraid
With that being said, here is what I have done thus far (so you may double check my work):
1. booted the gentoo 2006.0 livecd with 'gentoo dodmraid'
2. verified that dmraid found and mapped my drives (it did)
3. fdisked the 2 arrays as follows
| Code: |
2x32gb raptors (striped) nvidia_cfdhcdbe
--------------------------------------------------------
Part No. & purpose | name of new mapping
--------------------------------------------------------
1 /boot nvidia_cfdhcdbe1
2 /windows nvidia_cfdhcdbe2
3 / nvidia_cfdhcdbe3
4 none (extended) nvidia_cfdhcdbe4
5 /usr nvidia_cfdhcdbe5
6 /var nvidia_cfdhcdbe6
2x250 gb WD (mirrored) nvidia_bcffacec
-------------------------------------------------------
Part No. & purpose | name of new mapping
-------------------------------------------------------
1 /swap nvidia_bcffacec1
2 /home nvidia_bcffacec2
3 /storage nvidia_bcffacec3
|
4. Mounted the above partitions and continued installing gentoo as directed in the HOWTO
5. I followed the "hard way' directions to get the ram image built but appeared to go smoothly
6. installed grub
<< THIS is where I think I may have messed up >>
7. modified the grub.conf and put the following (as per the HOWTO)
| Code: |
title Gentoo Linux
root (hd0,0)
kernel /kernels/2.6.17-gentoo-r8.kernel root=/dev/ram0 init=/linuxrc real_root=/dev/mapper/nvidia_cfdhcdbe3 dodmraid video=vesafb:ywrap,pmipal,1280x1024-16@60
initrd (hd0,0)/initrd
|
*NOTE: I am _NOT_ sure that root is (hd0,0) but I assume it is.
When you follow the HOWTO, you manually set up grub by setting the drive mapping = /dev/null. Then you put in your mappings. I am not sure, but I believe that you can map hd0,0 to /dev/mapper/nvidia_cfdhcdbe1 and treat hd0,0 as such. Am I correct?
If not, I have _NO_ idea which drive\array is hd0 or hd1 etc.
8. After doing all this, I go to reboot and I get the following error:
| Code: |
Block device /dev/mapper/nvidia_cfdhcdbe3 is not a valid root device.
The root block device is unspecified or not detected
|
Sure enough, when I look a little above that point where the boot fails, I see dmraid trying to detect things, but it says it cannot find any devices.
What did I miss?
Please and Thank you VERY VERY much in advance! |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54209
Location: 56N 3W
|
| Posted: Sat Sep 16, 2006 6:45 pm Post subject: |
|
|
BlackHatRob,
Have a read of the thread I've merged your post to. I expect its the kernel/dmraid pairing versioning issue or the genkernel issue. The fixes to both are discussed here
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
flipy
Apprentice
Joined: 15 Jul 2004
Posts: 232
|
| Posted: Sun Sep 17, 2006 8:57 pm Post subject: |
|
|
well, I've been reading this post lately, while trying to find a solution for my fake raid device.
the fact is that I've used to have dmraid working with old kernel versions (< 2.6.15), but now it won't work.
can't post any info because it's a dual boot machine, so I'll try to explain the more I remember.
My biggest problem is that when it loads the initrd, it seems to not find any device. (no blocks detected -- or something like that)
first time I've get into the shell, and did an dmraid -V, it seemed to not have any device-mapper version, so I've modified the genkernel.conf to use 1.02.07, along with the latest dmraid version (rc12-pre1 I believe).
So now I can go into the shell, do a dmraid -V and see that it's using a version of device-mapper, but still get a "no block detected" if I run dmraid -ay.
I don't know if it has to do something with the kernel config or something else...
So right now I've dmraid installed in the system, manually edited genkernel.conf to use device-mapper-1.02.07 and dmraid-rc12-pre1, and compiled the kernel with the usual things I've used to do...
So if anyone has any clue... I'll appreciate any kind of help!
thanks |
|
| Back to top |
|
|
devsk
Advocate
Joined: 24 Oct 2003
Posts: 2995
Location: Bay Area, CA
|
| Posted: Sun Sep 17, 2006 9:18 pm Post subject: |
|
|
| flipy wrote: | So if anyone has any clue... I'll appreciate any kind of help!
thanks |
sorry to tell you this, but you haven't read this thread completely. |
|
| Back to top |
|
|
flipy
Apprentice
Joined: 15 Jul 2004
Posts: 232
|
| Posted: Sun Sep 17, 2006 10:02 pm Post subject: |
|
|
| devsk wrote: | | flipy wrote: | So if anyone has any clue... I'll appreciate any kind of help!
thanks |
sorry to tell you this, but you haven't read this thread completely. |
uhm why?
I think I did...
by the way, it's really annoying to try to find a solution while having to back to another OS... |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54209
Location: 56N 3W
|
| Posted: Sun Sep 17, 2006 10:13 pm Post subject: |
|
|
flipy,
Go back to your old working kernel.
Add another booting block into grub.conf for your experimential new kernel.
This allows you to choose at boot, which kernel you will run.
It also allows easy recovery when you make a broken kernel, and we all do that from time to time.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
flipy
Apprentice
Joined: 15 Jul 2004
Posts: 232
|
| Posted: Sun Sep 17, 2006 11:08 pm Post subject: |
|
|
| NeddySeagoon wrote: | flipy,
Go back to your old working kernel.
Add another booting block into grub.conf for your experimential new kernel.
This allows you to choose at boot, which kernel you will run.
It also allows easy recovery when you make a broken kernel, and we all do that from time to time. |
the fact is that I'm doing a fresh install, so right now I just have a stage3 uncompressed system.
don't wanna make this a talk post, it was great to find new hints (but none of them worked), so I guess I'll have to reread everything again and do all the stuff until it get fixed.
(my last hope was genkernel-3.4.1, but it failed too).
I'll be watching this
good luck |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54209
Location: 56N 3W
|
| Posted: Sun Sep 17, 2006 11:36 pm Post subject: |
|
|
flipy,
There is a problem with recent genkernel - it omits dmraid from the initrd entirely.
The older genkernel uses dmraid-1.0.-0-rc8, which is only usegly up to 2.6.15 kernels.
This thread offers several workarounds pending a proper fix.
1. Use 2.6.15 and dmraid-1.0.0-rc8
2. Use 2.6.17 and dmraid-1.0.0-rc12 or there abouts.
Solution 1 just works - you get all the old bits and use them.
Solution 2 needs some editing of config files - this thread goes through several ways to make dmraid work with later kernels.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
NoControl
n00b
Joined: 06 Apr 2004
Posts: 74
|
| Posted: Mon Sep 18, 2006 3:48 am Post subject: |
|
|
| Just to let everyone know: when using genkernel-3.4.1 (recently marked stable), I can boot my dmraid just fine with the initrd built by genkernel. No editing of any config files required. This is on a Intel ICH5R fakeraid with kernel 2.6.16-gentoo-r13. |
|
| Back to top |
|
|
RaceTM
Apprentice
Joined: 16 Feb 2004
Posts: 281
|
| Posted: Mon Sep 18, 2006 12:23 pm Post subject: |
|
|
| NeddySeagoon wrote: |
Solution 2 needs some editing of config files - this thread goes through several ways to make dmraid work with later kernels. |
I have been working with this solution, using genkernel to generate a ramdisk...however I have not had any luck. I am working with a boot partition off of the raid array right now (I will migrate it to the array after I can actually get the system to boot the root partition from the array properly). I have been able to get the kernel to boot, but there seeems to be a problem either loading the ramdisk, or loading the root partition..i'm not sure which it is. Sometime after the kernel loads it complains about something like
VFS: Unable to mount root fs
I don't know if anyone has any idea as to whether this is referring to the ramdisk, or the root partition..and how to go about resolving it. but I can post a more exact error message tonight if needed.
as a note, I do have a proper combination of kernel and dmraid, as I can see all partitions when I am actually in the environment |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54209
Location: 56N 3W
|
| Posted: Mon Sep 18, 2006 12:30 pm Post subject: |
|
|
RaceTM,
A more exact error would help, if it ends in unknown-block (X,Y) where Xand Y are numbers, the numbers are very important to identify the cause of the error.
Also, at the time of the error, does the system offer you a shell ?
If so, is the shell busybox or bash ?
Busybox is included in the initrd, so if you have a busybox shell, the initrd is mounted but not the real_root. If the shell is bash, real_root is mounted.
See the post by NoControl too.
It looks like it just works for klater kernels now too
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
RaceTM
Apprentice
Joined: 16 Feb 2004
Posts: 281
|
| Posted: Mon Sep 18, 2006 2:14 pm Post subject: |
|
|
| NeddySeagoon wrote: | RaceTM,
A more exact error would help, if it ends in unknown-block (X,Y) where Xand Y are numbers, the numbers are very important to identify the cause of the error.
Also, at the time of the error, does the system offer you a shell ?
If so, is the shell busybox or bash ?
Busybox is included in the initrd, so if you have a busybox shell, the initrd is mounted but not the real_root. If the shell is bash, real_root is mounted.
See the post by NoControl too.
It looks like it just works for klater kernels now too |
Hi Neddy,
I do not get a shell, it ends in a kernel panic and I need to reboot. I believe the numbers were 'unknown block (0,0)' but I will doublecheck as soon as I get a chance. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54209
Location: 56N 3W
|
| Posted: Mon Sep 18, 2006 2:36 pm Post subject: |
|
|
RaceTM,
The unknown-block (0,0) means that the kernel cannot talk to the 'drive hardware'.
Since you don't get a shell at all, you are either not using and initrd and you must for booting with dmraid, or your kernel does not have initrd support compiled in.
Sight of your grub.conf and | Code: | $ grep INITRD /usr/src/linux/.config
# CONFIG_BLK_DEV_INITRD is not set |
would be useful. Thats my output, you need =y
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
Kernel & Hardware
