Bug 75 - install fails after swap partition formatted when primary drive=syquest sparq
install fails after swap partition formatted when primary drive=syquest sparq
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
5.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1998-11-15 06:15 EST by maxfield
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:
Environment:
Last Closed: 1999-06-28 12:20:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description maxfield 1998-11-15 06:15:24 EST
Syquest sparq 1.0gb ide drive is primary drive (fixed disk 0, /dev/hda, drive c:, the main drive, etc ;).  Motherboard is Intel Pentium, 166mhz, usb support, purchased October 98. Keyboard is standard keyboard. mouse is ps/2 mouse. cpu is Intel.

  drive partitions fine, and the format for the swap partition starts.  As soon as the format is finished, the system hangs and must be rebooted.  Cannot get past swap partition formatting.

  Caldera Linux installs just fine.  Window 95 installs just fine.  Windows NT 4.0 installs just fine.

  This behaviour was replicated with RH Linux 5.1 and 5.2.
Comment 1 David Lawrence 1998-11-24 18:01:59 EST
We will need to get a sparqdrive into the test lab to try to replicate
this problem.
Comment 2 David Lawrence 1999-06-28 12:20:59 EDT
6.0 may be better for this problem. Please try this again with 6.0 and
reopen bug if this still occurs. We still will try to get a Sparq
drive into the lab if possible to help provide a solution if this
still occurs. Until then check with the mailing lists to see if
someone else has the same type of drive and have been successful with
it.

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