| View previous topic :: View next topic |
| Author |
Message |
troymc
Guru
Joined: 22 Mar 2006
Posts: 553
|
 Posted: Thu Aug 10, 2006 8:33 pm Post subject: |
 |
|
This shows that is recognizes the hard disk:
| Code: |
Kernel panic - not syncing: VFS: cannot mount root fs on unkown block(8,3)
|
block(8,3) shows that it knows what /dev/sda3 is, so your SATA drive is recognized.
But it doesn't recognize what it sees there, so it cannot mount the filesystem there.
Do you have the drivers for your root filesystem built in? (ext3, reiserfs, etc)
Is sda3 your correct root partition?
troymc |
|
| Back to top |
|
 |
RageOfOrder
Tux's lil' helper
Joined: 06 Aug 2006
Posts: 99
Location: EH?!?!
|
| Posted: Thu Aug 10, 2006 11:23 pm Post subject: |
|
|
I have the drivers for ext2 and ext3 built in.
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
Here is my /etc/fstab:
| Code: |
# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/sda1 /boot ext2 defaults,noatime 1 2
/dev/sda2 none swap sw 0 0
/dev/sda3 / ext3 noatime 0 1
/dev/cdrom /mnt/cdrom auto noauto,user 0 0
#/dev/fd0 /mnt/floppy auto noauto,user 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs nodev,nosuid,noexec 0 0
|
/boot/grub/grub.conf:
| Code: |
#Boot the first entry by default
default 0
#Boot automatically after 15 seconds
timeout 15
#Splash Image
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
######## Windows XP ########
title=Windows XP Professional
rootnoverify (hd1,0)
map (hd0) (hd1)
map (hd1) (hd0)
makeactive
chainloader +1
######## Gentoo ########
title=Gentoo 2.6.17-r4
root (hd0,0)
kernel /boot/kernel15-2.6.17-gentoo-r4 root=/dev/sda3
|
My /usr/src/linux/.config is here.
Maybe those will help.
_________________
...And then stuff happened. |
|
| Back to top |
|
|
RazielFMX
l33t
Joined: 23 Apr 2005
Posts: 835
Location: NY, USA
|
| Posted: Fri Aug 11, 2006 12:03 am Post subject: |
|
|
Try disabling extended attribs... They are marked as experimental.
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
_________________
I am not anti-systemd; I am pro-choice. If being the latter makes you feel that I am the former, then so be it. |
|
| Back to top |
|
|
RageOfOrder
Tux's lil' helper
Joined: 06 Aug 2006
Posts: 99
Location: EH?!?!
|
| Posted: Fri Aug 11, 2006 12:28 am Post subject: |
|
|
Done. Didn't make any difference.
The extended attribs aren't marked as experimental for me either.
_________________
...And then stuff happened. |
|
| Back to top |
|
|
RazielFMX
l33t
Joined: 23 Apr 2005
Posts: 835
Location: NY, USA
|
| Posted: Fri Aug 11, 2006 2:15 am Post subject: |
|
|
In 2.6.16 they were marked as such, I used make oldconfig to migrate to 2.6.17, so I guess they got unmarked, lol. My mistake.
There has to be something else your kernel that is off... I'll think about this for awhile and see if I think of anything. I'm no kernel expert though...
_________________
I am not anti-systemd; I am pro-choice. If being the latter makes you feel that I am the former, then so be it. |
|
| Back to top |
|
|
troymc
Guru
Joined: 22 Mar 2006
Posts: 553
|
| Posted: Fri Aug 11, 2006 3:18 am Post subject: |
|
|
| RageOfOrder wrote: |
I have tried enabling every single sata driver under SATA low-level drivers except sata_promise, and it didn't make a difference.
|
grep'ing the kernel source for the pcid of the PDC20579, show it in sata_promise. Is there a reason you didn't try that one?
troymc |
|
| Back to top |
|
|
RageOfOrder
Tux's lil' helper
Joined: 06 Aug 2006
Posts: 99
Location: EH?!?!
|
| Posted: Fri Aug 11, 2006 4:49 am Post subject: |
|
|
| troymc wrote: | | Is there a reason you didn't try that one? |
I have tried that one. Any time it is enabled I get:
| Code: |
Code: 89 10 f3 c3 66 66 66 90 66 66 90 55 53 48 89 fb 48 83 ec 08
RIP <ffffffff803e3d65>{pdc_sata_scr_write+21} RSP <ffff81003ff83cc0>
CR2: 0000000000000008
<0>Kernel Panic - not syncing : Attempted to kill init
|
_________________
...And then stuff happened. |
|
| Back to top |
|
|
polyglot
n00b
Joined: 10 Mar 2004
Posts: 55
|
| Posted: Fri Aug 11, 2006 5:43 am Post subject: |
|
|
The kernel panic you are getting is because the kernel can't see the block device you've told it should contain your root fs, not necessarily that you have failed to load SATA drivers. When the SATA drivers come up, do they say anything about attached drives?
It is possible that you have perfectly built and loaded your drivers but incorrectly specified root=/dev/blah on the kernel command line.
Since you have the AIC79xx configured in... do you have such a scsi card installed with discs attached? It may well claim the first few sd device names; eg if you have 3 true scsi drives then the SATA drive will likely be sdd not sda.
I know you can't log it, but can you transcribe by hand the output of the kernel when the SATA driver and AIC79xx driver comes up? It should tell you which device names (sda, etc) are binding to which disc on which driver.
It tells us it's trying to boot from (8,3) which is sda3. Are you absolutely sure your rootfs is on the 3rd partition and that the drive is correctly partitioned? |
|
| Back to top |
|
|
RageOfOrder
Tux's lil' helper
Joined: 06 Aug 2006
Posts: 99
Location: EH?!?!
|
| Posted: Fri Aug 11, 2006 6:38 am Post subject: |
|
|
I don't have anything using SCSI except the two hard drives.
Is there a way to pause the screen while booting? Or scroll back up? I can't read, much less write down anything that comes up during the boot process, and when it halts on the kernel panic, there is nothing relevant there. It all scrolls by too fast.
I'm absolutely sure I partitioned /dev/sda, and correctly. It's done exactly as in the handbook.
Grub also has no troubles loading from /dev/sdb, which is my Windows hard drive.
sda1 is /boot
sda2 is my swap
sda3 is my root
ls /dev shows devices sda and sdb. Nothing further.
_________________
...And then stuff happened. |
|
| Back to top |
|
|
RazielFMX
l33t
Joined: 23 Apr 2005
Posts: 835
Location: NY, USA
|
| Posted: Fri Aug 11, 2006 6:43 am Post subject: |
|
|
you might want to disable all non-sata scsi hardware drivers (leave SCSI disk support, but the others are not helping). Not that this will fix it, it will make your kernel smaller.
_________________
I am not anti-systemd; I am pro-choice. If being the latter makes you feel that I am the former, then so be it. |
|
| Back to top |
|
|
RageOfOrder
Tux's lil' helper
Joined: 06 Aug 2006
Posts: 99
Location: EH?!?!
|
| Posted: Sat Aug 12, 2006 12:13 am Post subject: |
|
|
When I compile my kernel, it says at the end, Root device is (8,3).
My grub.conf says
root (hd0,0)
kernel /boot/kernel17-2.6.17-gentoo-r4 root=/dev/sda3
I'm absolutely sure that I mount /dev/sda3 as my root fs every time I load that Live CD.
Still no idea why it won't work...
Is there a way to scroll back up and read the text during boot? or pause it? There is no way I can read anything when it scrolls by that fast, and my system isn't logging it.
Edit:
It doesn't seem to matter what I put under root=/dev/blah
I booted with the parameter root=monkeyfetus and got the exact same kernel panic, which means it's not even getting that far...
_________________
...And then stuff happened. |
|
| Back to top |
|
|
troymc
Guru
Joined: 22 Mar 2006
Posts: 553
|
| Posted: Sat Aug 12, 2006 12:24 am Post subject: |
|
|
(8,3) == sda3
So that all looks good.
You might try <CTRL><S> or the Scroll Lock key to pause and <CTRL><Q> to continue. I don't know how soon they become active.
I'd really like to see the lines before that panic string.
troymc |
|
| Back to top |
|
|
RageOfOrder
Tux's lil' helper
Joined: 06 Aug 2006
Posts: 99
Location: EH?!?!
|
| Posted: Sat Aug 12, 2006 1:05 am Post subject: |
|
|
This happens very quickly into the boot. Under a second after I see text, I see the panic.
ctrl+s, and scroll lock don't seem to do anything.
I have transcribed the entire screen.. this is everything I see when the screen halts.
| Code: |
ffffffff803bf679 ffff81003f4c34f8 ffffffff803c2881 0000000000000000
0000000000000011 0000000000000002
Call Trace: <ffffffff803bee47>{__sata_phy_reset+103}
<ffffffff803bf679>{sata+phy_reset+9} <ffffffff803c2881>{ata_device_add+1025}
<ffffffff80231990>{process_timeout+0} <ffffffff803c71aa>{pdc_ata_init_one+970}
<ffffffff802fc616>{pci_device_probe+102} <ffffffff8035cfeb>{driver_probe_device+107}
<ffffffff8035d168>{__driver_attach+120} <ffffffff8035d0f0>{driver_attach+0}
<ffffffff8035c2c9>{bus_for_each_dev+73} <ffffffff8035c8f8>{bus_add_driver+136}
<ffffffff8035d71e>{driver_register+142} <ffffffff802fc415>{__pci_register_driver+69}
<ffffffff805f8df1>{ata_init+49} <ffffffff80207107>{init+183}
<ffffffff8020a1a2>{child_rip+8} <ffffffff803233e8>{acpi_ds_init_one_object+03}
<ffffffff80207050>{init+0} <ffffffff8020a19a>{child_rip+0}
Code: 89 10 f3 c3 66 66 66 90 66 66 90 55 53 48 89 fb 48 83 ec 08
RIP <ffffffff803c6725>{pdc_sata_scr_write+21} RSP <ffff81003ff83cb0>
CR2: 0000000000000008
<0>Kernel Panic - not syncing : Attempted to kill init
|
Fun.....
_________________
...And then stuff happened. |
|
| Back to top |
|
|
troymc
Guru
Joined: 22 Mar 2006
Posts: 553
|
| Posted: Sat Aug 12, 2006 1:37 am Post subject: |
|
|
| Code: |
ffffffff803bf679 ffff81003f4c34f8 ffffffff803c2881 0000000000000000
0000000000000011 0000000000000002
Call Trace: <ffffffff803bee47>{__sata_phy_reset+103}
<ffffffff803bf679>{sata+phy_reset+9} <ffffffff803c2881>{ata_device_add+1025}
<ffffffff80231990>{process_timeout+0} <ffffffff803c71aa>{pdc_ata_init_one+970}
<ffffffff802fc616>{pci_device_probe+102} <ffffffff8035cfeb>{driver_probe_device+107}
<ffffffff8035d168>{__driver_attach+120} <ffffffff8035d0f0>{driver_attach+0}
<ffffffff8035c2c9>{bus_for_each_dev+73} <ffffffff8035c8f8>{bus_add_driver+136}
<ffffffff8035d71e>{driver_register+142} <ffffffff802fc415>{__pci_register_driver+69}
<ffffffff805f8df1>{ata_init+49} <ffffffff80207107>{init+183}
<ffffffff8020a1a2>{child_rip+8} <ffffffff803233e8>{acpi_ds_init_one_object+03}
<ffffffff80207050>{init+0} <ffffffff8020a19a>{child_rip+0}
Code: 89 10 f3 c3 66 66 66 90 66 66 90 55 53 48 89 fb 48 83 ec 08
RIP <ffffffff803c6725>{pdc_sata_scr_write+21} RSP <ffff81003ff83cb0>
CR2: 0000000000000008
<0>Kernel Panic - not syncing : Attempted to kill init
|
That's kinda interesting. The driver was in its attach function, probing for the device, it timed out, tried to reset the device & BAM - panic.
I'd send that to the driver maintainer. It's probably a bug. Drivers should NOT panic the machine when probing hardware. You may have a broken hardware implementation.
Have you tried a different kernel version?
troymc |
|
| Back to top |
|
|
RageOfOrder
Tux's lil' helper
Joined: 06 Aug 2006
Posts: 99
Location: EH?!?!
|
| Posted: Sat Aug 12, 2006 1:43 am Post subject: |
|
|
Well... I guess I'll be buying an IDE drive instead.. Use the SATA drive for my music backups...
But no, I've never tried a different kernel version. How would I go about this, and do you think it will help?
_________________
...And then stuff happened. |
|
| Back to top |
|
|
troymc
Guru
Joined: 22 Mar 2006
Posts: 553
|
| Posted: Sat Aug 12, 2006 1:52 am Post subject: |
|
|
| RageOfOrder wrote: | Well... I guess I'll be buying an IDE drive instead I guess...
But no, I've never tried a different kernel version. How would I go about this, and do you think it will help? |
Sure! You can boot off of the LiveCD and access your SATA disks, right?
If so, then just copy the kernel from the CD into place & point GRUB at it. That should get your system up.
Then emerge a different kernel version.
I see multiple versions of 2.6.15, 2.6.16 & 2.6.17 in portage. Pick the one you want to try & emerge it specifically.
| Code: |
# pwd
/usr/portage/sys-kernel/gentoo-sources
#
# ls
ChangeLog gentoo-sources-2.6.15-r8.ebuild gentoo-sources-2.6.17-r3.ebuild
Manifest gentoo-sources-2.6.16-r12.ebuild gentoo-sources-2.6.17-r4.ebuild
files gentoo-sources-2.6.16-r13.ebuild gentoo-sources-2.6.17-r5.ebuild
gentoo-sources-2.4.32-r6.ebuild gentoo-sources-2.6.16-r9.ebuild gentoo-sources-2.6.17.ebuild
gentoo-sources-2.4.32-r7.ebuild gentoo-sources-2.6.17-r1.ebuild metadata.xml
gentoo-sources-2.6.15-r1.ebuild gentoo-sources-2.6.17-r2.ebuild
#
# emerge =gentoo-sources-2.6.15-r1
|
troymc |
|
| Back to top |
|
|
RageOfOrder
Tux's lil' helper
Joined: 06 Aug 2006
Posts: 99
Location: EH?!?!
|
| Posted: Sat Aug 12, 2006 2:20 am Post subject: |
|
|
Alright, I'll give that a shot. Thanks for all your help!
_________________
...And then stuff happened. |
|
| Back to top |
|
|
RageOfOrder
Tux's lil' helper
Joined: 06 Aug 2006
Posts: 99
Location: EH?!?!
|
| Posted: Sat Aug 12, 2006 8:59 pm Post subject: |
|
|
Ok, I emerged 2.6.15-r1 and everything seems to work just fine!!
Thanks everyone for your help!
_________________
...And then stuff happened. |
|
| Back to top |
|
|
Greven
Tux's lil' helper
Joined: 28 Jul 2002
Posts: 138
|
| Posted: Thu Sep 07, 2006 9:17 pm Post subject: |
|
|
I'm getting the same problem too! It only showed up with kernel 2.6.17, and I have the MSI "K8T NEO2-FIR" too! My problem is, the SATA drive is my mass storage drive of my DNG files. I have to turn every part of SATA off in the bios to boot up normally.
_________________
veritas vos liberabit...
Linux User Number: 346805
Wine-Wiki
AMD 64 3500+ | MSI "K8T NEO2-FIR" | mushkin Dual Channel DDR 400 |
|
| Back to top |
|
|
|
Installing Gentoo
