Find the answer to your Linux question:
Results 1 to 3 of 3
I recently compiled and installed a new kernel for my server running Suse 9.3. The new kernel has been has been installed next to the existing kernel, the old kernel ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined! nskid11's Avatar
    Join Date
    Aug 2010
    Posts
    2

    [SOLVED] Getting Waiting for device.... not found Despite SCSI and FS drivers being l


    I recently compiled and installed a new kernel for my server running Suse 9.3. The new kernel has been has been installed next to the existing kernel, the old kernel still boots fine but the new one doesn't, stopping on Waiting for device /dev/sda3 (root partition).

    I'm fairly sure I have loaded all the needed modules into initrd because I uncompressed the original one and expanded it and added in the modules in there to the new initrd. I don't know what could be missing, whether there is a module I need but don't know about. So any opinions or advice would be useful, if at all possible I would like to avoid updating/reinstalling the OS.

    Oh the reason I updated the kernel was so that I could get a new PCI-E card to work (Sil 3132).

    INITRD_MODULES="thermal edd processor fan ide-disk piix scsi_mod ips reiserfs sata_sil24"

    I know the sata_sil24 module doesn't need to be in there but I just added it to see if it had any effect.

    /boot/grub/menu.lst
    Code:
    # Modified by YaST2. Last modification on Thu Aug  5 11:48:39 BST 2010
    
    color white/blue black/light-gray
    default 0
    timeout 8
    gfxmenu (hd0,2)/boot/message
    
    ###Don't change this comment - YaST2 identifier: Original name: linux###
    title SUSE LINUX 9.3
        kernel (hd0,2)/boot/vmlinuz root=/dev/sda3 vga=0x317 selinux=0  splash=silent resume=/dev/sda2  showopts
        initrd (hd0,2)/boot/initrd
    
    
    title Test Kernel 2.6.32.14
        kernel (hd0,2)/boot/vmlinuz-2.6.31.14 root=/dev/sda3 vga=0x317
        initrd (hd0,2)/boot/initrd-2.6.31.14
    
    ###Don't change this comment - YaST2 identifier: Original name: windows###
    title Windows
        root (hd0,0)
        chainloader +1
    
    ###Don't change this comment - YaST2 identifier: Original name: floppy###
    title Floppy
        root (fd0)
        chainloader +1
    
    ###Don't change this comment - YaST2 identifier: Original name: failsafe###
    title Failsafe -- SUSE LINUX 9.3
        kernel (hd0,2)/boot/vmlinuz root=/dev/sda3 showopts ide=nodma apm=off acpi=off vga=normal noresume selinux=0 barrier=off nosmp noapic maxcpus=0  3
        initrd (hd0,2)/boot/initrd
    
    ###Don't change this comment - YaST2 identifier: Original name: memtest86###
    title Memory Test
        kernel (hd0,2)/boot/memtest.bin
    Working Kernel 2.6.11.4... partial dmesg log
    Code:
    SCSI subsystem initialized
    Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    ICH5: IDE controller at PCI slot 0000:00:1f.1
    ACPI: PCI interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 177
    input: PS/2 Generic Mouse on isa0060/serio1
    ICH5: chipset revision 2
    ICH5: not 100% native mode: will probe irqs later
        ide0: BM-DMA at 0x14a0-0x14a7, BIOS settings: hda:DMA, hdb:pio
        ide1: BM-DMA at 0x14a8-0x14af, BIOS settings: hdc:pio, hdd:pio
    Probing IDE interface ide0...
    hda: HL-DT-ST CD-ROM GCR-8482B, ATAPI CD/DVD-ROM drive
    ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    Probing IDE interface ide1...
    ACPI: PCI interrupt 0000:03:01.0[A] -> GSI 28 (level, low) -> IRQ 185
    scsi0 : IBM PCI ServeRAID 7.10.18  Build 731 <ServeRAID 6i>
      Vendor: IBM       Model: SERVERAID         Rev: 1.00
      Type:   Direct-Access                      ANSI SCSI revision: 02
    SCSI device sda: 143372288 512-byte hdwr sectors (73407 MB)
    SCSI device sda: drive cache: write through
    SCSI device sda: 143372288 512-byte hdwr sectors (73407 MB)
    SCSI device sda: drive cache: write through
     sda: sda1 sda2 sda3
    Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
      Vendor: IBM       Model: SERVERAID         Rev: 1.00
      Type:   Processor                          ANSI SCSI revision: 02
      Vendor: SEAGATE   Model: DAT    06240-XXX  Rev: 8240
      Type:   Sequential-Access                  ANSI SCSI revision: 03
      Vendor: IBM       Model: 02R0980a S320  1  Rev: 1
      Type:   Processor                          ANSI SCSI revision: 02
    hda: ATAPI 48X CD-ROM drive, 128kB Cache, UDMA(33)
    Uniform CD-ROM driver Revision: 3.20
    Attempting manual resume
    PM: Checking swsusp image.
    swsusp: Suspend partition has wrong signature?
    PM: Resume from disk failed.
    ReiserFS: sda3: found reiserfs format "3.6" with standard journal
    ReiserFS: sda3: using ordered data mode
    reiserfs: using flush barriers
    ReiserFS: sda3: journal params: device sda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
    ReiserFS: sda3: checking transaction log (sda3)
    reiserfs: disabling flush barriers on sda3
    ReiserFS: sda3: Using r5 hash to sort names
    bootsplash: status on console 0 changed to on
    md: Autodetecting RAID arrays.
    md: autorun ...
    md: ... autorun DONE.
    New Kernel 2.6.31.14 copy of whats on screen
    Code:
    Loading kernel/drivers/ide/ide-gd_mod.ko
    ide-gd driver 1.18
    Loading kernel/drivers/ide/piix.ko
    piix 0000:00:1f.01: IDE controller (0x8086:0x24db rev 0x02)
    PIIX_IDE 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    piix 0000:00:1f.1: not 100% native mode: will probe irqs later
    	ide0: BM-DMA at 0x14a0-0x14a7
    	ide1: BM-DMA at 0x14a8-0x14af
    input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input2
    hda: HL-DT-ST CD-ROM GCR-8482B, ATAPI CD/DVD-ROM drive
    hda: UDMA/33 mode selected
    ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    ide1 at 0x170-0x177,0x376 on irq 15
    Loading kernel/drivers/scsi/ips.ko
    ips 0000:03:01.0: PCI INT A -> GSI 28 (level, low) IRQ 28
    scsi0: IBM PCI ServeRAID 7.12.05 Build 761 <ServeRAID 6i>
    scsi 0:0:0:0: Direct-Access	IBM	SERVERAID	1.00	PQ: 0 ANSI: 2
    sd 0:0:0:0: [sda] 143372288 512-byte logical blocks: (73.4 GB/68.3 GiB)
    sd 0:0:0:0: [sda] Assuming Write Enabled
    sd 0:0:0:0: [sda] Assuming drive cache: write through
    sd 0:0:0:0: [sda] Assuming Write Enabled
    sd 0:0:0:0: [sda] Assuming drive cache: write through
     sda:
    scsi 0:0:15:0: Processor	IBM	SERVERAID	1.00 PQ: 0 ANSI: 2
     sda1 sda2 sda3
    scsi 0:1:6:0: Sequential-Access SEAGATE	DAT	06240-XXX 8240 PQ: 0 ANSI: 3
    sd 0:0:0:0: [sda] Assuming Write Enabled
    sd 0:0:0:0: [sda] Assuming drive cache: write through
    sd 0:0:0:0: [sda] Attached SCSI disk
    scsi 0:2:8:0: Processor	IBM	02r0980a S320	1 1	PQ: 0 ANSI: 2
    Loading kernel/drivers/ata/libata.ko
    Loading kernel/drivers/ata/sata_sil24.ko
    sata_sil24 0000:05:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    scsi1: sata_sil24
    scsi2: sata_sil24
    ata1: SATA max UDMA/100 host m128(at)0xd0404000 port 0xd0400000 irq 16
    ata2: SATA max UDMA/100 host m128(at)0xd0404000 port 0xd0402000 irq 16
    ata1: SATA link down (SStatus 0 SControl 0)
    ata2: SATA link down (SStatus 0 SControl 0)
    Loading kernel/drivers/cdrom/cdrom.ko
    Loading kernel/drivers/ide/ide-cd_mod.ko
    ide-cd driver 5.00
    ide-cd: hda: ATAPI 48X CD-ROM drive, 128kB Cache
    Uniform CD-ROM driver Revision: 3.20
    Loading kernel/fs/reiserfs/reiserfs.ko
    Waiting for device /dev/sda3 to appear: .....not found -- exiting to /bin/sh
    sh: can't access tty; job control turned off
    $

  2. #2
    Linux Engineer Segfault's Avatar
    Join Date
    Jun 2008
    Location
    Acadiana
    Posts
    877
    Normally there is no reason to use initrd with custom kernel.
    I'd build the kernel without modules and see if there still is a problem.

    You should not use IDE drivers, they are depreciated. Please use libata.

  3. #3
    Just Joined! nskid11's Avatar
    Join Date
    Aug 2010
    Posts
    2
    Arr your a life saver, compiling the modules that was needed to boot into the kernel and getting rid of initrd got it to boot, thanks.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •