At home I run a server with Nextcloud for keeping my family pictures, movies, documents and important stuff. Not only it serves as private storage, but also it’s important to me that I don’t loose the gathered over time memories. The whole server was running already on RAID-1 mirrored disks, but some time ago, one of them failed - and I needed a replacement.
So I bought a new non-SSD drive, with 5400rpm, fully enough for my needs: storage access, and the price.I got this 500GB drive for ~40$.
The server configuration before the disk failure, was rather easy. Two disks, one old 650GB WD connected externally to USB and a 750GB Seagate connected to SATA. There was a Linux setup RAID-1 on all 3 partitions: OS, swap, data. My oh my, nothing fancy, but gets the job done. Unfortunately, the SATA drive was the one to die :(, so I was left with a USB drive only. The changes I needed to do to keep the system running after the failure was to make sure that the server boots from USB drive. Fair enough.
So I bought a new drive. My WD holded something around 200GB of data, since last 6 years. Quick calculation and I got stingy buying a 500GB drive as replacement. I salvaged also a 160GB drive from some laptop I don’t use anymore. The reason for that was, that I wanted to get rid of mirroring the system, swap space and GRUB. I remember that maintaining that configuration and remembering that with every bootloader update, both disks need MBR changes was something I wanted to get rid of.
And this is how I ended up installing newest Ubuntu on to the 160GB drive. Moved all of my settings from the old drive and started to feel happy about the end of crisis. Needed to install and configure Docker Swarm cluster again, but since all of my deployed apps (Nexcloud included) are dockerized and idempotent (infrastructure as code) I got everything running smooothly in (managable) notime. So what I got was 3 disks:
What’s next? Looks like just recovering RAID with
And here it comes. New operating system means, there’s no RAID-1 configured. Oh ho, ok, I need to create RAID-1 again. Thought quickly and said that’s fine. Let’s do it. Unfortunately, it wouldn’t make sense to create RAID-1 from the existing disk, since the
/dev/sdb5 partition (the one with the data to be mirrored) was already bigger than the full size of the new disk. Damn - spend the 10$ more next time. I already saw the ~200GB of data I’d need to copy during new RAID setup. Damn it.
So first of all, create a new partition on the new disk with fdisk:
Now, since the partition is created the hard work starts and that’s just because I made a simple mistake. I started copying the files to this drive instead of just creating RAID-1 on top of it. It was the most stupid and not obvious mistake I could do. I mounted the new partition, and copied all of the 200GB data onto it. Than with fdisk I created partition on WD drive matching the new one with:
I think this was the time I realized I’ve made my work doubled. And there was nothing left for me to do, but just to create the RAID volume/device and copy the data once again onto the new partition on old drive, since that was the one right now without the data, so I could create RAID on top of it and choose the filesystem type.
Now… mounting and copying the ~200GB back, but this time onto (not yet fully setup) RAID. This was the time I was a little bit sad, that my drives aren’t SSD :D. After the data was copied, adding the partition to RAID device was easy as:
In order to check the RAID status in Ubuntu, just invoke:
Probably I should have executed the steps with more thinking attached to it :). If I’d remember that RAID recreation without data loss requires manual data copying, I’d just buy and 1TB drive (~50$) and leave the system and swap partitions untouched. Not really sure of that, but I’d think twice, because my private time is limited. The second, and huge mistake was actually copying the data without creating the RAID in the first place. Not really sure what I was thinking. Just forgot about that, I think I was stuck with the thinking that I need to use the “old drive” as the RAID basis, because it was in RAID in the old configuration. Echhh…