Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 100473 - anaconda crashes before fdisk, ide-enclosure-usb
Summary: anaconda crashes before fdisk, ide-enclosure-usb
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux Beta
Classification: Retired
Component: anaconda
Version: beta1
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks: CambridgeBlocker
TreeView+ depends on / blocked
 
Reported: 2003-07-22 19:31 UTC by shrek-m
Modified: 2007-04-18 16:55 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-08-14 16:40:44 UTC
Embargoed:

Attachments (Terms of Use)
anacdump.txt (deleted)
2003-07-22 19:32 UTC, shrek-m 		no flags Details
View All

Description shrek-m 2003-07-22 19:31:31 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
Netscape/7.1

Description of problem:
while harddisk-installation from an external ide-enclosure-usb
anaconda crashes before fdsik can be run


Version-Release number of selected component (if applicable):
severn beta1

How reproducible:
Always

Steps to Reproduce:
1. floppy boot
2. [enter]
3. german harddisk-install ide-enclosure-usb
   

Actual Results:  crash before fdisk

Expected Results:  no crash

Additional info:

later under rh 8.0 (i have no severn-1386-disc3.iso just now)
# mount /dev/sda3 /mnt/sda3

# fsck.ext3 /dev/sda3
e2fsck 1.27 (8-Mar-2002)
/dev/sda3: clean, 13/6979584 files, 557361/13948436 blocks

# md5sum -c MD5SUM
severn-i386-disc1.iso: Ok
severn-i386-disc2.iso: Ok
Comment 1 shrek-m 2003-07-22 19:32:59 UTC 
Created attachment 93056 [details]
anacdump.txt
Comment 2 shrek-m 2003-07-22 21:34:35 UTC 
after moving the severn-i386-disc[12].iso from '/dev/sda3' to '/dev/hdb4'
fdisk (diskdruid) works now, but "sda" is lost :-(

while choosing the severn-iso - partitions "sda*" are shown
but diskdruid shows only "hda" "hdb"


the next brake will be "there is no cd #3"
Comment 3 Michael Fulbright 2003-07-29 20:05:27 UTC 
Do you have any other SCSi drives on the system?
Comment 4 shrek-m 2003-07-29 21:58:59 UTC 
no  :(

perhaps  hdd=ide-scsi

grep "hdd" anacdump.txt

<6>    ide1: BM-DMA at 0xe808-0xe80f, BIOS settings: hdc:DMA, hdd:DMA
<4>hdd: SAMSUNG CD-R/RW SW-408B, ATAPI CD/DVD-ROM drive
<4>hdd: attached ide-cdrom driver.
<6>hdd: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache, DMA
* trying to mount device hdd
Comment 5 Michael Fulbright 2003-08-11 20:45:58 UTC 
Try adding 'expert' to the boot command line.

We basically throw out USB HD devices in the installer since we don't want
people installing to them (this just causes more trouble later). If you specify
'expert' then we allow them.
Comment 6 Michael Fulbright 2003-08-11 20:56:21 UTC 
BTW - BE SURE to deselect the USB HD from the list of drives that automatic
partitioning uses or it could possibly erase the contents of the USB drive!
Comment 7 shrek-m 2003-08-13 09:40:35 UTC 
"linux expert"   ok :-)

the usb-ide-hd sda3 is now available for further hd-iso-installation
while and after the partitioning --> no_crash

thanks.


your info about the usb-storage-devices should be available via
[F2-Options]  or  [F3-General]


about partitioning:
i choose manual-partitioning,
  the new created partition " / hda5"
  and the existing "swap"-partition
are selected for formatting, this is ok,
i deselect the swap
--> no problems
Comment 8 Michael Fulbright 2003-08-14 16:40:44 UTC 
Well expert mode has changed its meaning over time, and we've never been
comfortable documenting its behavior.  Its there as a 'relief valve' if someone
runs into a problem like you did.  It really is not recommended or supported to
create filesystems in anaconda on removable media.
Note You need to log in before you can comment on or make changes to this bug.