LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-02-2019, 02:49 PM   #1
pr0xibus
Member
 
Registered: Apr 2004
Location: Scotland
Distribution: Slackware
Posts: 164

Rep: Reputation: 24
Slackware-Current Install Issue LVM


Evening folks

So decided to remove one of my SSD's from another computer running slackware and put it in my main PC and do a new install of Current.

I will usually clear the table to start with

Code:
(gdisk /dev/sda) x then z to zap the table
then Ill create the partitions

Code:
(gdisk /dev/sda) 1 Partition of ef00 and 1 partition of 8e00
Code:
Mkfs.vfat -F 32 /dev/sda1
Code:
pvcreate /dev/sda2
Code:
vgcreate blah /dev/sda2
Code:
lvcreate 3 partitions swap / root / home
Code:
mkswap && swapon /dev/blah/lv_swap
The first problem I noticed that after all of the LVM commands I get a small error "Failed to Clear Hint File"

I didnt think it was much of a problem as it continues fine

When I setup and start to configure the partitions I get a list of 6 partitions instead of 3

3 will start with /dev/VG's
3 will start with /dev/mapper/VG's/

So on my first install I selected the /dev/VG's as my default.

Once installed I

Code:
Chroot /mnt
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh /boot/vmlinuz-generic-kernel ver
and copy the relevant initrd and kernel to /boot/efi/EFI/Slackware and edit elilo

So far so good.

But on reboot nothing. No Slackware, just straight to BIOS.

listing my disk on the bios shows just the disk name nothing else, usually I can see at least another partition.

So i go through the install again but this time select the relevant /dev/mapper/VG instead of the /dev/VG's. Continue with the install and reboot etc and all works fine.

So finally to the questions.

What would the Hint File refer too?
Whats the difference and or Why do I need to select /dev/mapper instead of /dev/VG's.

Apologies I cant be more specific or with any important information as the second time round the install went fine. Just curious to see if anyone else has had this issue


The ONLY difference from now and every other time I have installed Slackware is this time round I used Aliens usb ISO, Previously I had used another slackware ISO from erm I think Didier
 
Old 12-03-2019, 08:15 AM   #2
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 569

Rep: Reputation: 172Reputation: 172
Are you creating an initrd and does it include LVM?
 
Old 12-03-2019, 09:30 AM   #3
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, arch, ubuntu, others
Posts: 3,673

Rep: Reputation: 606Reputation: 606Reputation: 606Reputation: 606Reputation: 606Reputation: 606
If there are not other systems on the computer, coping the contents /boot/efi/EFI/Slackware/ to /boot/efi/EFI/BOOT/ and copy the lilo.efi to /boot/efi/EFI/BOOT/bootx64.efi, or use efibootmgr to register efi loader to the bios uefi-firmware

Last edited by colorpurple21859; 12-03-2019 at 10:03 AM.
 
Old 12-04-2019, 02:07 AM   #4
pr0xibus
Member
 
Registered: Apr 2004
Location: Scotland
Distribution: Slackware
Posts: 164

Original Poster
Rep: Reputation: 24
Morning folks

Quote:
Chuck56 Are you creating an initrd and does it include LVM?
Yup Initrd was created and included the relevant contents.

Quote:
colorpurple21859 If there are not other systems on the computer, coping the contents /boot/efi/EFI/Slackware/ to /boot/efi/EFI/BOOT/ and copy the lilo.efi to /boot/efi/EFI/BOOT/bootx64.efi, or use efibootmgr to register efi loader to the bios uefi-firmware
No other OS's on the computer only Slackware.

1. The problem here lies that on setup and after selecting the /dev/logicalvolumes and including the F32 on /dev/sda1 no partions are found on reboot

2. yet on setup and selecting the /dev/mapper/logicalvolumes it all works just fine

Using I think Didiers ISO for UEFI support all i used to select was /dev/logicalvolumes, using AlienBobs script to create a new USB i need to select /dev/mapper/logicalvolumes

As I said in my OP its not a problem now as it all works but just wanted to know about the "Hint File" after each LVM command and why this time around it needs to be /dev/mapper/logicalvolume instead.

Cheers for the replies folks
 
Old 12-04-2019, 05:07 AM   #5
GazL
LQ Guru
 
Registered: May 2008
Posts: 5,298
Blog Entries: 18

Rep: Reputation: 3063Reputation: 3063Reputation: 3063Reputation: 3063Reputation: 3063Reputation: 3063Reputation: 3063Reputation: 3063Reputation: 3063Reputation: 3063Reputation: 3063
The hints file is a cache that speeds up some lvm operations, usually /run/lvm/hints. Judging by your report, it sounds like the install initrd is having difficulties accessing/creating it, but that's just a guess.

The /dev/vgname/lvname devices are convenience symlinks created by udev. They will point to the same /dev/dm-* file as the /dev/mapper/vgname-lvname symlinks. Presenting both sets to the user during the setup dialog is certainly confusing to the uninitiated and a little de-duplication wouldn't hurt, but they should both point to the same device so it shouldn't matter which you select, but I suppose it's possible that the install scripts/initrd generation could be making some sort of bad decision when the /dev/vgname/* links are used.

disclaimer: I last installed clean back in 2016, so it's been a good while since I've looked into installer environment/initrd scripts and what have you, so this is all conjecture.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
slackware live current or slackware live current lemonade Slackware 5 03-23-2018 07:28 AM
[SOLVED] Slackware 14.2 glibc-2.23 vs Slackware Current glibc-2.24 and the Current 4.4.17 Kernel kjhambrick Slackware 10 08-13-2016 02:00 AM
[SOLVED] Script to build always a current ISO image of Slackware (slackware-current) robertjinx Slackware 2 12-09-2010 03:00 AM
Slackware64 -current vs Slackware -current or Slackware onebuck Slackware 16 06-23-2009 02:19 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:07 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration