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

Bug#619521: upgrade-reports: "dist-upgrade" -using DVDs cannot be completed



On Fri, 2011-03-25 at 04:40 +1100, Felix Karpfen wrote:
> Package: upgrade-reports
> Severity: critical
> Justification: causes serious data loss

You have not explained this claim.

> I have submitted the report (details below) before.  But, because I am new to
> "reportbug, I incorrectly selected to report it under #609566.  As a result,
> my posting was filed and ignored.
> 
> So, here is a copy of the posting - with additional information:
> 
> I attempted to use the DVDs of the Official release of Debian 6.0 by
> following the routines described in the release notes - chapter 4.  
> 
> Everything worked correctly until I got to Section 4.4.6.
> 
> "apt-get dist-upgrade" found 607 packages to be upgraded, 753 packages to be
> newly installed and 70 packages to be removed.  It invited me to load the
> first DVD, made all the changes to packages that were on that DVD and then
> asked me to insert the second DVD.
> 
> This command could not be carried out - for the following reason:
> 
> When the dist-upgrade started the sym-link "/cdrom -> /dev/hdc" was correct.

Do you mean that /dev/hdc was mounted on /cdrom?

> But during the that stage of the "dist-upgrade, the mounted drive had
> been renamed from /dev/hdc to "/dev/sr0".

This cannot happen during an upgrade, unless you also reboot into a new
kernel version.  Did you do that?

Is the linux-base package installed?

> Since "/cdrom" still pointed to "/dev/hdc", the drive carriage could not be
> opened.
[...]

If /cdrom is indeed a symlink to /dev/hdc, then you should remove the
symlink and create an empty directory in its place.  If it is a
mountpoint and /etc/fstab says that the non-existent /dev/hdc should be
mounted there, you should fix /etc/fstab.  Neither of these errors
prevents you from ejecting the DVD tray with the 'eject' command.

> Attached is the script of the crashed "dist-upgrade"
>
> If that is not enough, I could probably also locate the kernel log
> that covers the time period of the crash.

I see no crash, only what looks like failure to mount the right disc.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: