vgscan fails to find volume groups
I have been attempting to get LVM set up on a freshly-installed Slackware 8.0 system (custom 2.4.18 monolithic kernel, LVM 1.0.3, no kernel patches). It works fine in multi-user mode, it works fine in single-user mode, however I set up the single-user init script like this:
(/ is mounted read only at this point)
mount -o remount,rw /
vgscan
vgchange -a y
mount -o remount,ro /
(stock Slackware fsck and mount bits)
The only volume group I have contains one physical volume (/dev/sdb, on an Adaptec 7xxx controller). For some reason, vgscan doesn't pick up the volume group. The exit code is 0, and looking at the debug output it hits /dev/sdb and spits out the same messages as when it hits all the other devices.
As an experiment I put a call to sulogin before the vgscan and tried running it by hand; same thing happened. I tried running pvcreate (on the whole disk, and after creating an LVM partition /dev/sdb1) and it failed with error code 7.
As another experiment, I tried setting up a loopback filesystem on a file in the root directory. That worked perfectly; vgscan picked it up, vgchange activated it, and the rest of the init script ran fsck and mounted it. Other than setting up the loopback file the only thing I did was add a call to losetup before the vgscan.
Not sure if this is a problem with the kernel (i.e. SCSI driver) or a problem with LVM, or some boneheaded thing I'm doing wrong. Any advice you can give would be appreciated -- let me know if I can provide more information.
thanks,
jafager
Quoted 13 lines · Jason A. Fager
I have been attempting to get LVM set up on a freshly-installed Slackware 8.0 system (custom 2.4.18 monolithic kernel, LVM 1.0.3, no kernel patches). It works fine in multi-user mode, it works fine in single-user mode, however I set up the single-user init script like this:
(/ is mounted read only at this point)
mount -o remount,rw /
vgscan
vgchange -a y
mount -o remount,ro /
(stock Slackware fsck and mount bits)
Quoted 5 lines
The only volume group I have contains one physical volume (
/dev/sdb, on an Adaptec 7xxx controller). For some reason, vgscan doesn't pick up the volume group. The exit code is 0, and looking at the debug output it hits/dev/sdband spits out the same messages as when it hits all the other devices.
Hrm...you're root is mounted read-write, so the /etc directory should be able to be updated by the tools. Do you have /proc mounted at this point? I'm assuming the SCSI driver is loaded at this point as well...Can't think of anything else off the top of my head that would be wrong with that...
I'll see if I can reproduce on a system I have.
Regards,
Signature · 10 lines
AJ Lewis Sistina Software Inc. Voice: 612-638-0500 1313 5th St SE, Suite 111 E-Mail: [email protected] Minneapolis, MN 55414 http://www.sistina.com Current GPG fingerprint = 7792 2F3E 9D86 DA4C 9111 7837 982D 737B 9DBC 4EC9 -----Begin Obligatory Humorous Quote---------------------------------------- FATAL ERROR! SYSTEM HALTED! - Press any key to do nothing... -----End Obligatory Humorous Quote------------------------------------------
Jason,
can you access /dev/sdb while running the below part of your startup script?
IOW: is the Adaptec driver present then and does it work properly?
Regards,
Heinz -- The LVM Guy --
Quoted 36 lines · Jason A. Fager
I have been attempting to get LVM set up on a freshly-installed Slackware 8.0 system (custom 2.4.18 monolithic kernel, LVM 1.0.3, no kernel patches). It works fine in multi-user mode, it works fine in single-user mode, however I set up the single-user init script like this:
(/ is mounted read only at this point)
mount -o remount,rw /
vgscan
vgchange -a y
mount -o remount,ro /
(stock Slackware fsck and mount bits)The only volume group I have contains one physical volume (
/dev/sdb, on an Adaptec 7xxx controller). For some reason, vgscan doesn't pick up the volume group. The exit code is 0, and looking at the debug output it hits/dev/sdband spits out the same messages as when it hits all the other devices.As an experiment I put a call to sulogin before the vgscan and tried running it by hand; same thing happened. I tried running pvcreate (on the whole disk, and after creating an LVM partition
/dev/sdb1) and it failed with error code 7.As another experiment, I tried setting up a loopback filesystem on a file in the root directory. That worked perfectly; vgscan picked it up, vgchange activated it, and the rest of the init script ran fsck and mounted it. Other than setting up the loopback file the only thing I did was add a call to losetup before the vgscan.
Not sure if this is a problem with the kernel (i.e. SCSI driver) or a problem with LVM, or some boneheaded thing I'm doing wrong. Any advice you can give would be appreciated -- let me know if I can provide more information.
Quoted 8 lines
thanks,
jafager_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf Germany
[email protected] +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-