Gee, thanks, whippersnapper! What does that make me, then? 
Get off my lawn! 
On account of the partitioning thing, if you already have a spare partition that you can use for /home, then you can read through this guide with regard to moving the contents of your current /home to the new partition. 
If you do not have a spare partition available right now, then I’m afraid you’re going to have to make room for one, even if it means reinstalling.
Another alternative to having a separate partition for /home is to use btrfs as the filesystem, with two subvolumes ─ @ and @home. The installer can set that up for you ─ you do of course still need separate partitions for the EFI system partition and the swap partition.
The advantage of btrfs is that subvolumes behave as if they are separate partitions, but at the same time, the free space is shared among all the available subvolumes. So you don’t have to worry about partition sizes when creating a separate / and /home, because technically they are on the same partition, but they are still separate namespaces in how the system sees and treats them.
As for the error you had on your /home partition during the first install, that could be caused by anything, ranging from disk failure over having chosen incorrect partition boundaries ─ which shouldn’t happen, because the partitioning tool is supposed to correctly align the partitions.
Lastly, even if you decide not to go with btrfs, the filesystem type used for both / and /home must be a Linux-native filesystem such as ext4, XFS, btrfs, JFS, reiserfs et al. You cannot use a Microsoft- or Apple-native filesystem for that, because the Apple-native filesystems are only poorly supported, and the Microsoft-native filesystems do not support POSIX file ownership and permissions.