Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
DMRAID works fine in LiveCD, but SegFault's at boot [SOLVED]
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
Phk
Guru
Guru


Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time

PostPosted: Wed Apr 05, 2006 3:29 am    Post subject: DMRAID works fine in LiveCD, but SegFault's at boot [SOLVED] Reply with quote

I there everyone!

I installed gentoo using Lxnay RR64 LiveCD, on a DualCore Amd64, with two Sata disk with DFI Lanparty motherboard RAID-0.

Here, in the liveCd, i can do this:
Quote:
rr64dvd ~ # ls /dev/mapper/
control
rr64dvd ~ # dmraid -ay
ERROR: sil: only 1/4 metadata areas found on /dev/sda, picking...
/dev/sda: "sil" and "nvidia" formats discovered (using nvidia)!
/dev/sdb: "sil" and "nvidia" formats discovered (using nvidia)!
rr64dvd ~ # ls /dev/mapper/
control nvidia_didfcfaf1 nvidia_didfcfaf3 nvidia_didfcfaf6
nvidia_didfcfaf nvidia_didfcfaf2 nvidia_didfcfaf5 nvidia_didfcfaf7
rr64dvd ~ #


Notice the error... But everything works fine. I did the installation using this.

Then i followed the Gentoo NVidia DMRAID Wiki, and finally, when i rebooted, i got a segmentation fault...

This is the output when booting:

Quote:
Activating device-mapper RAID(s)
ERROR: sil: only 2/4 metadata areas found on /dev/sda, electing...
Segmentation fault
Determining root device...
!! Block device /dev/mapper/nvidia_didfcfaf3 is not a valid root device
(...)


..
What can the problem be? BTW, i use the latest no-sources, and also tried with the latest CK sources..

Here is the DMESG output in the Ash shell after the segfault:

Quote:
scsi6 : sata_nv
ata8: SATA link up 1.5 Gbps (SStatus 113)
ata8: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4063 85:7c69 86:3e01 87:4063 88:407f
ata8: dev 0 ATA-7, max UDMA/133, 398297088 sectors: LBA48
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
ata8: dev 0 configured for UDMA/133
scsi7 : sata_nv
Vendor: ATA Model: Maxtor 6B200M0 Rev: BANC
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: Maxtor 6B200M0 Rev: BANC
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
sd 6:0:0:0: Attached scsi disk sda
SCSI device sdb: 398297088 512-byte hdwr sectors (203928 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
SCSI device sdb: 398297088 512-byte hdwr sectors (203928 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
sdb: unknown partition table
sd 7:0:0:0: Attached scsi disk sdb
Fusion MPT base driver 3.03.07
Copyright (c) 1999-2005 LSI Logic Corporation
Fusion MPT SPI Host driver 3.03.07
ACPI (acpi_bus-0216): Device 'USB2' is not power manageable [20060210]
ACPI: PCI Interrupt Link [APCL] enabled at IRQ 20
GSI 21 sharing vector 0x42 and IRQ 21
ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCL] -> GSI 20 (level, low) -> IRQ 66
PCI: Setting latency timer of device 0000:00:02.1 to 64
ehci_hcd 0000:00:02.1: EHCI Host Controller
ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:02.1: debug port 1
PCI: cache line size of 64 is not supported by device 0000:00:02.1
ehci_hcd 0000:00:02.1: irq 66, io mem 0xfeb00000
ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: new device found, idVendor=0000, idProduct=0000
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.16-rc5-no3 ehci_hcd
usb usb1: SerialNumber: 0000:00:02.1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 10 ports detected
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI (acpi_bus-0216): Device 'USB0' is not power manageable [20060210]
ACPI: PCI Interrupt Link [APCF] enabled at IRQ 23
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 23 (level, low) -> IRQ 225
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: OHCI Host Controller
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:02.0: irq 225, io mem 0xfe02f000
usb usb2: new device found, idVendor=0000, idProduct=0000
usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: OHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.16-rc5-no3 ohci_hcd
usb usb2: SerialNumber: 0000:00:02.0
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 10 ports detected
USB Universal Host Controller Interface driver v3.0
Initializing USB Mass Storage driver...
usb 2-3: new low speed USB device using ohci_hcd and address 2
usb 2-3: new device found, idVendor=046d, idProduct=c01e
usb 2-3: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-3: Product: USB-PS/2 Optical Mouse
usb 2-3: Manufacturer: Logitech
usb 2-3: configuration #1 chosen from 1 choice
usb 2-4: new low speed USB device using ohci_hcd and address 3
usb 2-4: new device found, idVendor=0603, idProduct=00f2
usb 2-4: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-4: Product: USB Keyboard
usb 2-4: Manufacturer: NOVATEK
usb 2-4: configuration #1 chosen from 1 choice
usb 2-5: new full speed USB device using ohci_hcd and address 4
usb 2-5: new device found, idVendor=093a, idProduct=2468
usb 2-5: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-5: Product: CIF Single Chip
usb 2-5: Manufacturer: Pixart Imaging Inc.
usb 2-5: configuration #1 chosen from 1 choice
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
input: Logitech USB-PS/2 Optical Mouse as /class/input/input0
input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:02.0-3
input: NOVATEK USB Keyboard as /class/input/input1
input: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-0000:00:02.0-4
input: NOVATEK USB Keyboard as /class/input/input2
input: USB HID v1.10 Device [NOVATEK USB Keyboard] on usb-0000:00:02.0-4
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
i2c_adapter i2c-0: nForce2 SMBus adapter at 0x1c00
i2c_adapter i2c-1: nForce2 SMBus adapter at 0x1c40
device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com
device-mapper: dm-multipath version 1.0.4 loaded
device-mapper: dm-round-robin version 1.0.0 loaded
Advanced Linux Sound Architecture Driver Version 1.0.11rc3 (Thu Feb 02 07:50:46 2006 UTC).
ACPI (acpi_bus-0216): Device 'MACI' is not power manageable [20060210]
ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCJ] -> GSI 22 (level, low) -> IRQ 50
PCI: Setting latency timer of device 0000:00:04.0 to 64
intel8x0_measure_ac97_clock: measured 58690 usecs
intel8x0: clocking to 46952
ALSA device list:
#0: NVidia CK804 with ALC850 at 0xfe02d000, irq 50
oprofile: using NMI interrupt.
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 4
Suspend2 Core.
Suspend2 Compression Driver loading.
Suspend2 Encryption Driver loading.
Suspend2 Swap Writer loading.
initcall at 0xffffffff802a8da6: software_resume+0x0/0x9f(): returned with error code -2
ACPI: wakeup devices: HUB0 XVR0 XVR1 XVR2 XVR3 USB0 USB2 MMAC MMCI UAR1
ACPI: (supports S0 S1 S3 S4 S5)
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
initcall at 0xffffffff807dd7b6: rtc_hctosys+0x0/0x15e(): returned with error code -19
Freeing unused kernel memory: 216k freed
Buffer I/O error on device sda7, logical block 270237312
Buffer I/O error on device sda7, logical block 270237313
Buffer I/O error on device sda7, logical block 270237314
Buffer I/O error on device sda7, logical block 270237315
Buffer I/O error on device sda7, logical block 270237312
Buffer I/O error on device sda7, logical block 270237313
Buffer I/O error on device sda7, logical block 270237314
Buffer I/O error on device sda7, logical block 270237315
Buffer I/O error on device sda7, logical block 270237396
Buffer I/O error on device sda7, logical block 270237396
dmraid[1643]: segfault at 0000000000000000 rip 000000000040f236 rsp 00007fffb5a84440 error 4
dmraid[1668]: segfault at 0000000000000000 rip 000000000040f236 rsp 00007fff162a4c60 error 4
dmraid[1672]: segfault at 0000000000000000 rip 000000000040f236 rsp 00007fff547430f0 error 4




Thanks rightaway,
Phk!
_________________
"# cat /dev/urandom >> /tmp/life"


Last edited by Phk on Thu Apr 06, 2006 4:38 pm; edited 3 times in total
Back to top
View user's profile Send private message
Phk
Guru
Guru


Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time

PostPosted: Wed Apr 05, 2006 4:20 pm    Post subject: Reply with quote

bump? :( i'm really in deep trouble :(
_________________
"# cat /dev/urandom >> /tmp/life"
Back to top
View user's profile Send private message
ebichu
Apprentice
Apprentice


Joined: 03 Jul 2002
Posts: 231
Location: Manchester, England

PostPosted: Wed Apr 05, 2006 4:36 pm    Post subject: Reply with quote

It's probably more to do with those "Buffer I/O Errors" than dmraid per se. (Sorry, not much help!)
_________________
Ebichu wa chiizu ga daisuki dechu!
Back to top
View user's profile Send private message
nixnut
Bodhisattva
Bodhisattva


Joined: 09 Apr 2004
Posts: 10974
Location: the dutch mountains

PostPosted: Wed Apr 05, 2006 6:16 pm    Post subject: Reply with quote

Moved from Installing Gentoo to Kernel & Hardware.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered

talk is cheap. supply exceeds demand
Back to top
View user's profile Send private message
Phk
Guru
Guru


Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time

PostPosted: Thu Apr 06, 2006 12:04 am    Post subject: Reply with quote

OMG....

I'm now with the LiveCD. I open 2 shells, one chrooted to my new-crashy environment.
Both answer like this:
Quote:
rr64dvd ~ # dmraid -V
dmraid version: 1.0.0.rc8 (2005.05.19) shared
dmraid library version: 1.0.0.rc8 (2005.05.19)
device-mapper version: 4.4.0


so the version should be equal in both (LiveCD and my gentoo), but not.

When i boot to the new OS and it crashes and i type "shell", i noticed this:
Quote:
# dmraid -V
dmraid version: 1.0.0.rc9 (2006.03._) static
dmraid library version: 1.0.0.rc9 (2006.03._)
device-mapper version: 4.5.0


How is this possible? I've chrooted once again into my new environment, and checked: the version is rc8, with device-mapper 4.4.0!!!!!

So stopping for a second reminds me only of one thing: dmraid version is directly related to kernel version?
.. re-using genkernel made me look at this:
Quote:
* Merging
* initramfs-base-layout.cpio.gz
* initramfs-aux.cpio.gz
* initramfs-busybox-1.00-rt-mdstart.plasmaroo.cpio.gz
* initramfs-insmod-0.9.15-pre4.cpio.gz
* initramfs-udev-077.cpio.gz
* initramfs-dmraid-1.0.0.rc9.cpio.gz
* initramfs-modules-2.6.15-ck7.cpio.gz
*
* Kernel compiled successfully!


If anyone knows how to downgrade this little module inside genkernel, answer this..

See us,
Phk
_________________
"# cat /dev/urandom >> /tmp/life"
Back to top
View user's profile Send private message
ebichu
Apprentice
Apprentice


Joined: 03 Jul 2002
Posts: 231
Location: Manchester, England

PostPosted: Thu Apr 06, 2006 10:27 am    Post subject: Reply with quote

You can set the version of dmraid that genkernel uses in the /etc/genkernel.conf file, but you will have to put the tarball into /usr/share/genkernel/pkg/ manually if it is different to the version in the genkernel ebuild.

The other thing you could try to resolve your problem (which is possibly due to having two different ataraid signatures on your disks) is to use the dodmraid="xxx" option on your kernel boot command line in grub/lilo. Maybe dodmraid="-f nvidia -ay" but you will need to experiment! You could also try and wipe the bogus "sil" signatures if you can work out where they are on the disks.
_________________
Ebichu wa chiizu ga daisuki dechu!
Back to top
View user's profile Send private message
Phk
Guru
Guru


Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time

PostPosted: Thu Apr 06, 2006 2:32 pm    Post subject: Reply with quote

ebichu wrote:
You can set the version of dmraid that genkernel uses in the /etc/genkernel.conf file, but you will have to put the tarball into /usr/share/genkernel/pkg/ manually if it is different to the version in the genkernel ebuild.


I tried to replace the tar.bz2 file in /usr/share/genkernel/pkg/, but forgot to set it in /etc/genkernel.conf.. Thanks for the tip, ill try it rightaway.

ebichu wrote:
The other thing you could try to resolve your problem (which is possibly due to having two different ataraid signatures on your disks) is to use the dodmraid="xxx" option on your kernel boot command line in grub/lilo. Maybe dodmraid="-f nvidia -ay" but you will need to experiment!


I'll try this too in next reboot.

ebichu wrote:
You could also try and wipe the bogus "sil" signatures if you can work out where they are on the disks.


This part i didn't understand. Where or how are those signatures on the disk? How can i catch\delete them? I thought they were possible chipsets found, not data on the disks.

I'll report a.s.a.p.

Ah.. and THANKS ebichu =)
Phk
_________________
"# cat /dev/urandom >> /tmp/life"
Back to top
View user's profile Send private message
Phk
Guru
Guru


Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time

PostPosted: Thu Apr 06, 2006 4:39 pm    Post subject: Reply with quote

SOLVED!

Editing genkernel.conf and setting version to prior (1.0.0-rc8) fixed it.

Thanks ebichu, =)

/me is happy now.
_________________
"# cat /dev/urandom >> /tmp/life"
Back to top
View user's profile Send private message
ebichu
Apprentice
Apprentice


Joined: 03 Jul 2002
Posts: 231
Location: Manchester, England

PostPosted: Fri Apr 07, 2006 10:17 am    Post subject: Reply with quote

Phk wrote:
ebichu wrote:
You could also try and wipe the bogus "sil" signatures if you can work out where they are on the disks.


This part i didn't understand. Where or how are those signatures on the disk? How can i catch\delete them? I thought they were possible chipsets found, not data on the disks.

There is marker data on the disks placed there by the RAID creation routines and checked by the RAID detection routines in the ATARAID BIOS. The different vendors use different markers on the disk. DMRAID is checking the markers on the disks, not the chipset. (This is good when your computer's mobo blows up - as long as you can still connect the disks to another PC running Linux, you can use dmraid to access the RAID array for data recovery purposes no matter what chipset the other PC is using.)


Phk wrote:
SOLVED!

Editing genkernel.conf and setting version to prior (1.0.0-rc8) fixed it.

That's good, but I wonder what's different in rc9?
_________________
Ebichu wa chiizu ga daisuki dechu!
Back to top
View user's profile Send private message
Phk
Guru
Guru


Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time

PostPosted: Fri Apr 07, 2006 1:55 pm    Post subject: Reply with quote

ebichu wrote:
Phk wrote:
ebichu wrote:
You could also try and wipe the bogus "sil" signatures if you can work out where they are on the disks.


This part i didn't understand. Where or how are those signatures on the disk? How can i catch\delete them? I thought they were possible chipsets found, not data on the disks.

There is marker data on the disks placed there by the RAID creation routines and checked by the RAID detection routines in the ATARAID BIOS. The different vendors use different markers on the disk. DMRAID is checking the markers on the disks, not the chipset. (This is good when your computer's mobo blows up - as long as you can still connect the disks to another PC running Linux, you can use dmraid to access the RAID array for data recovery purposes no matter what chipset the other PC is using.)


Phk wrote:
SOLVED!

Editing genkernel.conf and setting version to prior (1.0.0-rc8) fixed it.

That's good, but I wonder what's different in rc9?


I dunno, maybe it should be reported... shouldn't it?
How can i?

Thanks again
_________________
"# cat /dev/urandom >> /tmp/life"
Back to top
View user's profile Send private message
ebichu
Apprentice
Apprentice


Joined: 03 Jul 2002
Posts: 231
Location: Manchester, England

PostPosted: Fri Apr 07, 2006 3:18 pm    Post subject: Reply with quote

Phk wrote:
ebichu wrote:
Phk wrote:
SOLVED!

Editing genkernel.conf and setting version to prior (1.0.0-rc8) fixed it.

That's good, but I wonder what's different in rc9?


I dunno, maybe it should be reported... shouldn't it?
How can i?

It might be hard to reproduce without your disks, but perhaps you could see if it's been fixed in rc10? That should just be a case of downloading it from http://people.redhat.com/~heinzm/sw/dmraid/src/, copying it into /usr/share/genkernel/pkg/, bumping the dmraid version in /etc/genkernel.conf and rerunning genkernel.

If it hasn't been fixed, you could try contacting the developer Heinz Mauelshagen directly, but I'm sure he'd rather receive questions on the mailing list <ataraid-list@redhat.com>.
_________________
Ebichu wa chiizu ga daisuki dechu!
Back to top
View user's profile Send private message
Phk
Guru
Guru


Joined: 02 Feb 2004
Posts: 428
Location: [undef], Lisbon, Portugal, Europe, Earth, SolarSystem, MilkyWay, 23Q Radius, Forward Time

PostPosted: Fri Apr 07, 2006 3:43 pm    Post subject: Reply with quote

Okidoki!! Thanks little bichu ;) You were much helpfull :D

Phk
_________________
"# cat /dev/urandom >> /tmp/life"
Back to top
View user's profile Send private message
ebichu
Apprentice
Apprentice


Joined: 03 Jul 2002
Posts: 231
Location: Manchester, England

PostPosted: Fri Apr 07, 2006 3:52 pm    Post subject: Reply with quote

Phk wrote:
ebichu wrote:
You could also try and wipe the bogus "sil" signatures if you can work out where they are on the disks.


This part i didn't understand. Where or how are those signatures on the disk? How can i catch\delete them? I thought they were possible chipsets found, not data on the disks.


You can delete the bogus "sil" signatures using dmraid itself, e.g. running it from the LiveCD:
Code:
dmraid -r -f sil -E

The above finds all block devices that appear to be part of a "sil" format raid set and prompts you to erase the metadata on each one. It will probably be a good idea to answer "n" the first time you try it. Deleting the wrong metadata would be slightly disastrous, but not impossible to recover from. It dumps the old metadata to some files and the man page has instructions for how to restore the old metadata from these files. But if running on a LiveCD you'd better save them onto something more permanent than a RAM disk!
_________________
Ebichu wa chiizu ga daisuki dechu!
Back to top
View user's profile Send private message
zxy
Veteran
Veteran


Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer

PostPosted: Wed Apr 12, 2006 6:49 am    Post subject: Reply with quote

I have the same problem. My running kernel is 2.6.15-r1 patched with reiser4.
I tried two no-sources kernels. 2.6.16-? and 2.6.17-?.
Both of them produced the same as above during boot. Dmraid partitions were not recognised, so I couldn't boot.

I'm afraid to recompile dmraid with symlink for kernel sources linked to no-sources kernel, because then I might not be able to boot back with my current 2.6.15-r1 kernel.

Any Idea, how to solve this. I don't use genkernel.
Back to top
View user's profile Send private message
zxy
Veteran
Veteran


Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer

PostPosted: Wed Apr 12, 2006 7:23 am    Post subject: Reply with quote

I've set symlink for /usr/src/linuxI to no-sources kernel recompiled device-mapper and dmraid. And then recompiled kernel. No change. Still boot error.
Back to top
View user's profile Send private message
ebichu
Apprentice
Apprentice


Joined: 03 Jul 2002
Posts: 231
Location: Manchester, England

PostPosted: Wed Apr 12, 2006 9:20 am    Post subject: Reply with quote

zxy wrote:
I've set symlink for /usr/src/linuxI to no-sources kernel recompiled device-mapper and dmraid. And then recompiled kernel. No change. Still boot error.

Are you using genkernel to build the initrd needed for booting? The versions of device-mapper and dmraid that genkernel uses are independent from the the sys-fs/device-mapper and sys-fs/dmraid ebuilds. You can configure the versions that genkernel uses in /etc/genkernel.conf, but if those versions disagree with the versions fetched by the sys-kernel/genkernel ebuild, you will have to fetch the different versions and place them in /usr/share/genkernel/pkg/ manually, as explained in earlier posts in this thread.
_________________
Ebichu wa chiizu ga daisuki dechu!
Back to top
View user's profile Send private message
zxy
Veteran
Veteran


Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer

PostPosted: Wed Apr 12, 2006 9:28 am    Post subject: Reply with quote

As I wrote. I don't use genkernel.
Back to top
View user's profile Send private message
ebichu
Apprentice
Apprentice


Joined: 03 Jul 2002
Posts: 231
Location: Manchester, England

PostPosted: Wed Apr 12, 2006 12:20 pm    Post subject: Reply with quote

zxy wrote:
As I wrote. I don't use genkernel.

But presumably you are using an initrd if your root filesystem is on the RAID array?
_________________
Ebichu wa chiizu ga daisuki dechu!
Back to top
View user's profile Send private message
zxy
Veteran
Veteran


Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer

PostPosted: Wed Apr 12, 2006 4:20 pm    Post subject: Reply with quote

Yes, I use initrd
Back to top
View user's profile Send private message
ebichu
Apprentice
Apprentice


Joined: 03 Jul 2002
Posts: 231
Location: Manchester, England

PostPosted: Wed Apr 12, 2006 4:36 pm    Post subject: Reply with quote

Well you probably know more than me then. Genkernel seemed the easiest way to go when I started using 2.6 kernels on an ATARAID system. I've never tried mkinitrd or constructing initrds manually. Genkernel's not so bad though. :)
_________________
Ebichu wa chiizu ga daisuki dechu!
Back to top
View user's profile Send private message
zxy
Veteran
Veteran


Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer

PostPosted: Wed Apr 12, 2006 5:20 pm    Post subject: Reply with quote

Here is the howto with genkernel and without genkernel
http://gentoo-wiki.com/HOWTO_Install_Gentoo_with_NVRAID_using_dmraid

Genkernel is easy, but without you can have only what you want in your kernel. Genkernel is no solution for me, that's why I dont use it.

If i recompile dmraid and create new initrd with no-sources symlinked to my /usr/src/linux folder, then I don't know if I'll still be able to boot with my older kernels.
Back to top
View user's profile Send private message
ebichu
Apprentice
Apprentice


Joined: 03 Jul 2002
Posts: 231
Location: Manchester, England

PostPosted: Thu Apr 13, 2006 10:45 am    Post subject: Reply with quote

zxy wrote:
Genkernel is easy, but without you can have only what you want in your kernel. Genkernel is no solution for me, that's why I dont use it.

You can use custom kernel configurations with genkernel pretty easily. Typically, I copy the old .config into the new kernel sources, run "make oldconfig" and sometimes "make menuconfig". Then when I'm happy, I run genkernel with the --oldconfig option and the --dmraid option. It may be possible to skip some of those steps, but I don't trust genkernel that much yet!

Quote:
If i recompile dmraid and create new initrd with no-sources symlinked to my /usr/src/linux folder, then I don't know if I'll still be able to boot with my older kernels.

I'm not entirely sure why dmraid needs the /usr/src/linux folder - it must be to access some private header files. I don't think dmraid would be that fussy which particular kernel sources it is compiled against unless something pretty major has changed in the userspace-kernelspace interface. Besides, the dmraid binary in the initrd is built independently from the one built by emerge sys-fs/dmraid. On booting with the dmraid-enabled initrd, it is the version in the initrd that sets up device-mapper, before the real root partition containing the dmraid built by emerge dmraid has even been mounted! So I'd forget about re-emerging sys-fs/dmraid for now and concentrate on getting the dmraid in the initrd working.
_________________
Ebichu wa chiizu ga daisuki dechu!
Back to top
View user's profile Send private message
zxy
Veteran
Veteran


Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer

PostPosted: Thu Apr 13, 2006 6:49 pm    Post subject: Reply with quote

I tried your way, ebichu.
Compiling errors ocurred with my old configuration, so I said, let's try this genkernel once again after a long, long time. I compiled full tree for no-sources-2.6.16-no1 and no-sources-rc1-2.6.17-no2 both produced the same error.
Code:

* ERROR: Failed to compile the "EXTRAS="extras/scsi_id extras/volume_id extras/ata_id extras/run_directory extras/usb_id extras/floppy extras/cdrom_id extras/firmware" USE_KLIBC=true KLCC=/var/tmp/genkernel/4833.23453.13179.3792/klibc-build/bin/klcc USE_LOG=false DEBUG=false udevdir=/dev all" target...

* -- End log... --


Any ideas?
--- EDIT ---

Doesnot work with gentoo-sources either.
Back to top
View user's profile Send private message
zxy
Veteran
Veteran


Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer

PostPosted: Thu Apr 13, 2006 8:40 pm    Post subject: Reply with quote

Problem was with udev and genkernel. I changed udev version in gekernel's ebuild, emerged it again and it compiled kernel ok.

But...

It now doesn't find my nvidia-raid partitions. Boots ok, but dmraid doesn't find disks. Before dmraid starts I see in the output that devfs doesn't find /dev...

What now?

I thought that devfs is obsolete

I'll try with no automounter support in pseudo filesystems (kernel config)

I can still boot my other kernels and they work ok.
Back to top
View user's profile Send private message
zxy
Veteran
Veteran


Joined: 06 Jan 2006
Posts: 1160
Location: in bed in front of the computer

PostPosted: Thu Apr 13, 2006 11:52 pm    Post subject: Reply with quote

I found out that it is dmraid problem. Version 1.0.0-rc11 will solve this problem with 2.6.16 kernels.

See this bug here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186842
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