Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 14958 - Install on non-Linux partition fails
Install on non-Linux partition fails
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Winston gold
Depends On:
  Show dependency treegraph
Reported: 2000-08-01 08:18 EDT by Jos Vos
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-08-04 11:07:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Anaconda dump (traceback) (1.41 KB, text/plain)
2000-08-01 08:19 EDT, Jos Vos
no flags Details

  None (edit)
Description Jos Vos 2000-08-01 08:18:19 EDT
When choosing to assign / to a 0x0b (WIndows) partition, it warns me that I
should not do that, that is has speed penalties (why?) and when I insist,
it crashes. I'll attach the Anaconda dump as a file to this bug.
Comment 1 Jos Vos 2000-08-01 08:19:08 EDT
Created attachment 1740 [details]
Anaconda dump (traceback)
Comment 2 Michael Fulbright 2000-08-01 18:23:39 EDT
Was the windows partition formatted with a FAT-style filesystem?
Comment 3 Jos Vos 2000-08-02 02:42:38 EDT
No.  It was actually an ext2 filesystem, but before installation I changed the
partition type to 0x0b (it was for some tests I was doing with the installer).
Comment 4 Glen Foster 2000-08-04 11:07:01 EDT
This defect is considered MUST-FIX for Winston Gold-release
Comment 5 Erik Troan 2000-08-10 15:35:27 EDT
You have to manually format DOS filesystems for loopback installs; we don't
format devices automatically.
Comment 6 Jos Vos 2000-08-11 02:52:24 EDT
What do you mean with "loopback installs"?  Whatever that means, at least
Anaconda shouldn't crash.

Note You need to log in before you can comment on or make changes to this bug.