Bug 187963 - FC5 dmraid issue in /etc/rc.sysinit script
Summary: FC5 dmraid issue in /etc/rc.sysinit script
Keywords:
Status: CLOSED DUPLICATE of bug 183959
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: 5
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-04 22:11 UTC by Max Pyziur
Modified: 2014-03-17 02:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-04-26 16:21:21 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Max Pyziur 2006-04-04 22:11:05 UTC 
+++ This bug was initially created as a clone of Bug #187962 +++

Description of problem:
When booting up the
/etc/rc.d/rc.sysinit script reports the following error:
ERROR: No arguments allowed with -i

ERROR: No arguments allowed with -i

ERROR: No arguments allowed with -i



Version-Release number of selected component (if applicable):
initscripts-8.31.1-1
dmraid-1.0.0.rc9-FC5_5.2
How reproducible:


Steps to Reproduce:
1. Boot the machine; you'll see the error just before the init.d scripts start
running.  My machine is: PIII-1400MHZ, 1GB RAM, 40GB HDD as /dev/hda and 120GB
HDD as /dev/hdb. The machine is setup not to run RAID.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Ed 2006-04-26 05:53:44 UTC 
I noticed this also and added echo statements to rc.sysinit to try and narrow it
down. The error message is generated by the following call (line 266 on my system):

                        if [ -z "$dmname" ]; then
                                /sbin/dmraid -ay --ignorelocking "$x"
                        fi
Comment 2 Milan Broz 2006-04-26 06:55:07 UTC 
The problem is related to -i parameter in dmraid - see bug 183959.
Comment 3 Bill Nottingham 2006-04-26 16:21:21 UTC 

*** This bug has been marked as a duplicate of 183959 ***
Note You need to log in before you can comment on or make changes to this bug.