SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I was installing Slackware 14.1 64-bit in Vmware workstation with a different partition scheme than I'm used to of. I wanted LVM with xfs root and btrfs home. So my partition scheme was :-
Normal partitions :-
/boot ext2 - 100mb
swap - 2GB
I followed exactly the same steps as mentioned in official README_LVM.txt, except that the root FS I used was xfs and for home btrfs. And there was no 3.10.17-smp kernel, just 3.10.17 and thus created the initrd accordingly.
It seems /dev/myvg/root is trying to mount in /mnt (which doesn't exist, since it shouldn't)... It should be mounted in '/' ...
Check that '/etc/lilo.conf' (from that partition) is correct and possibly redo your initrd image
P.S. it is ok to use the Slackware installation disk if you need a clean simple console... Basicaly, instead of running 'setup' you should mount the root partition and chroot to it ( mkdir -p /mnt && mount -t xfs /dev/myvg/root /mnt && chroot /mnt ) .. From there on, recheck lilo configuration (and maybe reinstall it) and redo the init image... Insure that the -r parameter for the mkinitrd command is '-r /dev/myvg/root'
Last edited by Smokey_justme; 02-27-2014 at 05:49 AM.
It seems /dev/myvg/root is trying to mount in /mnt (which doesn't exist, since it shouldn't)... It should be mounted in '/' ...
Check that '/etc/lilo.conf' (from that partition) is correct and possibly redo your initrd image
P.S. it is ok to use the Slackware installation disk if you need a clean simple console... Basicaly, instead of running 'setup' you should mount the root partition and chroot to it ( mkdir -p /mnt && mount -t xfs /dev/myvg/root /mnt && chroot /mnt ) .. From there on, recheck lilo configuration (and maybe reinstall it) and redo the init image... Insure that the -r parameter for the mkinitrd command is '-r /dev/myvg/root'
That's the strangest thing.
I did the steps you mentioned above. The LVs were inactive so I activated the VG using vgchange -a y first.
The /etc/fstab looks totally fine:-
Previously I created initrd using :-
# $( /usr/share/mkinitrd/mkinitrd_command_generator.sh -r )
This time I did it the manual way :-
# mkinitrd -c -k 3.10.17 -m xfs -f xfs -r /dev/myvg/root -L
The lilo also looked pretty normal, however when I ran #lilo, it threw an error of /proc/partitions not found and after reboot I'm still at square 1. The same error, mounting on /mnt, why oh why?
That's the strangest thing.
I did the steps you mentioned above. The LVs were inactive so I activated the VG using vgchange -a y first.
The /etc/fstab looks totally fine:-
Previously I created initrd using :-
# $( /usr/share/mkinitrd/mkinitrd_command_generator.sh -r )
This time I did it the manual way :-
# mkinitrd -c -k 3.10.17 -m xfs -f xfs -r /dev/myvg/root -L
The lilo also looked pretty normal, however when I ran #lilo, it threw an error of /proc/partitions not found and after reboot I'm still at square 1. The same error, mounting on /mnt, why oh why?
Did you install lilo to MBR or root? Lilo can't boot if it has been installed to a root partition formatted with XFS. make sure it is installed to MBR.
Did you install lilo to MBR or root? Lilo can't boot if it has been installed to a root partition formatted with XFS. make sure it is installed to MBR.
Hi gezley, I'm aware of that and thus I installed it in MBR.
why is it trying to mount root to /mnt?
Ok, I've created an initrd and browse over the init.. It is normal to mount in /mnt and 'switch_root' after...
So now, can you please (at the console after the error) do an 'ls /', 'ls /sbin' and 'ls /dev/myvg'. Check that /mnt folder does exist and that /sbin/vgchange executable file does exist? And, ofcourse... see that /dev/myvg/root device file exists...
I think you're missing one of these for some reason...
Ok, so for some reason you logical volume isn't recognized... hmm... at this point, since I don't really use LVM I'm kind of out of ideeas... Maybe I'll give it a shot later on a Virtual box.. Or maybe someone else knows more about this..
Ok, so for some reason you logical volume isn't recognized... hmm... at this point, since I don't really use LVM I'm kind of out of ideeas... Maybe I'll give it a shot later on a Virtual box.. Or maybe someone else knows more about this..
For now, sorry..
Not a problem mate, thanks for the help so far. I've been using all my CentOS VMs with LVM and never faced such problem. Lets see what I'm missing here.
Anybody else with any suggestion please?
This will probably fail but still, it might be worth trying:
The mkinitrd in 14.1 has a bug which requires you to use the -L flag even if you only need to unlock a LUKS partition wit the -C flag. Just -C should suffice, but not all files are copied to initrd.gz unless you pass -L too. So maybe you could try adding -C to see if the same weird thing happens.
This will probably fail but still, it might be worth trying:
The mkinitrd in 14.1 has a bug which requires you to use the -L flag even if you only need to unlock a LUKS partition wit the -C flag. Just -C should suffice, but not all files are copied to initrd.gz unless you pass -L too. So maybe you could try adding -C to see if the same weird thing happens.
Hi, I'm not using LUKS. However thanks for noticing. I'll read more about the bug.
I was attempting to reproduce this using libvirt and virt-manager, but lilo doesn't recognize the virtualio disk type that is used during the installation. I will give it another try this evening, but what I had attempted to do was:
I don't try to run lilo during the initial setup. There's no initrd created, so whatever lilo does at that point won't be correct.
After setup is finished and you are back at the command prompt, I did these additional steps:
Once inside the chroot, I ran the mkinitrd_command_generator.sh script, then ran liloconfig and then ran lilo itself. Things worked as expected up to executing lilo, which failed when it didn't recognize the virtual disk's characteristics.
OK, I was able to install lilo on my virtual image and the system booted correctly.
liloconfig was pretty useless, however. I ran it, selected "simple", and chose reasonable answers to the questions. When it failed, it at least left /etc/lilo.conf behind that I could edit.
So, after "setup" completed, I exited setup and then ran the following commands...
Code:
mount -R /proc /mnt/proc
mount -R /sys /mnt/sys
mount -R /dev /mnt/dev
chroot /mnt
$(/usr/share/mkinitrd/mkinitrd_command_generator.sh -r)
liloconfig
selected "simple", answered questions with reasonable values, watched lilo installation fail.
/usr/share/mkinitrd/mkinitrd_command_generator.sh -l /boot/vmlinuz-generic-3.10.17 >>/etc/lilo.conf
edited /etc/lilo.conf to remove the section liloconfig added
lilo -v
exit
...and then shut down the VM and restarted it since the lilo output told me that lilo worked.
FWIW, mkinitrd_command_generator.sh in my case provided the following command line:
I also changed the boot device in /etc/lilo.conf to /dev/vda and added the line "device = /dev/vda bios=0x80 max-partitions=7" so that lilo would work. You probably won't have to do that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.