[SOLVED] Kernel panic - not syncing

[IrishGuy]

OK, here's what comes up when I boot the system. Apologies for the poor quality, mobile phone camera image.



Here's the menu.lst

Code: [Select]

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,0)/boot/gfxmenu
default 0

title linux
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=d361e038-dbb4-48db-9e65-09342edf7c36 resume=UUID=cc59aaf8-e77b-4f24-95ea-4e7ee4a9e380 splash=silent vga=788
initrd (hd0,0)/boot/initrd.img

title linux-nonfb
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=d361e038-dbb4-48db-9e65-09342edf7c36 resume=UUID=cc59aaf8-e77b-4f24-95ea-4e7ee4a9e380
initrd (hd0,0)/boot/initrd.img

title failsafe
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=d361e038-dbb4-48db-9e65-09342edf7c36 failsafe
initrd (hd0,0)/boot/initrd.img

title 2.6.32.11-pclos2.bfs
kernel (hd0,0)/boot/vmlinuz-2.6.32.11-pclos2.bfs BOOT_IMAGE=2.6.32.11-pclos2.bfs root=UUID=d361e038-dbb4-48db-9e65-09342edf7c36 resume=UUID=cc59aaf8-e77b-4f24-95ea-4e7ee4a9e380 splash=silent vga=788
initrd (hd0,0)/boot/initrd-2.6.32.11-pclos2.bfs.img

title 2.6.32.24-pclos1.a64
kernel (hd0,0)/boot/vmlinuz-2.6.32.24-pclos1.a64 BOOT_IMAGE=2.6.32.24-pclos1.a64 root=UUID=d361e038-dbb4-48db-9e65-09342edf7c36 resume=UUID=cc59aaf8-e77b-4f24-95ea-4e7ee4a9e380 splash=silent vga=788
initrd (hd0,0)/boot/initrd-2.6.32.24-pclos1.a64.img

title 2.6.33.7-pclos6.a64
kernel (hd0,0)/boot/vmlinuz-2.6.33.7-pclos6.a64 BOOT_IMAGE=2.6.33.7-pclos6.a64 root=UUID=d361e038-dbb4-48db-9e65-09342edf7c36 resume=UUID=cc59aaf8-e77b-4f24-95ea-4e7ee4a9e380 splash=silent vga=788
initrd (hd0,0)/boot/initrd-2.6.33.7-pclos6.a64.img
The hard drive is SATA running in IDE mode. The BIOS gives the options of either RAID or AHCI. Since I don't have A RAID setup, I left it as IDE.

[melodie]

Hi,

What proc is on this mobo ? Please give the output from a user console:

Code: [Select]

cat /proc/cpuinfo
Is the kernel 2.6.33.7-pclos6.a64 the latest that you have installed, while in chroot ?

Can you also show us where the kernel symlink points to ? This is by doing a "ls -l" in the /boot directory of the installed PCLinuxOS. => I would like you to copy the whole output, so that we can see if all the kernels listed in your menu.lst are installed --

And also the list of kernel module directories in /lib/modules:

Code: [Select]

ls -lR /lib/modules
And just in case : what version PCLinuxOS have you installed ? (flavor, and number version)

How I see things : the bootloader is looking for the kernel modules, and seeks for them in a directory where they have already been removed from -- which would indicate that it's not looking for the right kernel. This is why I am asking you that.

Based on your next answers, it could be possible to write a menu.lst that will allow your system to boot. (Hopefully)

[IrishGuy]

Here you go:

Code: [Select]

[root@localhost guest]# cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 107
model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 5600+
stepping        : 2
cpu MHz         : 1000.000
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch
bogomips        : 2009.43
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps

processor       : 1
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 107
model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 5600+
stepping        : 2
cpu MHz         : 1000.000
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
apicid          : 1
initial apicid  : 1
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch
bogomips        : 2009.43
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps

Yes, that is the latest kernel I installed from chroot

[IrishGuy]

the lib/modules is too long to post in one piece. I can break it up if you want

[melodie]

the lib/modules is too long to post in one piece. I can break it up if you want

It's not necessary. You are going to look in /lib/modules and check which directories are there for which version kernels, then you will dive inside them one by one and check in which one you have the /lib/modules/kernel-xxx-yyy/kernel filled with directories and subdirectories.

I give you an example:

$ pwd
/lib/modules/2.6.33.7-pclos5.bfs/kernel/drivers // this is the directory where I am from within the console
$ ls
acpi/        clocksource/  firmware/  infiniband/  message/  platform/  telephony/
ata/         connector/    gpio/      input/       misc/     power/     uio/
atm/         cpufreq/      gpu/       isdn/        mmc/      pps/       usb/
auxdisplay/  crypto/       hid/       leds/        mtd/      rtc/       uwb/
block/       dca/          hwmon/     lguest/      net/      scsi/      video/
bluetooth/   dma/          i2c/       md/          parport/  serial/    virtio/
cdrom/       edac/         ide/       media/       pci/      ssb/       w1/
char/        firewire/     ieee1394/  memstick/    pcmcia/   staging/   watchdog/
$

it's full.

I wonder if the modules are not put at their right place only once you have rebooted. Strange, I remember I have done that kind of thing before ? Or not ? 

Maybe it was not with a kernel, and on a new motherboard...

For a "ls -l" in the /boot directory, is that possible too ? I can prepare the menu.lst in the meanwhile. Do you see the entries for all kernels at Grub start or not all of them ?

[melodie]

Based on what I see on your /etc/fstab I have supposed that the / directory is /dev/sda1 : is that right ? It's not /dev/sda6 that is probably the partition where /home is ?

Based on this supposition, here is a menu.lst:

Code: [Select]

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,0)/boot/gfxmenu
default 0

title linux
root (hd0,0)
kernel /boot/vmlinuz BOOT_IMAGE=linux root=/dev/sda1 resume=/dev/sda5 splash=noquiet vga=788
initrd /boot/initrd.img

title linux-nonfb
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=/dev/sda1 resume=/dev/sda5
initrd (hd0,0)/boot/initrd.img

title failsafe
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=/dev/sda1 failsafe
initrd (hd0,0)/boot/initrd.img

title 2.6.32.11-pclos2.bfs
kernel (hd0,0)/boot/vmlinuz-2.6.32.11-pclos2.bfs BOOT_IMAGE=2.6.32.11-pclos2.bfs root=/dev/sda1 resume=/dev/sda5 splash=silent vga=788
initrd (hd0,0)/boot/initrd-2.6.32.11-pclos2.bfs.img

title 2.6.32.24-pclos1.a64
kernel (hd0,0)/boot/vmlinuz-2.6.32.24-pclos1.a64 BOOT_IMAGE=2.6.32.24-pclos1.a64 root=/dev/sda1 resume=/dev/sda5 splash=silent vga=788
initrd (hd0,0)/boot/initrd-2.6.32.24-pclos1.a64.img

title 2.6.33.7-pclos6.a64
kernel (hd0,0)/boot/vmlinuz-2.6.33.7-pclos6.a64 BOOT_IMAGE=2.6.33.7-pclos6.a64 root=/dev/sda1 resume=/dev/sda5 splash=silent vga=788
initrd (hd0,0)/boot/initrd-2.6.33.7-pclos6.a64.img
For the kernels I didn't change anything, because I need the content of /boot directory and mini to know in what kernel dir you have the kernel modules.

What is changed is "root=/dev/sda1" instead of uuid, same for resume.

If this still does not work, try to change "sda1" for "hda1". If this still doesn't work check the kernels (as said just above).

If nothing works I don't have solution left for you apart from reinstall.

[IrishGuy]

Yes, / should be in sda1.

I'll copy this into me menu.lst and give it a shot. I'll let you know how it goes.

Either way I really appreciate all your help, for someone whose not particularly code-literate, it's been a roller-coaster ride!

[Old-Polack]

The hard drive is SATA running in IDE mode. The BIOS gives the options of either RAID or AHCI. Since I don't have A RAID setup, I left it as IDE.

Choose AHCI, and if it insists on a RAID setting, set the type of RAID to JBOD. (Just a Bunch Of Drives)

That IDE emulation thing was a workaround for Windows XP, because it couldn't recognize SATA drives, in their native form. Linux thrives on AHCI and native SATA controllers.

[melodie]

Yes, / should be in sda1.

I'll copy this into me menu.lst and give it a shot. I'll let you know how it goes.

Either way I really appreciate all your help, for someone whose not particularly code-literate, it's been a roller-coaster ride!

I learn new slang/ or idiomatic everyday here : what does "roller-coaster" mean please ? ^^

The hard drive is SATA running in IDE mode. The BIOS gives the options of either RAID or AHCI. Since I don't have A RAID setup, I left it as IDE.

Choose AHCI, and if it insists on a RAID setting, set the type of RAID to JBOD. (Just a Bunch Of Drives)

That IDE emulation thing was a workaround for Windows XP, because it couldn't recognize SATA drives, in their native form. Linux thrives on AHCI and native SATA controllers.

Good tech info ! I like when I read from O-P !

Hi Old-Polack, how are you ? o/

[IrishGuy]

OK, I'll give that a shot now and see what I get.

I learn new slang/ or idiomatic everyday here : what does "roller-coaster" mean please ? ^^

I believe it's called a montagnes russes in French, like at Disneyland! Pardon me if that is not correct, I did German in school ^-^

[melodie]

OK, I'll give that a shot now and see what I get.

I learn new slang/ or idiomatic everyday here : what does "roller-coaster" mean please ? ^^

I believe it's called a montagnes russes in French, like at Disneyland! Pardon me if that is not correct, I did German in school ^-^

Ok !
No problem. I took English and Spanish at school.

Now that Old Polack has given you the main info missing, with the rest and maybe not much more (what about theses kernels and modules ?) you should end with a reboot.

I may read about it tomorrow, time for sleep here.

[IrishGuy]

I'm afraid I got the same problems as before. It definitely must be a hardware issue with the new motherboard. if we've reloaded the packages and re-written the GRUB and MBR and it still cannot load the OS from the drive, then there is something else going on that we can't see.

A fresh install is probably the safest bet at this stage. I will need the computer by tomorrow morning and we've already spent a fair amount of time on it.

I appreciate all the help, it's great when I can ask people about stuff like this and get so many ideas

[melodie]

I'm afraid I got the same problems as before. It definitely must be a hardware issue with the new motherboard. if we've reloaded the packages and re-written the GRUB and MBR and it still cannot load the OS from the drive, then there is something else going on that we can't see.

A fresh install is probably the safest bet at this stage. I will need the computer by tomorrow morning and we've already spent a fair amount of time on it.

I appreciate all the help, it's great when I can ask people about stuff like this and get so many ideas

Sorry to contradict, but you have not said in this post what you have done : have you setup the bios fine ? And you seem not to understand the relation between the messages at boot and the content of /lib/modules : all is there. This is why I asked you the list which is in /boot/, and in /lib/modules  : even a "ls -l" in /lib/modules and a list similar to the one I have shown you just before : in the kernel-xyversion-number directory that is under /lib/modules, you have a directory kernel, in there must be modules. If they are not found at boot it is probably because it is in another directory : need to get it's name in order to point Grub to the right direction, it it's config file : the menu.lst.

I will be looking forward to your answers (tomorrow).

Regards,
Mélodie

[IrishGuy]

Yes, I set the BIOS to AHCI, it discovers the drive during boot.

The kernels are in /boot, below is the ls -l output:

Code: [Select]

[root@localhost boot]# ls -l
total 39352
-rw-rw-r-- 1 root root     440 2010-04-24 18:42 boot.backup.sda
lrwxrwxrwx 1 root root      27 2010-11-05 15:46 config -> config-2.6.32.24-pclos1.a64
-rw-r--r-- 1 root root  109905 2010-04-07 13:38 config-2.6.32.11-pclos2.bfs
-rw-r--r-- 1 root root  110010 2010-10-03 13:24 config-2.6.32.24-pclos1.a64
-rw-r--r-- 1 root root  112713 2010-10-22 01:03 config-2.6.33.7-pclos6.a64
-rwxr-xr-x 1 root root  502784 2010-04-24 18:42 gfxmenu*
drwxr-xr-x 2 root root    4096 2010-11-08 07:27 grub/
-rw------- 1 root root 6919694 2010-06-17 17:59 initrd-2.6.32.11-pclos2.bfs.img
-rw------- 1 root root 6887776 2010-10-06 06:27 initrd-2.6.32.24-pclos1.a64.img
-rw------- 1 root root 6474681 2010-11-07 23:11 initrd-2.6.33.7-pclos6.a64.img
lrwxrwxrwx 1 root root      30 2010-11-07 23:11 initrd.img -> initrd-2.6.33.7-pclos6.a64.img
-rw------- 1 root root 8373270 2010-06-17 17:58 initrd.img.old
lrwxrwxrwx 1 root root      35 2010-11-05 15:46 kernel.h -> /boot/kernel.h-2.6.32.24-pclos1.a64                                                                 
-rw-r--r-- 1 root root    1493 2010-10-06 05:25 kernel.h-2.6.32.11-pclos2.bfs
-rw-r--r-- 1 root root    1493 2010-11-05 15:46 kernel.h-2.6.32.24-pclos1.a64
-rw-r--r-- 1 root root  254766 2006-11-05 23:23 message-graphic
lrwxrwxrwx 1 root root      31 2010-10-06 06:29 System.map -> System.map-2.6.32.24-pclos1.a64
-rw-r--r-- 1 root root 1454342 2010-04-07 13:38 System.map-2.6.32.11-pclos2.bfs
-rw-r--r-- 1 root root 1454288 2010-10-03 13:24 System.map-2.6.32.24-pclos1.a64
-rw-r--r-- 1 root root 1407376 2010-10-22 01:03 System.map-2.6.33.7-pclos6.a64
-rw-rw-r-- 1 root root     256 2010-04-24 18:42 us.klt
lrwxrwxrwx 1 root root      27 2010-11-07 23:11 vmlinuz -> vmlinuz-2.6.33.7-pclos6.a64
-rw-r--r-- 1 root root 2056848 2010-04-07 13:38 vmlinuz-2.6.32.11-pclos2.bfs
-rw-r--r-- 1 root root 2060432 2010-10-03 13:24 vmlinuz-2.6.32.24-pclos1.a64
-rw-r--r-- 1 root root 2062144 2010-10-22 01:03 vmlinuz-2.6.33.7-pclos6.a64


Here is the output for the ls in /lib/modules:

Code: [Select]

[root@localhost boot]# cd /media/disk/lib/modules
[root@localhost modules]# ls -l
total 12
drwxr-xr-x 3 root root 4096 2010-11-07 23:05 2.6.32.11-pclos2.bfs/
drwxr-xr-x 3 root root 4096 2010-10-18 17:16 2.6.32.24-pclos1.a64/
drwxr-xr-x 3 root root 4096 2010-11-07 23:11 2.6.33.7-pclos6.a64/

Here's the ls -l from the three kernel directories in lib/modules

Code: [Select]

[root@localhost 2.6.32.11-pclos2.bfs]# ls -l
total 3772
lrwxrwxrwx  1 root root     42 2010-04-24 18:41 build -> /usr/src/kernel-devel-2.6.32.11-pclos2.bfs/                                                           
drwxr-xr-x 11 root root   4096 2010-04-15 11:58 kernel/
-rw-r--r--  1 root root 569642 2010-11-07 23:05 modules.alias
-rw-r--r--  1 root root 496387 2010-11-07 23:05 modules.alias.bin
-rw-r--r--  1 root root     69 2010-11-07 23:05 modules.ccwmap
-rw-r--r--  1 root root 302809 2010-11-07 23:05 modules.dep
-rw-r--r--  1 root root 445332 2010-11-07 23:05 modules.dep.bin
-rw-r--r--  1 root root  98449 2010-04-07 13:40 modules.description
-rw-r--r--  1 root root   1405 2010-11-07 23:05 modules.ieee1394map
-rw-r--r--  1 root root    218 2010-11-07 23:05 modules.inputmap
-rw-r--r--  1 root root  24193 2010-11-07 23:05 modules.isapnpmap
-rw-r--r--  1 root root     74 2010-11-07 23:05 modules.ofmap
-rw-r--r--  1 root root  93284 2010-04-07 13:38 modules.order
-rw-r--r--  1 root root 377476 2010-11-07 23:05 modules.pcimap
-rw-r--r--  1 root root   1513 2010-11-07 23:05 modules.seriomap
-rw-r--r--  1 root root 244715 2010-11-07 23:05 modules.symbols
-rw-r--r--  1 root root 320994 2010-11-07 23:05 modules.symbols.bin
-rw-r--r--  1 root root 840753 2010-11-07 23:05 modules.usbmap
lrwxrwxrwx  1 root root     42 2010-04-24 18:41 source -> /usr/src/kernel-devel-2.6.32.11-pclos2.bfs/     

Code: [Select]

[root@localhost 2.6.32.24-pclos1.a64]# ls -l
total 3892
lrwxrwxrwx  1 root root     42 2010-10-06 06:28 build -> /usr/src/kernel-devel-2.6.32.24-pclos1.a64                                                             
drwxr-xr-x 11 root root   4096 2010-10-06 06:27 kernel/
-rw-rw-r--  1 root root 590577 2010-10-18 17:16 modules.alias
-rw-rw-r--  1 root root 512666 2010-10-18 17:16 modules.alias.bin
-rw-rw-r--  1 root root     69 2010-10-18 17:16 modules.ccwmap
-rw-rw-r--  1 root root 303030 2010-10-18 17:16 modules.dep
-rw-rw-r--  1 root root 446286 2010-10-18 17:16 modules.dep.bin
-rw-r--r--  1 root root  98560 2010-10-03 13:25 modules.description
-rw-rw-r--  1 root root   1405 2010-10-18 17:16 modules.ieee1394map
-rw-rw-r--  1 root root    218 2010-10-18 17:16 modules.inputmap
-rw-rw-r--  1 root root  24732 2010-10-18 17:16 modules.isapnpmap
-rw-rw-r--  1 root root     74 2010-10-18 17:16 modules.ofmap
-rw-r--r--  1 root root  93431 2010-10-03 13:24 modules.order
-rw-rw-r--  1 root root 383391 2010-10-18 17:16 modules.pcimap
-rw-rw-r--  1 root root   1513 2010-10-18 17:16 modules.seriomap
-rw-rw-r--  1 root root 253394 2010-10-18 17:16 modules.symbols
-rw-rw-r--  1 root root 336742 2010-10-18 17:16 modules.symbols.bin
-rw-rw-r--  1 root root 896501 2010-10-18 17:16 modules.usbmap
lrwxrwxrwx  1 root root     42 2010-10-06 06:28 source -> /usr/src/kernel-devel-2.6.32.24-pclos1.a64                 

Code: [Select]

[root@localhost 2.6.33.7-pclos6.a64]# ls -l
total 3844
lrwxrwxrwx  1 root root     41 2010-11-07 23:11 build -> /usr/src/kernel-devel-2.6.33.7-pclos6.a64                                                             
drwxr-xr-x 11 root root   4096 2010-11-07 23:11 kernel/
-rw-r--r--  1 root root 578239 2010-10-22 01:04 modules.alias
-rw-r--r--  1 root root 503149 2010-10-22 01:04 modules.alias.bin
-rw-r--r--  1 root root   2769 2010-10-22 01:03 modules.builtin
-rw-r--r--  1 root root     69 2010-10-22 01:04 modules.ccwmap
-rw-r--r--  1 root root 309270 2010-10-22 01:04 modules.dep
-rw-r--r--  1 root root 453014 2010-10-22 01:04 modules.dep.bin
-rw-r--r--  1 root root 100782 2010-10-22 01:04 modules.description
-rw-r--r--  1 root root   1405 2010-10-22 01:04 modules.ieee1394map
-rw-r--r--  1 root root    218 2010-10-22 01:04 modules.inputmap
-rw-r--r--  1 root root  24853 2010-10-22 01:04 modules.isapnpmap
-rw-r--r--  1 root root     74 2010-10-22 01:04 modules.ofmap
-rw-r--r--  1 root root  94768 2010-10-22 01:03 modules.order
-rw-r--r--  1 root root 370287 2010-10-22 01:04 modules.pcimap
-rw-r--r--  1 root root   1513 2010-10-22 01:04 modules.seriomap
-rw-r--r--  1 root root 250841 2010-10-22 01:04 modules.symbols
-rw-r--r--  1 root root 329362 2010-10-22 01:04 modules.symbols.bin
-rw-r--r--  1 root root 868265 2010-10-22 01:04 modules.usbmap
lrwxrwxrwx  1 root root     41 2010-11-07 23:11 source -> /usr/src/kernel-devel-2.6.33.7-pclos6.a64   
The listing in /kernel/drivers is the same as yours:

Code: [Select]

[root@localhost drivers]# ls -l
total 228
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 acpi/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 ata/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 atm/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 auxdisplay/
drwxr-xr-x  4 root root 4096 2010-04-15 11:58 block/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 bluetooth/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 cdrom/
drwxr-xr-x  9 root root 4096 2010-04-15 12:01 char/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 clocksource/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 connector/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 cpufreq/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 crypto/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 dca/
drwxr-xr-x  3 root root 4096 2010-04-15 11:58 dma/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 edac/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 firewire/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 firmware/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 gpio/
drwxr-xr-x  3 root root 4096 2010-04-15 11:58 gpu/
drwxr-xr-x  3 root root 4096 2010-04-15 11:58 hid/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 hwmon/
drwxr-xr-x  5 root root 4096 2010-04-15 11:58 i2c/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 ide/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 ieee1394/
drwxr-xr-x  5 root root 4096 2010-04-15 11:58 infiniband/
drwxr-xr-x 11 root root 4096 2010-04-15 11:58 input/
drwxr-xr-x 14 root root 4096 2010-04-15 11:58 isdn/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 leds/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 lguest/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 md/
drwxr-xr-x  6 root root 4096 2010-04-15 11:58 media/
drwxr-xr-x  4 root root 4096 2010-04-15 11:58 memstick/
drwxr-xr-x  4 root root 4096 2010-04-15 11:58 message/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 mfd/
drwxr-xr-x  6 root root 4096 2010-04-15 11:58 misc/
drwxr-xr-x  5 root root 4096 2010-04-15 11:58 mmc/
drwxr-xr-x 10 root root 4096 2010-04-15 11:58 mtd/
drwxr-xr-x 37 root root 4096 2010-04-15 11:58 net/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 parport/
drwxr-xr-x  3 root root 4096 2010-04-15 11:58 pci/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 pcmcia/
drwxr-xr-x  3 root root 4096 2010-04-15 11:58 platform/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 power/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 pps/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 rtc/
drwxr-xr-x 24 root root 4096 2010-04-15 11:58 scsi/
drwxr-xr-x  3 root root 4096 2010-04-15 11:58 serial/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 ssb/
drwxr-xr-x 39 root root 4096 2010-04-15 11:58 staging/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 telephony/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 uio/
drwxr-xr-x 12 root root 4096 2010-04-15 11:58 usb/
drwxr-xr-x  4 root root 4096 2010-04-15 11:58 uwb/
drwxr-xr-x 18 root root 4096 2010-04-15 11:58 video/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 virtio/
drwxr-xr-x  4 root root 4096 2010-04-15 11:58 w1/
drwxr-xr-x  2 root root 4096 2010-04-15 11:58 watchdog/
It would seem that everything is indeed where it ought to be, it's just that the computer can't seem to mount/locate sda1 in order to access the files. I've tried loading all the kernels and each one gives either the error message shown here http://s3.amazonaws.com/twitpic/photos/large/189598701.jpg?AWSAccessKeyId=0ZRYP5X5F6FSMBCCSE82&Expires=1289178048&Signature=K2hhqS9qfTRmOj5ZV5SVGoLd%2BZE%3D, or that it's looking for sda1 with a 1 minute timeout.

[Old-Polack]

IrishGuy:

Post the contents of your /etc/fstab.

[root@localhost ~]# cat /etc/fstab                     <Enter>