Koozali.org, home of the SME Server

Diskusage contrib

Offline BobJF

  • 9
  • +0/-0
Diskusage contrib
« on: March 14, 2021, 08:33:31 AM »
Beta Diskusage contrib works giving expected output on test server. But, is this correct for an array of 3 x 4GB disks with a standard install?

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/kss-root   50G  3.6G   47G   8% /
devtmpfs              3.9G     0  3.9G   0% /dev
tmpfs                 3.9G   12K  3.9G   1% /dev/shm
tmpfs                 3.9G     0  3.9G   0% /sys/fs/cgroup
tmpfs                 3.9G  8.7M  3.9G   1% /run
/dev/sda2            1014M   68M  947M   7% /boot
/dev/mapper/kss-home   11T  344G   11T   4% /home
......

Offline TerryF

  • grumpy old man
  • *
  • 1,662
  • +1/-0
Re: Diskusage contrib
« Reply #1 on: March 14, 2021, 09:38:12 AM »
not a user but, looks as expected to me..

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/kss-root   50G  3.6G   47G   8% /
devtmpfs              3.9G     0  3.9G   0% /dev
/dev/sda2            1014M   68M  947M   7% /boot

Filesystem                      Size  Used Avail Use% Mounted on
/dev/mapper/kss-home   11T  344G   11T   4% /home

and thanks for giving the tyres a kick

has now been verified and will make its way to contribs repo shortly

Best to choose what to kick from this list..

https://bugs.contribs.org/buglist.cgi?action=wrap&bug_status=RESOLVED&f1=bug_status&list_id=93061&o1=notequals&product=SME%20Contribs&v1=CLOSED
« Last Edit: March 14, 2021, 09:54:05 AM by TerryF »
--
qui scribit bis legit

Offline BobJF

  • 9
  • +0/-0
Re: Diskusage contrib
« Reply #2 on: March 14, 2021, 10:15:00 AM »
Not an issue with the contrib but I am confused by the 11T home as I was under the impression a 3 disk install should be Raid 1 plus hot spare, 11T implies it's not a Raid array. I did have some initial problems getting the install completed.
......

Offline TerryF

  • grumpy old man
  • *
  • 1,662
  • +1/-0
Re: Diskusage contrib
« Reply #3 on: March 14, 2021, 10:39:47 AM »
Now need Mr raid guru who has massaged the sme10Beta1 install to be able to do what she does now..

I had thought that 3 disks would produce a Raid1 and 1 spare

a # cat /proc/mdstat  would be worthwhile
--
qui scribit bis legit

Offline BobJF

  • 9
  • +0/-0
Re: Diskusage contrib
« Reply #4 on: March 14, 2021, 10:50:18 AM »
Ah, does look like it's not raid

# cat /proc/mdstat
Personalities :
unused devices: <none>

I'll re-install and see what transpires.

Thanks to all the devs btw
......

Offline TerryF

  • grumpy old man
  • *
  • 1,662
  • +1/-0
Re: Diskusage contrib
« Reply #5 on: March 14, 2021, 11:01:21 AM »
no worries, at my tethers end on this sort of shite :-)  need one of the gurus..must see if I can send some smoke signals..
--
qui scribit bis legit

Offline ReetP

  • *
  • 3,186
  • +5/-0
Re: Diskusage contrib
« Reply #6 on: March 14, 2021, 11:13:53 AM »
no worries, at my tethers end on this sort of shite :-)  need one of the gurus..must see if I can send some smoke signals..

Uh oh. Chris has some work to do... :lol:

Trying to think what it should have created? Did Chris wiki that?
...
1. Read the Manual
2. Read the Wiki
3. Don't ask for support on Unsupported versions of software
4. I have a job, wife, and kids and do this in my spare time. If you want something fixed, please help.

Bugs are easier than you think: http://wiki.contribs.org/Bugzilla_Help

If you love SME and don't want to lose it, join in: http://wiki.contribs.org/Koozali_Foundation

Offline TerryF

  • grumpy old man
  • *
  • 1,662
  • +1/-0
Re: Diskusage contrib
« Reply #7 on: March 14, 2021, 11:29:54 AM »
He had said he was preparing some wiki changes, maybe hanging off until latest changes are done and RC or at least B2...

--
qui scribit bis legit

Offline BobJF

  • 9
  • +0/-0
Re: Diskusage contrib
« Reply #8 on: March 14, 2021, 11:56:19 AM »
I've done a reinstall, deleted all existing partitions using the graphical installer then auto install. The mdstat result is the same as before, no raid present.
Added to bug list
« Last Edit: March 14, 2021, 12:42:19 PM by BobJF »
......

Offline Jean-Philippe Pialasse

  • *
  • 2,043
  • +6/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Diskusage contrib
« Reply #9 on: March 14, 2021, 01:44:39 PM »
have you played with the gui partitionning tool or get straight to install after just setting/ clicking on localization related icons ?

Offline BobJF

  • 9
  • +0/-0
Re: Diskusage contrib
« Reply #10 on: March 14, 2021, 02:12:00 PM »
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.
« Last Edit: March 14, 2021, 02:17:52 PM by BobJF »
......

Offline csn

  • *
  • 11
  • +0/-0
Re: Diskusage contrib
« Reply #11 on: March 14, 2021, 07:10:25 PM »
Hey folks, the RAID wiki has been updated so with three disks you're spot on - it should be RAID 1 + a hot spare.

Using the GUI partitioning tool, even in auto partition, will overwrite our defaults and do a single disk install.

Note that the minimum disk size for a SME10 install is 5GB - if you're using 4GB disks that may be what's causing the 'error checking storage configuration' message.

Can you please share the output of lsblk? Thanks!

Offline BobJF

  • 9
  • +0/-0
Re: Diskusage contrib
« Reply #12 on: March 14, 2021, 08:29:23 PM »
see also Bug 11456

without USB stick

# lsblk -ap
NAME                     MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
/dev/sda                   8:0    0  3.7T  0 disk
├─/dev/sda1                8:1    0    1M  0 part
├─/dev/sda2                8:2    0    1G  0 part /boot
└─/dev/sda3                8:3    0  3.7T  0 part
  ├─/dev/mapper/kss-root 253:0    0   50G  0 lvm  /
  ├─/dev/mapper/kss-swap 253:1    0  7.9G  0 lvm  [SWAP]
  └─/dev/mapper/kss-home 253:2    0 10.9T  0 lvm  /home
/dev/sdb                   8:16   0  3.7T  0 disk
└─/dev/sdb1                8:17   0  3.7T  0 part
  └─/dev/mapper/kss-home 253:2    0 10.9T  0 lvm  /home
/dev/sdc                   8:32   0  3.7T  0 disk
└─/dev/sdc1                8:33   0  3.7T  0 part
  └─/dev/mapper/kss-home 253:2    0 10.9T  0 lvm  /home

# cat /proc/mdstat
Personalities :
unused devices: <none>


With USB Stick

NAME                     MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
/dev/sda                   8:0    0  3.7T  0 disk
├─/dev/sda1                8:1    0    1M  0 part
├─/dev/sda2                8:2    0    1G  0 part /boot
└─/dev/sda3                8:3    0  3.7T  0 part

  ├─/dev/mapper/kss-root 253:0    0   50G  0 lvm  /
  ├─/dev/mapper/kss-swap 253:1    0  7.9G  0 lvm  [SWAP]
  └─/dev/mapper/kss-home 253:2    0 10.9T  0 lvm  /home
/dev/sdb                   8:16   0  3.7T  0 disk
└─/dev/sdb1                8:17   0  3.7T  0 part
  └─/dev/mapper/kss-home 253:2    0 10.9T  0 lvm  /home
/dev/sdc                   8:32   0  3.7T  0 disk
└─/dev/sdc1                8:33   0  3.7T  0 part
  └─/dev/mapper/kss-home 253:2    0 10.9T  0 lvm  /home
/dev/sdd                   8:48   1 28.9G  0 disk
├─/dev/sdd1                8:49   1  1.5G  0 part
└─/dev/sdd2                8:50   1  8.6M  0 part

During the install I waited 10 minutes before going into the GUI partitioning tool.
« Last Edit: March 14, 2021, 09:15:46 PM by BobJF »
......

Offline ReetP

  • *
  • 3,186
  • +5/-0
Re: Diskusage contrib
« Reply #13 on: March 14, 2021, 09:09:48 PM »
It's a pity the 5GB minimum disk size is not mentioned anywhere!

We're trying. But we are few and have little help. We're still at Beta so it isn't perfect yet and needs lots more testing and documenting.

Do please ask for wiki permissions so you can help, and a Rocket.Chat account to talk to us and test this. Every little helps :-)

Quote
see also Bug 11456

https://bugs.contribs.org/show_bug.cgi?id=11456
...
1. Read the Manual
2. Read the Wiki
3. Don't ask for support on Unsupported versions of software
4. I have a job, wife, and kids and do this in my spare time. If you want something fixed, please help.

Bugs are easier than you think: http://wiki.contribs.org/Bugzilla_Help

If you love SME and don't want to lose it, join in: http://wiki.contribs.org/Koozali_Foundation

Offline BobJF

  • 9
  • +0/-0
Re: Diskusage contrib
« Reply #14 on: March 14, 2021, 10:03:49 PM »
We're trying. But we are few and have little help. We're still at Beta so it isn't perfect yet and needs lots more testing and documenting.

quote]


Guys, please don't take the comment as criticism, just, assuming were all getting GB and TB confused, frustration on my part having bought  3 new drives. I do appreciate the efforts you're all putting in. I'll be back tomorrow.
« Last Edit: March 14, 2021, 10:07:09 PM by BobJF »
......

Offline Jean-Philippe Pialasse

  • *
  • 2,043
  • +6/-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.


see
- 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 »

Offline TerryF

  • grumpy old man
  • *
  • 1,662
  • +1/-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.