login
Search
Hello there,
I have a mandrake 10.1 distro and upgraded my kernel from 2.6.8mdk to 2.6.10. At boot time I get a mount error 6 when the kernel tries to mount the root filesystem, i.e. the kernel boots and after a few microseconds, just after udev is loaded, I get this mount error 6, shortly followed by a kernel panic.
I've been struggling for many hours now to know where this comes from, without any single improvement. I came across several posts that were related to this problem, I tried the suggestions, but nothing changed.
So to be more precise, although grub boots from a sata disc, this disc is actually a WinXP and storage disk, and linux stands on a IDE disk. The root partition is a reiserfs, and yes, reiserfs, ext2 and ext3 are built inside the kernel, not as modules.
I suspect the problem is in the kernel configuration, as the 2.6.8 kernel boots like a charm with the same grub entry and fstab. BTW yes, I did a mkinitrd for the new kernel. And I think I read somewhere udev was the culprit, which makes sense as the error occurs just after its loading; but unfortunately I can't find where I read this anymore...
If it can be of any relevance, you'll find my fstab and grub entry below. Any help or suggestion is more than welcome!
fstab:
/dev/hdb1 / reiserfs notail 1 1
none /mnt/cdrom supermount dev=/dev/hda,fs=auto,ro,--,iocharset=iso8859-15,umask=0 0 0
none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-15,sync,codepage=850 0 0
/dev/hdb6 /mnt/idecommon vfat umask=0,iocharset=iso8859-15,codepage=850 0 0
none /mnt/mpman supermount dev=/dev/mpman,fs=auto,--,rw,umask=0 0 0
none /mnt/pscflash supermount dev=/dev/pscflash,fs=auto,--,rw,umask=0 0 0
/dev/sata5 /mnt/satacommon vfat umask=0,iocharset=iso8859-15,codepage=850 0 0
/dev/sata1 /mnt/winxp ntfs umask=0,nls=iso8859-15 0 0
none /mnt/xdrive/cf supermount dev=/dev/xdrivecf1,fs=auto,--,rw,umask=0 0 0
none /mnt/xdrive/hd supermount dev=/dev/xdrivehd,fs=auto,--,rw,umask=0 0 0
none /proc proc defaults 0 0
/dev/usbdevfs /proc/bus/usb usbdevfs defaults 0 0
/dev/hdb5 swap swap defaults 0 0
menu.lst:
timeout 10
default 0
title Mandrake 10.1 kernel 2.6.8mdk
kernel (hd0,0)/boot/vmlinuz-2.6.8.1-12mdksmp root=/dev/hdb1 vga=791
initrd (hd0,0)/boot/initrd-smp.img
title Mandrake 10.1 kernel 2.6.10
kernel (hd0,0)/boot/vmlinuz-2.6.10 root=/dev/hdb1
initrd (hd0,0)/boot/initrd-2.6.10.img
title Windows XP
root (hd1,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1
same problem
Having the same problem using Yoper distro 2.2.0-6 Pre-Release with kernel 2.6.10-2. I don't have a partition with kernel 2.6.8 to test if that would work, but maybe.
I run a single SATA drive in IDE mode from my Promise FasTrak 378 controller. The SATA drive has a WindowsXP NTFS partition, then a FAT32 partition for transfer between os's, then a reiserfs partition, and finally a linux-swap partition.
Cfdisk output below:
Disk Drive: /dev/sda
Size: 120060444672 bytes, 120.0 GB
Heads: 255 Sectors per Track: 63 Cylinders: 14596
Name Flags Part Type FS Type [Label] Size (MB)
------------------------------------------------------------------------------
sda1 Boot Primary NTFS ] 77103.78
sda2 Primary W95 FAT32 (LBA) 21476.21
sda5 Logical Linux ReiserFS 20423.38
sda6 Logical Linux swap / Solaris 1052.84
The distro boots fine from a cheap IDE PATA drive, and can see & read from the SATA drive (hence the output above). However, when attempting to boot from linux loaded onto the sda5 partition, grub loads OK and will start the boot process, but only gets as far as the "Error 6" you mentioned followed by a kernel panic.
I have no idea why this happens, but I read somewhere that the appropriate modules must be compiled into the kernel - they cannot just be accessed as modules, because they are needed so early in the boot process. I am new to this, so any info would be helpful.
@kanka: did you get this to work? tell me how!
~Fisslefink
Best to compile your sata sup
Best to compile your sata support strait in. Sata module never worked for me, compiled it in and and work like a charm. Of course I hear that Promise controllers tend to be dodgy regardless. I'm not to familer with that controller, but have read a lot of posts on the subject of sata and promise is always giving people grief. I suggest you update to the latest stable, and compile sata support in, it should with any luck fix your problem.
-dw
I got the same problem. This
I got the same problem.
This it the reason of my troubles:
All the time my HDD was "named" hdd but suddenly when i used rescue CD, HDD was named hdb. So i just edited lilo.conf and fstab and appended all hdd with hdb. After that i was able to boot up and everything work like a charm.
Dual Booting with Promise 378 TX2 and GRUB
I've made some significant progress on this topic since my last post. The problem turned out to be two-fold. The first problem is the lack of driver support in the kernel. For the sake of simplicity, let's say you've compiled the appropriate drivers into the kernel. Knoppix 4.0 has already done this, and it installed to my SATA hard drive in IDE mode just fine, and was even able to boot. Ah, but now the tricky part: How to boot from another partition (in my case, /dev/sda5) when the Windows bootloader is on the MBR?
The most elegant solution to that problem is outlined here: http://www.redlog.com/dualboot.html ... It involves using "dd" to copy the 512 bytes of code from the MBR of the properly installed bootloader, stick it in a DOS readable file, and then execute that file from the windows boot menu. It's clean, simple, and it works.
So here is the chronology:
1) From the Knoppix 4.0 live CD/DVD, use Qtparted to shrink your WinXP partition (if needed) to make room for linux (ext3 or reiserfs) and Swap partitions on the end of the drive.
2) In a knoppix console, type "su" to become root. Connect to the internet and type:
knoppix-installer-latest-web
3) Follow the prompts to perform a knoppix HD install to /dev/sda5.
4) When prompted to install the GRUB boot loader, be sure to install it to the PARTITION and NOT TO THE MBR. If you fuck this up and overwrite the MBR on /dev/sda, you will overwrite the Windows boot loader. [NOTE: To get it back, you'll have to boot from the WInXP CD, load your SATA drivers, go to the Recovery Console, and then use "fixboot c:" and "fix mbr c:".] But don't do it!
5) Once installation has succeeded, reboot into the Knoppix 4.0 live CD or DVD.
6) Put in a DOS formatted floppy disk or USB key.
7) From a console as root, type:
dd if=/dev/sda5 of=/YOURFLOPPYORUSBKEY/boot.lnx
8) Boot into windows and copy "boot.lnx" to C: Then, follow the instructions at http://www.redlog.com/dualboot.html to edit boot.ini to recognize the new file on boot.
9) Reboot, and select the new Knoppix entry on the boot menu. The GRUB boot loader should pop up, allowing you to start Knoppix.
Please confirm if this works for you!
Good luck,
Fisslefink
Fisslefink [at] yahoo dot com
CORRECTION
Oops -- in the above post, I forgot an important step.
Depending on your BIOS, it may have used different drive mappings when you booted from the install CD, vs. from when you boot from the Windows drive. If this is the case, you may have to modify the device mappings and menu.lst for the GRUB bootloader before copying to a DOS file. See my post here for information on how to do this:
http://www.linuxquestions.org/questions/showthread.php?s=&postid=1799853...
Good luck,
Fisslefink [at] yahoo.com