mikemck Posted June 30, 2006 Report Share Posted June 30, 2006 (edited) Hardware: Asus P4S800D-X, WD1600JS HD, 2.4GHz P4 Occurs when installed from PowerPac PRo or DVD. Insstall procedds fine until reboot, where it hangs after the graphical lilo menu. When doing a failsafe boot selection there is a kernel Panic: Part of diplayed messages: Mounting tempfs on /dev Creating root device Mounting root file system on /dev/root Mount error 6 mounting ext3: flags default Mount error 6 mounting ext3: without option flags Mount error 6 mounting ext3: without any flag Initrd finisshed Free unused kernel memory: 296K freed Kernel Panic - not syncing: No init found ..... When trying to mount the partitions from my 2006.0 running from a pata drive it tells me that the drive is not ext2. Also, did a quick install of Fedora 5.0 on to the WD1600JS which works just fine. Bu t I didnt look aaat the fs tab or other details. This is a solo drive and not a raid install, but do I need something like fake raid or dmraid to make this work??? Edited June 30, 2006 by mikemck Quote Link to comment Share on other sites More sharing options...
Guest arun babu Posted June 30, 2006 Report Share Posted June 30, 2006 Hardware: Asus P4S800D-X, WD1600JS HD, 2.4GHz P4 Occurs when installed from PowerPac PRo or DVD. Insstall procedds fine until reboot, where it hangs after the graphical lilo menu. When doing a failsafe boot selection there is a kernel Panic: Part of diplayed messages: Is your partition hidden ? If you have more than one primary partitions only one can be active at a time. Quote Link to comment Share on other sites More sharing options...
mikemck Posted June 30, 2006 Author Report Share Posted June 30, 2006 THanks for quick reply but I sent post befre I finished, new here. and the partitions consist of sda1 - /, swap, and sda6 - home Quote Link to comment Share on other sites More sharing options...
AussieJohn Posted July 1, 2006 Report Share Posted July 1, 2006 I'd like to extend a warm welcome to you both, Arun and Mike. No doubt some more experienced hands will come to your aid soon but it is extremely nice to se a newly joined member already offering some help . It could be you do not have the video driver appropiate for your video card. Good stuff. Cheers. John. Quote Link to comment Share on other sites More sharing options...
mikemck Posted July 1, 2006 Author Report Share Posted July 1, 2006 UPDATE: Not sure waht is happening, but, I can now mount the partitions sda1 and sda6 with my working 2006.0 and see the files therein. Is this a case of the sata_sis module not loading soon enough - or be compiled into the kernel (ver 2.6.12smp - default with install)? Now that I can mount the partitions on the sata drive - might be worth taking a look and see what modules is being loaded when. Mike Quote Link to comment Share on other sites More sharing options...
arctic Posted July 1, 2006 Report Share Posted July 1, 2006 I just did a quick research on the problem and there are three possibilities that can cause this: 1. Most probable: The ext3.o module is not directly compiled into the kernel but loaded as a separate module that somehow fails to get loaded at times. Only fix: Use a patched kernel. (can also be caused by point 4 (see below)) 2. You have an easyboot option in your bios that does not work well together with the harddrives partition structure and thus confuses the BIOS. Solution: Disable it or take the hdd out and plug it back in and let the bios detect the drive again. 3. The initrd file is bad and needs some manual fixing. 4. Your installation media was bad and caused a read/write error during the install, borking your system. Fix: download new images, check with md5sum and burn with high quality media at low speed. Quote Link to comment Share on other sites More sharing options...
scarecrow Posted July 1, 2006 Report Share Posted July 1, 2006 You can even try when lilo appears pressing escape and then typing in linux acpi=off just to exclude acpi related conflicts with your IDE controller. Quote Link to comment Share on other sites More sharing options...
mikemck Posted July 3, 2006 Author Report Share Posted July 3, 2006 Aussie John - Thanks for the welcome! First, to scarecrow varios combos of no acpi and no apic have no effect, And artic, I believe the install media is good, as I recall I did check them when burned, and have done several installs without problems with both sets. The term easyboot does not ring a bell at the moment unless you're talking about the short form of post. At the moment I cannot run mkinitrd - it just displays the help screen (usage) . I did a chroot to the mounted / partition (sda1) and as root. I probabily try my rusty skill at recommpiling the kernel. I see that that there are several bugs reported on qa.mandriva.com -- most have no real resolution -- some people have succeeded by listing the saata driver in the modules.preload file, some have not --most have been closed from inactivity. It appears that the drive is not seen at all after the install. And Fedor sets the drive up as a logical volume (jbod I suspect) it appears. Will have to study up on that. Maybe I will need a second drive and setup a formal raid drive. The sata controller is part of the sis 964 south bridge Quote Link to comment Share on other sites More sharing options...
AussieJohn Posted July 6, 2006 Report Share Posted July 6, 2006 If you are using a newish Mainboard with SATA on board and not from an add-in card, then your bios will have a couple of specific settings for sata and I don't just mean the ability to set up raid arrays. You need to look in the bios and make sure that SATA is activated and that you select to boot from a sata hdd other wise you are just flaying around especially if you also have IDE HDDs installed. Since you are not intending to use raid I suspect that you have not checked your bios settings------a big mistake but easily overlooked. I am using 2 of WD 120Gb SATA-2 HDDS on an ASUS A7V600-X (I have no ide HDDS only ide optical devices) and one of the things I learnt was DO NOT setup raid first if planning raid-1 and then doing the Mandriva install. If you do then Mandriva gives the partitions some weird alphabetical numbering e.g. /ahfmyjt instead of numerals and that is OK if you stay on raid-1 but if for some reason you decide to discontinue to use the raid-1 mode to use the primary sata on its own and put something else on the other sata drive then it will not boot up no matter what you try, you end up having to reinstall the OS entirely. However if you do the OS install on the primary sata first and then create raid-1 then the primary sata is mirrored to the secondary sata. You can break the raid-1 later and even later again remake it with no difficulty because in the instance of the first install the partitions are numbered in the usual manner e.g., sda0, sda1, sdb1 and so on. Cheers. John Quote Link to comment Share on other sites More sharing options...
mikemck Posted July 9, 2006 Author Report Share Posted July 9, 2006 Sorry AussieJohn, I thought I had given that info, shich is: chipset sata controller: on The sata drive is the only hard drive installed in the system. The mootherboard came out in 2004 with a SIS chipset consisting of a SIS655FX north bridge and a SIS964 south bridge (about the same as the SIS180 sata controller). Wish I unerstood just what is going on a little better, because, SUSE 10.1 and Fedora 5 final have no problems with their default install. (SUSE as normal basic filesystems and Fedora as a virtual filesystem - as in windows big boy os/s) I quick look shows no great difference in what they do in places like modules.preload or elsewhere. Thanks, Mike Quote Link to comment Share on other sites More sharing options...
AussieJohn Posted July 9, 2006 Report Share Posted July 9, 2006 Did you double check your bios settings, especially now we know that your sata is onboard and not a seperate card ???. Cheers. John. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.