Mailinglist Archive: opensuse-bugs (14787 mails)
| < Previous | Next > |
[Bug 222492] New: Installation aborted due to mounted partition, expect correction possibility
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Sat, 18 Nov 2006 08:51:31 -0700 (MST)
- Message-id: <bug-222492-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=222492
Summary: Installation aborted due to mounted partition, expect
correction possibility
Product: openSUSE 10.2
Version: Beta 2 plus
Platform: i586
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Installation
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: richard.bos@xxxxxxxxx
QAContact: jsrain@xxxxxxxxxx
The installation of suse-10.2b aborted due to a mounted partition, to be
used by the new linux. Reproduction scenario:
- Install suse-10.2
- When the install linux is up, mount e.g. /dev/hda1 at /mnt
(I had to do that, to verify the partition table ((/mnt)/etc/fstab)
- Proceed the installation with custom partitioning and assign /dev/hda1
to e.g. '/' and have the partition formatted
- Proceed with the installation. As soon as the installation wants to
make the file system in /dev/hda1 the installation is aborted. It falls
back from the QT interface to the ncurses interface.
I would expect yast2 to stop/interrupt the installation and give the
user the possibility to correct the problem. After the user unmounted
the partition /dev/hda1, yast should continue with the installation.
This seems doable to me. This would save the user a lot of time as it would
prevent to do the whole installation over again!
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Summary: Installation aborted due to mounted partition, expect
correction possibility
Product: openSUSE 10.2
Version: Beta 2 plus
Platform: i586
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Installation
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: richard.bos@xxxxxxxxx
QAContact: jsrain@xxxxxxxxxx
The installation of suse-10.2b aborted due to a mounted partition, to be
used by the new linux. Reproduction scenario:
- Install suse-10.2
- When the install linux is up, mount e.g. /dev/hda1 at /mnt
(I had to do that, to verify the partition table ((/mnt)/etc/fstab)
- Proceed the installation with custom partitioning and assign /dev/hda1
to e.g. '/' and have the partition formatted
- Proceed with the installation. As soon as the installation wants to
make the file system in /dev/hda1 the installation is aborted. It falls
back from the QT interface to the ncurses interface.
I would expect yast2 to stop/interrupt the installation and give the
user the possibility to correct the problem. After the user unmounted
the partition /dev/hda1, yast should continue with the installation.
This seems doable to me. This would save the user a lot of time as it would
prevent to do the whole installation over again!
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
| < Previous | Next > |