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

Bug#470423: debian-installer: CDROM drive lockup during multiple CD installation



On Wednesday 12 March 2008, Frans Pop wrote:
> Thanks a lot for the additional info.
>
> On Tuesday 11 March 2008, Philip Charles wrote:
> > At the switch-over from scanning by cdset to install software.
>
> Right. From the logs I can see that it is actually at the beginning of
> install software. The configuration of apt was completed when the loop
> happened.
>
> I saw a similar problem myself recently, but for me the loop happened
> the first time the installer needed to switch from CD1 to CD2, so quite
> a bit further along in the install software step.
>
> From your log I can tell that both issues have the same root cause, and
> that was already fixed in version 1.18 of pkgsel (you were using 1.17),
> which will be included in the upcoming Beta1 release of the installer.
>
> However, I am still puzzled as to what exactly caused your installation
> to behave so different from mine.
>
> Let's look at your log in detail.
>
**************
> Here apt-cdrom has completed scanning CD 5.
>
> I would guess that you selected "No" here and pressed <enter> without
> actually changing the CD.
> Is that correct? Or did you insert CD 1 immediately after CD 5 was
> scanned?

CD5 was still in the drive at this point

Insert CD1 - hit return (still cdset)
[a couple of things happen.  To quick to record]

Is (was) this the problem?
>
> Mar 11 10:45:39 kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
> Mar 11 10:45:39 kernel: ISO 9660 Extensions: RRIP_1991A
>
> This is where the installer mounts the CD to check if CD1 is inserted.
>
> Mar 11 10:46:04 load-install-cd: E: Failed to mount the cdrom.
>
> And this is strange. If CD 1 is not inserted at this point, it should
> not be trying to mount it but it should instead prompt you to insert CD
> 1. And if CD 1 was inserted, there's no reason why the mount should
> fail.

The perversity of inanimate objects.

>
> Can you remember what exactly happened here?

Insert CD1 - hit return (still cdset)
[a couple of things happen.  To quick to record]
>
> Mar 11 10:47:25 kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
> Mar 11 10:47:25 kernel: ISO 9660 Extensions: RRIP_1991A
> Mar 11 10:47:26 kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
> Mar 11 10:47:26 kernel: ISO 9660 Extensions: RRIP_1991A
>
> A CD gets mounted two more times, and I'd guess that the second time it
> is recognized as CD 1 and the installation continues.
>
> Mar 11 10:47:26 apt-setup: warning:
> /usr/lib/apt-setup/generators/50mirror returned error code 1;
> discarding output
> Mar 11 10:47:26 apt-setup: warning:
> /usr/lib/apt-setup/generators/90services-select returned error code 30;
> discarding output
> Mar 11 10:47:26 apt-setup: warning:
> /usr/lib/apt-setup/generators/91security output added commented out
>
> This is where the apt configuration is finished and the main menu
> starts the software installation component.
>
> Mar 11 10:47:28 main-menu[961]: INFO: Falling back to the package
> description for auto-install Mar 11 10:47:28 main-menu[961]: INFO:
> Falling back to the package description for ai-choosers Mar 11 10:47:28
> main-menu[961]: INFO: Menu item 'pkgsel' selected Mar 11 10:47:28
> apt-install: umount: Couldn't umount /cdrom: Invalid argument
>
> Here is the start of the actual cause of the loop. The CD gets
> unmounted 2 times (the second time fails).

Would have <eject> been better?
>
> Mar 11 10:47:29 in-target: Reading package lists...
> Mar 11 10:47:29 in-target:
> Mar 11 10:47:29 in-target: Building dependency tree...
> Mar 11 10:47:29 in-target:
> Mar 11 10:47:29 in-target: Reading state information...
> Mar 11 10:47:29 in-target:
> Mar 11 10:47:30 in-target: laptop-detect is already the newest version.
> Mar 11 10:47:30 in-target: 0 upgraded, 0 newly installed, 0 to remove
> and 0 not upgraded. Mar 11 10:47:30 kernel: ISO 9660 Extensions:
> Microsoft Joliet Level 3 Mar 11 10:47:30 kernel: ISO 9660 Extensions:
> RRIP_1991A
>
> The installer again checks that is is indeed CD 1.
>
> Mar 11 10:47:31 kernel: ISO 9660 Extensions: Microsoft Joliet Level 3
> Mar 11 10:47:31 kernel: ISO 9660 Extensions: RRIP_1991A
>
> And the real cause of the loop: the CD gets mounted while it should not
> be. This (the second umount and this mount) is what was fixed in 1.18.
>
> [...]
> Mar 11 10:48:53 in-target: Media change: please insert the disc labeled
> Mar 11 10:48:53 in-target:  'Debian GNU/Linux testing _Lenny_ -
> Official Snapshot i386 CD Binary-1 20080308-20:17'
> Mar 11 10:48:53 in-target: in the drive '/cdrom/' and press enter
>
> This is probably the start of your loop. The strange thing here is that
> CD 1 should already be inserted here, so why is the installer asking
> for it?
>
> Mar 11 10:48:53 in-target: Media change: please insert the disc labeled
> Mar 11 10:48:53 in-target:  'Debian GNU/Linux testing _Lenny_ -
> Official Snapshot i386 CD Binary-1 20080308-20:17'
> Mar 11 10:48:53 in-target: in the drive '/cdrom/' and press enter
>
> This is apparently where you ran eject. The installation now continues
> normally.
>
> Mar 11 10:48:53 in-target: Selecting previously deselected package
> popularity-contest.
>
> The popcon question is asked after this point.
> <log analysis end>
>
>
> I kind of expect that pkgsel 1.18 will have also fixed the behavior you
> saw. But I still have an uncomfortable feeling about some details of
> what happened.
> Can you provide some more detail about what CD was inserted at what
> point? I understand that that's difficult as there are no visual clues.

Done my best.


> There are two options at this point:
> - either we assume that pkgsel 1.18 indeed fixed the issue and close
> this report but stay alert for other reports of similar experiences -
> or I ask you to try to reproduce the problem, but with extra debugging
> added so we can find out in more detail what happened

Let us see how 1.18 behaves.  Will is be used for next week's snapshot?
I will do another test installion when it is available
>
> The last would be a fair amount of work, and possibly for no good
> reason if the problem is indeed already fixed.
>

All the best.

Phil.



-- 
  Philip Charles; 39a Paterson Street, Abbotsford, Dunedin, New Zealand
   +64 3 488 2818        Fax +64 3 488 2875        Mobile 027 663 4453
   philipc@copyleft.co.nz - personal.    info@copyleft.co.nz - business



Reply to: