Continuation from Home Linux File Server
Challenges 9: Reinstall Core Operating system, configure it up, and mount and use /md.
The scenario is simple: We didn’t mirror our boot partition, so now we have to reinstall the operating system and make sure we can preserve everything we need to keep business consistency.
Continuation from Home Linux File Server
Challenges 6, 7, and 8: Break the RAID, again, Verify that we can still create/make files, and Rebuild the RAID with the Spare.
This is the crux of all of this. We need to be able to know that when a physical drive/volume fails that iSCSI won’t drop anything, that the RAID5 will still operate seamlessly in degraded mode, and that we can have the spare from our “Previously RMA’d drive” scenario take the place of the dead drive.
Continuation from Home Linux File Server
Challenge 4 and 5: Setup and configure iSCSI Target and Mount the LUN from a separate computer
I’m going to be using a guide here: [Set up an iSCSI Target and Initiator]
In my previous post I listed 10 steps to acquiring what I needed to do to feel comfortable in making a Linux File Server. This is Challenge 2 and 3 of 10: Breaking the Raid, and Add the Spare and Rebuild.
Yays! Fun stuff in route!
Part of my 2018 goals is to be able to have a universally-accessible resource where I can be able to store all the data that I need to, and more, without worry of fault or loss. One of the ways to approach this is to create a File Server that I can mount from a majority of operating systems and be able to store anywhere in the world. So, I’ve come to the conclusion to build a Linux File Server, complete with a Software RAID5 (as opposed to a hardware RAID5), and make it so that we can use iSCSI to mount the LUNs.
We need to do this on a budget, too.