Skip to main content

I just parted...

The recent disk management utility in the Fedora/RHEL installers are a bit challenging.   Since I don't know why things had changed, I won't bother commenting.  But, I don't find them nearly as easy/convenient as before.... Anyhow...

I installed a 500GB SSD in my Intel NUC to build up as a "NAS" host (NFS and iSCSI).  The OS will take around 20GB, then SWAP, /boot.. whatever.  So, I wanted the remainder of the disk to be in it's own VG

[root@rhel7-nas registry]# parted -l | grep Disk
Disk /dev/sda: 480GB
Disk Flags:
Disk /dev/mapper/vg_exports-lv_registry: 21.5GB
Disk Flags:
Disk /dev/mapper/rhel7--nas-home: 1074MB
Disk Flags:
Disk /dev/mapper/rhel7--nas-swap: 8389MB
Disk Flags:
Disk /dev/mapper/rhel7--nas-root: 32.2GB
Disk Flags:
[root@rhel7-nas ~]# parted -s /dev/sda print free
Model: ATA INTEL SSDSC2BP48 (scsi)
Disk /dev/sda: 480GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name                  Flags
        17.4kB  1049kB  1031kB  Free Space
 1      1049kB  211MB   210MB   fat16        EFI System Partition  boot
 2      211MB   735MB   524MB   xfs
 3      735MB   42.4GB  41.7GB                                     lvm
        42.4GB  480GB   438GB   Free Space

[root@rhel7-nas ~]# parted -s /dev/sda mkpart pri ext3 42.4GB 100% set 4 lvm on
[root@rhel7-nas registry]# parted /dev/sda print free
Model: ATA INTEL SSDSC2BP48 (scsi)
Disk /dev/sda: 480GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name                  Flags
        17.4kB  1049kB  1031kB  Free Space
 1      1049kB  211MB   210MB   fat16        EFI System Partition  boot
 2      211MB   735MB   524MB   xfs
 3      735MB   42.4GB  41.7GB                                     lvm
 4      42.4GB  480GB   438GB                pri                   lvm
        480GB   480GB   860kB   Free Space
[root@rhel7-nas ~]# partprobe /dev/sda
[root@rhel7-nas ~]# ls -l /dev/sda*
brw-rw----. 1 root disk 8, 0 Dec 15 18:53 /dev/sda
brw-rw----. 1 root disk 8, 1 Dec 15 18:53 /dev/sda1
brw-rw----. 1 root disk 8, 2 Dec 15 18:53 /dev/sda2
brw-rw----. 1 root disk 8, 3 Dec 15 18:53 /dev/sda3
brw-rw----. 1 root disk 8, 4 Dec 15 18:53 /dev/sda4
[root@rhel7-nas ~]# pvcreate /dev/sda4
  Physical volume "/dev/sda4" successfully created
[root@rhel7-nas ~]# vgcreate vg_exports /dev/sda4
  Volume group "vg_exports" successfully created


Comments

Popular posts from this blog

RHN Satellite Server (spacewalk) repomd.xml not found

"repomd.xml not found" If you add a channel, or if your RHN cache gets corrupted, and one of your guests complains that it cannot find repomd.xml for jb-ews-2-x86_64-server-5-rpm (for example) - you need to rebuild your repodata cache. Normally this is an automated job - which is exemplified by the fact that you have obviously built out your entire Satellite environment and never had to do any of the steps you are about to do. So - some prep work: Open 3 terminals to your Satellite Server and run: # Term 1 cd /var/cache/rhn watch "ls -l | wc -l" # Term 2 pwd cd /var/log/rhn tail -f rhn_taskomatic_daemon.log # Term 3 satellite-sync --channel=jb-ews-2-x86_64-server-5-rpm Once the satellite-sync has completed, you >should< see the count increment by one.  If you are unlucky (like me) you will not. You then need to login to the Satellite WebUI as the satellite admin user. Click on the Admin tab (at the top) Task Schedules (on the left) fin

Install RHEL 7 on old HP DL380 g5

Someone at work had been running RHEL on an HP DL380 G5 and blew it up.  After several attempts at doing an installation that made me conclude the hardware was actually bad... I kept digging for the answer. Attempt install and Anaconda could not find any disks - try a Drivers Disk (dd.img) both cciss and hpsa.   -- once we did that, when the system would reboot it would say it could not find a disk. hmmm. Boot from your installation media and interrupt the startup at grub. Add hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1 to the line starting with linuxefi press CTRL-X to boot. Once the system restarts after the install, you need to once again interrupt the startup and add the line from above. After the system starts, edit /etc/default/grub and add those 2 parameters to the end of the line starting with GRUB_CMDLINE_LINUX (which likely has quiet at the end of the line currently). then run # cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.orig # grub2-mkconfig -o /boot/grub2

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un