[linux-lvm] LVM

Thu Sep 13 02:04:17 UTC 2001

Dear Sir:

	I have placed below a copy of the dmesg output from my attempt at booting the /dev/vg/root I created. However, I then was able to boot using the /dev/hda1 (which has a ReiserFS non-LVM bootable partition).

	Any analysis you can provide would be well appreciated. I will try some of the issues you mention here within.

Linux version 2.4.8-12mdk (root at linux02) (gcc version 2.96 20000731 (Linux-Mandrake 8.0 2.96-0.48mdk)) #20 Wed Sep 12 04:22:13 PDT 2001
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001ffea800 (usable)
 BIOS-e820: 000000001ffea800 - 0000000020000000 (reserved)
 BIOS-e820: 00000000feea0000 - 00000000fef00000 (reserved)
 BIOS-e820: 00000000ffb80000 - 0000000100000000 (reserved)
On node 0 totalpages: 131050
zone(0): 4096 pages.
zone(1): 126954 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=linux_hda1 ro root=301 ramdisk=8192 hdb=ide-scsi idebus=66 ide0=dma ide1=dma
ide_setup: hdb=ide-scsi
ide_setup: idebus=66
ide_setup: ide0=dma
ide_setup: ide1=dma
Initializing CPU#0
Detected 997.833 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 1992.29 BogoMIPS
Memory: 512248k/524200k available (1164k kernel code, 11564k reserved, 312k data, 216k init, 0k highmem)
Dentry-cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: Before vendor init, caps: 0383f9ff 00000000 00000000, vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After vendor init, caps: 0383f9ff 00000000 00000000 00000000
CPU:     After generic, caps: 0383f9ff 00000000 00000000 00000000
CPU:             Common caps: 0383f9ff 00000000 00000000 00000000
CPU: Intel Pentium III (Coppermine) stepping 0a
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch at atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfc06e, last bus=8
PCI: Using configuration type 1
PCI: Probing PCI hardware
Unknown bridge resource 2: assuming transparent
Unknown bridge resource 2: assuming transparent
PCI: Using IRQ router PIIX [8086/244c] at 00:1f.0
PnP: PNP BIOS installation structure at 0xc00fe2d0
PnP: PNP BIOS version 1.0, entry at f0000:e2f4, dseg at 40
PnP: 14 devices detected total
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.14)
Starting kswapd v1.8
VFS: Diskquotas version dquot_6.5.0 initialized
ACPI: APM is already active, exiting
vesafb: framebuffer at 0xe8000000, mapped to 0xe0800000, size 32768k
vesafb: mode is 1024x768x16, linelength=2048, pages=20
vesafb: protected mode interface info at c000:6238
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
block: queued sectors max/low 340170kB/209098kB, 1024 slots per queue
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 66MHz system bus speed for PIO modes
PIIX4: IDE controller on PCI bus 00 dev f9
PIIX4: chipset revision 3
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xbfa0-0xbfa7, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xbfa8-0xbfaf, BIOS settings: hdc:DMA, hdd:pio
hda: IBM-DJSA-232, ATA DISK drive
hdb: TOSHIBA CD-RW/DVD-ROM SD-R2002, ATAPI CD/DVD-ROM drive
hdc: LS-120 SLIM3 00 UHD Floppy, ATAPI FLOPPY drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 62506080 sectors (32003 MB) w/1874KiB Cache, CHS=3890/255/63, UDMA(66)
ide-floppy driver 0.97
hdc: 1440kB, 2880 blocks, 512 sector size
hdc: 1440kB, 80/2/18 CHS, 150 kBps, 512 sector size, 720 rpm
Partition check:
 hda: hda1 hda2 hda3
 hdc: hdc1 hdc2 hdc3 hdc4
ide-floppy driver 0.97
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 32768)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Uncompressing.................................................................................................................................................................................................................................................................................done.
Freeing initrd memory: 869k freed
VFS: Mounted root (ext2 filesystem).
attempt to access beyond end of device
01:00: rw=0, want=8198 x(=0x), limit=8198
EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=8199, block=8197
attempt to access beyond end of device
01:00: rw=0, want=16390 x(=0x), limit=16390
EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=16387, block=16389
attempt to access beyond end of device
01:00: rw=0, want=8198 x(=0x), limit=8198
EXT2-fs error (device ramdisk(1,0)): ext2_read_inode: unable to read inode block - inode=8194, block=8197
reiserfs: checking transaction log (device 03:01) ...
Using r5 hash to sort names
ReiserFS version 3.6.25
VFS: Mounted root (reiserfs filesystem) readonly.
change_root: old root has d_count=2
Trying to unmount old root ... okay
Freeing unused kernel memory: 216k freed
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17519 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17519 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
LVM version 0.9.1_beta3  by Heinz Mauelshagen  (25/01/2001)
lvm -- Module successfully initialized
clm-6005: writing inode 17393 on readonly FS
clm-6005: writing inode 17519 on readonly FS
 hdc: hdc1 hdc2 hdc3 hdc4
 hdc: hdc1 hdc2 hdc3 hdc4
ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
end_request: I/O error, dev 16:01 (hdc), sector 0
 hdc: hdc1 hdc2 hdc3 hdc4
ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
end_request: I/O error, dev 16:02 (hdc), sector 0
 hdc: hdc1 hdc2 hdc3 hdc4
ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
end_request: I/O error, dev 16:03 (hdc), sector 0
 hdc: hdc1 hdc2 hdc3 hdc4
ide-floppy: hdc: I/O error, pc = 28, key =  5, asc = 21, ascq =  0
end_request: I/O error, dev 16:04 (hdc), sector 0
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6005: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6006: writing inode 17393 on readonly FS
clm-6005: writing inode 17393 on readonly FS
SCSI subsystem driver Revision: 1.00
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
  Vendor: TOSHIBA   Model: DVD-ROM SD-R2002  Rev: 1D26
  Type:   CD-ROM                             ANSI SCSI revision: 02
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
Linux Kernel Card Services 3.1.22
  options:  [pci] [cardbus] [pm]
PCI: Found IRQ 11 for device 02:0f.0
PCI: Sharing IRQ 11 with 00:1f.2
PCI: Sharing IRQ 11 with 02:0f.1
PCI: Sharing IRQ 11 with 02:0f.2
PCI: Found IRQ 11 for device 02:0f.1
PCI: Sharing IRQ 11 with 00:1f.2
PCI: Sharing IRQ 11 with 02:0f.0
PCI: Sharing IRQ 11 with 02:0f.2
Yenta IRQ list 06d8, PCI irq11
Socket status: 30000006
Yenta IRQ list 06d8, PCI irq11
Socket status: 30000006
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x378-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw at saw.sw.com.sg> and others
eth0: OEM i82557/i82558 10/100 Ethernet, 00:20:E0:66:C5:8A, I/O at 0xecc0, IRQ 11.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly 727095-002, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x04f4518b).
  Receiver lock-up workaround activated.
Installing knfsd (copyright (C) 1996 okir at monad.swb.de).
Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ...
SMSC Super-IO detection, now testing Ports 2F0, 370 ...
PnPBIOS: Parport found PNPBIOS PNP0401 at io=0378,0778 irq=7 dma=1
0x378: FIFO is 16 bytes
0x378: writeIntrThreshold is 8
0x378: readIntrThreshold is 8
0x378: PWord is 8 bits
0x378: Interrupts are ISA-Pulses
0x378: ECP port cfgA=0x10 cfgB=0x00
0x378: ECP settings irq=<none or set by other means> dma=<none or set by other means>
parport0: PC-style at 0x378 (0x778), irq 7, dma 1 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
lp0: using parport0 (interrupt-driven).

Very Respectfully, 

Stuart Blake Tener, IT3, USNR-R, N3GWG 
Beverly Hills, California
VTU 1904G (Volunteer Training Unit) 
stuart at bh90210.net 
west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 
east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 

Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) 

JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. 

Wednesday, September 12, 2001 7:00 PM

-----Original Message-----
From: Jason Edgecombe [mailto:jedgecombe at carolina.rr.com]
Sent: Wednesday, September 12, 2001 6:02 PM
To: stuart at bh90210.net
Cc: linux-lvm at sistina.com
Subject: Re: [linux-lvm] LVM

hi,

  according to reiserfs's FAQ:
http://www.reiserfs.org/faq.html#ReiserFS-as-root

you need the notail option on the /boot partition.
the fstab might look as follows:
/dev/hda1    /boot   reiserfs    defaults,notail  0 0
/dev/hda2    /   reiserfs    defaults  0 0

if there isn't the word "notail" in the fourth column of your root fstab
entry, then you ARE booting with tails.

according the lilo changelog:
ftp://brun.dyndns.org/pub/linux/lilo/CHANGES

lilo has been able to boot from a reiserfs partition with tail support
since version 21.6 (Oct. 1, 2000)

*under an rpm-based distro such as redhat or mandrake, "rpm -qi lilo"
should give you the version. (assuming you haven't downloaded lilo as a
tarball and compiled it.)

Both were last modified in August 2001, I don't know which to believe.
For safety sake, I made my /boot ext2. Most recent computers (within the
past two years) can boot from a partition after the 1024 boundary. I
just like to make a separate /boot at the beginning of the drive as a
precaution.

as for the matter of initrd's, this is the way that I understand it:
in a non-lvm root fs, your root fs type must either be compiled in or in
the initrd image.
in a lvm root, you MUST have an initrd even if lvm is compiled into the
kernel (not as a module) because you need to run a vgchange -ay and you
need your lvm config files in the initrd.

as for having /boot (booting the kernel) straight in an lvm fs, I have
no idea.

If I am wrong, someone please correct me.

Sincerely,
Jason Edgecombe

"IT3 Stuart B. Tener, USNR-R" wrote:
>         I am curious what version of lilo in fact supports ReiserFS tails. I am running Mandrake 8.0, and using the lilo supplied therewith, and have been booting a / partition as ReiserFS (with tails I believe, how do I check?).