rc problems when /usr is on another partition

mightymaan · 2007-04-11 22:12:03

After much reading of results produced by 6 different keyword searches I really have not gleaned an answer to this question.
Why do the startup/shutdown scripts stop working properly when /usr is on another partition and mounted in fstab? Specifically my pcmcia orinoco card ( no connection after login) does not work. And when doing a shutdown -r now the /usr gets unmounted and then when shutdown tries to reboot, the system crashes.
Is there something in /usr that is needed during init and shutdown? I've read lots of threads here where folks have partitioning schemes ALL kinds of different ways and never any mention of /usr not being available during bootup being a problem.

Or is it just me?
no special options in fstab for the /usr mount.....maybe that what I'm missing, dunno.

klixon · 2007-04-12 07:55:37

Could you post your fstab here?
I have no problems whatsoever with usr on a seperate patition.
It's nomal for it to be unmounted on shutdown, just not for it not to be remounted on reboot...

mightymaan · 2007-04-12 14:51:16

First, thanks for responding:)

/dev/hda3    /    ext3    defaults   0   1
/dev/hda1   /boot   ext2   defaults   0   1
/dev/hda2   swap   swap   defaults   0   0
/dev/hda4   /usr   ext3   defaults   0   1

(along with the normal cd,dvd fd0,pts, and shm lines)
If I keep all the files in /usr on the root everything works fine. Hda4 mounts and unmounts over the /usr mount point just fine. But when I delete those files in the original /usr things go wrong. Something needs to see those files before /usr is mounted on bootup and after it's unmounted on shutdown.
My startup scripts are bone stock.

Last edited by mightymaan (2007-04-12 14:51:59)

klixon · 2007-04-13 05:36:19

Well. nothing truly wrong there, except maybe for the 1's at the end of the /boot and /usr lines...
You should really set them to 2, so they get fsck'd after / gets fsck'd on boot.
Any chance you could post your rc.conf?

mightymaan · 2007-04-13 13:47:24

I'll work on geting that posted today. I've been removing blocks of files from the /usr on hda3 and going thru a boot/shtdown cycle to try and narrow it down but I'm doing it at work where I can't get a wirless connection anyway. So my reslts may be inconclusive.

I better read up on fstab and fix those numbers as well.

mightymaan · 2007-04-13 17:47:53

OK here is rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
TIMEZONE="US/Central"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
#   - prefix a module with a ! to blacklist it
#
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
#HOSTNAME="compaqlap"
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
#eth0="dhcp"
#wlan0="dhcp"
INTERFACES=(lo wlan0)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
#
#
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
NET_PROFILES=(main)

#
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond)


# End of file

And main from network profiles

#
# Network Profile
#

DESCRIPTION="Default Main Network Profile"

# Network Settings
INTERFACE=wlan0
HOSTNAME=compaqlap

# Interface Settings (use IFOPTS="dhcp" for DHCP)
IFOPTS="dhcp"
GATEWAY=10.168.1.1

# DNS Settings (optional)
DOMAIN=localdomain
DNS1=10.168.1.1
DNS2=

# Wireless Settings (optional)
ESSID=xxxxx
KEY=xxxxxxxxxx
IWOPTS="mode managed essid $ESSID key $KEY"

#WIFI_INTERFACE=wifi0   # use this if you have a special wireless interface
                        # that is linked to the real $INTERFACE

WIFI_WAIT=5            # seconds to wait for the wireless card to
                        # associate before bringing the interface up

#USEWPA="yes"           # start wpa_supplicant with the profile
#WPAOPTS=""             # use "" for normal operation or specify additional
                        # options (eg, "-D ipw")
                        # see /etc/wpa_supplicant.conf for configuration

mightymaan · 2007-04-13 23:32:29

OK I found the file that NEEDS to be available for reboot to succeed.
It is basename
Now this is a laptop so maybe acpi or something needs basename to see where it's at. But i makes no sense to me.

When /usr gets unmounted before reboot in the scripts, if basename in not present in the mountpoint, the computer crashes instead of rebooting.

Snowman · 2007-04-14 00:14:06

Maybe the wireless scripts use it...

Submit a bug report.

mightymaan · 2007-04-16 16:54:17

Snowman
Maybe the wireless scripts use it...
Submit a bug report.

Turned off those daemons too still no correct reboot.
I'm going to try and get more ifo before I file a bug.

Maybe it has some thing to do with the kernel message I see on boot about not being able to detect the base address of the VIA 686 chipset and to supply it if known?
Where would I find this info and how do I tell the kernel on the load line?

Still dont really understand why the availability of the basename command has ANYTHING to do with it working or not tho.

Cerebral · 2007-04-16 18:35:58

quick grep on my system turns up:

$ sudo grep "basename" /etc/* /etc/*/*  /bin/* /lib/*
/etc/ppp/pppoe.conf:CF_BASE=`basename $CONFIG`
/etc/tripwire/twpol.txt:  /bin/basename                        -> $(SEC_CRIT) ;
/etc/vmware/installer.sh:    echo 'Usage: '"`basename "$0"`"' {kind|version|convertdb|uninstall}'
Binary file /bin/groups matches
Binary file /bin/login matches
Binary file /lib/libc-2.5.so matches
Binary file /lib/libc.so.6 matches
Binary file /lib/libdevmapper.a matches
Binary file /lib/libdevmapper.so matches
Binary file /lib/libdevmapper.so.1.02 matches
Binary file /lib/libncurses.so.5 matches
Binary file /lib/libncurses.so.5.6 matches
Binary file /lib/libutil-2.5.so matches
Binary file /lib/libutil.so.1 matches

So if you use pppoe maybe that has something to do with it. Can't verify the significance of those /lib and /bin matches though

Arch Linux

#1 2007-04-11 22:12:03

rc problems when /usr is on another partition

#2 2007-04-12 07:55:37

Re: rc problems when /usr is on another partition

#3 2007-04-12 14:51:16

Re: rc problems when /usr is on another partition

#4 2007-04-13 05:36:19

Re: rc problems when /usr is on another partition

#5 2007-04-13 13:47:24

Re: rc problems when /usr is on another partition

#6 2007-04-13 17:47:53

Re: rc problems when /usr is on another partition

#7 2007-04-13 23:32:29

Re: rc problems when /usr is on another partition

#8 2007-04-14 00:14:06

Re: rc problems when /usr is on another partition

#9 2007-04-16 16:54:17

Re: rc problems when /usr is on another partition

#10 2007-04-16 18:35:58

Re: rc problems when /usr is on another partition

Board footer