problem compiling kernel on DELL PowerEdge

willigi · 06-18-2006, 09:15 AM

hi you all,

i got a big problem setting up a Dell PowerEdge Server.

I compiled a new Kernel for this machine and i thought i have choosen all the needed Modules. But if i want to boot the new kernel there appears the following error message

Code:

Kernelpanic: VFS: Unable to mount root fs on unknown-block(8,1)

I tried both to compile ext3, scsi, raid-adapter support into the kernel and to compile it as module. do anyone know a solution?

here is my dmesg output (its not the whole):

Code:

VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
Initializing Cryptographic API
PCI: Via IRQ fixup for 0000:02:06.0, from 5 to 1
PCI: Via IRQ fixup for 0000:02:06.1, from 3 to 9
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
NET: Registered protocol family 8
NET: Registered protocol family 20
ACPI: (supports S0 S4 S5)
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 5120 blocks [1 disk] into ram disk... |/-\
VFS: Mounted root (cramfs filesystem) readonly.
Freeing unused kernel memory: 168k freed
vesafb: probe of vesafb0 failed with error -6
NET: Registered protocol family 1
SCSI subsystem initialized
Loading Adaptec I2O RAID: Version 2.4 Build 5go
Detecting Adaptec I2O RAID controllers...
ACPI: PCI interrupt 0000:00:06.1[A] -> GSI 28 (level, low) -> IRQ 185
Adaptec I2O RAID controller 0 at e8880000 size=100000 irq=185
dpti: If you have a lot of devices this could take a few minutes.
dpti0: Reading the hardware resource table.
TID 008  Vendor: ADAPTEC      Device: AIC-7899     Rev: 00000001    
TID 519  Vendor: ADAPTEC      Device: FIRST        Rev: 320R        
scsi0 : Vendor: Adaptec  Model: 2100S            FW:320R
Using anticipatory io scheduler
  Vendor: ADAPTEC   Model: FIRST             Rev: 320R
  Type:   Direct-Access                      ANSI SCSI revision: 02
ACPI: Processor [CPU0] (supports C1)
ACPI: Processor [CPU1] (supports C1)
usbcore: registered new driver usbfs
usbcore: registered new driver hub
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
ACPI: PCI interrupt 0000:00:0f.2[A] -> GSI 11 (level, low) -> IRQ 11
ohci_hcd 0000:00:0f.2: ServerWorks OSB4/CSB5 OHCI USB Controller
ohci_hcd 0000:00:0f.2: irq 11, pci mem e881e000
ohci_hcd 0000:00:0f.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
USB Universal Host Controller Interface driver v2.2
ACPI: PCI interrupt 0000:02:06.0[A] -> GSI 20 (level, low) -> IRQ 193
uhci_hcd 0000:02:06.0: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
uhci_hcd 0000:02:06.0: irq 193, io base 0000dce0
uhci_hcd 0000:02:06.0: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:02:06.1[B] -> GSI 19 (level, low) -> IRQ 201
uhci_hcd 0000:02:06.1: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2)
uhci_hcd 0000:02:06.1: irq 201, io base 0000dcc0
uhci_hcd 0000:02:06.1: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI interrupt 0000:02:06.2[C] -> GSI 18 (level, low) -> IRQ 209
ehci_hcd 0000:02:06.2: VIA Technologies, Inc. USB 2.0
ehci_hcd 0000:02:06.2: irq 209, pci mem e884c800
ehci_hcd 0000:02:06.2: new USB bus registered, assigned bus number 4
ehci_hcd 0000:02:06.2: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 4 ports detected
usbcore: registered new driver usbkbd
drivers/usb/input/usbkbd.c: :USB HID Boot Protocol keyboard driver
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
usbcore: registered new driver usbserial_generic
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
vga16fb: initializing
vga16fb: mapped to 0xc00a0000
fb0: VGA16 VGA frame buffer device
Console: switching to colour frame buffer device 80x30
ieee1394: Initialized config rom entry `ip1394'
ohci1394: $Rev: 1223 $ Ben Collins <bcollins@debian.org>
ACPI: PCI interrupt 0000:02:06.3[A] -> GSI 20 (level, low) -> IRQ 193
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[193]  MMIO=[f5010000-f50107ff]  Max Packet=[2048]
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
inserting floppy driver for 2.6.8-3-686-smp
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
usb 4-1: new high speed USB device using address 2
scsi1 : SCSI emulation for USB Mass Storage devices
  Vendor: SAMSUNG   Model: SP0802N           Rev:  0 0
  Type:   Direct-Access                      ANSI SCSI revision: 02
USB Mass Storage device found at 2
SvrWks OSB4: IDE controller at PCI slot 0000:00:0f.1
SvrWks OSB4: chipset revision 0
SvrWks OSB4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x08b0-0x08b7, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0x08b8-0x08bf, BIOS settings: hdc:pio, hdd:pio
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[0011060000007590]
hda: _NEC CD-RW NR-7800A, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
PDC20271: IDE controller at PCI slot 0000:02:08.0
ACPI: PCI interrupt 0000:02:08.0[A] -> GSI 21 (level, low) -> IRQ 217
PDC20271: chipset revision 2
PDC20271: ROM enabled at 0xf4000000
PDC20271: 100% native mode on irq 217
    ide2: BM-DMA at 0xdc80-0xdc87, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0xdc88-0xdc8f, BIOS settings: hdg:pio, hdh:pio
hde: SAMSUNG SP2014N, ATA DISK drive
ide2 at 0xdcb8-0xdcbf,0xdcb2 on irq 217
hdg: Maxtor 6Y120L0, ATA DISK drive
ide3 at 0xdca0-0xdca7,0xdc9a on irq 217
hde: max request size: 1024KiB
hde: 390721968 sectors (200049 MB) w/8192KiB Cache, CHS=24321/255/63, UDMA(100)
 /dev/ide/host2/bus0/target0/lun0: unknown partition table
hdg: max request size: 128KiB
hdg: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(133)
 /dev/ide/host2/bus1/target0/lun0: unknown partition table
hda: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache, (U)DMA
Uniform CD-ROM driver Revision: 3.20
sbp2: $Rev: 1219 $ Ben Collins <bcollins@debian.org>
e100: Intel(R) PRO/100 Network Driver, 3.0.18
e100: Copyright(c) 1999-2004 Intel Corporation
ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 177
e100: eth0: e100_probe: addr 0xfe102000, irq 177, MAC addr 00:B0:D0:AA:87:07
ip1394: $Rev: 1224 $ Ben Collins <bcollins@debian.org>
ip1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
SCSI device sda: 35561472 512-byte hdwr sectors (18207 MB)
SCSI device sda: drive cache: write through
 /dev/scsi/host0/bus0/target0/lun0: p1 p2 < p5 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 156368016 512-byte hdwr sectors (80060 MB)
sdb: assuming drive cache: write through
 /dev/scsi/host1/bus0/target0/lun0: p1
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Generic RTC Driver v1.07
input: PS/2 Logitech Mouse on isa0060/serio1
mice: PS/2 mouse device common for all mice
ts: Compaq touchscreen protocol output
device-mapper: 4.1.0-ioctl (2003-12-10) initialised: dm@uk.sistina.com
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Maximum main memory to use for agp memory: 564M
agpgart: unable to determine aperture size.
agpgart: agp_backend_initialize() failed.
agpgart-serverworks: probe of 0000:00:00.0 failed with error -22
agpgart: Maximum main memory to use for agp memory: 564M
agpgart: unable to determine aperture size.
agpgart: agp_backend_initialize() failed.
agpgart-serverworks: probe of 0000:00:00.1 failed with error -22
cpci_hotplug: CompactPCI Hot Plug Core version: 0.2
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.4
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
input: PC Speaker
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Adding 755012k swap on /dev/sda5.  Priority:-1 extents:1
EXT3 FS on sda1, internal journal
piix4-smbus 0000:00:0f.0: Found 0000:00:0f.0 device
Capability LSM initialized
NET: Registered protocol family 10
Disabled Privacy Extensions on device c031f0c0(lo)
IPv6 over IPv4 tunneling driver
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
eth0: no IPv6 routers present
mtrr: Serverworks LE detected. Write-combining disabled.
mtrr: your processor doesn't support write-combining
mtrr: Serverworks LE detected. Write-combining disabled.
mtrr: your processor doesn't support write-combining

and if needed here is my /etc/fstab

Code:

proc            /proc           proc    defaults        0       0
/dev/sda1       /               ext3    defaults,errors=remount-ro,usrquota,grpquota 0       1
/dev/sda5       none            swap    sw              0       0
/dev/hda        /media/cdrom0   iso9660 ro,user,noauto  0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0

it would be nice if anyone can help me...

thanks a lot

willigi

burntfuse · 06-19-2006, 11:12 AM

Um, since your root filesystem is on an ext3 partition, you'll need to build ext3 support (and probably those other modules you mentioned) into the kernel. Otherwise, how is it supposed to mount to drive to load the modules?

willigi · 07-01-2006, 06:03 AM

ohh hi, thanks for reply

but i compiled them as modules and then packed an initrd, to load the scsi raid controller driver on which the root filesystem is. is this the wrong way?

on my other computers i ever compiled ext3 as module and then built an initrd. and now im very confused, why it isnt running on this f***ing DELL PowerEdge..

Do anyone else have an idea?

thanks a lot!!

burntfuse · 07-01-2006, 03:01 PM

Might as well just try building them into the kernel anyways and seeing if it works.

willigi · 07-02-2006, 07:51 AM

thanks, but you mean all the drivers, scsi, ext3, raid-driver? or only the ext3?

burntfuse · 07-09-2006, 01:31 PM

You could try all of them.