Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
RAID-0 Si3112: Dmraid doesnt see partitions at boot [SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
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: Sun Mar 06, 2005 7:36 pm    Post subject: RAID-0 Si3112: Dmraid doesnt see partitions at boot [SOLVED] Reply with quote

Hi there everyone!

I'm installing Gentoo 2004.3 with a Stage 1 on Stage 3 Tarball install, everything went fine, until now (the boot time..)
My system has a MoBo (a7n8x-e Deluxe) RAID'0 working, and i want to keep it so that i can enjoy the 90MB\s access, in windows and linux =)

So, i've thought about booting from a 64MB USB-HDD, having a NTFS partition for the gaming console, and a REISER4; everything working with raid (except for the USB-Hdd, of course..)

I've followed the following tutorials:

:arrow: Installing Gentoo: Stage 1 NPTL on a Stage 3 Tarball
:arrow: [HOWTO] HPT, Promise, Medley, Intel, Nvidia RAID Dualboot

So, i did: [EDIT]

:arrow: Booted an HardcoreGamingMachine BootCD (winXPsp2)
:arrow: Partitioned my hard-drive (when i used linux's fdisk to do this, PMagic stopped working, saying "Disk Geometry Fault".. .. ..)
:arrow: Installed the gaming console, reboot. (lol)
:arrow: Booted from the great RR4 boot-CD available by lxnay
:arrow: Created /etc/raidtab, pointing disks /dev/sda and /dev/sdb to device /dev/md0
:arrow: Created /etc/device-mapper-rootPartition, swapPartition (using fdisk -ul /dev/md0 to see the block info)
:arrow: "raid0run /dev/md0", everything fine, all partitions correct.
:arrow: Used "dmsetup create rootRaid /etc/device-mapper-rootPartition" (to provide access to my root partition)
:arrow: Formatted /dev/mapper/rootRaid with REISER4
:arrow: Mounted everything to start the install.
(...)
:arrow: Followed the 1on3 tutorial and installed everything.
(...)
:arrow: Now i've rebooted using the gen2dmraid 0.99a.iso, which detected my root, swap, windows, and the 2 backup partitions
:arrow: I've compiled a 2.6.11-love2 kernel, with attention.. (if u want i can post my .conf)
:arrow: I've made the initrd like on the second tutorial, and also copied it to the USB-HDD
:arrow: Reboot.

And now.. the mess.....

Quote:
devfs_mk_dev: could not append to parent for md/0
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compresses image found at block 0
VFS: Mounted root (ext2 filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 220k freed
>> Mounting filesystems...
>> Preparing environment for dmraid...
rm: unable to remove /dev/mapper/control: Operation not permitted
>> Creating /dev/mapper/control character device with major:10 minor:61...
mknod: /dev/mapper/control: file exists
>> Calling dmraid...
no block devices found
>> dmraid was run successfully
>> Determining root device...
>> Block device /dev/mapper/sil_afadafceafccb5 is not a valid root device...
>> the root block device is unspecified or not detected
>> Specify real_root=<root_blockdevice> on the kernel cmdline
Please specify a device to boot, or shell for a shell...
boot() :: shell


When i open the shell and do "ls /dev/mapper" i only get the "control", not the partitions.
[/EDIT]

.... :cry:

[[ ]]'s
_________________
"# cat /dev/urandom >> /tmp/life"


Last edited by Phk on Tue Mar 22, 2005 2:11 pm; edited 5 times in total
Back to top
View user's profile Send private message
garlicbread
Apprentice
Apprentice


Joined: 06 Mar 2004
Posts: 182

PostPosted: Wed Mar 09, 2005 11:53 pm    Post subject: Reply with quote

from the looks of things it's not so much the raid more of the grub file that's the problem

From grub's perspective it's loaded initially from the boot sector at the beginning of the disk
so it has no idea where your root volume is unless you tell it which disk / which partition on the disk to use

this is a copy of a section from my own

Code:

#
# Sample boot menu configuration file
#

# Boot automatically after 30 secs.
timeout 10
# By default, boot the first entry.
default 0
# Fallback to the second entry.
fallback 1
# Image to display
splashimage=(hd0,0)/grub/splash.xpm.gz

# Gentoo Linux 2.6.10 stable based on gentoo-dev-sources
title  Gentoo Linux 2.6.10 Stable
root   (hd0,0)
kernel (hd0,0)/kernel-2.6.11-mygen-r2 root=/dev/ram0 real_root=/dev/evms/lvm2/vg/root_first splash=0 video=vesa-tng:ywrap,mtrr vga=0x31A ramdisk_size=12000 devfs=nomount gentoo=nodevfs
initrd (hd0,0)/initramfs-evms-udev-1.cpio.gz


(hd0,0) means first disk, first partition seen by grub
(hd1,0) would mean second disk first partition
(hd0,1) would mean first disk second partition
disk / partition numbers start from 0 with grub

with my own system the /boot directory actually a mount of the first partition of the disk
hda1 within /dev or (hd0,0) in grub speak

typically you have to pass 2 things
1. the kernel image to load
2. the initrd image to load (if one is used which I'm assuming it would be use with Raid)

when grub is first loaded at boot time it only needs to read these 2 files (not write) from the Raid Array
since it's not using the linux kernel at this point it sees whatever the bios sees (similar to what you would see in DOS with pqmagic e.g.)
since you using a USB HDD I'm not sure the bios would recognise the array as an array but if the bios can see it okay then so can grub
once the initrd is loaded then the kernel has to do it's own thing, to make the root fs visible (which may involve running some software raid utility built into the initrd)
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: Sat Mar 19, 2005 2:47 pm    Post subject: Reply with quote

And now, here my reduced 2.6.11-love2 kernel config:

Code:
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.11-love2 "The Time is Now"
# Fri Mar 18 15:38:14 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=y
# CONFIG_BLK_DEV_COMPRESSLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_SX8=y
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=8192
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_LBD=y
# CONFIG_CDROM_PKTCDVD is not set

#
# IO Schedulers
#
# CONFIG_ATA_OVER_ETH is not set

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=y
# CONFIG_IDE_TASK_IOCTL is not set

#
# IDE chipset support/bugfixes
#
# CONFIG_IDE_GENERIC is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_IT821X is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
CONFIG_BLK_DEV_SIIMAGE=y
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=y
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=m
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
CONFIG_SCSI_SATA=y
# CONFIG_SCSI_ATA_ADMA is not set
# CONFIG_SCSI_SATA_AHCI is not set
# CONFIG_SCSI_SATA_SVW is not set
# CONFIG_SCSI_ATA_PIIX is not set
CONFIG_SCSI_SATA_NV=y
# CONFIG_SCSI_PATA_PDC2027X is not set
# CONFIG_SCSI_SATA_PROMISE is not set
# CONFIG_SCSI_SATA_QSTOR is not set
# CONFIG_SCSI_SATA_SX4 is not set
CONFIG_SCSI_SATA_SIL=y
# CONFIG_SCSI_SATA_SIS is not set
# CONFIG_SCSI_SATA_ULI is not set
# CONFIG_SCSI_SATA_VIA is not set
# CONFIG_SCSI_SATA_VITESSE is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=y
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=y
CONFIG_MD_RAID1=m
# CONFIG_MD_RAID10 is not set
CONFIG_MD_RAID5=m
# CONFIG_MD_RAID6 is not set
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=y
CONFIG_DM_SNAPSHOT=y
CONFIG_DM_MIRROR=y
CONFIG_DM_ZERO=y

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
CONFIG_REISER4_FS=y
# CONFIG_REISER4_DEBUG is not set
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
# CONFIG_REISERFS_FS_XATTR is not set
CONFIG_JFS_FS=y
# CONFIG_JFS_POSIX_ACL is not set
# CONFIG_JFS_SECURITY is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_FS_POSIX_ACL=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-15"
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_TMPFS_XATTR is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
CONFIG_CRAMFS=y
CONFIG_SQUASHFS=y
CONFIG_SYSV_FS=y
CONFIG_UFS_FS=y
CONFIG_LUFS_FS=y

#
# Network File Systems
#
CONFIG_SMB_FS=y
CONFIG_CIFS=y
CONFIG_SH_FS=y

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
CONFIG_MSDOS_PARTITION=y
CONFIG_LDM_PARTITION=y


#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-15"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_ISO8859_15=y
CONFIG_NLS_UTF8=y

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
CONFIG_DEBUG_PREEMPT=y
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_FRAME_POINTER is not set
# CONFIG_CFLAGS_EDIT is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_4KSTACKS is not set
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y

________________________________________________________________


And here is my GRUB.CONF:

Code:
timeout 3
default 0
fallback 0
splashimage=/grub/gentoo.xpm.gz

title Gentoo Mega mega beta...
kernel /new_kernel root=/dev/ram0 real_root=/dev/mapper/sil_afadafceafccb5 init=/linuxrc video=vesafb:1280x1024-24@75 splash=verbose,theme:emergence
initrd /initrd

________________________________________________________________

Guess this is all that's needed..... Can you see where the error is??

Thanks....
_________________
"# 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: Sun Mar 20, 2005 4:53 pm    Post subject: Reply with quote

... Sorry guys, i had "DevFS" turned on at the kernel, and i didn't even noticed....

However, new problem appeared:
Quote:
* Starting up RAID devices:
* Trying md0.../dev/md0: Invalid argument
handling MD device /dev/md0
analyzing super-block
mkraid: aborted.
An error occurred during the RAID startup, dropping your to a shell:
the system will reboot after you do manteinance


Just after the kernel boots, and the gentoo system starts booting....


"catting" /proc/mdstat gives me:
Quote:
Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6] [raid10]
md0 : inactive
unused devices: <none>


My dmesg said:
Quote:
[ 41.965798] md: raidstart(pid 5460) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6
[ 41.965810] md: could not bd_claim sda.
[ 41.965815] md: autostart failed!
[ 41.972675] md: could not bd_claim sda.
[ 41.972681] md: error, md_import_device() returned -16


Tips........... please.... :D
_________________
"# 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: Sun Mar 20, 2005 9:49 pm    Post subject: Reply with quote

Well, i've changed the "/etc/init.d/checkfs" script, so that it wont break if a filesystem-check-error occurs...
I know this is a bad policy, but it's only temporary :) I won't keep the installation until i've fixed this.

Now, all the above problem have disappeared, except for this one:

Quote:
* Using /sbin/hotplug as hotplug agent ...
* Mounting devpts at /dev/pts ...
* Activating (possible) swap ...
* Remounting root filesystem read-only (if necessary) ...
* Skipping root filesystem check (fstab's passno == 0) ...
* Remounting root filesystem read/write ...
* You should stop using /etc/hostname and use /etc/conf.d/hostname
* Setting hostname to Darkness ...
* Calculating module dependencies ...
* Starting up RAID devices: ...
* Trying md0.../dev/md0: Invalid argument
handling MD device /dev/md0
analyzing super-block
mkraid: aborted.
(In addition to the above messages, see the syslog and /proc/mdstat as well
for potential clues.)

* Checking all filesystems ...
* Mounting local filesystems ...
* Mounting USB device filesystem (usbfs) ...
* Activating (possibly) more swap ...
* Setting system clock to hardware clock [UTC] ...
* Starting hdparm ...
* Configuring kernel parameters ...
* Updating environment ...
* Cleaning /var/lock, /var/run ...


And after this, the system boots normally...

I think this problem is in a boot-up script too, which tries to start the array again, without it beeing necessary.

Here's my "rc-update show":
Quote:
acpid | default
bootmisc | boot
checkfs | boot
checkroot | boot
clock | boot
coldplug | default
consolefont | boot
crypto-loop |
dm | boot
domainname | default
gpm | default
hdparm | boot
hostname | boot
hotplug | default
keymaps | boot
local | default nonetwork
localmount | boot
modules | boot
net.eth0 | default
net.lo | boot
netmount | default
nscd |
ntp-client | default
ntpd |
numlock | default
rmnologin | boot
rsyncd |
serial | boot
splash | default
sshd | default
syslog-ng | default
urandom | boot
vixie-cron | default
xdm |
xfs |
xinetd | default


Please tell me if you know what's happenning! Thanks ;)
_________________
"# 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: Tue Mar 22, 2005 2:15 pm    Post subject: Reply with quote

!! SOLVED !!

If i was using the gen2dmraid made INITRD, it should already take take of making all the partitions under the "/dev/mapper".

So.... What was my old /etc/raidtab doing?? :D:D

Code:
# rm /etc/raidtab


Solved it.

Because "/etc/init.d/checkfs" checks for a /etc/raidtab or /etc/mdadm.conf, and if they exist, it "mounts" their partitions in order to check them...
Of course, /dev/md0 was already active, so the error appeared.

......

Ahhh... It's nice to finally boot the fastest but most unsecure FS in the world:
......a REISER4 RAID-0 partition ;)


Thanks to all who helped. Cheers!
_________________
"# cat /dev/urandom >> /tmp/life"
Back to top
View user's profile Send private message
MiddleBrooker
n00b
n00b


Joined: 26 Oct 2005
Posts: 5

PostPosted: Wed Oct 26, 2005 2:07 pm    Post subject: Reply with quote

Hy guys,
I'm new member of this forum and I've the same problem.

I've already red a lot of post into the forum but avtually I'm not able to fix the problem that is driving me mad!

I think that is a kernel configuration problem, I've the latests gentoo-r3 (installed today) and I've understood that this problem is due to the DevFS
(CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y)

sorry but I don't have these entryes in my kernel configuration file......any suggestion will be very appreciated!!

Thanks a lot for all the support.


Quote:
devfs_mk_dev: could not append to parent for md/0
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compresses image found at block 0
VFS: Mounted root (ext2 filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 220k freed
>> Mounting filesystems...
>> Preparing environment for dmraid...
rm: unable to remove /dev/mapper/control: Operation not permitted
>> Creating /dev/mapper/control character device with major:10 minor:61...
mknod: /dev/mapper/control: file exists
>> Calling dmraid...
no block devices found
>> dmraid was run successfully
>> Determining root device...
>> Block device /dev/mapper/sil_afadafceafccb5 is not a valid root device...
>> the root block device is unspecified or not detected
>> Specify real_root=<root_blockdevice> on the kernel cmdline
Please specify a device to boot, or shell for a shell...
boot() :: shell
Back to top
View user's profile Send private message
MiddleBrooker
n00b
n00b


Joined: 26 Oct 2005
Posts: 5

PostPosted: Wed Oct 26, 2005 2:26 pm    Post subject: Reply with quote

Sorry, the kernel is the 2.6.13-gentoo-r3 !

Thanks in advice
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: Sun Oct 30, 2005 11:11 pm    Post subject: Reply with quote

Well man... I can't tell you for sure, but it seems that you're passing the wrong argument "real_root=" in your kernel!!

Check the /dev/mapper/sil###### numbers you've used... (i think you've already done it, haven't you?)

Cheers,
Phk
_________________
"# cat /dev/urandom >> /tmp/life"
Back to top
View user's profile Send private message
MiddleBrooker
n00b
n00b


Joined: 26 Oct 2005
Posts: 5

PostPosted: Mon Oct 31, 2005 10:30 am    Post subject: Reply with quote

Phk wrote:
Well man... I can't tell you for sure, but it seems that you're passing the wrong argument "real_root=" in your kernel!!

Check the /dev/mapper/sil###### numbers you've used... (i think you've already done it, haven't you?)

Cheers,
Phk


Hi Guys,
I've solve my problem :)

It was due to a bad kernel configuration because the SCSI support for SATA controllers must be statically compiled into the kernel and not as module.

Infact with this module compiled into the kernel it was not able to load correctly the device-mapper to map the partition table and mount the correct mount partition.

Now is all correct :)
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: Mon Oct 31, 2005 11:41 am    Post subject: Reply with quote

Nice thing its all fixed :)
I bet it's fast as hell, isn't it? ;)

Cheers,
Phk
_________________
"# cat /dev/urandom >> /tmp/life"
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo 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