Bug 172031

Summary:	Modules required for USB stick not loaded during boot
Product:	[Fedora] Fedora	Reporter:	wdef200
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-05-05 20:36:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description wdef200 2005-10-29 15:46:35 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
Samsung Mighty Drive 500MB usb stick cannot be mounted after plugging in because
device /dev/sda1 does not exist.  On investigation, the required modules are not being loaded during boot.  This is fixed after boot by either running System Tools --> Hardware Browser, or manually loading scsi_mod, sd_mod and usb-storage.

More permanent workaround is to edit /etc/rc.sysinit to load the required modules during boot.  Usb stick connected during boot can then be automounted and icon will be present on desktop as expected.

Suggests something wrong in /etc/rc.sysinit?

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


How reproducible:
Always

Steps to Reproduce:
1. Add usual line to /etc/fstab to allow mounting of usb stick
2. Plug in usb stick
3. Try to mount
  

Actual Results:  Mount fails.  /dev/sda1 does not exist.

Expected Results:  vfat filesystem on /dev/sda1 should get mounted on mountpoint.

Additional info:

My apologies if this duplicates another report - I could not find one quite the same however there are complaints that are conceivably related -  see

https://bugzilla.redhat.com/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=NEEDINFO&bug_status=REOPENED&field0-0-0=product&type0-0-0=substring&value0-0-0=Fedora&field0-0-1=component&type0-0-1=substring&value0-0-1=Fedora&field0-0-2=short_desc&type0-0-2=substring&value0-0-2=Fedora&field0-0-3=status_whiteboard&type0-0-3=substring&value0-0-3=Fedora&field1-0-0=product&type1-0-0=substring&value1-0-0=usb&field1-0-1=component&type1-0-1=substring&value1-0-1=usb&field1-0-2=short_desc&type1-0-2=substring&value1-0-2=usb&field1-0-3=status_whiteboard&type1-0-3=substring&value1-0-3=usb&field2-0-0=product&type2-0-0=substring&value2-0-0=device&field2-0-1=component&type2-0-1=substring&value2-0-1=device&field2-0-2=short_desc&type2-0-2=substring&value2-0-2=device&field2-0-3=status_whiteboard&type2-0-3=substring&value2-0-3=device

Inspiration for the workaround came from

https://www.redhat.com/archives/fedora-list/2005-October/msg00724.html

which is related?

Comment 1 wdef200 2005-10-29 16:06:20 UTC

*** Bug 172032 has been marked as a duplicate of this bug. ***

Comment 2 wdef200 2005-10-29 16:08:36 UTC

I unwittingly submitted this twice, hence #172032

Comment 3 Bill Nottingham 2005-10-31 20:25:39 UTC

Can you post the kernel messages that appear when you insert the stick?

Comment 4 John Thacker 2006-05-05 20:36:03 UTC

Closing due to lack of response by reporter.