trurl

Did you shutdown or try to fix it "hot"? Shutown, unplug DAS from PC and unplug both from power before trying again.

Parity rebuilt to new parity disk. Did you preclear the new data disk? Or did you let Unraid clear the new data disk? Or did you New Config and rebuild parity again?

DId you always have a disk2 when you set this up? Or was it added later?

I would expect it to be less safe, except for the fact that nothing is working anyway. And whether you shutdown or not, I wouldn't be surprised if it was back to this

Might as well stop the rebuild. Maybe try reseating all drives, checking all connections. You will have to start the rebuild over. Did you every successfully build parity with this hardware? Even though disk2 is empty, all sectors of disk2 (and all sectors of parity) must be reliably read to reliably rebuild disk1.

The real solution to your problems is a build with individual SAS/SATA connections for each assigned disk.

You can't rebuild disk1 unless ALL other array disks are working well. Post new diagnostics.

Any time you are unsure what to do, you should ask on the forum and post your diagnostics. Since you are using USB, I wouldn't be surprised if this doesn't happen any time you need to replace a disk. Actually getting Unraid to rebuild a disk after New Config requires several steps that have to be followed exactly, with some checks along the way to decide what needs to be done next. I've never needed to use UFS Explorer. But it isn't going to be like rebuilding a disk. It is going to scan the disk and try to find files that it can recover individually. The trial edition will let you see what files it can recover but you will have to pay to actually recover anything. Standard edition will be fine for recovering an Unraid array disk since it is just a single Linux filesystem.

Do you know how to fix those? Seems kind of strange to actually have user shares named mnt and etc. What are those for?

Reassign disk1, start the array to begin rebuilding disk1. The result will still be an empty disk, but it will be as if you accidentally formatted the disk after you rebuilt it with its data. Then you can try something to help recover deleted data from a disk, such as UFS Explorer. Do you have backups? You must always have another copy of anything important and irreplaceable. Parity is not a substitute for backup, whether Unraid or any other system. Plenty of more common ways to lose data besides a failed disk, including user error.

Those show disk1 empty as expected,. But disk2 also appears empty. Is that expected also?

In normal (not maintenance) mode

Unassign the formatted disk. Start the array without it. Post diagnostics.

Have you used the array at all since you formatted?

Attach Diagnostics ZIP to your NEXT post in this thread

Parity doesn't contain any of your data of course. It just allows the data from a missing disk to be calculated from all the other disks. And format doesn't completely wipe out every trace of the original disks data from the array. It just writes an empty filesystem to the disk, and parity agrees the disk has an empty filesystem after that. But maybe if we make it emulated and rebuild it from parity, even though the result would be an empty filesystem, all the rest of the bits from the original data would still be there and UFS Explorer might be able to recover some of it.

There is a way you could have made the new disk emulated, and we could have told you how if you had asked before doing anything. But now parity agrees it has been formatted Are you sure the original disk is unreadable?

Looks like you probably have other shares like that, because the config/shares folder on flash has some .cfg files that are for user shares with a different upper/lower case. Linux is case-sensitive, so Media is different than media. But the flash drive is not case-sensitive, so it can't work with a .cfg file for Media and also a .cfg file for media. It looks like most of these "wrong-case" .cfg files don't really have corresponding user shares with actual contents. Go to the User Shares page and click the CLEAN UP button at the bottom, then post new diagnostics.

Attach Diagnostics ZIP to your NEXT post in this thread.

Can you get Diagnostics from command line?

The "zero" timestamp for DOS (FAT) is 00:00:00 1980-01-01, so it probably just doesn't timestamp those FSCK files

The date of those FSCK files are meaningless. And deleting them won't help anything but they can be deleted since they are taking up space. Unraid stores the array started/stopped status on the flash drive. If the array is started, that status is stored on flash. Then, when the array is stopped, unless it can write that stopped status to the flash drive, next time it boots it will see that array status as still started (not stopped) and so it is an unclean shutdown. Reading that status is literally how it decides if there was an unclean shutdown.

If your flash drive couldn't be written while stopping the array, such as might happen if it dropped offline or was made read-only due to corruption, then it will look like an unclean shutdown since the flash drive is where stopped/started is saved. There are a couple of FSCK files on flash which would be due to "fixing" corruption.

Your questions touch on several different settings you need to be aware of and understand. We could probably give more detailed and specific advice if you Attach Diagnostics ZIP to your NEXT post in this thread.

HDDs in array, with one as parity. Data disks formatted XFS SSDs mirrored pool, ZFS or btrfs, might as well name the pool 'cache' but will be used for Docker/VM related shares also.