Koozali.org: home of the SME Server

Diskusage contrib

Online Jean-Philippe Pialasse

  • *
  • 2,298
  • +8/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Diskusage contrib
« Reply #15 on: March 15, 2021, 02:44:37 AM »
The gui disk partition icon showed a !  and Error checking storage configuration, presumably due to the previous install as it indicated not enough disk space for an install.
I used the gui to delete all the existing partitions.
I then clicked done and was offered a choice to manually partition  or accept auto install. I don't recall the exact wordings but can run install again and fully document if required.

that is the reason of you partitionning. you did not used SME default partitionning but CentOS one. Your disks were not empty, then our kickstart did not use them to avoid data loss.
When GUI showed up it signal there was no disk ready. CentOS default is two partitions: /boot on XFS, and LVM for the rest. Within the LVM VG there are three LVs: swap, home, and root. Both /home and / are on XFS.

so you should use the disk utility to erase all partition then reboot to get the automatic partitionning or create yoir own raid.

- https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/sect-disk-partitioning-setup-x86#sect-custom-partitioning-x86
- https://forums.centos.org/viewtopic.php?t=51061

- https://docs.centos.org/en-US/centos/install-guide/CustomSpoke-x86/

note: not accusing here. just pointing something lacking documentation.
« Last Edit: March 15, 2021, 02:50:17 AM by Jean-Philippe Pialasse »

Online TerryF

  • grumpy old man
  • *
  • 1,732
  • +3/-0
Re: Diskusage contrib
« Reply #16 on: March 15, 2021, 04:56:27 AM »
My bad as well, the GB size of disks did not register was seeing TB, damn, its that huge thing standing out you cant see.

Should have noticed, answer would have been simple..
qui scribit bis legit

Offline csn

  • *
  • 11
  • +0/-0
Re: Diskusage contrib
« Reply #17 on: March 15, 2021, 03:51:43 PM »
Thanks for the lsblk output. It sounds like the SME auto-partitioning hasn't worked if you were seeing an error in the installer - our logic should overwrite everything on the disks and set up a custom partitioning scheme ready for the installer to use - there should be nothing to do in the GUI.

From the 1M partition and no EFI I'm guessing you're using a BIOS rather than EFI system? If so, this is a known issue with beta 1 not supporting drives >2TB on BIOS systems.

I'm working on an updated ISO at the moment which it would be great to get you to test in the next couple of days.

Offline BobJF

  • 9
  • +0/-0
Re: Diskusage contrib
« Reply #18 on: March 15, 2021, 07:10:52 PM »
Yes, it's BIOS not EFI on the machine, although latest version. I was surprised that the installation required manual intervention as I know previous smeserver versions did wipe the disks after warning.
I believe on on of my many early tries at installing I did delete a raid congratulation on the three drives, deleted because after the installation the machine failed to boot from the raid disks. I looks like you're on the right track already.

Offline csn

  • *
  • 11
  • +0/-0
Re: Diskusage contrib
« Reply #19 on: March 15, 2021, 07:50:20 PM »
Yep, that sounds about right. The defaults would have created the RAID array but it wouldn't have booted due to the BIOS and >2TB combo.

Should be resolved this week - I'll share an ISO for you to test on the bug.