Fails to create ext4 partition

ricklinux · July 20, 2020, 1:02am

Try clicking on /dev/md126 and delete.

killbotvii · July 20, 2020, 1:03am

I did so and deleted it, but I still don’t seem to be able to alter the child drives. The lock is still there.

ricklinux · July 20, 2020, 1:04am

Do you have all unallocated space then? create GPT if it will work.

FLVAL · July 20, 2020, 1:04am

Just delete all the space to get one unallocated space then GTP a clean table then show us the list of all disks you have in GParted after it

killbotvii · July 20, 2020, 1:07am

I’ve done so, but there’s no changes for the child drives.

I’m not sure I understand. I went ahead and tried running the same command on the child drives though and it didn’t seem to work.

[liveuser@eos-2020.07.15 ~]$ sudo mdadm --remove /dev/sda
mdadm: /dev/sda does not appear to be an md device
[liveuser@eos-2020.07.15 ~]$ sudo mdadm --remove /dev/sdb
mdadm: /dev/sdb does not appear to be an md device

FLVAL · July 20, 2020, 1:10am

could you show us the list of all disks now that you GPT a new table ?

ricklinux · July 20, 2020, 1:11am

Maybe now in gparted you can delete each disc? /dev/sda and /dev/sdb

killbotvii · July 20, 2020, 1:12am

Seems to be the same as before.

Sadly no, the drives are still locked.

FLVAL · July 20, 2020, 1:15am

When you click btn right on the this sda do you have unmount accessible or everything is not available ?

ricklinux · July 20, 2020, 1:15am

Okay i have an idea.

mdadm --stop /dev/md126

mdadm --stop /dev/sda

mdadm --stop /dev/sdb

mdadm --remove /dev/sda

mdadm --remove /dev/sdb

killbotvii · July 20, 2020, 1:17am

Seems like only the first part worked.

[liveuser@eos-2020.07.15 ~]$ sudo mdadm --stop /dev/md126
mdadm: stopped /dev/md126
[liveuser@eos-2020.07.15 ~]$ sudo mdadm --stop /dev/sda
mdadm: /dev/sda does not appear to be an md device
[liveuser@eos-2020.07.15 ~]$ sudo mdadm --stop /dev/sdb
mdadm: /dev/sdb does not appear to be an md device
[liveuser@eos-2020.07.15 ~]$ mdadm --remove /dev/sda
mdadm: error opening /dev/sda: Permission denied
[liveuser@eos-2020.07.15 ~]$ sudo mdadm --remove /dev/sda
mdadm: /dev/sda does not appear to be an md device
[liveuser@eos-2020.07.15 ~]$ sudo mdadm --remove /dev/sdb
mdadm: /dev/sdb does not appear to be an md device

All greyed out still.

ricklinux · July 20, 2020, 1:18am

Okay try remove on the md126

sudo mdadm --remove /dev/md126

FLVAL · July 20, 2020, 1:18am

mdadm could only act on md drive maybe

killbotvii · July 20, 2020, 1:19am

[liveuser@eos-2020.07.15 ~]$ sudo mdadm --remove /dev/md126
mdadm: error opening /dev/md126: No such file or directory

I think this is happening because we already stopped it, right?

EDIT: ONE SEC GOT SOMETHING NEW

FLVAL · July 20, 2020, 1:20am

Yep stop it then remove it.
Close GParted and reopen it

ricklinux · July 20, 2020, 1:20am

I’m not entirely sure. What happens if you restart and then go back into gparted on the live ISO.

killbotvii · July 20, 2020, 1:22am

I closed and reopened gparted and got this

I clicked ignore

I hit okay, and now I can make changes!

ricklinux · July 20, 2020, 1:23am

Is this just on the one drive or both?

killbotvii · July 20, 2020, 1:24am

Interestingly, here’s how the second drive looks:

ricklinux · July 20, 2020, 1:26am

I think you have to try to remove it.

sudo mdadm --remove /dev/sdb