disk device does not exist when booting Feisty herd 4 on GA-965GM-S2

Bug #86586 reported by Marc Tardif
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

After successfully installing Feisty herd 4 on a Gigabyte GA-965GM-S2 motherboard, the Ubuntu splash screen appears but then disappears with the following error message on a black background:

Check root= bootarg cat /proc/cmdline
or missing modules, devices: cat /proc/modules ls /dev
ALERT! /dev/disk/by-uuid/2a7df3ea-8da1-4c7a-843a-e26d79198272 does not exist. Dropping to a shell!

The boot process then provides an initramfs prompt. There, I tried to ls /dev/disk to check if the uuid might be wrong, but the directory doesn't exist.

So, I then tried booting without the quiet and splash kernel options. I noticed a stack trace which starts with the following line:

Modules linked in: ohci1394 ieee1394 ehci_hcd generic uhci_hcd usbcore thermal processor fan fbcon tileblit font bitblit softcursor vesafb capability commoncap

And the stack trace ends with the following lines:

udevd-event[2017]: run_program: '/sbin/modprobe' abnormal exit <6>usb 5-1: new low speed USB device using uchci_hcd and address 2
usb 5-1: configuration #1 chosen from 1 choice
usb 5-2: new low speed USB device using uhci_hcd and address 3
usb 5-2: configuration #1 chosen from 1 choice

I'm not sure if this stack trace is related to the disk device which is reported not to exist, but I thought I would provide this information anyhow.

Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

This seems similar to bug 84964.

Revision history for this message
Glenn Kidd (glenn-kidd) wrote :

I am seeing the exact same problem on Feisty Fawn, kernel version 2.6.20-14. I would post my lspci but I cannot boot and don't have a LiveCD handy right now.

Revision history for this message
reef (renzo-mischianti) wrote :
Download full text (4.1 KiB)

I am seeing the exact same problem on Feisty Fawn, kernel version 2.6.20-14 too. (After the update of 11/4/2007 (but i'm not really sure of the date)).
With the same uuid I can boot with the old kernel (I upgrade from edgy) 2.6.17-10-generic (2.6.17-11-generic don't go).

My Grub
reef@portatireef:~$ cat /boot/grub/menu.lst
default 0

timeout 10

title Ubuntu, kernel 2.6.20-14-lowlatency
root (hd0,3)
kernel /boot/vmlinuz-2.6.20-14-lowlatency root=UUID=dd2fff11-bfc0-4235-8557-ad9679166a1f ro quiet splash
initrd /boot/initrd.img-2.6.20-14-lowlatency
quiet
savedefault

title Ubuntu, kernel 2.6.20-14-lowlatency (recovery mode)
root (hd0,3)
kernel /boot/vmlinuz-2.6.20-14-lowlatency root=UUID=dd2fff11-bfc0-4235-8557-ad9679166a1f ro single
initrd /boot/initrd.img-2.6.20-14-lowlatency

title Ubuntu, kernel 2.6.20-14-generic
root (hd0,3)
kernel /boot/vmlinuz-2.6.20-14-generic root=UUID=dd2fff11-bfc0-4235-8557-ad9679166a1f ro quiet splash
initrd /boot/initrd.img-2.6.20-14-generic
quiet
savedefault

title Ubuntu, kernel 2.6.20-14-generic (recovery mode)
root (hd0,3)
kernel /boot/vmlinuz-2.6.20-14-generic root=UUID=dd2fff11-bfc0-4235-8557-ad9679166a1f ro single
initrd /boot/initrd.img-2.6.20-14-generic

title Ubuntu, kernel 2.6.17-10-generic
root (hd0,3)
kernel /boot/vmlinuz-2.6.17-10-generic root=UUID=dd2fff11-bfc0-4235-8557-ad9679166a1f ro quiet splash
initrd /boot/initrd.img-2.6.17-10-generic
quiet
savedefault

title Ubuntu, kernel 2.6.17-10-generic (recovery mode)
root (hd0,3)
kernel /boot/vmlinuz-2.6.17-10-generic root=UUID=dd2fff11-bfc0-4235-8557-ad9679166a1f ro single
initrd /boot/initrd.img-2.6.17-10-generic

title Ubuntu, memtest86+
root (hd0,3)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root

# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title Microsoft Windows XP Professional
root (hd0,0)
savedefault
makeactive
chainloader +1

My lspci
reef@portatireef:~$ lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 755 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 25)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0)
00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f)
00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Et...

Read more...

Revision history for this message
Ray Ward (ray-ward4) wrote :

I think I have the same sort of problem. When I upgraded from 6.10 one of my disks went missing. There is only one device recognised on a SCSI bus (Sudo SCSI) controller the other device is missing.
lspci snapshot.
03:06.0 RAID bus controller: <pci_lookup_name: buffer too small> (rev 13)
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (2000ns min, 2000ns max)
        Interrupt: pin A routed to IRQ 19
        Region 0: I/O ports at bc00 [size=8]
        Region 1: I/O ports at b800 [size=4]
        Region 2: I/O ports at b400 [size=8]
        Region 3: I/O ports at b000 [size=4]
        Region 4: I/O ports at ac00 [size=16]
        [virtual] Expansion ROM at fdc00000 [disabled] [size=128K]
        Capabilities: <access denied>
 There are two IDE ports each with a drive only sda is visible the other is missing.
The drive exists because I can see it in windows and it was there before I upgraded.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.