I have a HP ProLiant ML 350 running with Novell SLES 10 SP2. I have
several partitions using LVM.
These partitions are not mounted during boot. So the system is not
working properly, i have a lot of errors during bootup.
I installed all patches automatically.
When i boot into runlevel 1, mount the partitions manually and type
init 5 afterwards, the systems starts up properly.
/etc/fstab looks good.
I had already one error before. While shutting down the system, the /-
filesystem did not umount properly. I found that the error was an
update of util-linux. I downgrades this package, and umount is working
properly.
But the LV's still don't mount while booting.
Thanks for any help.
Bernd
Volumes must be activated prior to mount. Usually the volumes are activated
from initial ramdisk by 'lvchange -ay'. Make sure you use LVM-enabled ramdisk.
-miky
-- 
Jakub Fišer AKA m...@MikyMaus.org
ICQ: I don't see kyou - http://icq.xmpp.cz/
JID: mr.Mi...@jabber.cz
Vyhýbejte se, prosím, přílohám typu Word nebo PowerPoint:
http://www.gnu.org/philosophy/no-word-attachments.cs.html
Please avoid sending me Word, PowerPoint, etc. attachments:
http://www.gnu.org/philosophy/no-word-attachments.html
Bernd
strange.. what does your /etc/fstab look like?
-m.
>
> strange.. what does your /etc/fstab look like?
>
> -m.
>
less /etc/fstab:
/dev/cciss/c0d0p3    /                    ext3
acl,user_xattr        1 1
/dev/cciss/c0d0p1    /boot                ext2
acl,user_xattr        1 2
/dev/vg1/lv3         /home                ext3
acl,user_xattr        1 2
/dev/vg1/lv4         /local               ext3
acl,user_xattr        1 2
/dev/vg1/lv1         /srv                 ext3
acl,user_xattr        1 2
/dev/vg1/lv2         /var                 ext3
acl,user_xattr        1 2
/dev/vg1/lv5         /opt                 ext3
acl,user_xattr        1 2
/dev/cciss/c0d0p2    swap                 swap
defaults              0 0
proc                 /proc                proc
defaults              0 0
sysfs                /sys                 sysfs
noauto                0 0
debugfs              /sys/kernel/debug    debugfs
noauto                0 0
usbfs                /proc/bus/usb        usbfs
noauto                0 0
devpts               /dev/pts             devpts
mode=0620,gid=5       0 0
/dev/fd0             /media/floppy        auto
noauto,user,sync      0 0
Hopefully better tor read.
Bernd
> On 20 Apr., 15:31, Bernd <bernd.len...@arcor.de> wrote:
> > On 20 Apr., 11:25, Jakub Fišer <m...@MikyMaus.org> wrote:
> >
> > > strange.. what does your /etc/fstab look like?
> >
> > less /etc/fstab:
> /dev/cciss/c0d0p3    /         ext3       acl,user_xattr  1 1
> /dev/cciss/c0d0p1    /boot   ext2       acl,user_xattr  1 2
> /dev/vg1/lv3         /home      ext3       acl,user_xattr  1 2
> /dev/vg1/lv4         /local       ext3       acl,user_xattr  1 2
> /dev/vg1/lv1         /srv          ext3       acl,user_xattr  1 2
> /dev/vg1/lv2         /var          ext3       acl,user_xattr  1 2
> /dev/vg1/lv5         /opt         ext3       acl,user_xattr  1 2
> ...
> 
This really looks OK. And you can forget my previous post - I thought you had
your / on an LV. If your root is not on LV you need no LVM support in
ramdisk at all..
Am I getting it right that only LVs aren't mounted while the rest is? 
Anyway, you mentioned some error messages - could you post them please? I'm out
of trumphs...
After boot only / and securityfs are mounted. So not only LV's are
missing, also things like /proc, /dev, the boot-Partition ...
I try to copy all error messages to the forum:
...
/var/log/boot.msg:
touch: cannot touch `/var/lock/subsys/PowerChute': No such file or
directory
...
Initializing random number generator/etc/init.d/random: line 40: /var/
lib/misc/random-seed: No such file or directory
chmod: cannot access `/var/lib/misc/random-seed': No such file or
directory
failed
...
startproc: execve (/usr/bin/dbus-daemon) [ /usr/bin/dbus-daemon --
system ], [touch: cannot touch `/var/lock/subsys/earlysyslog': No such
file or directory
...
Starting resource manager/etc/init.d/resmgr: line 68: cd: /var/run/
resmgr/classes: No such file or directory
...
touch: cannot touch `/var/lib/acpi/laptop_modules': No such file or
directory
/etc/init.d/acpid: line 164: /var/lib/acpi/laptop_modules: No such
file or directory
acpid: added /etc/init.d/acpid: line 87: /var/lib/acpi/laptop_modules:
No such file or directory
to /var/lib/acpi/laptop_modulesdone
...
Starting HAL daemon/usr/sbin/hald: error while loading shared
libraries: libgobject-2.0.so.0: cannot open shared object file: No
such file or directory
...
/etc/init.d/hpasm: line 40: /opt/compaq/hpasm/etc/hpasm: No such file
or directory
cmanic: No such file or directory
...
Starting nfsboot (sm-notify) /var/lib/nfs/sm: No such file or
directory
/var/lib/nfs/sm.bak: No such file or directory
...
touch: cannot touch `/var/lock/subsys/smbfs': No such file or
directory
...
Starting irqbalance /usr/sbin/irqbalance: error while loading shared
libraries: libglib-2.0.so.0: cannot open shared object file: No such
file or directory
startproc:  exit status of parent of /usr/sbin/irqbalance: 127
failed
Starting Name Service Cache Daemonfailed
...
Starting powersaved: /usr/sbin/powersaved: error while loading shared
libraries: libgobject-2.0.so.0: cannot open shared object file: No
such file or directory
startproc:  exit status of parent of /usr/sbin/powersaved: 127
failed
Missing privilege separation directory: /var/lib/empty
Initializing the PostgreSQL database at location /var/lib/pgsql/
datasu: warning: cannot change directory to /var/lib/pgsql: Permission
denied
-su: /var/lib/pgsql/.bash_profile: Keine Berechtigung
-su: initlog: Keine Berechtigung
failed
You can find a log of the initialisation in ~postgres/initlog .
Starting mail service (Postfix)failed
...
Starting /usr/sbin/cpqacuxe Can not run because of HP System
Management Homepage is not started or uninstalled.
Please try to use /etc/init.d/hpsmhd start to start it.
startproc:  exit status of parent of /usr/sbin/cpqacuxe: 1
failed
...
Starting CRON daemon/var/spool/cron: No such file or directory
/var/spool/cron: mkdir: No such file or directory
startproc:  exit status of parent of /usr/sbin/cron: 1
failed
...
/etc/init.d/nmu: line 29: /opt/PageScope_Net_Care/functions: No such
file or directory
Starting httpd2 (prefork) /etc/init.d/apache2: line 102: /var/log/
apache2/rcapache2.out: No such file or directory
cat: /var/log/apache2/rcapache2.out: No such file or directory
...
Failed services in runlevel 5: random haldaemon cmanic postfix
irq_balancer nscd postgresql powersaved apache2 cpqacu cron hpadu nmu
...
Bernd
> Jakub Fiser wrote:
> > Am I getting it right that only LVs aren't mounted while the rest is?
> > Anyway, you mentioned some error messages - could you post them please? I'm
> > out of trumphs...
> 
> After boot only / and securityfs are mounted. So not only LV's are
> missing, also things like /proc, /dev, the boot-Partition ...
All the error messages are just the consequence of not having the slices
mounted.
I see now, I was too focused on LVM that I missed some the point:
your /sys has the "noauto" option - now it all makes sense:
The /sys doesn't get mounted automatically (the "noauto" option) therefore udev
cannot work since, simply said, it needs /sys to communicate with kernel.
No udev, no /dev population. Nothing can be mounted 'cause there is nothing to
mount - no device nodes.
The "noauto" option means that system is aware of the filesystem, but it
doesn't get mounted automatically when "mount -a" is run (usually from init
scripts), it can however be mounted manually by "mount /dev/device" or
"mount /mountpoint".
Solution: either change all(*) "noauto" options to "auto", or erase them
("auto" is default).
(*) if you have some good reason to have some filesystems on manual, just leave
them as they are, but /sys must be automounted.
It is also generally a good idea to have all slices mounted with the "defaults"
option, unless you have a reason not to. See "man mount" and search for
"defaults" for more info.
You should also check your distribution init scripts. Mine (Arch Linux) for
example do the system mounting (/proc and /sys) on their own with no need
of /etc/fstab entry.
Hope this helps,
-miky
unfortunally i 'm making now a desaster recovery from the backup.
But maybe i have the error still afterwards, so i will test your
solution.
Thank you very much.
Bernd