Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[HOWTO] HPT, Promise, Medley, Intel, Nvidia RAID Dualboot
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9  Next  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
flipy
Apprentice
Apprentice


Joined: 15 Jul 2004
Posts: 229

PostPosted: Wed Dec 15, 2004 7:10 pm    Post subject: Reply with quote

Since i've been using dmraid and it works fine. Just one thing to complain about... is there any way to use fbsplah, gensplash, bootsplash..?
_________________
Si no entiendes algo leete detenidamente el Handbook.
Back to top
View user's profile Send private message
irondog
l33t
l33t


Joined: 07 Jul 2003
Posts: 715
Location: Voor mijn TV. Achter mijn pc.

PostPosted: Wed Dec 15, 2004 7:49 pm    Post subject: Reply with quote

Gentoo users should use gensplash (fbsplash). I'll explain how to do that. Bootsplash should be more easy as users can append bootsplash themes to their initrd, but Gentoo doesn't support bootspash anymore. So I won't discuss it.

Gensplash is easy to set up, but since we are using the initrd for dmraid we 'have to' use initramfs. I'm not sure we MUST, but using the initramfs is the way I recommend.

The idea is easy: Build-in the initramfs into the kernel image (of course a fbsplash patched kernel source tree is needed)
Code:

emerge splashutils -pv
emerge splashutils
cd /usr/src/linux
splash_geninitramfs -v -g usr/initramfs_data.cpio.gz -r 1024x768 emergence
touch usr/initramfs_data.cpio.gz #not sure this is needed
make
cp arch/i386/boot/bzImage /boot/vmlinuz


append splash=silent,theme:emergence to the kernel commandline and your system will have gensplash.

This also counts for people using LVM with a genkernel created initrd. The kernel seems to have no problem having both an initrd and initramfs :)
_________________
Alle dingen moeten onzin zijn.
Back to top
View user's profile Send private message
flipy
Apprentice
Apprentice


Joined: 15 Jul 2004
Posts: 229

PostPosted: Fri Dec 17, 2004 8:18 pm    Post subject: Reply with quote

Can you please post an grub example?
I'm using 2.6.10 with fb support built-in, and I've tryed all the steps several times and I can't get it to work...
_________________
Si no entiendes algo leete detenidamente el Handbook.
Back to top
View user's profile Send private message
tcostigl
Tux's lil' helper
Tux's lil' helper


Joined: 28 Jul 2004
Posts: 97

PostPosted: Fri Dec 24, 2004 4:08 am    Post subject: Reply with quote

Flippy, I suspect that the NEW kernel option for fbsplash in the 2.6.9-r10 kernel works differently than the setup irondog has described.

Try recompiling your kernel without that option or read /usr/src/linux/Documentation/fb/splash.txt to get the new kernel supported version working.
Back to top
View user's profile Send private message
tcostigl
Tux's lil' helper
Tux's lil' helper


Joined: 28 Jul 2004
Posts: 97

PostPosted: Fri Dec 24, 2004 4:18 am    Post subject: Reply with quote

Well, I upgraded to 2.6.9-r10 with fb built in and my splash that was previously working is no longer working. Then I tried my own suggestion and recompiled without that option and re-setup as irondog describes... and ... yep ... you geussed.... still not working.
Back to top
View user's profile Send private message
Erlend
Guru
Guru


Joined: 26 Dec 2004
Posts: 493

PostPosted: Sun Dec 26, 2004 3:52 pm    Post subject: Grub - Similar Problems to Flipy Reply with quote

I have the same problem flipy had earlier:
Quote:
error: the selected cylinder exceeds bios maximum

Except my partition table is just:
part1: ntfs (110GB)
part2: linux swap (512MB)
part3: linux / (110GB)

I've basically installed gentoo using gen2dmraid-0.99, but I cannot install my bootloader (I would slightly prefer to use grub, but I'm not really fussy so long as it works).

Quote:

This works:
Code:

device (hd0,2) /dev/mapper/ataraid3
grub> device (hd0) /dev/mapper/ataraid
grub> root (hd0,2)
...


If I do this I still get
Code:
Error18: Selected cylinder exceeds maximum supported by BIOS.


I think hd0 is correct, since if I do the same with (hd0,0) I get
Code:
"unknown filesystem, partition type 0x7"

but I'm at a complete loss about why grub won't see (hd0,2).

Thanks,

Erlend

Should probably mention that I don't actually have a specific boot partition, just forgot to make one.
Back to top
View user's profile Send private message
Erlend
Guru
Guru


Joined: 26 Dec 2004
Posts: 493

PostPosted: Mon Dec 27, 2004 8:25 pm    Post subject: Grub installed, can't boot Reply with quote

Got grub installed simply by using a grub boot floppy and installing from that.

I can't boot though. Kernel panic, ram0 doesn't exist. I can't really read any of the problems, since I can't scroll up. Is there any way of having the kernel errors logged to a floppy, or of getting a terminal so that I can look at what's happened?

Thanks,

Erlend
Back to top
View user's profile Send private message
anestis
n00b
n00b


Joined: 25 Feb 2004
Posts: 6

PostPosted: Wed Feb 09, 2005 4:20 pm    Post subject: I'm Stuck: STEP 9 PLZ HELP! Reply with quote

Hello,
I'm trying to install gentoo on my raid-0 ICH5R array and I followed the guide on this thread, the gentoo handbook and the instructions on the gerte web page that has the live cd with the dm step by step. I managed to pass all the stages up to stage 9...

I had spent far too much time reading forum threads and googleing so I won't give up!
Here's my config..

I made the following partitions:

1. (PRI) 100MB /boot
2. (PRI) 10GB /
3. (PRI) 35GB windows
4. (EXT) 1GB swap

dmraid recognized all the partitions and named them isw_blabla_RAID_Volume11 to Volume15 with Volume14 being the extended partion itself (not the logical drive in it) and Volume1 the whole raid array. So far so good
When it comes to configuring grub... I get this error:
Code:

#/sbin/grub --device-map=/dev/null

    GNU GRUB  version 0.94  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]

grub> device (hd0,0) /de
Error 12: Invalid device requested

grub> device (hd0,0) /dev/mapper/isw_bfbhjjacda_RAID_Volume11

Error 15: File not found


ok... when booting from the gen2dmraid livecd I can see the raid partions ok. But when I'm trying to install gentoo I have to chroot in /mnt/gentoo right? When I chroot, gentoo doesn't see the device mapper so how can I configure grub then?
What I mean is..

In the chroot :

livecd root # ls /dev/mapper
ls: /dev/mapper: No such file or directory

you see there are no devices in mapper, however if I exit the chroot the devices are there.. so my question then is how can I configure grub?

Any help is greatly appreciated as I'm stuck and can't do nothing about it. From that point on I can keep up with the gentoo handbook..
:roll: :oops:
Back to top
View user's profile Send private message
Erlend
Guru
Guru


Joined: 26 Dec 2004
Posts: 493

PostPosted: Wed Feb 09, 2005 4:38 pm    Post subject: Reply with quote

Quote:
When it comes to configuring grub... I get this error:

Looks familiar ;-). Make a grub bootdisk
Code:
Code Listing 2.5: Creating a GRUB bootdisk

# cd /boot/grub
# dd if=stage1 of=/dev/fd0 bs=512 count=1
# dd if=stage2 of=/dev/fd0 bs=512 seek=1

(from http://www.gentoo.org/doc/en/gentoo-x86-tipsntricks.xml#software-raid [scroll down just a little bit]).

Note when you reboot into the boot floppy your devices will be different (they are now actually being mapped by the onboard raid BIOS). type help if you are stuck. You can now type the following commands to install grub:

Code:

# n=partition number of /boot (zero in your case).
grub> root (hd0,n)          (Specify where your /boot partition resides)
grub> setup (hd0,n)           (Install GRUB to the nth partition /boot)
grub> quit                  (Exit the GRUB shell)


If you need a little more info:
http://www.gnu.org/software/grub/manual/html_node/Installing-GRUB-natively.html

Quote:
livecd root # ls /dev/mapper
ls: /dev/mapper: No such file or directory

In /etc/init.d/checkroot, just after
Code:
   if [[ ! -f /fastboot && -z ${CDBOOT} ]] ; then

you need to insert:
Code:
dmsetup mknodes # repopulate /dev/mapper!!!

You may have to make the /dev/mapper directory yourself, and perhaps also the control node (ask if you need this).

You're not far at all from getting it working!

Erlend

EDIT: remember to set your /boot partition to boot in your partitioning software (i.e. cfdisk).
Back to top
View user's profile Send private message
irondog
l33t
l33t


Joined: 07 Jul 2003
Posts: 715
Location: Voor mijn TV. Achter mijn pc.

PostPosted: Wed Feb 09, 2005 5:14 pm    Post subject: Reply with quote

Quote:
When it comes to configuring grub... I get this
Code:
livecd root # ls /dev/mapper
ls: /dev/mapper: No such file or directory

mount -o bind /dev /mnt/gentoo/dev before entering the chroot!

Quote:

Code:
dmsetup mknodes # repopulate /dev/mapper!!!

When configured correctly Gentoo's rc-scripts (baselayout) will do this!

There is no need to edit rc-scripts if you choose for the latest (~x86) baselayout.
_________________
Alle dingen moeten onzin zijn.
Back to top
View user's profile Send private message
anestis
n00b
n00b


Joined: 25 Feb 2004
Posts: 6

PostPosted: Thu Feb 10, 2005 1:15 am    Post subject: Cylinder Exceeds Maximu Supported by BIOS Reply with quote

Thanks guys, it really worked! 8O ... Grub config doesn't give me the
Code:
Error 12: Invalid device requested
however I get another error a few lines down :x :cry:

Code:
grub> device (hd0) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> device (hd0,2) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> root (hd0,2)

Error 18: Selected cylinder exceeds maximum supported by BIOS


I read the previous posts from flippy and irondog on the very same error but it didn't do me any good. Ok here's my new partition table:

1. (PRI) 35gb Win NTFS
2. (PRI) 100mb /boot ext3
3. (PRI) 10gb / reiser4
4. (EXT) 1gb swap swap

Here's what I get from dmraid:

Code:
livecd / # ls -ls /dev/mapper/
total 0
0 crw-rw----  1 root root  10, 63 Feb  9 18:21 control
0 brw-r-----  1 root root 254,  0 Feb  9 18:22 isw_bfbhjjacda_RAID_Volume1
0 brw-r-----  1 root root 254,  1 Feb  9 18:22 isw_bfbhjjacda_RAID_Volume11
0 brw-r-----  1 root root 254,  2 Feb  9 18:22 isw_bfbhjjacda_RAID_Volume13
0 brw-r-----  1 root root 254,  3 Feb  9 18:22 isw_bfbhjjacda_RAID_Volume14
0 brw-r-----  1 root root 254,  4 Feb  9 18:22 isw_bfbhjjacda_RAID_Volume15
livecd / # fdisk -l /dev/mapper/isw_bfbhjjacda_RAID_Volume1

Disk /dev/mapper/isw_bfbhjjacda_RAID_Volume1: 247.0 GB, 247044243456 bytes
255 heads, 63 sectors/track, 30034 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

                                   Device Boot      Start         End      Blocks   Id  System
/dev/mapper/isw_bfbhjjacda_RAID_Volume1p1   *           1        4569    36700461    7  HPFS/NTFS
/dev/mapper/isw_bfbhjjacda_RAID_Volume1p2            5886       30034   193976842+   f  W95 Ext'd (LBA)
/dev/mapper/isw_bfbhjjacda_RAID_Volume1p3            4570        4582      104422+  83  Linux
/dev/mapper/isw_bfbhjjacda_RAID_Volume1p4            4583        5885    10466347+   c  W95 FAT32 (LBA)
/dev/mapper/isw_bfbhjjacda_RAID_Volume1p5            5886        6016     1052226   82  Linux swap

Partition table entries are not in disk order


As you can see Volume1 is the name of my raidarray, Volume13 is the name of my linux boot, Volume14 is the name of my linux root.
Now I've tried every single combination on grub always following the order irondog said:
Code:
livecd / # /sbin/grub --device-map=/dev/null


grub> device (hd0,0) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd0) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> root (hd0,0)
 Filesystem type unknown, partition type 0x7

grub> device (hd0,1) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd1) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> root (hd0,1)

Error 18: Selected cylinder exceeds maximum supported by BIOS

grub> device (hd0,2) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd0) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> device (hd0,2) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> root (hd0,2)

Error 18: Selected cylinder exceeds maximum supported by BIOS

grub> device (hd0,3) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd0) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> root (hd0,3)

Error 18: Selected cylinder exceeds maximum supported by BIOS

grub> device (hd1,0) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd1) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> root (hd1,0)
 Filesystem type unknown, partition type 0x7

grub> device (hd1,1) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd1) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> root (hd1,1)

Error 18: Selected cylinder exceeds maximum supported by BIOS

grub> device (hd1,1) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd1) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> device (hd1,2) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd1) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> root (hd1,2)

Error 18: Selected cylinder exceeds maximum supported by BIOS

grub> device (hd1,3) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd1) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> root (hd1,3)

Error 18: Selected cylinder exceeds maximum supported by BIOS

....nothing :cry:

irondog, I know you said in a previous post that it has nothing to do with the actual geometry of the disk but what am I doing wrong? :?:
Back to top
View user's profile Send private message
Erlend
Guru
Guru


Joined: 26 Dec 2004
Posts: 493

PostPosted: Thu Feb 10, 2005 2:46 pm    Post subject: Reply with quote

Quote:
however I get another error a few lines down Mad Crying or Very sad

Code:
grub> device (hd0) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> device (hd0,2) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> root (hd0,2)

Error 18: Selected cylinder exceeds maximum supported by BIOS


Yeah I got this too for a while. The error isn't "real"; basically it's a grub configuration error, nothing wrong elsewhere. The only way I know to fix it is with the grub boot disk (floppy) which you should make as I specified above. For a detailed description read: http://www.gnu.org/software/grub/manual/grub.html#Installation the relevant sections are "Creating a GRUB boot floppy" and "Installing GRUB natively".

Quote:
Quote:

Code:
dmsetup mknodes # repopulate /dev/mapper!!!

When configured correctly Gentoo's rc-scripts (baselayout) will do this!

Is this true even for dmsetup (i.e. i'm not using dmraid)?

Erlend
Back to top
View user's profile Send private message
irondog
l33t
l33t


Joined: 07 Jul 2003
Posts: 715
Location: Voor mijn TV. Achter mijn pc.

PostPosted: Thu Feb 10, 2005 7:07 pm    Post subject: Re: Cylinder Exceeds Maximu Supported by BIOS Reply with quote

Quote:

Is this true even for dmsetup (i.e. i'm not using dmraid)?
Erlend


Yes it is. From the Gentoo developpers' point of view device-mapper nodes
shouldn't be handled by udev. In fact, I can live with that. So doing it the
way the Gentoo developpers want things to be, is the way I recommend.

cat /sbin/rc
Code:

[...]
populate_udev() {
        # Make sure we do not have udevd from initramfs running
        killall -q udevd
        # Now populate /dev
        /sbin/udevstart

        # Not provided by sysfs but needed
        ln -snf /proc/self/fd /dev/fd
        ln -snf fd/0 /dev/stdin
        ln -snf fd/1 /dev/stdout
        ln -snf fd/2 /dev/stderr
        ln -snf /proc/kcore /dev/core

        # Create nodes that udev can't
        [ -x /sbin/dmsetup ] && /sbin/dmsetup mknodes &>/dev/null
        [ -x /sbin/lvm ] && /sbin/lvm vgscan -P --mknodes
--ignorelockingfailure &>/dev/null

        # Create problematic directories
        mkdir -p /dev/{pts,shm}

        # Same thing as /dev/.devfsd
        touch /dev/.udev

        return 0
}
[...]


From the code snip above we can see, that if we are using udev and
/sbin/dmsetup exists, things in /dev/mapper will be created automaticly (No
matter if we are using dmraid or something else controlling the
device-mapper.)

Just emerge the right baselayout version and configure it correctly.



anestis wrote:

grub> device (hd0) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> device (hd0,2) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> root (hd0,2)

Error 18: Selected cylinder exceeds maximum supported by BIOS[/code]

Wrong order. First do device(hd0,0) device(hd0,1) device(hd0,2). After that device(hd0). Never reverse this order!!!!!
I don't think you need to do (hd0,1), but might be a good idea.

Quote:

grub> device (hd0,0) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd0) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> root (hd0,0)
Filesystem type unknown, partition type 0x7

Now you are installing on p1, that's NTFS. Reading grub's documentation you could discover grub has it's own filesystem interpreters. Very few builds of grub support NTFS. Don't try to do this, it will fail in Gentoo.

Quote:

grub> device (hd0,1) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd1) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> root (hd0,1)

Error 18: Selected cylinder exceeds maximum supported by BIOS

I have already explained this error.

Quote:

grub> device (hd0,2) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd0) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> device (hd0,2) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> root (hd0,2)

Error 18: Selected cylinder exceeds maximum supported by BIOS

blind attempt :)

Quote:

grub> device (hd0,3) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd0) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> root (hd0,3)

Error 18: Selected cylinder exceeds maximum supported by BIOS

Hmn, try explaining grub all partitions: 0,1,2,3

Quote:

grub> device (hd1,0) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd1) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> root (hd1,0)
Filesystem type unknown, partition type 0x7

Understand you are doing the same as earlier! Using (hd1) won't change anything!

Quote:

grub> device (hd1,1) /dev/mapper/isw_bfbhjjacda_RAID_Volume13

grub> device (hd1) /dev/mapper/isw_bfbhjjacda_RAID_Volume1

grub> root (hd1,1)

Error 18: Selected cylinder exceeds maximum supported by BIOS

?(hd1,0) is unknown?

And your partition table is not in disk order. Fix it!
Code:

/dev/mapper/isw_bfbhjjacda_RAID_Volume1p1   *           1        4569    36700461    7  HPFS/NTFS

/dev/mapper/isw_bfbhjjacda_RAID_Volume1p3            4570        4582      104422+  83  Linux

/dev/mapper/isw_bfbhjjacda_RAID_Volume1p4            4583        5885    10466347+   c  W95 FAT32 (LBA)

/dev/mapper/isw_bfbhjjacda_RAID_Volume1p2            5886       30034   193976842+   f  W95 Ext'd (LBA)

/dev/mapper/isw_bfbhjjacda_RAID_Volume1p5            5886        6016     1052226   82  Linux swap

Besides that, where are all those other cylinders?

One last remark: a partition just CAN exeed the bios limits! use a /boot within a normal offset on the disk.
_________________
Alle dingen moeten onzin zijn.
Back to top
View user's profile Send private message
Erlend
Guru
Guru


Joined: 26 Dec 2004
Posts: 493

PostPosted: Thu Feb 10, 2005 8:48 pm    Post subject: Reply with quote

Quote:
From the code snip above we can see, that if we are using udev and
/sbin/dmsetup exists, things in /dev/mapper will be created automaticly (No
matter if we are using dmraid or something else controlling the
device-mapper.)

Just emerge the right baselayout version and configure it correctly.

Yep, it works fine without my additional line in checkroot. Thanks.

Erlend
Back to top
View user's profile Send private message
kabage
Guru
Guru


Joined: 31 Jan 2005
Posts: 340

PostPosted: Sun Feb 13, 2005 3:20 pm    Post subject: I just boot in the chrooted env Reply with quote

Thank you for this how-to, I'm having a problem booting to my chrooted env.

Let me state that another way, if I do the grub config from the dmraid iso, (while chrooted in my raid env) then boot to the array it just boots the CD instead.

Same from my old ide with mandrake, I do the work in the array (chrooted in to the array) Then boot to the array it just boots mandrake.

Without the initrc in my grub.conf I can get to the splash screen but then the kernel panics on boot.

If anyone has seen this or has any ideas, it would be helpful?

Another chuck of info when I did the dmraidinit script the only way I could get to work was to emerge busybox myself because if could not seem to compile the version it was using.

Oh yeah, I'm on a amd64 if that has something to do with it.

Thank you Kabage
_________________
The solutions are easy. Its finding them that is hard.
Back to top
View user's profile Send private message
Erlend
Guru
Guru


Joined: 26 Dec 2004
Posts: 493

PostPosted: Sun Feb 13, 2005 3:33 pm    Post subject: Reply with quote

Quote:
Let me state that another way, if I do the grub config from the dmraid iso, (while chrooted in my raid env) then boot to the array it just boots the CD instead.

Remove the CD?

Quote:
Without the initrc in my grub.conf I can get to the splash screen but then the kernel panics on boot.

That's normal - the initrd is mapping the raid devices in /dev/mapper. If you don't let the initrd run then the kernel cannot mount / - hence kernel panic.

Quote:
Another chuck of info when I did the dmraidinit script the only way I could get to work was to emerge busybox myself because if could not seem to compile the version it was using.

Did you add busybox to the initrd? You can't just emerge it and hope that works. I would get the source to a new version of busybox and compile that manually, then add it to my initrd. There are plenty of howtos around the web on how to do this (google: busybox initrd).

Quote:
Oh yeah, I'm on a amd64 if that has something to do with it.

It could well be related. What's the error?

Erlend
Back to top
View user's profile Send private message
kabage
Guru
Guru


Joined: 31 Jan 2005
Posts: 340

PostPosted: Sun Feb 13, 2005 11:38 pm    Post subject: Reply with quote

- I cant even post a message correctly, why am I using a computer?

Erlend wrote:
Quote:
Let me state that another way, if I do the grub config from the dmraid iso, (while chrooted in my raid env) then boot to the array it just boots the CD instead.

Remove the CD?

"of course no just kidding removing the CD or my ide drive that I was working from gives me 'no boot media found'"

Quote:
Without the initrc in my grub.conf I can get to the splash screen but then the kernel panics on boot.

That's normal - the initrd is mapping the raid devices in /dev/mapper. If you don't let the initrd run then the kernel cannot mount / - hence kernel panic.

"True but it does prove grub is installed on my array, and that the array can be seen to a point anyway"


Quote:
Another chuck of info when I did the dmraidinit script the only way I could get to work was to emerge busybox myself because if could not seem to compile the version it was using.

Did you add busybox to the initrd? You can't just emerge it and hope that works. I would get the source to a new version of busybox and compile that manually, then add it to my initrd. There are plenty of howtos around the web on how to do this (google: busybox initrd).

"Yes, but since no one else in this area seems to have a problem with the dmraidinitrd-0.93 script, I feel so violated and cheated"
This is the only area I've seen an error, run as is it says

cp: cannot stat `/tmp/initrd/busybox-0.60.3/busybox': No such file or directory
Cleaning up...
Fatal error: did busybox fail to compile?

I changed one line

cp $TMPDIR/${BUSYBOX_DIR}/busybox ${TMPDIR}/tmp/bin || die 'Fatal error: did busybox fail to compile?'

to

cp /tmp/download/${BUSYBOX_DIR}/busybox ${TMPDIR}/tmp/bin || die 'Fatal error: X-dream busybox'

which makes it compile but probably not the right env...

Maybe the key is here since it seems to desire compiling in another chroot at /root/tmp

I will remark out the rm files section and see what it did in that area. I can't believe the dmraidinit script would have an error or I wouldn't be the only one with this, is it possible to have to many chroot'ed environments?


Quote:
Oh yeah, I'm on a amd64 if that has something to do with it.

It could well be related. What's the error?

As above the raw script just can find a made busybox, it looks in /root/tmp/initrd , so why is it compiled at /tmp/download/busybox-0.60.3/


Erlend


Thank you for your response by the way, I got a few hours sleep and hopefully will get this resolved.

Did anybody else have to patch this script for any reason?


Ok I proved it is a arch problem - so I used busybox-1.00 source , did a test compile , and it works, then borrowed the .config file and patch the orig dminitrd script to use the .config instead of
Config.h (is that right) anyway the dmraidinitrd script ran without complaint.

Edit:
Then booted and got GRUB Loading stage2Geom Error

Got the same thing with grub boot disk.


As usual I'lll do some reading, but the damn make config in busybox looks like a kernel config its a little intimidating considering I've not used busybox.
And also if anyone can just verify this busybox .config maybe can solve the problem or am I on the wrong planet.

Just a link is good
Thank you, Kevin the Kabage

Ok, I add the geometry command to grub , just after the device commands, this made it boot, but it is still searching for all devices except itself, gives itself a
add boot media error if the array is the only thing.


I guess I'll try to make the first partition active along with the 2nd partition, hmmm what to do.


7:21 pst 2/13
Did try that and it boots again with a kernel panic regarding not syncing and VFS: unable to mount root fs on unknown-block(1,0)

did change conf file back to hd1 instead of 0,

*the odd -- A get a splash screen even though I dont have that line in my grub.conf and my kernel doesn't have fb support - could grub be sharing space with lilo on my hda - no way - way -no way

I guess I'm just keeping notes to myself at this point surely some one had dmraid running on an amd64.


8:08 pm 2/13
Summary -getting closer
went back to hd0 -- no doubt
my /boot/grub/menu.lst was not a link (wont let me make a link to grub.conf so just copied grub.conf to menu.lst)
I gave grub every device partition and am now getting

kernel panic not syncing no init found try passing init= (yes already doing that, must be finding pdc_*6 since not getting root fs error so why not the
/boot/linuxrc file in my command line init=/linuxrc
i did try init=/boot/linuxrc also , I'm running out of direction

Have no idea what to try. I'll start at grub docs and see if it can enlighten me on passing the init info another way or something
I know what it is, I lost my linux wand.... what to do

10:47 pm 2/13 pt
Summary -- getting nowhere
kernel panic no init found blah blah

have tried everything not sure if it wants run level or initrd image
seems like it should run initrd before linuxrc, how else is going to find linuxrc without initrd
_________________
The solutions are easy. Its finding them that is hard.
Back to top
View user's profile Send private message
Erlend
Guru
Guru


Joined: 26 Dec 2004
Posts: 493

PostPosted: Mon Feb 14, 2005 2:57 pm    Post subject: Reply with quote

Your post is very hard to understand. I'm going to backtrack a few steps...

Assuming Gentoo is installed, and you are at the stage of needing to install grub...
1. Make Grub boot disk
2. Boot off it, grub will correctly automatically find your drive from the BIOS (since there is no device-mapper).
3. At this grub boot screen, type "root (hd<tab>" (meaning press the tab key). This will give you a list of possible hd's. Choose one and install to that. "root(hd0, grub_number_of_your_boot_partition)" - will give you output of the filesystem type: if it matches it's correct, if not - stop and think.
4. You should make sure you grub.conf (menu.lst) looks something like (rough):
Code:
root (hd0,3)
kernel /vmlinuz-2.6.10-gentoo-r6-3 root=/dev/ram0 real_root=/dev/mapper/[dmraid_dev_node] init=/linuxrc real_init=3
initrd /initrd-2.6.9-gentoo-r1-2

The reason you don't include the /boot (i.e. /boot/initrd) is that you have told grub to use the 2nd partition by saying root(hd0,3).

I didn't have to patch anything, except I wrote my own linuxrc (the "init" file inside the initrd). I had to do this because I'm not actually using dmraid (I'm just using dmsetup and manually mapping the devices). It's very similar to the dmraidinitrd linuxrc but I can post it is you really want.

As for busybox, I'm not sure if you've got that sorted now. Read the dmraidinitrd script and either change the version number of busybox that it downloads and compiles (UNTESTED, not sure if that will work) or base your own commands on what the script does.

Erlend
Back to top
View user's profile Send private message
kabage
Guru
Guru


Joined: 31 Jan 2005
Posts: 340

PostPosted: Mon Feb 14, 2005 6:13 pm    Post subject: Hard to follow Reply with quote

Erlend wrote:
Your post is very hard to understand. I'm going to backtrack a few steps...

Yes I believe I've lost all sanity.

Assuming Gentoo is installed, and you are at the stage of needing to install grub...
1. Make Grub boot disk
2. Boot off it, grub will correctly automatically find your drive from the BIOS (since there is no device-mapper).
3. At this grub boot screen, type "root (hd<tab>" (meaning press the tab key). This will give you a list of possible hd's. Choose one and install to that. "root(hd0, grub_number_of_your_boot_partition)" - will give you output of the filesystem type: if it matches it's correct, if not - stop and think.
4. You should make sure you grub.conf (menu.lst) looks something like (rough):
Code:
root (hd0,3)
kernel /vmlinuz-2.6.10-gentoo-r6-3 root=/dev/ram0 real_root=/dev/mapper/[dmraid_dev_node] init=/linuxrc real_init=3
initrd /initrd-2.6.9-gentoo-r1-2

The reason you don't include the /boot (i.e. /boot/initrd) is that you have told grub to use the 2nd partition by saying root(hd0,3).

I guess Grub is installed, I boot the array, and get menu choices, picking linux where it then panics out.
I guess this is a script error.


I didn't have to patch anything, except I wrote my own linuxrc (the "init" file inside the initrd). I had to do this because I'm not actually using dmraid (I'm just using dmsetup and manually mapping the devices). It's very similar to the dmraidinitrd linuxrc but I can post it is you really want.

I have a feeling yes I will need your script. Thank you so much

As for busybox, I'm not sure if you've got that sorted now. Read the dmraidinitrd script and either change the version number of busybox that it downloads and compiles (UNTESTED, not sure if that will work) or base your own commands on what the script does.

I did get it to compile with busybox-1.0 so I will assume the initrd is correct for now and blame the linuxrc. Although that real_init part in the kernel line I have not seen. So I will adjust grub.conf
and try the floppy install before hacking code. Unfortunatly I am relying on my gut more than brain.

I guess what I really want to know at the moment is which one is failing, grub, initrd, linuxrc. Do you know how to prove.
IMHO I think the fact grub comes up, and gives me a kernel panic regarding no init found- grub is probably good.

I think since dmraidinitrd script ran with no complaint using busybox 1.0, that the initrd is probably ok. (I feel like this is a big leap of faith)

So I will probably need to just redo the linuxrc.

But first I'll try the simple solution and just add the real_init=3 to my kernel line. If only....

Erlend


I appreciate the help. Time 10am pt 2/14

If you also have knowledge of how to eliminate things from my troublshooting loop, that would be helpful.


11:21am pt 2/14
I've made an assumption that is probably wrong - The /linuxrc refered to on the kernel line should just be a copy of the linuxrc-0.93 that dmraidinitrd-93 uses to make the initrd? yes

I get the same results from floppy or when booting the array -- kernel panic init not found.

As far as I can see no linuxrc never runs. Which means it cant be linuxrc since it never runs.



When I do the grub floppy * by the way the floppy says the array is (hd1) where grub on the array seems to think the array is (hd0)
I put in the line

Code:

root (hd1,<tab>



and I get something like

partition 0
partition 4
partition 5
partition 6

my problem with this is I thought grub looked at partitions in order like 0, 1, 2, 3


This probably does not matter at the moment since I want /linuxrc to run from 0 anyway


New thinking

from the grub menu, I pick linux - I go a get a sound card and various thinks loaded --- It Must Have Found The Kernel Image ---

linuxrc must have initrd to run and it is not running or I would some some echoes from it so must be the INITRD with problems ?

I guess to do my own initrd I need some amd64 compatible linux environment inside it with dmraid dev-mapper built in.
If by some miracle I got that far , I dont understand the use of the linuxrc, cant I just run the commands inside the initrd to map devices and transfer the info back to the kernel

Conclusion
I dont what is going on, not sure I have enough scripting/programming to even accomplish my goal even If I did.
The goal - (boot my array)
_________________
The solutions are easy. Its finding them that is hard.
Back to top
View user's profile Send private message
Erlend
Guru
Guru


Joined: 26 Dec 2004
Posts: 493

PostPosted: Mon Feb 14, 2005 8:36 pm    Post subject: Reply with quote

Quote:
I've made an assumption that is probably wrong - The /linuxrc refered to on the kernel line should just be a copy of the linuxrc-0.93 that dmraidinitrd-93 uses to make the initrd? yes

linuxrc is a file within the initrd image. You should take a look inside your initrd to check it's there...
Code:

mkdir /mnt/loop
gunzip initrd
mount -o loop initrd /mnt/loop
cd /mnt/loop

If it isn't there copy the file http://tienstra4.flatnet.tudelft.nl/~gerte/gen2dmraid/linuxrc-0.93 into it, umount gzip and cp the image back to /boot/initrd. NB: you should have called "dmraidinitrd-0.93 linuxrc-0.93 initrd" at some stage to make the initrd: linuxrc-0.93 will have to have been on the filesystem next to the dmraidinitrd-0.93 script.

Quote:
linuxrc must have initrd to run and it is not running or I would some some echoes from it so must be the INITRD with problems ?

You do have initrd in your grub.conf - might be an idea to post that here?

Quote:
I dont understand the use of the linuxrc, cant I just run the commands inside the initrd to map devices and transfer the info back to the kernel

That's what a linuxrc is: it's just a file (either shell script or binary) that's run before the kernel tries to mount stuff to set up necessary drivers and allow the kernel to mount /.

Erlend
Back to top
View user's profile Send private message
kabage
Guru
Guru


Joined: 31 Jan 2005
Posts: 340

PostPosted: Mon Feb 14, 2005 10:17 pm    Post subject: gunzip is mean Reply with quote

Erlend wrote:
Quote:
I've made an assumption that is probably wrong - The /linuxrc refered to on the kernel line should just be a copy of the linuxrc-0.93 that dmraidinitrd-93 uses to make the initrd? yes

linuxrc is a file within the initrd image. You should take a look inside your initrd to check it's there...
Code:

mkdir /mnt/loop
gunzip initrd
mount -o loop initrd /mnt/loop
cd /mnt/loop


Good stuff, I had a problem gunzipping the initrd until I moved it to initrd.gz then I could unzip it and mount it.
Could grub have the same problem, if so, can I just leave it unzipped at least for testing.

Yes linuxrc is in initrd, but could not find dmraid or device-mapper -- Shouldn't that be in the initrd ?



If it isn't there copy the file http://tienstra4.flatnet.tudelft.nl/~gerte/gen2dmraid/linuxrc-0.93 into it, umount gzip and cp the image back to /boot/initrd. NB: you should have called "dmraidinitrd-0.93 linuxrc-0.93 initrd" at some stage to make the initrd: linuxrc-0.93 will have to have been on the filesystem next to the dmraidinitrd-0.93 script.

Quote:
linuxrc must have initrd to run and it is not running or I would some some echoes from it so must be the INITRD with problems ?

You do have initrd in your grub.conf - might be an idea to post that here?

Code:
timeout 30
default 0

title Proof I'm getting my Conf
root (hd1,0)
kernel /xdream-v1 root=/dev/ram0 real_root=/dev/mapper/pdc_bajefichjd6 init=/linuxrc real_init=3
initrd /initrd

title WinXp
rootnoverify (hd1,1)
chainloader +1
makeactive


Here my menu.lst, please I wish this could be my problem.


Quote:
I dont understand the use of the linuxrc, cant I just run the commands inside the initrd to map devices and transfer the info back to the kernel

That's what a linuxrc is: it's just a file (either shell script or binary) that's run before the kernel tries to mount stuff to set up necessary drivers and allow the kernel to mount /.

OK I thought this referred to the file in the /boot directory so I removed that in case of conflict and will see what happens

Erlend


Thank you (cubed)
I really do appreciate this. Got a cold one just for you in the fridge.
Kevin the kabage
_________________
The solutions are easy. Its finding them that is hard.
Back to top
View user's profile Send private message
Erlend
Guru
Guru


Joined: 26 Dec 2004
Posts: 493

PostPosted: Mon Feb 14, 2005 10:22 pm    Post subject: Reply with quote

Quote:
root (hd1,0)

With your current set up of grub.conf - your boot partition should be on the first partition of hd1. Boot off the grub floppy again, and use the find comment to search your disks/partitions for initrd - that way you can see the disk as grub sees it.

Quote:
Yes linuxrc is in initrd, but could not find dmraid or device-mapper -- Shouldn't that be in the initrd ?

dmraid should be in the initrd - under /sbin i'm pretty sure. dmraidinitrd should have put it there - check for errors. That's not really the issue yet though - from what you said grub isn't even seeing your initrd or linuxrc.
Back to top
View user's profile Send private message
kabage
Guru
Guru


Joined: 31 Jan 2005
Posts: 340

PostPosted: Mon Feb 14, 2005 10:33 pm    Post subject: So close now Reply with quote

Erlend wrote:
Quote:
root (hd1,0)

With your current set up of grub.conf - your boot partition should be on the first partition of hd1. Boot off the grub floppy again, and use the find comment to search your disks/partitions for initrd - that way you can see the disk as grub sees it.

(hdX,0) is the first partition actually I changed that to (hd0,0) just now for array boot, floppy boot likes (hd1,0)

The good news? I left initrd unzipped and it is starting the script, but as expected no dmraid found and it gives me a shell option which works so I can conclude

grub -- working
initrd -- working
linuxrc -- working

just need to get the dmraid stuff into my initrd

Quote:
Yes linuxrc is in initrd, but could not find dmraid or device-mapper -- Shouldn't that be in the initrd ?

dmraid should be in the initrd - under /sbin i'm pretty sure. dmraidinitrd should have put it there - check for errors. That's not really the issue yet though - from what you said grub isn't even seeing your initrd or linuxrc.

_________________
The solutions are easy. Its finding them that is hard.
Back to top
View user's profile Send private message
Erlend
Guru
Guru


Joined: 26 Dec 2004
Posts: 493

PostPosted: Mon Feb 14, 2005 10:38 pm    Post subject: Reply with quote

Good stuff. I imagine you'll have learned a bit about the linux boot cycle from this, which is a positive way of looking at it.

Just compile a dmraid static binary and stick it in sbin within the initrd. You could try running dmraidinitrd as it should definitely do that for you, or just compile it yourself (it's easy). Do ./configure --enable-static to make sure it is statically linked. Read dmraidinitrd for help.

Erlend
Back to top
View user's profile Send private message
kabage
Guru
Guru


Joined: 31 Jan 2005
Posts: 340

PostPosted: Mon Feb 14, 2005 11:10 pm    Post subject: Hooray Reply with quote

Erlend wrote:
Good stuff. I imagine you'll have learned a bit about the linux boot cycle from this, which is a positive way of looking at it.

Just compile a dmraid static binary and stick it in sbin within the initrd. You could try running dmraidinitrd as it should definitely do that for you, or just compile it yourself (it's easy). Do ./configure --enable-static to make sure it is statically linked. Read dmraidinitrd for help.

Erlend


Sure enough I had uncommented something I shouldn't have in dmraidinitrd, fixed it up and did another.
Oh thank you it is working I booted gentoo from the array- Whoooooooooooooooooo, feels good.

Yes I've learned a lot. Though the more I learn the less I seem to know for sure. You know how that goes.

Having problems at the moment with windows boot, I think I know what that is .

Thank you

_________________
The solutions are easy. Its finding them that is hard.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8, 9  Next
Page 2 of 9

 
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