Question

0

GPT talbe corrupt after RAID1 setup

rated 0 times [ 0] [ 0] / answers: 1 / hits: 3919 / 2 Years ago, sat, january 29, 2022, 4:25:14

So I'm completely new to Ubuntu and am trying to set up a backup/media server at home. I saw the guide on Lifehacker and figured I'd give it a try.

My system is an i3 3225 on an Intel DH77DF mobo with 8GB of ram. There's a 64GB mSATA SSD as the boot drive and two 4TB WD Red drives for the RAID1 configuration.

I installed Ubuntu 14.04 LTS in UEFI mode on the SSD without issues but as soon as I create the software RAID1 (and it finishes syncing after 9 hours), gparted gives me the following errors:

Libparted Bug Found!

End of file while reading Invalid argument

The primary GPT table is corrupt, but the backup appears OK, so that will be used.

These appear twice as almost for each 4TB drive.

Am I doing something wrong when creating the RAID? The RAID also appears as md127 if that helps.

Thanks,
Mark

PS - This RAID setup has been a huge pain so far and I could write a good rant but I'll refrain for now. For example, mdadm wasn't initially installed so I had to figure that out. This was also after the fact I found out BIOS RAID is really FakeRAID.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

fittecanap

Add To Favorites

Follow

Total Points: 322

Total Questions: 100

Total Answers: 105

Location: Israel

Member since Tue, Nov 17, 2020

4 Years ago

fittecanap questions

1 Hibernate entry in the menu on 22.04

Tue, Nov 23, 21, 22:02, 3 Years ago

1 How do I upgrade from 20.04 to 22.04 now? Are most guides simply wrong?

Wed, Feb 1, 23, 18:08, 1 Year ago

1 I am having this issue while running 'sudo apt-get update', "Problem with MergeList" or "status file could not be parsed or opened."

Fri, May 12, 23, 17:09, 1 Year ago

1 Foreground task scheduling in Linux similar to Windows's Task Scheduler

Wed, May 10, 23, 02:52, 1 Year ago

1 Updates Warning

Tue, Aug 9, 22, 17:36, 2 Years ago

View All

answered 2 Years ago whipstder · Accepted Answer

With the help of a friend I figured it out!!

After doing more research because I wasn't entirely satisfied with having to create two raids on one set of drives (no offence), I managed to set it up how I want it. Moving over to the terminal rather than the GUI helped a lot and the big issue was left over GPT table data from my previous raid attempts. Once I figured out how to clear that data and create the raid from scratch, I had no other issues.

To check for left over data:

sudo mdadm -D /dev/sda

retuns "..does not appear to be an md device."
(same for /sdb)

But when I go to create the raid:

sudo mdadm –create /dev/md1 –level=1 –raid-devices=2 /dev/sda /dev/sdb

returns "../Dev/sda appears to be part of a raid array..."

So to clear the old GPT data I had to go to each drive and:

sudo gdisk /dev/sda 2 (for GPT) x (for expert commands) z (wipe the gpt data) Yes Yes

(credit goes to @Steve HHH for his answer here)

From there I created the raid1 in the terminal rather than the GUI using the same code above:

sudo mdadm –create /dev/md1 –level=1 –raid-devices=2 /dev/sda /dev/sdb

After that finished syncing I used the GUI based GParted to create the separate partitions and no more errors are appearing. I can finally move forward with this media server!