[SOLVED] Feb. 16 Slackware64-current iso will not recognize GPT
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.
Feb. 16 Slackware64-current iso will not recognize GPT
I'm using Eric's automatically generated ISO to install the sweet new February 16 Slackware64-current (glibc 2.21!). The problem is it won't recognize a GPT table, only MBR. I've never run into this issue before in the 500 or so times I've installed Slackware.
The message I get when entering setup is:
Code:
NO LINUX PARTITIONS DETECTED
There don't seem to be any partitions on this machine of type Linux.
...
Yet:
Code:
# gdisk -l /dev/sda
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Number Start (sector) End (sector) Size Code Name
1 2048 1953523711 931.5 GiB 8300 primary
Obviously I have condensed the output a little to save typing, but the partitioning is valid right?
I tried using both parted and gdisk to set up one big partition using GPT (w/ protective MBR), I even tried setting up the partitioning, formatting the big partition as ext4 (mkfs.ext4), and then rebooting, but am still receiving the same error.
This has never been an issue before (installing with the January 28 ISO did not have this problem, or any ISO I've installed back to 13.37).
P.S. MBR is recognized instantly.
Thanks for the help,
Ryan
Last edited by ryanpcmcquen; 02-17-2015 at 09:03 AM.
Reason: Grammar. Add more data.
I did a search through here, but I can't imagine what would be causing this. The only kernel change is related to APIC stuff, and the sysvinit changes just affect output.
Almost surely due to changes in util-linux. I've not looked at the installer, but perhaps it screen-scrapes something to determine presence of linux partitions, and util-linux changed the output format of that something. That's a place to start looking anyway...
All I know is that the script /sbin/probe (attached) in the initrd that makes the checks in Slackware64-14.1 and Slackware64-current is identical.
Here is the code snippet from /usr/lib/setup/setup that calls it (also unchanged):
Code:
# Before probing, activate any LVM partitions
# that may exist from before the boot:
vgchange -ay 1> /dev/null 2> /dev/null
if probe -l 2> /dev/null | grep -E 'Linux$' 1> /dev/null 2> /dev/null ; then
probe -l 2> /dev/null | grep -E 'Linux$' | sort 1> $TMP/SeTplist 2> /dev/null
else
dialog --title "NO LINUX PARTITIONS DETECTED" \
--msgbox "There don't seem to be any partitions on this machine of type \
Linux. You'll need to make at least one of these to install Linux. \
To do this, you'll need to leave 'setup', and make the partitions using \
'cfdisk' (MBR partitions) or 'cgdisk' (GPT partitions). For more \
information, read the 'setup' help file from the next menu." 10 64
I didn't investigate further.
Last edited by Didier Spaier; 02-17-2015 at 02:47 PM.
This gave me a good start. I'm not sure why, but removing the '$' from 'Linux$' in the if check fixes the issue. I tested it against having an 8300 type partition and a bf04 (I just wanted something that was definitely not 8300).
That seems reasonable, but without knowing what the probe used to output (i.e. in 14.1), I hate to say for sure.
EDIT: That ^^ was a reply to ryanpcmcquen, but it's pretty clear now (based on the post after ryan's) what the output used to be; thanks!
did get me through the install. But lilo had a weird error about a video adapter. I've attached a screenshot. I had to manually add a lilo entry after the installer finished:
image = /boot/vmlinuz
root = /dev/sda1
label = linux
read-only
Then I ran:
Code:
/mnt/sbin/lilo -C /mnt/etc/lilo.conf
The video adapter error was still there but 'linux' got added. I was able to reboot and the system seems fine. Running lilo after the reboot did not show the video adapter error.
I sent Pat a different fix for the issue, since pxesetup also depends on probe output and there was an additional issue detecting EFI system partitions.
The change I recommended to Pat was to add before the cat in /sbin/probe:
Code:
sed -i -e 's/ filesystem//g' $TMP/SeTfdisk
(Though I now realise you can just remove the -i from the sed and remove the cat command. Whoops.)
liloconfig depends on the probe output as well when run from an install disk. Line 539 of liloconfig is
# This is a different 'probe' than the function below.
PROBE() {
if [ -x /sbin/probe ]; then
/sbin/probe -l
Anyway don't worry: I'm pretty sure that Pat will cook his own fix or at least check carefully any proposed one, as he is very careful not to break anything in the installer
Last edited by Didier Spaier; 02-18-2015 at 11:00 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.