Installing Slackware (everything) on LVM
1 Attachment(s)
I've been trying almost a day to install Slackware v13.37 64 bit using LVM on my server. I think I've followed everything from http://slackware.osuosl.org/slackwar...README_LVM.TXT.
- Created one partition for the whole hardisk and set Linux LVM as its type. - Created LVM Code:
$ pvcreate /dev/sda1 Could you guys point me to the right direction to solve this error? Thanks in advance. UPDATE Setup partitions: http://i.imgur.com/amkQl.png After installation: http://imgur.com/OLCag Edit lilo: http://imgur.com/u8bMl Run lilo: http://imgur.com/bxTJy fstab: http://imgur.com/KkSVP All images: http://imgur.com/amkQl,OLCag,u8bMl,bxTJy,KkSVP |
Hi,
I'm not exactly and expert so I may be totally wrong, but your system says something about not being able to mount "/dev/vg01/root" to "/mnt". Shouldn't it be mounting "/dev/vg01/root" to "/" instead? How did you configure your mountpoints during the setup? Could you past your /etc/fstab content (after chroot, of course)? Also, is it possible to bypass the error with Code:
mount -rt ext4 /dev/vg01/root / |
I'll get you more info later since I can't access the server remotely. But thanks for answering, I'll try my best providing any info you want.
I configured my server using the guide at http://slackware.osuosl.org/slackwar...README_LVM.TXT. It says that after the setup is complete, I should use Code:
chroot /mnt Code:
mkinitrd -c -k 2.6.37.6 -m ext4 -f ext4 -r /dev/vg01/root -L |
Hi again,
if these commands work fine for other computers then it could possibly be a kernel issue. I had a similar issue a few weeks ago (not exactly the same, though; I was installing an encrypted Slackware 13.37 64bit system). The "huge" kernel was responsible for the error, as I found out after switching to the "generic" kernel, which you apparently use. Maybe some newer kernel could do the trick for you. I hope there's an easier solution but since two other computers work fine after this procedure then my money is on kernel (not to mention you can't write anything to fix the error - your hardware seems not to be properly recognized). You surely know the procedure - install the system, import the new kernel source, chroot, compile, install, mkinitrd, edit /etc/lilo.conf if needed and run lilo. Natharran |
I still can't believe those commands won't work on that server. I'll try the installation again in a few days (maybe I'll also try with slackware-current/slackware v14). This time I'll type in letter by letter slowly. There has to be some stupid newbie mistake that I made. In case anyone interested, I'm installing this on Dell R710.
Code:
$ lspci |
Depending on the kernel you are using, you might have to include some of the LVM modules in the mkinitrd.
Cheers. |
Quote:
|
Quote:
As asked earlier, what's the contents of /etc/fstab. You could also take a look at the comments in /etc/rc.d/rc.S regarding how the init process activates LVM, although I'm not sure exactly how that works, if you boot from an LVM partition. Quote:
Cheers. |
Quote:
|
I've updated the first post with all the necessary pictures. The content of the fstab is as follows:
Code:
/dev/vg01/swap swap swap defaults 0 0 |
Found the problem. I should not just load ext4 as the module instead I need to run this mkinitrd:
Code:
mkinitrd -c -k 2.6.37.6 -f ext4 -r /dev/vg01/root -m mptbase:mptscsih:mptsas:usbhid:ehci-hcd:uhci-hcd:jbd2:mbcache:ext4 -L -u -o /boot/initrd.gz |
All times are GMT -5. The time now is 11:16 PM. |