WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 464] Xen Demo Live CD 3.0 halts at "grub>" prompt

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 464] Xen Demo Live CD 3.0 halts at "grub>" prompt
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 18 Jan 2006 06:42:05 +0000
Delivery-date: Wed, 18 Jan 2006 06:54:40 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=464





------- Additional Comments From karsten@xxxxxxxxxxxxx  2006-01-18 06:42 -------
Thanks for the additional info.

Does the CD drive work when booted to any other installation (Linux, *BSD,
Windows, etc.)?

Were the 'cat /<tab>' and 'find' commands run from GRUB or from a Linux boot?  
Both exist as both GRUB and standard shell commands.

If you have a comperable drive available, have you tried swapping it and booting
the test CD?  If you can rule out misbehaving hardware it would help.  I'm
seeing the following which suggest a drive problem:

dmesg.txt-[4294700.634000] hdc: packet command error: status=0x51 { DriveReady
SeekComplete Error }
dmesg.txt-[4294700.634000] hdc: packet command error: error=0x50 {
LastFailedSense=0x05 }
dmesg.txt-[4294700.634000] ide: failed opcode was: unknown
dmesg.txt:[4294700.635000] cdrom: open failed.

Simply accessing the drive with no media should result in an "open failed"
message,  The 0x50 / 0x51 errors are typical of failing or improperly installed
hardware.

Please confirm that the drive itself is seated properly and any and all
cables/connectors are secure and free of any debris, dust, or corrosion.  Try an
alternate burn of the CD as well.

You should be able to confirm drive errors by doing long reads (dd if=/dev/hdc
of=/dev/null) with a known good CD in the drive and watching either dmesg output
(run repeatedly) or /var/log/messages in most distros.  You may also be able to
check for drive errors using smartmontools (see: 
http://smartmontools.sourceforge.net/ )

Otherwise, we don't have comperable HW to repro this on.  If you can't get this
to work and there's no additional debug info I'll close this in a week or so.

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs