Bug 55075 - libpopt.so.0 not available for raid0start
libpopt.so.0 not available for raid0start
Status: CLOSED DUPLICATE of bug 54587
Product: Red Hat Linux
Classification: Retired
Component: popt (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jeff Johnson
Depends On:
  Show dependency treegraph
Reported: 2001-10-25 02:03 EDT by Erik Selberg
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-10-25 02:04:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Erik Selberg 2001-10-25 02:03:56 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:
I upgraded my RH 7.1 to RH 7.2. After it booted, raid0start failed because 
it couldn't load libpopt.so.0. This file is in /usr/lib/libpopt.so.0, and 
on my system /usr (and /usr/lib) weren't mounted yet, as raid is started 
immediately after the root filesystem is mounted. Workaround: I copied 
libpopt.so.0 into /lib, which is on the root FS.

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

How reproducible:
Didn't try

Steps to Reproduce:
1. Use a software raid disk (/dev/md0)
2. Put /usr and / on different partitions
3. Upgrade from RH 7.1 to 7.2
4. Watch it crash


Actual Results:  raid0start halted, as did boot-up. Then got into maint 
mode. Wee!

Expected Results:  Either (a) raid0start would have found libpopt.so.0 in 
the root filesystem (/lib) or /usr would have been mounted before raid, 
so /usr/lib would be available for raid0start.

Random thought: this is /sbin/raid0start. Perhaps raid0start (symlink'd to 
mkraid) isn't STATIC like it should be in /sbin? :)

Additional info:
Comment 1 Bill Nottingham 2001-10-29 14:07:07 EST

*** This bug has been marked as a duplicate of 54587 ***

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