login
Search
I have been trying to get 2.6 running on Fedora Core 1
with the new 2.6 kernel. I've tried DAVEJ, ARJANV and
even built my own kernel. This machine is an IBM
intellistation with 2 scsi hard drives and a LSI Logic
scsi board. I've got Redhat 7.3 on the first hard
drive and Fedora Core 1 on the second hard drive.
I'm booting using GRUB installed in the MBR of drive 1
(the RH7.3 drive).The system does boot correctly with
the latest Fedora Core kernel. It does seem to be
loading the mptbase and mptscsih drivers. I did
remake my initrd using mkinitrd.
The error messages are :
Mounting root file system
mount : error 6 mounting ext3
pivotroot : pivot_root (/sysroot, /sysroot/initrd)
failed 2
Here is my modprobe.conf (converted from my modules
conf)
alias binfmt-204 binfmt_aout
alias binfmt-263 binfmt_aout
alias binfmt-264 binfmt_aout
alias binfmt-267 binfmt_aout
alias binfmt-387 binfmt_aout
alias binfmt-332 iBCS
alias binfmt--310 binfmt_java
alias block-major-1 rd
alias block-major-2 floppy
alias block-major-3 ide-probe-mod
alias block-major-7 loop
alias block-major-8 sd_mod
alias block-major-9 md
alias block-major-11 sr_mod
alias block-major-13 xd
alias block-major-15 cdu31a
alias block-major-16 gscd
alias block-major-17 optcd
alias block-major-18 sjcd
alias block-major-20 mcdx
alias block-major-22 ide-probe-mod
alias block-major-23 mcd
alias block-major-24 sonycd535
alias block-major-25 sbpcd
alias block-major-26 sbpcd
alias block-major-27 sbpcd
alias block-major-29 aztcd
alias block-major-32 cm206
alias block-major-33 ide-probe-mod
alias block-major-34 ide-probe-mod
alias block-major-37 ide-tape
alias block-major-44 ftl
alias block-major-46 pcd
alias block-major-47 pf
alias block-major-56 ide-probe-mod
alias block-major-57 ide-probe-mod
alias block-major-58 lvm-mod
alias block-major-88 ide-probe-mod
alias block-major-89 ide-probe-mod
alias block-major-90 ide-probe-mod
alias block-major-91 ide-probe-mod
alias block-major-93 nftl
alias block-major-97 pg
alias block-major-113 viocd
alias char-major-4 serial
alias char-major-5 serial
alias char-major-6 lp
alias char-major-9 st
alias char-major-10-0 busmouse
alias char-major-10-2 msbusmouse
alias char-major-10-3 atixlmouse
alias char-major-10-130 wdt
alias char-major-10-131 wdt
alias char-major-10-135 rtc
alias char-major-10-139 openprom
alias char-major-10-144 nvram
alias char-major-10-157 applicom
alias char-major-10-175 agpgart
alias char-major-10-184 microcode
alias char-major-10-200 tun
alias char-major-10-250 hci_vhci
alias char-major-13 input
alias char-major-13-0 joydev
alias char-major-13-32 mousedev
alias char-major-14 soundcore
alias char-major-19 cyclades
alias char-major-20 cyclades
alias char-major-21 sg
alias char-major-22 pcxx
alias char-major-23 pcxx
alias char-major-27 zftape
alias char-major-34 scc
alias char-major-35 tclmidi
alias char-major-36 netlink
alias char-major-37 ide-tape
alias char-major-48 riscom8
alias char-major-49 riscom8
alias char-major-57 esp
alias char-major-58 esp
alias char-major-63 kdebug
alias char-major-90 mtdchar
alias char-major-96 pt
alias char-major-99 ppdev
alias char-major-107 3dfx
alias char-major-108 ppp_generic
alias char-major-109 lvm-mod
alias char-major-161 ircomm-tty
alias char-major-171 raw1394
alias char-major-195 nvidia
alias char-major-200 vxspec
alias char-major-206 osst
alias char-major-216 rfcomm
alias dos msdos
alias dummy0 dummy
alias dummy1 dummy
alias eth0 tg3
alias iso9660 isofs
alias md-personality-1 linear
alias md-personality-2 raid0
alias md-personality-3 raid1
alias md-personality-4 raid5
alias md-personality-7 multipath
alias net-pf-1 unix
alias net-pf-2 ipv4
alias net-pf-4 ipx
alias net-pf-5 appletalk
alias net-pf-15 af_key
alias net-pf-17 af_packet
alias net-pf-31 bluez
alias netalias-2 ip_alias
alias irlan0 irlan
alias irda-dongle-0 tekram
alias irda-dongle-1 esi
alias irda-dongle-2 actisys
alias irda-dongle-3 actisys
alias irda-dongle-4 girbil
alias irda-dongle-5 litelink
alias irda-dongle-6 airport
alias irda-dongle-7 old_belkin
alias bt-proto-0 l2cap
alias bt-proto-2 sco
alias bt-proto-3 rfcomm
alias bt-proto-4 bnep
alias plip0 plip
alias plip1 plip
alias tunl0 ipip
alias cipcb0 cipcb
alias cipcb1 cipcb
alias cipcb2 cipcb
alias cipcb3 cipcb
alias ppp0 ppp
alias ppp1 ppp
alias scsi_hostadapter mptbase
alias slip0 slip
alias slip1 slip
alias tty-ldisc-1 slip
alias tty-ldisc-3 ppp_async
alias tty-ldisc-11 irtty
alias tty-ldisc-14 ppp_synctty
alias tty-ldisc-15 hci_uart
alias ppp-compress-18 ppp_mppe
alias ppp-compress-21 bsd_comp
alias ppp-compress-24 ppp_deflate
alias ppp-compress-26 ppp_deflate
alias parport_lowlevel parport_pc
alias usbdevfs usbcore
alias xfrm-type-2-50 esp4
alias xfrm-type-2-51 ah4
alias xfrm-type-2-108 ipcomp
alias xfrm-type-10-50 esp6
alias xfrm-type-10-51 ah6
alias xfrm-type-10-108 ipcomp6
alias cipher_null crypto_null
alias digest_null crypto_null
alias compress_null crypto_null
alias sha384 sha512
alias scsi_hostadapter1 mptscsih
alias sound-slot-0 i810_audio
alias usb-controller usb-uhci
alias usb-controller1 ehci-hcd
alias ieee1394-controller ohci1394
options sb io=0x220 irq=7 dma=1 dma16=5 mpu_io=0x330
install binfmt-0000 /bin/true
install binfmt_misc /sbin/modprobe --ignore-install
binfmt_misc &install char-major-10 /bin/true
install char-major-10-1 /bin/true
install dummy0 /sbin/modprobe -o dummy0
--ignore-install dummy
install dummy1 /sbin/modprobe -o dummy1
--ignore-install dummy
install hid /sbin/modprobe --ignore-install hid &install net-pf-10 /bin/true
install net-pf-19 /bin/true
install net-pf-3 /bin/true
install net-pf-6 /bin/true
install ov518_decomp { /sbin/modprobe ov511; } ;
/sbin/modprobe --ignore-install ov518_decomp
install sound-slot-0 /sbin/modprobe --ignore-install
sound-slot-0 &install usbmouse /sbin/modprobe --ignore-install
usbmouse &install wacom /sbin/modprobe --ignore-install wacom &remove binfmt_misc { /bin/umount
/proc/sys/fs/binfmt_misc > /dev/null 2>&1 || :; } ;
/sbin/modprobe -r --ignore-remove binfmt_misc
remove hid { /sbin/modprobe -r keybdev; /sbin/modprobe
-r mousedev; } ; /sbin/modprobe -r --ignore-remove hid
remove ov518_decomp /sbin/modprobe -r --ignore-remove
ov518_decomp &remove sound-slot-0 { /bin/aumix-minimal -f
/etc/.aumixrc -S >/dev/null 2>&1 || :; } ;
/sbin/modprobe -r --ignore-remove sound-slot-0
remove usbmouse { /sbin/modprobe -r hid; } ;
/sbin/modprobe -r --ignore-remove usbmouse
remove wacom { /sbin/modprobe -r evdev; } ;
/sbin/modprobe -r --ignore-remove wacom
My Grub entry
title=linux-2.6.1-rc2
root (hd1,0)
kernel /boot/vmlinuz-2.6.1-rc2 ro root=/dev/sdb1 rhgb
initrd /boot/initrd-2.6.1-rc2
My 2.4 kernel boot lines are set up the same way and
they work.
Any help anyone could provide would be appreciated.
you have to compile ext2 and
you have to compile ext2 and ext3 directly into your kernel
it wont work when you compiled it as module
added devices problem
desigabri
i've a problem with 2.6kernel Mandrake9.2 on KT600 ECS VIA SATA motherboard.
i tried 2.6kernel recompiled more times, and a mandrake 2.6 rpm version. All get me the same results: your results. I haven't resolved the problem but i think it comes because 2.6 kernel recognize new SATA devices and add them before the IDE ones. So the lilo.conf is not running at reboot. lilo and grub don't accept configuration with unexisting devices so i tried to pass root and init parameter at boot time.
Now the system boot and kernel is ok but i've another problem: root and init parameters run only for boot, when system try to mount the filesystem it looks for the previus setting and goes in repair mode.
kernel 2.4 (don't recognize sata devices)
hda -> ide 0,0
hdb -> ide 0,1
hdc -> ide 1,0
hdd -> ide 1,1
in lilo.conf root=/dev/hda5 SYSTEM OK !!!
kernel 2.6 (recognize new hardware but keep it before the existing devices as ide ones)
hda -> sata 0,0 !!!
hdb -> sata 0,1 !!!
hdc -> sata 1,0 !!!
hdd -> sata 1,1 !!!
hde -> ide 0,0 (ex hda)
hdf -> ide 0,1
hdg -> ide 1,0
hdh -> ide 1,1
in lilo.conf root=/dev/hda5 then i optain the same your error 6.....
lilo and grub (working from 2.4kernel) don't permit to set
root=/dev/hde5 init=hde5 so i must append them at boot time.
Now i pass the kernel loading time, but at filesystem mounting time system say me that can't mount ext3 at /dev/hda5 !!!! so it stop to work. I see the filesystem but it is mounted in readonly mode so i can't change files from console. Where can i set the root and init parameters for filesystem mount?
If i could recognize new devices as SCSI device or new ones behind the existing's i'm sure i had not the problem and system could run good.
Perhaps i given to you an idea, so now can you give me any one to solve my problems? I readed in forums about bios flags or kernel options on sata enhanced or compatible mode but i haven't any of them to set....
any idea? thanks
desigabri
got the same problem. solved
when i tried to use 2.6.2 on my redhat 9.0 box, i got the exact the same issue. recompile the 2.6.2 kernel with ext3 included not as a module because my box uses ext3 as the root. it works.
hezhu
calwink
Hi
Why dont you check out the implementation of RH 9.0 or for that matter any installation through CDs. You can observe that in the section /lib/modules//fs/ext3 you can see ext3.o. This means that they have come in as modules and they work fine even when compiled as modules.
the same error message...
desigabri
my system get back to me the same error message when i boot from new kernel 2.6
I run mandrake 9.2 and i tryed to compile some version downloaded from the web, later i tried also the mandrake 2.6 rpm version one. I recived the same messages from all of them. I compiled a lot of versions with different options as readed from varius forums, but always with the same results.
I have the KT600 ECS motherboard with via sata chipset built in. I think the problem comes from this configuration because the SATA's devices are revealed only with this new kernel. So at boot time appears 4 new devices added before the just existing IDE devices. In lilo.conf I can't configure the new devices because in 2.4 kernel version they don't exist and lilo or grub don't accept the set configuration prepared for the 2.6 kernel version.
2.4 kernel:
hda -> ide 0,0
hdb -> ide 0,1
hdc -> ide 1,0
hdd -> ide 1,1
the root is pointed at /dev/hda5
because 2.6 kernel add the sata devices before the ide's, the resultin devices resoult:
hda -> sata 0,0
hdb -> sata 0,1 (it doesn't exist bacause KT600 natively supplies only the primaries sata device/controller
hdc -> sata 1,0
hdd -> sata 1,1 (doesn't exist as you can read up)
hde -> ide 0,0
hdf -> ide 0,1
hdg -> ide 1,0
hdh -> ide 1,1
I tryed to supply root parameter and init parameters at boot time:
root=/dev/hde5 init=/dev/hde5 so i pass kernel panic but I receive an error about ext3 filesystem that can't be mounted and the system suggest to me to reboot or go in repair mode. The stuff that i can't understand is that system replay that it can't mount root partition at /dev/hda5!!! so it understood root and init parameters only for the first boot but when it try to mount the filesystem it forget them :(
Where can I pass to the system the ultimate parameters to complete the mount?
I think i'm nearly to resolve the problem but i'm a newbye so i was happy to get arrived in the installation of the last nvidia drivers (with problem of installation), the win4lin (with some problem of installation), vmware (with some problem of installation)...and now i've spent other hundred hours for 2.6 kernel....sigh.....so are anyone that can suggest me how to arrive at the finally solution? :)
(i read somewhere to compile kernel or set bios as sata enhanced not as compatible mode (to view devices as scsi devices not ide or to view them behind the ide's so nothing should changed in lilo.conf and all should go as the 2.4.....but i haven't found similar options in bios or in kernel configuration!)
please please please.....any idea is whelcome
desigabri
error 6 mounting ext3 kernel panic with the same error message
desigabri
my system get back to me the same error message when i boot from new kernel 2.6
I run mandrake 9.2 and i tryed to compile some version downloaded from the web, later i tried also the mandrake 2.6 rpm version one. I recived the same messages from all of them. I compiled a lot of versions with different options as readed from varius forums, but always with the same results.
I have the KT600 ECS motherboard with via sata chipset built in. I think the problem comes from this configuration because the SATA's devices are revealed only with this new kernel. So at boot time appears 4 new devices added before the just existing IDE devices. In lilo.conf I can't configure the new devices because in 2.4 kernel version they don't exist and lilo or grub don't accept the set configuration prepared for the 2.6 kernel version.
2.4 kernel:
hda -> ide 0,0
hdb -> ide 0,1
hdc -> ide 1,0
hdd -> ide 1,1
the root is pointed at /dev/hda5
because 2.6 kernel add the sata devices before the ide's, the resultin devices resoult:
hda -> sata 0,0
hdb -> sata 0,1 (it doesn't exist bacause KT600 natively supplies only the primaries sata device/controller
hdc -> sata 1,0
hdd -> sata 1,1 (doesn't exist as you can read up)
hde -> ide 0,0
hdf -> ide 0,1
hdg -> ide 1,0
hdh -> ide 1,1
I tryed to supply root parameter and init parameters at boot time:
root=/dev/hde5 init=/dev/hde5 so i pass kernel panic but I receive an error about ext3 filesystem that can't be mounted and the system suggest to me to reboot or go in repair mode. The stuff that i can't understand is that system replay that it can't mount root partition at /dev/hda5!!! so it understood root and init parameters only for the first boot but when it try to mount the filesystem it forget them :(
Where can I pass to the system the ultimate parameters to complete the mount?
I think i'm nearly to resolve the problem but i'm a newbye so i was happy to get arrived in the installation of the last nvidia drivers (with problem of installation), the win4lin (with some problem of installation), vmware (with some problem of installation)...and now i've spent other hundred hours for 2.6 kernel....sigh.....so are anyone that can suggest me how to arrive at the finally solution? :)
(i read somewhere to compile kernel or set bios as sata enhanced not as compatible mode (to view devices as scsi devices not ide or to view them behind the ide's so nothing should changed in lilo.conf and all should go as the 2.4.....but i haven't found similar options in bios or in kernel configuration!)
please please please.....any idea is whelcome
desigabri
sorry for the double message....now all go right
desigabri
I'm sorry for the double messages but there was a problem so the first and the second one didn't appeare in my browser so the first time i wrote it again and a second time (i saved a copy) i pasted it in the third...
OK now i resolved my problem looking about kernel boot parameters about ide periferals.
I had passed the ide0=1x1f0,0x3f6,14 ide1=1x170,0x376,15 parameters (seems that they are common for most mother boards) so kernel 2.6 see them before of the sata controller. Nothing change in boot steps and now linux start as with the 2.4 kernel.
thanks a lot for your help
desigabri
How to pass the ide parameters?
I am having the same problem when trying to run 2.6.2.
How do you pass the ide parameters as mentioned above?
Thanks, Nick.
Interested too
I have an Abit KV7 motherboard (KT600) and the same troubles as those described.
I would be very interested to know how you did manage to pass the ide parameters.
Thanks in advance,
Sagittarius
Jabber : Sagittarius at amessage.ch
ICQ : 172715547
Thank You! somewhat.... ;-)
desigabri,
This helped me on a problem installing Fedora Core 2 with a 4.3Gb ATA drive and a 160Gb SATA drive on a Silicon Image Sil3112A controller. I have been pulling my hair out, changing things in Grub.conf and fstab, then found your comment. I tried it and Voila!
Alas, my success is limited however. When I reboot the system, the problem returns. A hard boot however fixes it. I must look into how the kernel reboots my system now.
Thanks,
Cory
error 6 mounting ext3 - kernel panic with 2.6
Do not set ext3 as module, include it in the kernel:
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
# CONFIG_EXT3_FS_SECURITY is not set
It is OK.
error 6 mounting ext3
Thanks dude, after following this it worked!!!
error 6 mounting ext3 - kernel panic with 2.6
I have the exact same issue.. However since I am knew to Linux don't understand where are these to be included.. which file (kernel? how).
Oooops...
I had the exact same error message, and found that I had written root=/dev/hda6 instead of root=/dev/hda5 on the kernel line in /boot/grub/grub.conf. If you've messed up the name of the root device on your kernel command line, this error will occur.
I had this problem too, it tu
I had this problem too, it turned out that root=/dev/sda5 made it mad and i'm not really sure why. I changed it back to root=LABEL=/ and it worked... Now i know what some of you are thinking, 'you idiot /dev/sda5 wasnt your root partition', but it is...
~Shaun
re: I had this problem too, it tu
This fixed my ext3 failed mounting problem too. I was upgrading a buddy's old PC w/ a Fedora Core 3 stock kernel to a 2.6.10 (or 2.6.9). I had the file systems I was using built in (which shouldn't be a problem anyway since necessary kernel mods are loaded to a RAM disk before mounting root). It seems that the only thing grub needed to be happy was the "root=LABEL=/", not all that crap that make install puts in "ro root=LABEL=/ quiet rgbd"... that made it fail too.
Thanks for your help!
Having very similar problem
Using the "2.6.10-1.9_FC2" kernel built and distributed as a Fedora Core 2 update, I'm having exactly the same problem.
My boot partition is a SCSI drive. With precisely the same boot parameters, an older 2.6.8 kernel boots and runs just fine. However, I cannot get any of the FC2 kernels recently distributed to boot at all; they immediately fail with the "mount: error 6" problem.
I'm not picking the wrong device; as I wrote above, the exact same boot parameters (ie, "root=/dev/sda2") work fine with a different (older) kernel. This is not a kernel I built myself, it's one from the distribution. Is it possible that the distributed kernels are not built with ext2/3 support linked in? That seems astounding to me, as it should certainly cause issues with a vast number of installations.
My problem in this case seems
My problem in this case seems to be that the kernel as distributed does not have the appropriate SCSI driver available. Building my own kernel and including the SCSI driver (SYM53C8XX).
It seems a little weird that the distributed kernel would thusly fail.
hmm, guess i found the problem
hey guys i figured out that there at the newer 2.6.x kernels are two SATA driver. one of them is the SCSI SATA and the other is the IDE SATA
IDE SATA does hd devices
SCSI SATA does sd devices
hmm but i still cant boot with kernel 2.6.10 on ia 32 when i used a amd 64 solution on fedora core 3 i had not such strange problems.
so i think that the initrd uses the IDE drivers and the system later changes to the SCSI drivers ?!
hmm i donno .. i will try to disable the IDE stuff to get my 2.6.10 kernel running ..
i hope that works :)
cause i love to use a up to date kernel.
or i switch back to gentoo or vlos...
i feel kinda stupid cause i got it running on the 64 bit version without any strange problems..
but there u have nearly no support for desktop usage ;( so i switched back to 32 bit .. and got in trouble :(
if any one figured out a solution to solve that problem please let me know :) also will i tell you my solution if i get one without changing the operation system :)
what our a solution for lesser mortals
I have not tried to build my kernel. I am getting the same error : "error 6..."
ANy solution involving rescue commands and/or grub.conf changes ?
Thanks
LVM renaming can cause trouble, too.
If the root filesystem must be mounted from a LVM logical volume, and the logical volume and/or volume group is renamed, corresponding change must be made to grub.conf. Also, mkinitrd-4.2.15-1 includes a reference by name to the volume group containing the root partition--I've manually edited my own initrd (gunzip and cpio) to work with a changed volume group name. By the way, you'd have to boot from a CD or an alternate system to change the volume group name.
how to edit initrd file?
how to edit initrd file?