[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#222939: installation-reports: d-i installation report: boots from cdrom, but then fails to mount it



Moritz Lennert wrote:
> Here you go. I didn't know whether I should send all this to the bug
> address as well, so I'm sending it only to you.
> 
> Tell me if you need naything else.

Thank you, that at least narrows it down somewhat:

Dec  7 12:07:14 (none) user.notice cdrom-detect: Searching for Debian installation media...
Dec  7 12:07:14 (none) syslog.debug klogd: ISO 9660 Extensions: Microsoft Joliet Level 3
Dec  7 12:07:24 (none) syslog.warn klogd: hdc: DMA interrupt recovery
Dec  7 12:07:24 (none) syslog.err klogd: hdc: lost interrupt
Dec  7 12:07:24 (none) syslog.debug klogd: ISOFS: changing to secondary root
Dec  7 12:07:24 (none) syslog.warn klogd: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec  7 12:07:24 (none) syslog.warn klogd: hdc: status error: error=0x00
Dec  7 12:07:24 (none) syslog.err klogd: hdc: drive not ready for command
Dec  7 12:07:34 (none) syslog.warn klogd: hdc: DMA interrupt recovery
Dec  7 12:07:34 (none) syslog.err klogd: hdc: lost interrupt
Dec  7 12:07:34 (none) syslog.warn klogd: Interleaved files not (yet) supported.
Dec  7 12:07:34 (none) syslog.warn klogd: File unit size != 0 for ISO file (649216).
Dec  7 12:07:34 (none) syslog.warn klogd: hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Dec  7 12:07:34 (none) syslog.warn klogd: hdc: status error: error=0x04 Aborted Command 
Dec  7 12:07:34 (none) syslog.err klogd: hdc: drive not ready for command
Dec  7 12:07:38 (none) daemon.info init: Starting pid 55, console /dev/vc/2: '/bin/sh'
Dec  7 12:09:06 (none) syslog.warn klogd: VFS: Can't find ext2 filesystem on dev ide0(3,1).
Dec  7 12:09:06 (none) syslog.err klogd: cramfs: wrong magic
Dec  7 12:09:06 (none) syslog.warn klogd: Unable to identify CD-ROM format.

I don't know what is causing this though. I wonder if you could install
the debian kernel that is used by the debian installer on your existing
debian install, and boot it and see if it has similar problems accessing
the cdrom. It could be that this is a bug in the new version of the
kernel; I notice your existing install is using the older 2.4.18-586tsc 
kernel. The kernel used by the debian installer is in the package named
kernel-image-2.4.22-1-386

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


Reply to: