Power Outages are fun! Are they not?!

[juhendri]

All 10 non-default shares went missing after a power outage.

All dockers went missing as well.

It is like I never installed anything at all

I only had nextcloud with the default db engine on this server in dockers.

No fancy anything. This had ALL of our family pictures and important Documents that we scan to file.

 

Any help would be greatly appreciated.

Diagnostics attached.

hendricd-diagnostics-20210702-1212.zip

[JorgeB]

Fix filesystem on disk1:

 

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

 

Run it without -n or nothing will be done, if it asks for it use -L.

[JorgeB]

Just noticed that you have a parity check scheduled to run daily, we usually recommend doing it once a month.

[juhendri]

2 hours ago, JorgeB said:

Just noticed that you have a parity check scheduled to run daily, we usually recommend doing it once a month.

I didn't have that turned on until after the power outage. I thought maybe a parity check may help, but that failed.

[juhendri]

I am trying something else. On my other unraid server I have some disks that give me trouble from time to time due to the way they are connected. To fix this I just do the steps below.

Take array offline.

unassign troubled disk.

Put array back online then back offline.

re -assign troubled disk.

put array back online.

Start "Parity-Sync/Data-Rebuild.

 

 

[juhendri]

3 hours ago, JorgeB said:

Fix filesystem on disk1:

 

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

 

Run it without -n or nothing will be done, if it asks for it use -L.

I am sorry, but that didn't work.

[itimpi]

1 hour ago, juhendri said:

I am sorry, but that didn't work.

More detail in how it did not work might allow us to give help such as what was reported when you tried the suggested action.

[trurl]

1 hour ago, juhendri said:

thought maybe a parity check may help

No reason it should.

 

1 hour ago, juhendri said:

I just do the steps below

That is basically the method of rebuilding a disk to itself as documented here:

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

That won't fix corrupt filesystem.

 

1 hour ago, juhendri said:

I am sorry, but that didn't work.

You should do it again, capture the output and post it. Just saying it didn't work doesn't tell us anything.

[juhendri]

26 minutes ago, itimpi said:

More detail in how it did not work might allow us to give help such as what was reported when you tried the suggested action.

Both shares and dockers are still missing

 

[juhendri]

26 minutes ago, trurl said:

No reason it should.

 

That is basically the method of rebuilding a disk to itself as documented here:

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

That won't fix corrupt filesystem.

 

You should do it again, capture the output and post it. Just saying it didn't work doesn't tell us anything.

I will post the outcome of the capture after it is done with a parity rebuild.

 

Edited July 2, 2021 by juhendri

[trurl]

Jun 28 06:31:46 HENDRICD emhttpd: shcmd (232): /sbin/wipefs -a /dev/md1
Jun 28 06:31:46 HENDRICD root: /dev/md1: 4 bytes were erased at offset 0x00000000 (xfs): 58 46 53 42
Jun 28 06:31:46 HENDRICD emhttpd: shcmd (233): mkfs.xfs -m crc=1,finobt=1 -f /dev/md1

Looks like you formatted disk1. Parity rebuild will not get that data back and neither will repairing the filesystem.

[juhendri]

3 minutes ago, trurl said:

Jun 28 06:31:46 HENDRICD emhttpd: shcmd (232): /sbin/wipefs -a /dev/md1
Jun 28 06:31:46 HENDRICD root: /dev/md1: 4 bytes were erased at offset 0x00000000 (xfs): 58 46 53 42
Jun 28 06:31:46 HENDRICD emhttpd: shcmd (233): mkfs.xfs -m crc=1,finobt=1 -f /dev/md1

Looks like you formatted disk1

Would that be the parity drive?

[trurl]

No that would be disk1, which probably contained all that data you say you are missing, since that is the disk that would be chosen first by default when writing data. Parity is disk0 if you want to give it a number. Parity has no data and no format.

 

Do you have backups?

[juhendri]

1 minute ago, trurl said:

No that would be disk1, which probably contained all that data you say you are missing, since that is the disk that would be chosen first by default when writing data. Parity is disk0 if you want to give it a number. Parity has no data.

 

Do you have backups?

I have 2 parity drives and 3 data drives. No I do not have any back ups.

 

[trurl]

Parity is not a substitute for backups. Plenty of much more common ways to lose data besides a failed disk, including user error.

[juhendri]

26 minutes ago, trurl said:

Parity is not a substitute for backups. Plenty of much more common ways to lose data besides a failed disk, including user error.

Why would it tell me I need to format a disk after a power outage?

What could have I done other than what my server wanted me to do?

 

[trurl]

1 hour ago, juhendri said:

Why would it tell me I need to format a disk after a power outage?

What could have I done other than what my server wanted me to do?

It would have allowed you to format any unmountable disk assigned to a data slot, but it would have made you check a box confirming that you really intended to do that and warned you not to format the disk if it had data on it.

 

When a disk filesystem gets corrupted, it can't be mounted. An unmountable disk that should contain data needs to be repaired as suggested earlier.

 

Format means "write an empty filesystem to this disk". That is what it has always meant in every operating system you have ever used.

 

Unraid parity is realtime. All write operations in the parity array update parity at the same time. Since format is a write operation, after formatting a disk in the parity array, parity agrees the disk contains an empty filesystem. The only thing that can result from rebuilding at that point is an empty filesystem.

 

Here is the beginning of the documentation that discusses the problem you had:

 

https://wiki.unraid.net/Manual/Storage_Management#Drive_shows_as_unmountable

 

Really the best thing you could have done is asked for help before doing anything at all, since what you did was all wrong.