Array HDD marked as failed and listed as emulated so I rebuilt that HDD on a spare. Now the new disc will not mount and the check file system step results in a very long report that I do not understand.

[EH5]

Hardware:

BIOSTAR Group TP55
American Megatrends Inc., Version 080015
BIOS dated: Mon 14 Dec 2009 12:00:00 AM CST

Intel® Core™ i7 CPU 860 @ 2.80GHz

Memory: 16 GiB SDRAM

Gigabit Dual NIC with Intel 82576 Chip, 1Gb Network Card

StorageTekPro Flashed Dell H310 6Gbps SAS HBA to LSI 9211-8i P20 IT Mode for ZFS FreeNAS unRAID

Cable Matters Internal Mini SAS to SATA Cable 3.3 Feet

600W Thermaltake Smart Series 80 plus power supply

the original "failed" disc was an 8TB WD red

I still have the original disk but have not reinstalled it as an individual drive yet

There are 6 HDDs of various types in the array including this one and the parity disk.

 

Plugins:

Community Applications

Fix Common Problems

Unassigned Devices

Unassigned Devices Plus

Unassigned Devices Preclear

Unraid Connect

 

UNRAID version:  6.12.4 

 

The Story:

I have been working on this project for several months now and have made many mistakes including wrong type of boot drive, USB3 rather than USB2 plug, wrong LAN setup, bad LAN cables, not preclearing drives first (initially), set up shares which could only be accessed one at a time from windows machines, etc.  I thought I had sorted things out and got the system stable when the largest array drive seemed to fail.  It triggered an error message which I can't remember exactly and was no longer mounted.  The drive listed as emulated.  I followed some instructions from the internet for replacing a failed array drive and rebuilt to a new 8TB WD RED PRO drive.  The rebuild seemed to work fine until it completed and the drive was listed as "Unmountable: Unsupported or no file system".  I then did more research and found the links related to file system errors.  Based on what I am reading I should have tried more steps before just rebuilding the drive.  I had precleared the HDD that failed drive before I had started it up.  The results of the file system check are attached along with the system log and the diagnostic zip file.  The file system check is scary long so I decided to stop messing around and post here before doing anything else. 

 

Some other things I did that may be issues include:  I added a new cache drive at the same time I replaced the failed drive (since the case was open anyway).  I didn't think this would affect anything but I don't really know.  The new cache drive has the same "Unmountable: Unsupported or no file system" which is odd.  I also clicked update on the plugins any time a message to do so popped up.  Now I am thinking maybe I should have waited until I had stopped the array before clicking those. 

 

I saw in another post there was a recommendation to reinstall the "failed" HDD and see if it can be mounted independent of the array.  I have the disk available so that is an option.  

 

 

tower-syslog-20231125-2252.zip tower-diagnostics-20231125-1622.zip Disc Check Results.txt

[Squid]

Unlikely that the original drive isn't corrupted, since the parity information is reflecting a corruption on the disk.

 

You really should run memtest for at least a couple of passes to rule out it being the cause.  Any (keeping the original drive untouched) fix the filesystem on the rebuilt drive (remove the -n)

 

[EH5]

I ran memtest over night and was in the fourth pass with no errors this morning.  Ran File System Check Status without the -n and got this result:

 

xfs_repair status:

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... Log inconsistent or not a log (last==0, first!=1) empty log check failed zero_log: cannot find log head/tail (xlog_find_tail=22) ERROR: The log head and/or tail cannot be discovered. Attempt to mount the filesystem to replay the log or use the -L option to destroy the log and attempt a repair.

 

What should I try next?  Re-run the file system check status with a -L?

 

[JorgeB]

1 hour ago, EH5 said:

Re-run the file system check status with a -L?

Yes.

[EH5]

I reran the system check with the -L and I got some folders including lost+found.  There is nothing in the other folder but lost+found has thousands of numbered directories and a few hundred numbered files.  The total used space on the drive listed in the main tab is far less than what it should be.  What can I do next or am I out of luck on my files that were stored on this drive?

 

[JorgeB]

You can try to sort those files and/or restore from a backup if available, a filesystem check can always result in some data loss, depending on how serious the corruption was.

[EH5]

I did the pre clear thing before starting the disk.  Was this just bad luck or should I have done something different when I set my system up?  What can I do to help prevent data loss besides another system to act as a backup?

[JorgeB]

First you should see if the emulated disk is mounting before rebuilding, no point in rebuilding first, do you still have the old disk? It may not be completely dead.

[EH5]

I do have the drive.  how would I try to access the data on that drive?

[JorgeB]

You can use the UD plugin, you will likely need to change the UUID to mount the disk with the array started, but that can be done in UD.