I've been trying to get KaOS installed properly for a couple of weeks and I am, unfortunately, about to give up and go back to Mint.
I followed the instructions under GPT partitioning (https://kaosx.us/docs/bios_gpt/). Looking at sda in the partition manager, it appears to be set up properly. I installed KaOS manually this time and created a separate home partition, and everything installed fine.
However, when I boot, I get "Invalid Partition Table". If I hit enter, it continues to boot and load properly, albeit a bit slowly. Looking at partition manager after install, Calimares converted the xfs root partition I created to ext4 and then installed.???
I have installed KaOS several times. In earlier installs I noticed something odd. When I used the automatic install option , it worked great, but Calimares creates a msdos partition table, even if I set sda as a gpt table beforehand. Could this be a hardware issue?
/media/todd/DELLRESTORE/Screenshot from 2020-07-25 17-29-17.png

SYSTEM INFORMATION
Operating System: KaOS (2020)
KDE Plasma Version: 5.19.3
KDE Frameworks Version: 5.72.0
Qt Version: 5.15.0
Kernel Version: 5.7.8-1
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-3340M CPU @ 2.70GHz
Memory: 3.8 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000
Machine: Type: Laptop System: Dell product: Latitude E5530 non-vPro v: 01 serial: <filter>
Chassis: type: 9 serial: <filter>
Mobo: Dell model: 05GRXT v: A00 serial: <filter> BIOS: Dell v: A21 date: 11/30/2018
Battery: ID-1: BAT0 charge: 55.6 Wh condition: 55.6/57.7 Wh (96%) volts: 12.6/11.1
model: SMP DELL P8TC721 serial: <filter> status: Full
CPU: Topology: Dual Core model: Intel Core i5-3340M bits: 64 type: MT MCP arch: Ivy Bridge
rev: 9 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21529
Speed: 3190 MHz min/max: 1200/3400 MHz Core speeds (MHz): 1: 3190 2: 3189 3: 3190
4: 3383
Graphics: Device-1: Intel 3rd Gen Core processor Graphics vendor: Dell driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:0166
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x76860Hz
OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 19.0.8 compat-v: 3.0
direct render: Yes
Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Dell
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20
Sound Server: ALSA v: k5.0.0-32-generic
Network: Device-1: Broadcom and subsidiaries BCM43228 802.11a/b/g/n vendor: Dell
driver: bcma-pci-bridge v: N/A port: f040 bus ID: 02:00.0 chip ID: 14e4:4359
Device-2: Broadcom and subsidiaries NetXtreme BCM5761 Gigabit Ethernet PCIe
vendor: Dell driver: tg3 v: 3.137 port: f040 bus ID: 0c:00.0 chip ID: 14e4:1681
IF: enp12s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 510.11 GiB used: 6.48 GiB (1.3%)
ID-1: /dev/sda vendor: Toshiba model: MK5061GSYN size: 465.76 GiB speed: 3.0 Gb/s
serial: <filter> temp: 46 C
ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive size: 29.81 GiB
serial: <filter>
ID-3: /dev/sdc type: USB model: USB Flash Memory size: 14.54 GiB serial: <filter>
RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0
bus ID: 00:1f.2 chip ID: 8086.282a
Partition: ID-1: / size: 1.88 GiB used: 61.1 MiB (3.2%) fs: overlay source: ERR-102
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002
Hub: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
chip ID: 8087:0024
Device-1: 1-1.2:3 info: Toshiba Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB /
PNY Attache 4GB Stick
type: Mass Storage driver: usb-storage rev: 2.0 chip ID: 0930:6545
Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002
Hub: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0
chip ID: 8087:0024
Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 1d6b:0002
Device-2: 3-1:2 info: Logitech Unifying Receiver type: Mouse,HID
driver: hid-generic,usbhid rev: 2.0 chip ID: 046d:c52f
Device-3: 3-2:3 info: Lexar Media type: Mass Storage driver: usb-storage rev: 2.0
chip ID: 05dc:c75c
Hub: 4-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 chip ID: 1d6b:0003
Sensors: System Temperatures: cpu: 52.0 C mobo: 43.0 C sodimm: 39.0 C
Fan Speeds (RPM): cpu: 3212

  • demm replied to this.

    Unfortunately, needed info is missing. Not clear if this is a BIOS or UEFI system, and installation log is needed, see:
    https://kaosx.us/docs

    ctfolmar Calimares converted the xfs root partition I created to ext4 and then installed.???

    XFS is default during the install & automated option, so no way will the installer just use ext4.

    ctfolmar but Calimares creates a msdos partition table, even if I set sda as a gpt table beforehand

    If you boot in BIOS mode, automated still defaults to msdos (there is work done upstream to at least move the automated - full disk install to GPT for BIOS too).

    ctfolmar Could this be a hardware issue?

    Probably boot option missed when starting Live mode (before ISO loads), most systems nowadays can boot in legacy BIOS or UEFI, you can select that in the BIOS menu.

          All I'm trying to do is put KaOS/Root on a 50GB partition and leave the rest of the drive for an ext4 HOME partition. I may want to add another distro in the future, so I don't want HOME to be xfs.
          Using the fully automated install provided a clean install, but I couldn't shrink the xfs partition to create the HOME partition. I didn't know at the time it couldn't be done.

          When I set my boot for UEFI, without legacy support, the live usb won't boot. When legacy support is on, it appears to create a bios boot. Which is fine with me, I don't care which boot I use. However, then I get the Invalid Partition Table error.
          If there is an easier way to do what I am attempting, I'm willing to re-install. I've done it so many times, I'm getting pretty good at it. I'm also learning alot about partition management. But, I'm ready to quit learning and start using.:

          BTW, thank you so much for your help.

          So far I can see no errors in the setup (though the formatted sda1 is not 8Mb but 42), and since you mention not being able to boot in UEFI mode, it could be the BIOS has issues with GPT setup (a few older laptops are known for this, but rare nowadays), so if you don't need GPT, it might be in this case msdos is the better choice (unless you can find something in the BIOS setting that allows you to switch to GPT).

          Ok, I was beginning to think it might be the laptop. I'll set it up as msdos and see what happens.

          It worked. I re-installed with a msdos partition. I have it all installed as I wanted and working as it should. I am a bit disappointed at npt being able to use gpt, but I have worked with logical partitions before, so it is not a big deal. I am really looking forward to getting settled into regular use of KaOS. Thank you again for your help, I really appreciate it.

          10 days later

          How do I mark his as solved?

          7 days later

          This issue came back after I installed OpenSuse Tumbleweed alongside KaOS. In the OpenSuse bootloader configuration I found a pull down menu with 2 options, GRUBEFI and GRUB2. It was set for GRUBEFI, I changed it to GRUB2 and my issue cleared itself up.