Bsrgvty

Who originated the dangerous avocado-pitting technique?

What are those two silvery objects resting on Ben Kenobi's table when R2-D2 plays Princess Leia's message?

How offensive is Fachidiot?

Can Parliament be compelled to let the UK leave the EU on October 31st?

Why are VW tail light bulbs listed as 12W / 5W?

What are the applications of the Mean Value Theorem?

Australian visas - any difference between tourist and business?

ASCII Expansion

Does the difficulty for the Google dinosaur game infinitely increase or stops at a certain point?

Why are Poisson regression coefficients biased?

Why do some PCBs have the courtyard in the silkscreen layer?

Why do textbooks and other sources pretend special katakana don't exist?

Trading stock more quickly vs. holding it

Simple n-body class in C++

Calculate the internal angles of a regular polygon with N sides

How did CGP Grey get his hands on old New York Times papers?

How can I manage my team to maintain a reasonable productivity when my employer doesn't treat employees well?

Is it okay to have an email address called "SS"?

How do I handle a paladin who falls, but wants to choose a different class instead of taking the Oathbreaker subclass?

I can be found near gentle green hills and stony mountains

Why combine commands on a single line in a Bash script?

Locating "Bankhead of ..." in parish of Forfar

Best way to get my money back from a friend having family problems

What are the practical differences between the exposure settings my camera picked for me in auto mode and my own choices?

Invalid bitmap file for superblock: bad magic. How to reassemble RAID array?

MDADM Raid 0 won't mount: one drive has bad superblockmdadm warning (system unbootable) from update-initramfs, mkconf's suggested fix seems inconsistent with mdadm's description of problemmdadm - Obsolete Array and current Array have same UUID. Current array won't assemble on bootRecovering a healthy RAID disk from an Ubuntu server: mdadm no recogniseable superblockDifficulty removing an un-needed arrayRAID array doesn't reassemble after rebootHow to resize a mdadm RAID array

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;

0

I recently set up Ubuntu 18.04.2 Server installed onto a RAID1 array, and all seemed well until I had a system lockup after which it seems that the superblock of my RAID1 array became corrupted. I'm pretty sure this is not an issue with my drives themselves, because I had the same problem under similar circumstances (prior to crash I was using KVM on Ubuntu Server 18.04.2 installed on RAID1) with a different pair of drives.

What can I try to fix my superblocks and repair my installation? There is no critical data there, but I'd rather not have to reinstall and reconfigure my entire system again.

Edit: If I boot in Gparted, I am able to get a "MBR magic", but that confuses me because I had set up these disks for UEFI boot (EFI partition is on a separate USB by the way)

.

boot mount raid mdadm initramfs

share|improve this question

edited Jun 14 at 17:52

Stonecraft

asked Jun 14 at 8:22

StonecraftStonecraft

13277 bronze badges

add a comment
 | 

0

I recently set up Ubuntu 18.04.2 Server installed onto a RAID1 array, and all seemed well until I had a system lockup after which it seems that the superblock of my RAID1 array became corrupted. I'm pretty sure this is not an issue with my drives themselves, because I had the same problem under similar circumstances (prior to crash I was using KVM on Ubuntu Server 18.04.2 installed on RAID1) with a different pair of drives.

What can I try to fix my superblocks and repair my installation? There is no critical data there, but I'd rather not have to reinstall and reconfigure my entire system again.

Edit: If I boot in Gparted, I am able to get a "MBR magic", but that confuses me because I had set up these disks for UEFI boot (EFI partition is on a separate USB by the way)

.

boot mount raid mdadm initramfs

share|improve this question

edited Jun 14 at 17:52

Stonecraft

asked Jun 14 at 8:22

StonecraftStonecraft

13277 bronze badges

add a comment
 | 

I recently set up Ubuntu 18.04.2 Server installed onto a RAID1 array, and all seemed well until I had a system lockup after which it seems that the superblock of my RAID1 array became corrupted. I'm pretty sure this is not an issue with my drives themselves, because I had the same problem under similar circumstances (prior to crash I was using KVM on Ubuntu Server 18.04.2 installed on RAID1) with a different pair of drives.

What can I try to fix my superblocks and repair my installation? There is no critical data there, but I'd rather not have to reinstall and reconfigure my entire system again.

Edit: If I boot in Gparted, I am able to get a "MBR magic", but that confuses me because I had set up these disks for UEFI boot (EFI partition is on a separate USB by the way)

.

boot mount raid mdadm initramfs

share|improve this question

edited Jun 14 at 17:52

Stonecraft

asked Jun 14 at 8:22

StonecraftStonecraft

13277 bronze badges

share|improve this question

edited Jun 14 at 17:52

Stonecraft

asked Jun 14 at 8:22

StonecraftStonecraft

13277 bronze badges

share|improve this question

edited Jun 14 at 17:52

Stonecraft

asked Jun 14 at 8:22

StonecraftStonecraft

13277 bronze badges

asked Jun 14 at 8:22

StonecraftStonecraft

13277 bronze badges

asked Jun 14 at 8:22

StonecraftStonecraft

13277 bronze badges