I am trying to install SuSE 9.0 on an Intel machine but I want everything to be managed by the LVM. This should be possible but I'm having problems. I wonder if anyone can help? The main problem I'm having is that when the system first reboots towards the end of the installation process, I get lots of errors: [snip] Freeing initrd memory: 1223k freed VFS: Mounted root (ext2 filesystem) Loading kernel/drivers/scsi/scsi_mod.o insmod: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory Loading kernel/drivers/scsi/sd_mod.o insmod: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory Loading kernel/drivers/message/fusion/mptbase.o insmod: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory Loading kernel/drivers/message/fusion/mptscsih.o insmod: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory Loading kernel/drivers/scsi/ips.o insmod: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory Loading kernel/fs/reiserfs/reiserfs.o insmod: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory Loading kernel/drivers/md/lvm-mod.o insmod: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory createpartitions: /proc/partitions: no such file mount: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory vgscan: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory vgchange: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory umount: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory cat: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory umount: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory kmod: failed to exec /sbin/modprobe -s -k block-major-58: errno=2 VFS: Cannot open root device "3a01" on 3a:01 Please append a correct "root=" boot option Try booting with pci=noacpi, acpi=ht, or acpi=off on the command line DMI: BIOS: IBM -[T2E125AUS-1.06]-, 6/2/2003 System: IBM, eserver xSeries 335 -[867611X]- Kernel panic: VFS: Unable to mount root fs on 3a:01 I have tried setting up with: - /boot on a small non-LVM partition - swap on a non-LVM partition - everything else in LVM-managed logical volumes This doesn't work (although it does on Red Hat 8 and 9, let me say!) and produces the messages above. I have also tried partitioning the disc as one large LVM partition, then add logical volumes for swap space and a root filesystem. (I want to have extra filesystems but for the moment I'm just having one until I get things working.) This produces the same result (so LILO is perfectly capable of finding /boot on the logical volume.) I have tried using a Rescue System to build a new initrd with lvmcreate_initrd but this produces lots of 'unresolved symbols' errors. It does produce a new initrd anyway and I've tried using this by changing the symbollic link /boot/initrd to point at the new .gz file, but it made no difference. The only configuration that works so far is to have - Root filesystem on a non-LVM partition - swap on a non-LVM partition - everything else in the LVM I'm sure everything could go into the LVM though if the files in /boot were just built with the right stuff in them. Can anybody offer any help? Thanks Chris Eason ********************************************************************* Notice: This email is confidential and may contain copyright material of the John Lewis Partnership. If you are not the intended recipient, please notify us immediately and delete all copies of this message. (Please note that it is your responsibility to scan this message for viruses). Email to and from the John Lewis Partnership is automatically monitored for operational and lawful business reasons. ********************************************************************* John Lewis plc Registered in England 233462 Registered office 171 Victoria Street London SW1E 5NN Websites: http://www.johnlewis.com and http://www.waitrose.com
Chris_Eason@JohnLewis.co.uk wrote:
I am trying to install SuSE 9.0 on an Intel machine but I want everything to be managed by the LVM. This should be possible but I'm having problems. I wonder if anyone can help?
The main problem I'm having is that when the system first reboots towards the end of the installation process, I get lots of errors:
[snip] Freeing initrd memory: 1223k freed VFS: Mounted root (ext2 filesystem) Loading kernel/drivers/scsi/scsi_mod.o insmod: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory Loading kernel/drivers/scsi/sd_mod.o insmod: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
[snip] I don't remember what the exact issue (perhaps it was the grub package shipped with SuSE) but you need /boot, / and swap to be non LVM partitions. As pointed out by your errors above, while booting your server can't load necessary modules located in /lib/modules/2.4.21-166-default/
DMI: BIOS: IBM -[T2E125AUS-1.06]-, 6/2/2003 System: IBM, eserver xSeries 335 -[867611X]- Kernel panic: VFS: Unable to mount root fs on 3a:01
On an unrelated note.. what has your experience been like with SuSE 9.0 on the IBM xSeries servers? I will be installing 9.0 on an xSeries 225. I know IBM doesn't officially support SuSE 9.0 Professional on the xSeries so I'm curious as to how their technical support department deals with any requests for help or information.
The only configuration that works so far is to have
- Root filesystem on a non-LVM partition - swap on a non-LVM partition - everything else in the LVM
Yup that is how I set up my server.
On Monday 19 January 2004 13:26, Chris_Eason@JohnLewis.co.uk wrote:
I am trying to install SuSE 9.0 on an Intel machine but I want everything to be managed by the LVM. This should be possible but I'm having problems. I wonder if anyone can help?
The main problem I'm having is that when the system first reboots towards the end of the installation process, I get lots of errors:
[snip] Freeing initrd memory: 1223k freed VFS: Mounted root (ext2 filesystem) Loading kernel/drivers/scsi/scsi_mod.o insmod: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
I am unsure why you are having this problem. I have had no problem creating systems in which all but /boot resides on logical volumes, including / and swap. For example, on a Dell PE2650: # df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/system/root 262132 143664 118468 55% / /dev/sda2 54444 5482 46151 11% /boot /dev/system/opt 1155032 475800 679232 42% /opt /dev/system/srv 876512 34424 842088 4% /srv /dev/system/tmp 655336 38308 617028 6% /tmp /dev/system/usr 1994684 1051852 942832 53% /usr /dev/system/var 1470412 144668 1325744 10% /var tmpfs 1940932 0 1940932 0% /dev/shm /dev/data/home 262132 33088 229044 13% /home /dev/data/vm 16776700 32840 16743860 1% /vm That system's /var/log/boot.msg contains [snip] <6>Freeing initrd memory: 1186k freed <4>VFS: Mounted root (ext2 filesystem). <6>SCSI subsystem driver Revision: 1.00 <3>kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 <6>Red Hat/Adaptec aacraid driver (1.1.3 Nov 14 2003 00:40:58) <6>AAC0: kernel 2.7.4 build 3170 <6>AAC0: monitor 2.7.4 build 3170 <6>AAC0: bios 2.7.0 build 3170 <6>AAC0: serial eed021d3fafaf001 <6>scsi0 : percraid <4> Vendor: DELL Model: PERCRAID RAID5 Rev: V1.0 <4> Type: Direct-Access ANSI SCSI revision: 02 <4>Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0 <4>SCSI device sda: 106633728 512-byte hdwr sectors (54596 MB) <4>sda: Write Protect is off <6>Partition check: <6> sda: sda1 sda2 sda3 sda4 <6>lvm-mp: allocating 42 lowmem entries at cdfb0000 <6>LVM version 1.0.5+(mp-v6c)(22/07/2002) module loaded <4>lvm -- lvm_blk_ioctl: unknown cmd 0x5310 <4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device lvm(58,0)) ... <4>for (lvm(58,0)) <4>Using r5 hash to sort names <4>VFS: Mounted root (reiserfs filesystem) readonly. <5>Trying to move old root to /initrd ... failed <5>Unmounting old root <5>Trying to free ramdisk memory ... okay <6>Freeing unused kernel memory: 188k freed <6>md: Autodetecting RAID arrays. <6>md: autorun ... <6>md: ... autorun DONE. <4>reiserfs: enabling write barrier flush mode <6>Adding Swap: 262136k swap-space (priority 42) <4>reiserfs: found format "3.6" with standard journal <4>reiserfs: enabling write barrier flush mode <4>reiserfs: using ordered data mode <4>reiserfs: checking transaction log (device lvm(58,4)) ... [snip] That system's initrd content follows. Note the presence of libc.so.6. # ls -lR /tmp/initrd /tmp/initrd: total 11 drwxr-xr-x 9 root root 1024 2003-12-31 14:00 . drwxrwxrwt 16 root root 512 2004-01-21 11:03 .. drwxr-xr-x 2 root root 1024 2003-12-31 14:00 bin drwxr-xr-x 3 root root 1024 2003-12-31 14:00 dev drwxr-xr-x 3 root root 1024 2003-12-31 14:00 etc drwxr-xr-x 4 root root 1024 2003-12-31 12:50 lib -rwxr-xr-x 1 root root 1278 2003-12-31 14:00 linuxrc drwxr-xr-x 2 root root 1024 2003-12-31 14:00 mnt drwxr-xr-x 2 root root 1024 2003-12-31 14:00 proc drwxr-xr-x 2 root root 1024 2003-12-31 14:00 sbin /tmp/initrd/bin: total 192 drwxr-xr-x 2 root root 1024 2003-12-31 14:00 . drwxr-xr-x 9 root root 1024 2003-12-31 14:00 .. -rwxr-xr-x 1 root root 56132 2003-09-23 13:29 ash -rwxr-xr-x 1 root root 15224 2003-09-23 13:51 cat -rwsr-xr-x 1 root root 77488 2003-09-23 13:12 mount -rwsr-xr-x 1 root root 40788 2003-09-23 13:12 umount /tmp/initrd/dev: total 3 drwxr-xr-x 3 root root 1024 2003-12-31 14:00 . drwxr-xr-x 9 root root 1024 2003-12-31 14:00 .. crw------- 1 root root 5, 1 2003-12-31 14:00 console crw-rw---- 1 root root 29, 0 2003-12-31 14:00 fb0 crw-r----- 1 root root 109, 0 2003-12-31 12:38 lvm brw-rw---- 1 root root 9, 0 2003-12-31 14:00 md0 crw-rw-rw- 1 root root 1, 3 2003-12-31 14:00 null lrwxrwxrwx 1 root root 4 2003-12-31 14:00 ram -> ram0 brw-rw---- 1 root root 1, 0 2003-12-31 14:00 ram0 brw-rw---- 1 root root 1, 1 2003-12-31 14:00 ram1 brw-rw---- 1 root root 1, 2 2003-12-31 14:00 ram2 lrwxrwxrwx 1 root root 4 2003-12-31 14:00 ramdisk -> ram0 drwxr-xr-x 2 root root 1024 2003-12-31 14:00 system crw-rw---- 1 root root 4, 1 2003-12-31 14:00 tty1 crw-rw---- 1 root root 4, 2 2003-12-31 14:00 tty2 crw-r--r-- 1 root root 1, 5 2003-12-31 14:00 zero /tmp/initrd/dev/system: total 2 drwxr-xr-x 2 root root 1024 2003-12-31 14:00 . drwxr-xr-x 3 root root 1024 2003-12-31 14:00 .. brw-rw---- 1 root disk 58, 0 2003-12-31 12:41 root /tmp/initrd/etc: total 4 drwxr-xr-x 3 root root 1024 2003-12-31 14:00 . drwxr-xr-x 9 root root 1024 2003-12-31 14:00 .. -rw-r--r-- 1 root root 29 2003-12-31 14:00 fstab drwxr-xr-x 2 root root 1024 2003-12-31 14:00 lvmtab.d /tmp/initrd/etc/lvmtab.d: total 2 drwxr-xr-x 2 root root 1024 2003-12-31 14:00 . drwxr-xr-x 3 root root 1024 2003-12-31 14:00 .. /tmp/initrd/lib: total 315 drwxr-xr-x 4 root root 1024 2003-12-31 12:50 . drwxr-xr-x 9 root root 1024 2003-12-31 14:00 .. drwxr-xr-x 2 root root 1024 2003-12-31 12:26 i686 -rwxr-xr-x 1 root root 112347 2003-09-23 19:05 ld-2.3.2.so lrwxrwxrwx 1 root root 11 2003-12-31 14:00 ld-linux.so.2 -> ld-2.3.2.so lrwxrwxrwx 1 root root 16 2003-12-31 14:00 liblvm-10.so.1 -> liblvm-10.so.1.0 -r-xr-xr-x 1 root root 202974 2003-09-24 09:22 liblvm-10.so.1.0 drwxr-xr-x 3 root root 1024 2003-12-31 13:59 modules /tmp/initrd/lib/i686: total 1436 drwxr-xr-x 2 root root 1024 2003-12-31 12:26 . drwxr-xr-x 4 root root 1024 2003-12-31 12:50 .. -rwxr-xr-x 1 root root 1461208 2003-09-23 19:05 libc.so.6 /tmp/initrd/lib/modules: total 3 drwxr-xr-x 3 root root 1024 2003-12-31 13:59 . drwxr-xr-x 4 root root 1024 2003-12-31 12:50 .. drwxr-xr-x 3 root root 1024 2003-12-31 13:59 2.4.21-144-smp4G /tmp/initrd/lib/modules/2.4.21-144-smp4G: total 3 drwxr-xr-x 3 root root 1024 2003-12-31 13:59 . drwxr-xr-x 3 root root 1024 2003-12-31 13:59 .. drwxr-xr-x 4 root root 1024 2003-12-31 13:59 kernel /tmp/initrd/lib/modules/2.4.21-144-smp4G/kernel: total 4 drwxr-xr-x 4 root root 1024 2003-12-31 13:59 . drwxr-xr-x 3 root root 1024 2003-12-31 13:59 .. drwxr-xr-x 4 root root 1024 2003-12-31 13:59 drivers drwxr-xr-x 3 root root 1024 2003-12-31 13:59 fs /tmp/initrd/lib/modules/2.4.21-144-smp4G/kernel/drivers: total 4 drwxr-xr-x 4 root root 1024 2003-12-31 13:59 . drwxr-xr-x 4 root root 1024 2003-12-31 13:59 .. drwxr-xr-x 2 root root 1024 2003-12-31 13:59 md drwxr-xr-x 3 root root 1024 2003-12-31 13:59 scsi /tmp/initrd/lib/modules/2.4.21-144-smp4G/kernel/drivers/md: total 62 drwxr-xr-x 2 root root 1024 2003-12-31 13:59 . drwxr-xr-x 4 root root 1024 2003-12-31 13:59 .. -rw-r--r-- 1 root root 59786 2003-11-13 20:10 lvm-mod.o /tmp/initrd/lib/modules/2.4.21-144-smp4G/kernel/drivers/scsi: total 170 drwxr-xr-x 3 root root 1024 2003-12-31 13:59 . drwxr-xr-x 4 root root 1024 2003-12-31 13:59 .. drwxr-xr-x 2 root root 1024 2003-12-31 13:59 aacraid -rw-r--r-- 1 root root 149933 2003-11-13 20:10 scsi_mod.o -rw-r--r-- 1 root root 18418 2003-11-13 20:10 sd_mod.o /tmp/initrd/lib/modules/2.4.21-144-smp4G/kernel/drivers/scsi/aacraid: total 48 drwxr-xr-x 2 root root 1024 2003-12-31 13:59 . drwxr-xr-x 3 root root 1024 2003-12-31 13:59 .. -rw-r--r-- 1 root root 45220 2003-11-13 20:10 aacraid.o /tmp/initrd/lib/modules/2.4.21-144-smp4G/kernel/fs: total 3 drwxr-xr-x 3 root root 1024 2003-12-31 13:59 . drwxr-xr-x 4 root root 1024 2003-12-31 13:59 .. drwxr-xr-x 2 root root 1024 2003-12-31 13:59 reiserfs /tmp/initrd/lib/modules/2.4.21-144-smp4G/kernel/fs/reiserfs: total 281 drwxr-xr-x 2 root root 1024 2003-12-31 13:59 . drwxr-xr-x 3 root root 1024 2003-12-31 13:59 .. -rw-r--r-- 1 root root 281786 2003-11-13 20:10 reiserfs.o /tmp/initrd/mnt: total 2 drwxr-xr-x 2 root root 1024 2003-12-31 14:00 . drwxr-xr-x 9 root root 1024 2003-12-31 14:00 .. /tmp/initrd/proc: total 2 drwxr-xr-x 2 root root 1024 2003-12-31 14:00 . drwxr-xr-x 9 root root 1024 2003-12-31 14:00 .. /tmp/initrd/sbin: total 223 drwxr-xr-x 2 root root 1024 2003-12-31 14:00 . drwxr-xr-x 9 root root 1024 2003-12-31 14:00 .. -rwxr-xr-x 1 root root 9311 2003-09-23 13:31 insmod -rwxr-xr-x 1 root root 177466 2003-09-23 13:31 insmod.old -r-xr-xr-x 1 root root 20140 2003-09-24 09:22 vgchange -r-xr-xr-x 1 root root 13572 2003-09-24 09:22 vgscan
On Wednesday 21 January 2004 17:17, Gary Gapinski wrote:
I am unsure why you are having this problem. I have had no problem creating systems in which all but /boot resides on logical volumes, including / and swap.
Why would you want to have swap on LVM anyway?
On Wed, 2004-01-21 at 12:05, Gary Gapinski wrote:
On Wednesday 21 January 2004 11:25, Anders Johansson wrote:
Why would you want to have swap on LVM anyway?
So I can manage it as I do all the other volumes. It's only used on rare occasions.
I was never aware of anything to manage concerning the swap partition, must be something new. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
On Wednesday 21 January 2004 14:01, Kenneth Schneider wrote:
On Wed, 2004-01-21 at 12:05, Gary Gapinski wrote:
On Wednesday 21 January 2004 11:25, Anders Johansson wrote:
Why would you want to have swap on LVM anyway?
So I can manage it as I do all the other volumes. It's only used on rare occasions.
I was never aware of anything to manage concerning the swap partition, must be something new.
Swap is just a chunk of storage, and I find LVM the easiest way to manage storage.
On Wed, 2004-01-21 at 14:36, Gary Gapinski wrote:
On Wednesday 21 January 2004 14:01, Kenneth Schneider wrote:
On Wed, 2004-01-21 at 12:05, Gary Gapinski wrote:
On Wednesday 21 January 2004 11:25, Anders Johansson wrote:
Why would you want to have swap on LVM anyway?
So I can manage it as I do all the other volumes. It's only used on rare occasions.
I was never aware of anything to manage concerning the swap partition, must be something new.
Swap is just a chunk of storage, and I find LVM the easiest way to manage storage.
The problem with having swap on a file system is it is really slow compared to a raw disk partition. That is why 99.9% of sysadmins us a raw partition for swap. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
On Wednesday 21 January 2004 15:04, Kenneth Schneider wrote:
The problem with having swap on a file system is it is really slow compared to a raw disk partition. That is why 99.9% of sysadmins us a raw partition for swap.
Who said anything about file systems? I use logical volumes. Partitions are quite awkward in comparison to logical volume management.
The problem with having swap on a file system is it is really slow compared to a raw disk partition. That is why 99.9% of sysadmins us a raw partition for swap.
Hi Ken. I also prefer raw swap vs file system swap, just what i learned also when I first started sysadmin-ing (and at the time, it was true). And it just seems intuitively true since raw swap you bypass the one layer of overhead. I've heard that recently it just depends on the disks. Modern disks are faster and that you may not notice much of a difference anymore. Especially since swapping out to a disk will slow you down anyway (raw or filesystem). Has anyone on this list performed any such tests? I haven't and would be interested in hearing from anybody who has. Ben Yau
From tests done when drives first started exceeding 4gig and 64meg drive ram caches so a year or so ago), it all depends on cache sizes and block sizes. If your working with files greater than the ram cache of the drive, raw is worse as the cache has to add start/end blocks to file splits before writing to disc, if not it just writes and reads it straight. I hope that makes some sence. regards scsijon At 01:55 PM 22/01/2004, Ben Yau wrote:
The problem with having swap on a file system is it is really slow compared to a raw disk partition. That is why 99.9% of sysadmins us a raw partition for swap.
Hi Ken.
I also prefer raw swap vs file system swap, just what i learned also when I first started sysadmin-ing (and at the time, it was true). And it just seems intuitively true since raw swap you bypass the one layer of overhead.
I've heard that recently it just depends on the disks. Modern disks are faster and that you may not notice much of a difference anymore. Especially since swapping out to a disk will slow you down anyway (raw or filesystem).
Has anyone on this list performed any such tests? I haven't and would be interested in hearing from anybody who has.
Ben Yau
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (7)
-
Anders Johansson -
Avtar Gill -
Ben Yau -
Chris_Eason＠JohnLewis.co.uk -
Gary Gapinski -
Kenneth Schneider -
scsijon